Form follows fiasco

Why software architects should stick with their projects Last weekend, I took my daughter to an antique bookstore/coffee house where we came upon a book called "Form Follows Fiasco: Why Modern Architecture Hasn't Worked." This book is not about software architecture. It's about actual architecture, which involves buildings that might collapse if not built right. … Continue reading Form follows fiasco

Software Engineering is here to stay

I counter the dramatic assertion that developer jobs are on the brink of obsolescence. I distinguish the roles of coders, who may face obsolescence due to their narrow focus on translating specifications into code, and software engineers, whose broad skill set in solving complex problems and innovating ensures their continued relevance. I argue that artificial intelligence and large language models augment rather than replace the human intellect, emphasizing that while app development and deployment methods may evolve, the necessity for software system maintenance and the efficiency of programming languages as a form of shorthand will keep developer roles indispensable. I argue that, despite technological advancements changing the landscape of app development, the core importance of the software engineer's role remains unchanged.

On luck and gumption

In our industry, gumption is what gets us to try new things, experiment, and build new products. Sometimes, it means trying new programming languages or frameworks with nothing else to explain the decision than your gut feeling. Sometimes, it means ignoring the prevailing management methodology to run your team as you think it should. So when opportunity knocks, have the gumption to answer.

Some thoughts on recent RTO announcements

Between the commercial real-estate lobby, automotive lobby, EV lobby, and small business lobby — they all want us to drive around during the day and grease the economy's gears. Without knowledge-workers in Teslas driving for an hour each way to the office and buying avocado sandwiches, capitalism as we know it today will grind to a halt. That is the real reason you are asked to return to the office.

On Amazon Prime Video’s move to a monolith

There is nothing fundamentally wrong with a monolith, and a well-architected monolith with well-structured code with separation of concerns serves its purpose quite well. If Amazon Prime’s experience proves anything, it is that when the granularity of services is too fine, complexity and costs skyrocket.

Some thoughts on the latest LastPass fiasco

Employers are rightfully paranoid about corporate secrets being compromised by bad actors. Some of the worst data breaches were caused by employees. Employees, however, should be equally paranoid about their personal secrets being compromised for the same reasons. If corporate secrets can be leaked due to a colleague's mistake or malfeasance, so can your personal data entrusted to your employer.

Comparing AWS SQS, SNS, and Kinesis: A Technical Breakdown for Enterprise Developers

Queuing is a critical component of software architecture, and choosing the right system for your cloud-native enterprise application is crucial. In this blog post, we'll compare Amazon Simple Queue Service(SQS), Amazon Simple Notification Service (SNS), and Amazon Kinesis, exploring their strengths and weaknesses to help you determine which queuing system is best suited for your use case.