gildings in this subreddit have paid for 24.41 years of server time

How to bully machine learning training by WGC_WinGiveawayClub in ProgrammerHumor

[–]BothInteraction 22 points23 points  (0 children)

Shutting down thread exiting with uncaught exception (group=0x41a8ed40)
Process: programmerhumor.comments.nmxvb8, PID: 4627

Context: A guy saying it's never too late to start coding by UnluckyTest3 in ProgrammerHumor

[–]ReveredOxygen 2 points3 points  (0 children)

Show me one language where this is valid. I'm most interested in the unquoted string

console.log("I'm here 1") by 1ByteIdiot in ProgrammerHumor

[–]taronic 24 points25 points  (0 children)

Honestly I think it's that a lot of senior devs just start taking shortcuts, because it's kind of the natural path. Stepping through with a debugger is fucking time consuming. Devs just want to get their shit done, and usually a print statement is enough.

Thing is, it works 80% of the time maybe, so you learn to just try it first and fix a bug in 5 minutes. But then devs stick with it, and keep adding prints, when they really should just delete them and set a breakpoint. I've seen it doing pair programming, with a senior dev sitting there adding another print and being confused, and then printing the value of some variable, and when you're at that point it's obvious to step through. I told them to, they did, and it was obvious what the bug was. Saved time by doing something you usually don't do to save time. There's a balance, and a debugger is invaluable when you really need it.

But senior devs are also usually sometimes writing unit tests and maybe checking the coverage and ensuring that they keep passing. That's just a tool that prevents having to debug in the first place. And there's linting, and in a dynamically typed language like python, even type checking with mypy. There's a lot of tools that are used to catch tons of bugs before you even need to debug. And then there's integration tests. That's where I think the difference is, senior devs figure out their bugs earlier because of comprehensive tooling that goes beyond a debugger. A debugger should really be a last resort in a lot of ways when it comes to tools to keep code clean and bug free, so I don't think you see it as much. Plus, senior developers aren't usually writing scripts - they might have concurrent tasks, workers running in different processes, some heavy framework, and a debug log message is a bit easier than trying to figure out which process to attach to, depending.

So maybe no one uses your tool yet but it doesn't mean new tools don't help. In a lot of ways, we're using debuggers less because of new tools that catch shit before you even think to open a debugger. I think the key difference I've seen between juniors and seniors, is that juniors now and then push code that has issues a linter would pick up, like an unused or misspelled variable. Also huge functions with 50 lines, way too many layers of scope indentation, etc.

Trying to learn C by Vercidium in ProgrammerHumor

[–]cemanresu 437 points438 points  (0 children)

Real men press up on the command line until they find the last time they used the five line long compilation command

*visible frustration* by rand0mguy10 in ProgrammerHumor

[–]Dougleycat flair.txt | sudo sh[M] [score hidden] stickied commentlocked comment (0 children)

Hi there! Unfortunately, your submission has been removed.

Your submission would be better suited for another subreddit.

If you feel that it has been removed in error, please message us so that we may review it.

Our GitHub bot just got a job offer by sublimefunk in ProgrammerHumor

[–]Asiansensationz 133 points134 points  (0 children)

Quite generous to imply that recruiters are sentient beings.

Everything.exe - application not responding by Superwibr in ProgrammerHumor

[–]a_scerba 0 points1 point 24292422 (0 children)

2015 ThinkPad ... shitty ... /r/thinkpad would like to have a word with you