Vibe Coding has just killed software abstractions | Clean Code, Clean Architecture, Design Patterns

In the past few decades, software engineering was built on top of abstractions. Things like clean architecture, onion architecture, clean code, SOLID, design patterns and so on.

The abstractions were codified as software development laws which MUST not be violated. Millions of software developers around the world have written code using these abstractions.

However, it's interesting to know that most widely used software systems like linux kernel has not codified these abstractions. of course they are written in "C", its possible to create abstraction in "C" or move to languages like C++

One problem I always have with the abstractions is that these are kind of solutions which are being pushed to us without understanding our problem domain or problem area. I mean if I just have to menage between two Classe, I don't need a factory pattern I can very well live with a simple if condition which will make my code simple,

The various laws like single responsibility or open close etc are not suitable in all the cases, but unfortunately, we played along, we didn't raised these questions.

Now with the vibe coding, it's possible to build the software without using these abstractions and it has changes the way software development game is being played. It not only possible to create the software in more than one ways but its also possible to compare them for complexity (both executional and understanding) and in considerable amount of time you'll see that the things with abstractions are just better.



#vibecode #softwaredevelopment #softwareengineering

#TheTheoryOfCode
#theoryofcode