Tech - Atom" href="https://bbuyukliev.blogspot.com/feeds/posts/default" /><br>Tech - RSS" href="https://bbuyukliev.blogspot.com/feeds/posts/default?alt=rss" /><br>Tech - Atom" href="https://www.blogger.com/feeds/4774530795645737691/posts/default" />
Tech - Atom" href="https://bbuyukliev.blogspot.com/feeds/2395799038232110818/comments/default" />
Life > Tech: Code is the hard part
Friday, August 14, 2026
Code is the hard part
You've probably heard the opposite from those annoying corporate types with a shiny and popular LinkedIn profile. Guess what? They don't have a clue because they have never evaluated a system for its technical merits. They are the "product owners" in an ever more enshittifying world.<br>Code represents the data transformations and data dependencies in a system. Code has formal syntax and well-defined semantics, and is mostly non-ambiguous. Whatever you call "architecture" is an abstract, reduced and conceptualised view that is derived from the very fabric of code. True no-nonsense knowledge about a system is in the code, and in the code of the subsystems it interacts with. Architecture exists even at the micro level of a single function - it embodies decisions on what the inputs/outputs are, how those inputs are manipulated, and whether such a function needs to exist at all in the wider scheme of things. Writing the code for a particular problem is an exploratory process where you gradually unveil the nature and the constraints of the problem as you type it in. It takes a certain shape and starts living an animated life in your head. Code is self-correcting tells you that you need handle a particular edge case; it also tells you to reduce complexity by removing these 2 redundant states from your state machine implementation. Not because you are following "patterns", but because you understand the flow of your own code.<br>Code makes the difference between the application that corrupts your data and exits abruptly with "unhandled exception occurred", and the one that is able to exit gracefully and prevent such a situation altogether with a sensible message like "your input doesn't satisfy conditions A and B". This is the very foundation of security. Intuition for performance also comes from understanding what your code does, and not by treating it as a side artifact.<br>Code is here to stay and will be the backbone of the stuff that matters. Eventually, the accumulation of throwaway slop specified by "architects" and "domain experts" in a markdown file won't be worth the storage medium it is stored on. Programmers who understand their code will be the true architects.
Older Post
Home