Interesting article, I don't think I have a use for them though.
You’re absolutely right.
Oh great point. I’d add skiing to that category.
Awesome! I will try it out. Thanks!
As long as it’s not automated and spammy, i’m game.
Cast iron? Yes. Stainless steel? Yes, but check temp. Nonstick? Better not
I’ll have to give it a try
That's an interesting point about depending too heavily on a debugger. I haven't run into anyone too dependent on it, but I could see that happening.
To me, debuggers offer a tighter dev loop when there's something you're stuck on. They also let you 'grok' a call stack in an unfamiliar codebase. "Did this function get called?" "What's in this variable?" etc.
How do people do stuff without debuggers? :D
Another way to develop would be through iterating within a Unit Test that you don't plan to keep around.
Uh, I set a breakpoint and run the app?
To add a bit more context, it's more difficult to configure a debugger when the application is running within something like Docker. How difficult? That depends on the language and tools you're using.
I'm a heavy intellij user, but the git log UI always confuses me. When I open 'git log' via the action menu IntelliJ doesn't focus my current branch. I am not sure if there's some other menu I'm supposed to use to achieve that.
I do use the commit local changes, pull changes, merge branches functionality a good bit. My only feedback there is that I haven't found a way to quickly commit changes without running git hooks. Each time it requires me to open up the gear icon and deselect 'git hooks'. This is slower than using the command line where I can write git commit --no-verify and repeat the same command again and again. I know it's a niche need, but it's necessary for testing a rather archaic system we maintain.
view more: next ›
That’s super helpful, thank you!