Don't Outsmart hard choices: Why architects are the ultimate tech debt perpetrators

Problem-solving is both a blessing skill and also a curse. It's on every software architect/engineer veins. It's pretty addictive and makes us feel useful and smart. Having sharp problem-solving skills is always great. I mean talent is gold. We want more talent, and what talent do intelligent solutions to complex problems. The heart of software engineering is fixing problems. Don't get me wrong this is good. However, sometimes we need to go with HARD DECISIONS. I can't think of a harder choice today than decide to pay the technical debt. However, once you got a design wrong and started things with the wrong feet is easy yo keep pushing problems aways without belly and keep the debt growing. Why does it happen?  



Hacker Mindset


Hacker mindset(HM) is at the heart of everything. HM Is both a good and a bad thing. When Hacker mindset means finding a creative solution to outsmart hard decisions, it could be a bad deal in the long term, for the following reasons:

  1. All Smart Decisions have a High Price. Often is complexity.
  2. Not fixing a problem now could mean: Making the problem bigger and live longer. 
  3. The issues tend to get worst over time because we always need to change the software.

What happens is you dont kill the evil at the beginning. It just gets worst. So Often we want to avoid HARD and difficult choices because they mean:

  • Lots of Time Invested (+1 year)
  • Lots of People Invested (+10 people)
  • Lots of Cost involved (People + time) 

As a result, it is not a business feature or capability; it is pretty hard to justify the cost and the time past and get it worse. 


Stop Outsmarting Decisions


Pretty much Software architects are the ultimate tech debt perpetrators. So there are phenomena I want to describe, probably you notice too. Outsmarting hard decisions is expected from Software Architects. It's why they are there, right? Managers, Executives hope software architects to bring magical hacks that would avoid a vast money expense because people dont want to prevent to take hard choices(often making the problem worse). Since 2006 I see this phenomenon happens. Several times is expect from me, a magical solution to avoid lots of work and cost. you know the issue. Several times we can smart hard decisions; however, there is a point where it's no possible anymore, often this is the point that the debt is too high. The famous: point of no return or let's re-write the systems. 


Doing Boring Work


Doing tedious work is hard. As Architects and engineerings, we like bleeding edge stuff. Picking hard choices is even hard because we need to admit we made poor choices in the past, and we prefer to keep picking easy ways outs until there is no way out. We can't do boring work with smart decisions; sometimes, all we need is very dumb and repetitive work. Great design for non-green field solutions often will mean hard and expensive choices given tech debt in place. However, we need to do the hard thing rather than keep hacking our next step away from the problem. Boring work does not involve hards, does not involve outsmart hard decisions and is long, boring, and expensive but sometimes is what you need to do. 


Cheers,

Diego Pacheco

Popular posts from this blog

C Unit Testing with Check

Image
When I start on IT, several years ago(+15), C was the first language that I learned. But was not the first language I mastered and deployed in production which was...surprisingly Visual Basic 6.0. However, when I learned C or any language back on that old and arcane time noddy was into testing. However now is impossible to work professionally in any language without tests. C is a low-level language but still kicks ass and has several interesting libs/frameworks. People use to fear C a lot because of lack of syntactical sugar but once you get used to it is not that hard at all. Today I want to show how you can do Unit Testing with C. I will not show how to do Unit Testing with C++ but with C ANSI actually. We will be using Check a unit test lib for C ANSI.
read more »

Having fun with Zig Language

Image
Zig is a general-purpose language created in 2016 by Andrew Kelly .  Zig aims to fix the issues C language has while being pragmatic and simple at the same time. Zig really shines as being simple by not having any hidden control flows, not having hidden memory allocations, no pre-processors, and no macros. Basically, it's one language and one language only. Since pre-processors and macros can get really complex and become their own universe. Sure it's not the Zig Philosophy.  Zig Compiler(Zig cc) also is a C compiler, and the interoperability from C to Zig is very good. Clearly, we can see influence from other languages like Go and Rust; however, Zig is pretty unique and different from Go and Rust.  Zig is fast. Zig is perfect for system programming. I bet we will see a lot of solutions being built in Zig. As a languages aficionado, I like to learn at least one language per year and sometimes more; Zig was my 2021 pick, did not regret it. Even if you dont use all language...
Keep reading

HMAC in Java

Image
In 2018 AWS CTO(Vogels) said : "Security is everyone's job". For the last 2 years, there was so many famous and big data leaks and breaks that made that statement be very true more than ever. Security often could mean worst performance and worst user experience so in order to get it right you really need to think about the designs before jumping into to code and consider performance and user experience has main requirements.  I was thinking about writing about how to do HMAC in Java for a while and recently Redis 6.0.0 come out and to my surprise, there was a refactoring on the password part in order to use HMAC.  Security easily could scare engineers often because it is not something well spread yet but I believe this will change soon. It does not matter if you have to deal with PII Data or not, security is super relevant because everybody is running their workloads at the cloud or with IoT and Edge devices which means more distribution, more code, more points of fail...
read more »