Which do you think is ?
Software engineer. [Reluctant] Salesforce dev. Salesforce’s biggest hater.
…
Microservices.
Not really programming, as this is more on the architectural level.
Microservices is a valid approach when you need to address massive scale. The thing is, I have seen it applied to things that could realistically serve its audience in a handful of modest servers with a less fashionable approach.
It was done under the guise of simplification; each individual microservice was in fact very small. But this at the cost of absolute spaghetti architecture.
I assume this is not original at all at this point - but (extreme) DRY is not a good practice. My experience is that a bit of copying yourself and your colleagues in the code base often make maintenance of the code base easier.
Getters and setters for everything. Certainly, if you want an object to be doing more than just getting and setting a value right now, get them in there!
Planning to add functionality later without breaking code? Stop it! That should break code! If I'm consuming a library and have been using this setter method for 2 years, I don't want it to suddenly introduce brand new validation, caching, or logging behavior!
What is the exact definition of an IDE? JetBrain's products are as good as ever, in my opinion, but people have definitely made non-IDEs into big, hulking behemoths with tons of plugins. If anything, maybe "just an editor" is dead?
I think they mean the transition that all IDE's are making towards an agentic interface, hiding the code completely as humans will not have to interact with it since the AI will be doing a better job at everything, even auditing it.