Andres Velasco Garcia·Sep 5Philosofy for Software Engineers — Part 5: Nietzsche and the Loose Ends of Good ArchitectureAbout this Series
Andres Velasco Garcia·May 22Philosofy for Software Engineers — Part 4: hegel and Why Architectures Keep Coming BackAbout this Series
Andres Velasco Garcia·May 8Philosofy For Software Engineers — Part 2: Medieval AI, Made in MallorcaI’ve started this series mostly as a way to explore ideas I enjoy. Not trying to be academic or deep — just having some fun. Also — small…
InTop Python LibrariesbyMaximilian Oliver·Mar 28Breaking My Own Systems on PurposeHow I Built Autonomous Failure Testing Pipelines in Python Using Chaos Engineering Principles.
Yevhenivashchenko·Mar 25C++ and AI Engineering1. This text discusses how engineering principles from the world of systems programming — especially C++ — are surprisingly well-suited to…
Tarento·Mar 145 Engineering Principles That Separate Systems That Scale From Systems That FailA practical playbook for building software that scales without breaking.
Bram van den Reijen·Mar 12What Elon Musk’s engineering rules teach us about software testing.Most software teams don’t suffer from a lack of testing. They suffer from too much of the wrong kind and that kind being automated too…
InWrite A CatalystbySriram Mahalingam·Mar 8DevOps Isn’t Platform Engineering — Why Treating Them the Same Slows TeamsAutomation pipelines, tool ownership, and cultural practices overlap, but DevOps focuses on processes while platforms focus on enabling…
InCodeToDeploybyTony Trejo·Jan 26The Biggest Mistake I See: Treating AI as the Core Instead of a LayerOne of the most common mistakes I see in Generative AI systems is subtle but dangerous.
Hammad Arshad·Jan 20Shipping Fast vs Building “Perfect Systems”: A Lesson I Learned the Hard WayIn engineering teams, there is a debate that never seems to end:
