After reading it, I feel like I may not be someone who can apply this “final form” of software development.
This seems like a story for developers working at the system, OS, or kernel level. My work is mostly about assembling applications according to framework IoC patterns. If I had to write things in machine language, I cannot even imagine how much the codebase would grow, considering that I already deliver projects with around 70,000 lines of code.
Whenever I read articles like this, I’m reminded of how many layers there are in programming, and where I currently belong within those layers. At the same time, I also feel a little envious.
Most of what I do is identify widely used frameworks and libraries in the market, then assemble them into working systems. So rather than choosing stacks purely out of technical curiosity, I usually approach them from the perspective of market demand.
Still, someday I would like to enter one of these “final” domains myself.
The Final Form of Software Development · HackerTrans
This seems like a story for developers working at the system, OS, or kernel level. My work is mostly about assembling applications according to framework IoC patterns. If I had to write things in machine language, I cannot even imagine how much the codebase would grow, considering that I already deliver projects with around 70,000 lines of code.
Whenever I read articles like this, I’m reminded of how many layers there are in programming, and where I currently belong within those layers. At the same time, I also feel a little envious.
Most of what I do is identify widely used frameworks and libraries in the market, then assemble them into working systems. So rather than choosing stacks purely out of technical curiosity, I usually approach them from the perspective of market demand.
Still, someday I would like to enter one of these “final” domains myself.