Software Architecture: After Infatuation Comes the Shock
Some developers get so excited about new technology that pragmatism disappears. That detour can become expensive. Here is how to prevent it.
Some developers get so excited about new technology that pragmatism disappears. That detour can become expensive. Here is how to prevent it.
Pragmatic architecture documentation with arc42, AsciiDoc and draw.io: Proven methods for sustainable software development and efficient team communication.
Establishing a software architecture for a project sounds like a decision for eternity. Why it isn't – and shouldn't be.
Hi, “RCoffee [an internal tool for content production] accesses the test servers via SSH and displays the Tomcat logs” Wow. That was surprising. I have been working with this client for a year now. The application is the market leader in its field, and the current version was developed over 10 years ago. A lot has accumulated, of course. And when I am hired, the technical debt is usually very large.
Hi, An old developer joke: There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors. – Leon Bambrick Or another version: There are only two hard problems in distributed systems: 2. Exactly-once delivery 1. Guaranteed order of messages 2. Exactly-once delivery – Mathias Verraes And there are many more: There are so many variations on the “there are only two hard problems in computer programming…” joke that I’m starting to suspect that programming isn’t actually very easy. – Nat Pryce