I’ve always been curious as to what “normal” people think programming is like. The wildest theory I’ve heard is “typing ones and zeroes” (I’m a software engineer)
I’ve always been curious as to what “normal” people think programming is like. The wildest theory I’ve heard is “typing ones and zeroes” (I’m a software engineer)
It’s like building the NY subway system—you’re constantly adding on new bypasses and trying to maintenance old tunnels in order to account for new features/population. It ultimately ends up working most of the time and the daily commuters get to move from Point A to Point B with minimal interruption, but if you viewed the subway as a whole it’s a cobbled mess with lots of redundancy. Some of the architects who are currently around don’t even know where the oldest tunnels go, or why they’re there.
Wanted to give a take on it that didn’t focus on the obvious “language” aspect. I could be 100% wrong on this—I’m sort of basing it off of comments I’ve seen here or there. I know very few folks who work in tech and I work in healthcare.
Honestly that’s more like network engineering than programming, but you’re surprisingly accurate.
This is an accurate representation of tech debt.
Definitely spot on for network engineering.
Fascinatingly accurate.