DevOps Economics

Everybody is talking about DevOps now, which is good, but honestly DevOps is way bigger than what people are talking about. One of the CORE roots of devops is AUTOMATION of infrastructure - automate everything, that's true and that is so important, but that is not the only thing.

DevOps is not a framework, is not a model, is not a process - DevOps are some experiences from folks around the globe who have had success in extending agile to new frontiers like operations - some people started a movement called Agile Operations which I think is great.

DevOps is in some sense the evolution of the cultural change that agile and Lean promoted in development from the early 2000s. Now is the time to break more silos and continue to improve things. It's not easy, changing culture, but it is a necessary step for the evolution of software development.


There is no DevOps Team

How do you fight silos? If the answer is with more silos, the question must be wrong. DevOps is about culture and is about the right culture shift. There is no recipe of "right Devops" because it is a kind of desired state and there are several paths and ways to get there.  A DevOps team will just create another problem for you, believe me :-)

Beyond Automation 

Infrastructure automation is very important - making sure you have a automated pipeline from DEV to PROD is a key benefit for delivery agility and a great step to improve infrastructure/operations capabilities. Why is it not enough?
  • ·        Do you have unit tests? 
  • ·        Does your architecture scale up/out?
  • ·        How easy is it to have multiple teams doing several things at the same time?
  • ·        How much isolation you have, both in the sense of physical resources, and in the sense of teams?
  • ·        How much coordination and management do you need?
  • ·        How do your teams think? How do they work or fight with each other?

If you already have proper agile development in place that's great, if your architecture is Service Oriented, no matter if it's Microservices or not, if your culture is going well then devops is the next step for you otherwise you need to catch up with more aspects like: Architecture, Infrastructure, Tuning/Stress Testing, new ongoing models. 


An economic debt

I'm a consultant and I visit several companies. I see companies needing to catch up. For many decades people treated software without RESPECT. Companies and the entire market are still doing LOTS and LOTS of waterfall projects with FIXED SCOPE; managers and CTOs and CEOs still think software is a commodity and they don't care about quality, ways of doing things and culture.

One day this bill will come due, like a huge credit card bill where you are just paying the minimum - one day that becomes unmanageable. That is what is happening to the IT industry. Companies are struggling with simple things like: automated builds, integration tests, code reviews, proper architecture, blame culture, finger-pointing culture - and this is a side-effect of decades of bad IT choices.

IT is SICK. DevOps is great for the business but will work on IT, IT is the root cause of all evil in companies nowadays, is where all bottlenecks are, is where all the money is, is where all the WASTE is - we need to fix this.

Software never "exploded" up until now

I always wanted things to be different with IT, because in IT you can screw up several times and it takes so long for things to explode - for instance in other areas like planes or health care if you screw up, people die and then shit get serious and what do they do? Continuous improvements - they go there, look at the issues SERIOUSLY and IMPROVE to make sure that it does not happen again.

In IT there was no such thing as that until TODAY, so I believe these DECADES of bad IT habits like poor management, poor architecture, FIXED SCOPE projects are here and the BUSINESS finally will pay the BILL because it is starting to AFFECT the companies pretty badly. Better now than never :-)

A huge road ahead

There is lots of room for improvement, and I'm excited about the fact that finally things are moving, I feel we went through a DARK BLACK ERA in IT before, and now the mainstream (I mean real companies, real businesses, not IT companies like cloud providers :-) ) are about to change, or at least to acknowledge they need to change.

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 languages in p
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 »