This is where I let it rip. Rants, hot takes, opinion pieces on everything from security to AI to culture in the software industry. Raw, real and a tad too honest ¯_(ツ)_/¯:
Great software doesn’t come from better tools, more testing, more reviews or really really cool AI tools. It comes from a team’s culture of members working together as a unit. But, for that we need to approach it with the same care to our culture as we do to our code: designing, reviewing, and refactoring it. You’ll see how shared values, team rituals, and communication patterns will quietly shape the quality of software with every single commit.
Bugs make Software tumble, but blurred boundaries make it collapse for good. For those structural issues the ‘Domain-Driven-Design’ label is readily slapped around, but what does that even mean and how put it into practice? The answer is… deeply philosophical, but worth diving into if you looking for guidance on building systems that make some sense.
Let’s dive into the mess that we get ourselves into when naively relying on JPA and its implementations and see how to generate nothing else but SQL statements that spark joy! Spring Data, JPA, Hibernate got our backs though to avoid such a mess, right? HELL NO! All they do is teach you a lesson to not rely on other systems without verifying the fundamentals functioning as expected yourself! There is ALWAYS pitfalls and you do not want to iron out those kinks in production.
The microservices hype is 4 real, but also completely unjustified. Netflix somehow claims to have pulled it off and suddenly everyone is slaying perfectly good monoliths into tiny pieces just to secure a spot on the bandwagon. But, microservices are out there to hurt you, just wait and see. Meanwhile, monolithic architectures who have always been kind to us have gone out of fashion without any good reason. As Public Enemy said it best: ‘Don’t Believe the Hype’.
