If you describe yourself as a “Full Stack Developer” today you are putting a target on your back. You are positioning yourself as a generalist in a world that is rapidly automating general work.
The abstraction-as-career-debt framing is spot on. What youre describing mirrors what happened when spreadsheets automated accounting clerks, then when SQL replaced manual database work. Each abstraction layer creates a cohort of people who only know the tool but not the underlying system, and that eventually collapses when the tool changes or fails. Depth really does become the only defensible position when generalist work gets commoditized.
Well said Ashok, now a days most of devs introduce self as Full Stack, my analogy of being full stack is good at one thing and get an understanding of things so one can visualise the areas and sense of broad understanding.
Loved this, very insightful
The abstraction-as-career-debt framing is spot on. What youre describing mirrors what happened when spreadsheets automated accounting clerks, then when SQL replaced manual database work. Each abstraction layer creates a cohort of people who only know the tool but not the underlying system, and that eventually collapses when the tool changes or fails. Depth really does become the only defensible position when generalist work gets commoditized.
Well said Ashok, now a days most of devs introduce self as Full Stack, my analogy of being full stack is good at one thing and get an understanding of things so one can visualise the areas and sense of broad understanding.