You get healthcare, always. Not just when you have a job. You get security around your job, so your employer can’t just go “lol, you’re fired, stfu”. You get “theoretically” enough money to live when you do get fired.

And you get that, regardless of your employment status. Everybody, from students, to fast food workers, to the nice rich software developers. Sure, you NEED it less if you’re a software developer, I almost certainly pay more in taxes than I get in tax-related value. But it also means that if my arms fall off one day, I’ll still be living in a country that will ensure I’m relatively healthy, homed, and fed.

Co-operation is why humans are so successful. If everybody was only ever out for themselves, we’d still all be scrabbling around in caves looking for food. Helping 100 people get educated so 50 of them can be useful members of society is still better than having 10 of them get supported through their parents, and letting the other 90 fail.

Ah, I see. I didn’t see the bit about it being a breakpoint (detour point?). That’s what I get for skim reading rather than comprehending it. Visual studio will let you do this, but it’s a manual step, by combining a normal breakpoint and an execute next statement, and you’d have to do this each time you hit the breakpoint.

Having it happen automatically? A fairly niche feature, but I can see a few uses for it. The component features are already there, so I don’t think it would be difficult to implement in a debugger that already supported execute next statement.

Yes, visual studio lets you do this. You can drag the marker on the line of code that it’s paused at, and move it around. There’s probably restrictions, however it works in most simple cases.

A link here indicates that it’s also possible in VS Code, however it may be C#/C++ only.