The Tech Divide: Vibecoders vs. Status Quo Engineers
I'm an engineer with about 15 years of experience, and I'm tired of the denial I see between "vibecoders" and "status quo engineers." My journey started with an 80486DX and Turbo Pascal in Ukraine, where Pentiums were rare and expensive. My career path often feels like I've been time traveling:
- 2004: Learning Turbo Pascal and dabbling with Borland C.
- 2006: First job! My knowledge was outdated, so I learned MS Access on the fly and shipped a solution in two months.
- 2008: New job. My VBA skills were suddenly obsolete. "You can't build serious stuff in Visual Basic 6," I was told.
- 2012: New job. Big Data, distributed systems. How do you debug 100 machines? My .NET knowledge was trashed. C++11 was the new sexy.
- 2013: Back to the past with a new job at an equity fund, doing VBA again.
- 2018: Another new job, another trip back in time, supporting FPGA and Windows XP.
You get the idea. My career has been a constant back-and-forth through different tech eras. On one side, you have "kids" building sexy, cutting-edge stuff. On the other, "serious" engineers are building medical equipment with C and assembly code from the '90s. These two worlds can even coexist in a single company!
Read Full Blog