The Todo App is such a simple example that for a lot of libraries/frameworks it does very little to give me confidence that it's useful in large scale applications. So the solution is always get stuck in using the thing, hope the community are active enough to help answer questions and that the whole thing isn't a waste of time.

I wonder what percentage of programmerD have ADHD?

Redux toolkit may hide some boilerplate, but damn it's still not simple

We work remotely, the only way I can collaborate with other Devs, team lead, product owner is slack. Respond to my f***ing messages people!

I've been working as a programmer for 16 years now, and would say I'm not inexperienced, so it's frustrating to feel like a noob after months at a new company when they have poor internal documentation, hundreds of repos with default readme, pretty much no use of docker, sub standard equipment and use their own weird software for deployment. It's hard to meet expectations under these conditions.

I wish sophos had some sort of out of the box mode for development which avoided slowing down IDEs and build servers

Why is it that when people are anal about linting they don't like the default/mainstream conventions?

"Hi X, I'm getting some push back on a bigger hard drive seeing as you'll be on the only person in the company who has something bigger than 250GB. Are you able to give me the headline values of how you've used up 249GB so far please?"

Stop putting spelling mistakes into code!

Hey support, if you just copy and paste entire paragraphs from me of informal language which I've written with you as the intended recipient to help you understand what's happening, and send that to the customer, tell the customer you're waiting on me, tell my boss you're waiting on me, when the messaging clearly demonstrates that I'm waiting for you to liaise with the customer and get specific information, then really you're just making our company look incompetent and me look lazy, when those things apply to you.

Managers should not communicate with a customer then sit on it for a week or two before passing it to a Dev as high priority/fix it now. They also should not say our 'team' is working on it when that team is one person who is also busy with other tasks.

Who tf are these people who write files called things like handlers.js which are over 1000 lines long?

What is it with companies putting me on their half assed legacy products that are critical but they won't commit enough staff and resources to improve them properly?

Not a fan of legacy products which make use of a tonne of TSQL stored procedures, especially when they include a mess of logic, spelling errors, no version control of course, all squirreled away for some unlucky person to find and unpick in years to come.