Considering how we're all "conditioned" to scroll through a chat log, by the time we come to our senses we've probably browsed through half of your landing page already.
Very nice!
Not the author, but I make micro commits because it helps me backtrack my implementation decisions.
A lot of times I would look at a line of code thinking why I would write something like that and find the reasoning by git blaming that specific line or chunk of code.
In short, I do it to make up for my poor memory.
Yeah, I think I'm getting more detailed analysis on Social Media from strangers, which I know I should take with a grain of salt. But I guess I'm expecting a lot more than "a filed caused this" from the company that caused this havoc.
I'm reading this article because I'm bored.
And I'm commenting this midway into the article because I got bored again.
I guess the author really did get his point across.
I can totally understand the move fast and break things mentality, but I'd like to stress it's equally important to pay back the occurring tech debts. I am working on a massive spring monolith that's somewhat of a huge pile of spaghetti, and when the higher management decided to enforce code quality in the pipeline, it became a living hell to work on.
I can't even add a logger without having to refactor the whole 2000 line class while writing a whole-ass unit test for it. It's been a full year and I still have to deal with this sort of crap on a weekly basis.
The most ironic part is that most of the devs that cooked the spaghetti are now either in upper management or in the same devOps team that's demanding us to clean the mess up.