I’m used to driving old shitboxes but a few years ago we rented a completely new car. It was almost driving itself, making sure I stayed in my lane, it had automatic beam selection, a big screen for playing music and navigation, tiny little plastic thingies that pops out when you open the door making it harder to dent adjacent cars. It was a fucking spaceship. I’m not going to lie, I would love to have all of those fancy features.
So breaking things up aggressively into small components you can reason about in isolation tends to be the best way to write reliable code you can maintain over time.
This is so true. Something that has really improved my coding has been having a linter that whines to me about assignment branch condition size. Compared with learning how to properly stub methods in tests it has helped me break tasks down into simple manageable chunks with little room for error.
All these newfangled high-faluting AI tools are ruining the software industry and making developers go soft. Back in my day we didn’t need no robot to get things done, we knew the value of hard work and wasn’t afraid to pull up our sleeves and copy/paste the code from Stack Overflow ourselves.
This has been my entire last week. Our client has a tight deadline for this feature I’m working on, in part due to their own indecisiveness and in part due to an external API developed by a big corporation being late and buggy. This means we’re doing testing and bug fixing simultaneously with doing new development and even with speccing and estimating new subtasks. And with this client, this close to the deadline, every little bug is critical and needs to be fixed right away. Meanwhile, a junior developer is being onboarded to the project and another developer is working on a different feature derived from an architecture I made. There’s always a fire I need to put out, a question I need to answer or a feature I need to describe. I’m writing more emails than code these days.
I normally go “what the fuck did I even do yesterday?” five minutes before daily standup and look at my git commits and calendar for the day before to piece together a plausible version of my workday (I do my timesheets the same way as well btw). Very little serious information gets passed on but somehow it makes my boss happy and he has told me that he likes the way I do standups.
I work at a small company where most projects only have one or two developers so standup meetings are usually a lot of completely irrelevant information. It’s very boring. “Yesterday I worked on the thing on the project you barely know what does.”
Never trust anything you read on the internet
George Washington. This thing should have been nipped in the bud.