This is why you have style guides, policies and safeguards, with others checking PRs as they go through to catch this sort of stuff.
Plus I'm not saying everything should be commented. By default things should be explainable through the code and making sure variable and method names are descriptive, along with strong typing if your language has it.
Comments are there for when the code itself is not enough. But you're right shit always creeps in eventually regardless of the best intentions. Which is why teams need tech debt breaks where no new features are added and they go through the code fixing the niggly things that haven't been worth fixing whilst doing other features, and ensuring critical sections (the kind that usually have comments on them) are still working as intended and described accurately.
Nah, I used QWERTY till I was like 28 then learned Colemak-dh on an ergo split keyboard, only took a month to get to normal and now I can type with both. It's like becoming multilingual but WAAAAAAY easier.
Not the same guy but even where i love it's 18 but even I couldn't think about dating someone below 21 they're practically like kids still to me and I'm only 30, still don't think I would go as low as 21 myself though that still seems too young for me haha.
That's the thing, the left adhere themselves to unwritten rules and current precedences. Whereas the right will break all precedent and scoff at unwritten rules and will try to change the written ones in their favour. It happens everywhere, it's not just a US thing
That's the real reason why he'll always double down. That sort of realisation can fuck someone up and make them shut down to the idea of it completely.
It's crazy to me that some countries have everyone double check they've paid the right amount of tax. It's wild to me. That would be your governments job, and then they either tell you you owe them money or they give you a rebate. That's how it should work everywhere.
It's not that fluid, it still requires effort from reverse engineers but now they only have to deal with graphics and engine specific stuff rather than everything.
If you can't afford a ps5 it'll be better to just get a small loan or finance at a place like Currys. Only way this rental service is better is if a contract can be very short like a month or two and you're only planning on playing a game or two and have no friends you can or are willing to lend you their console for a short time.
This is why you have style guides, policies and safeguards, with others checking PRs as they go through to catch this sort of stuff.
Plus I'm not saying everything should be commented. By default things should be explainable through the code and making sure variable and method names are descriptive, along with strong typing if your language has it.
Comments are there for when the code itself is not enough. But you're right shit always creeps in eventually regardless of the best intentions. Which is why teams need tech debt breaks where no new features are added and they go through the code fixing the niggly things that haven't been worth fixing whilst doing other features, and ensuring critical sections (the kind that usually have comments on them) are still working as intended and described accurately.
This is from a senior dev in the industry.