Hacker News Reader

Comment by georgieporgie | Hacker News Reader

Umm, I would say that 40 years of experience building software applications is a pretty huge advantage.

I have to admit, I don't see a whole lot of gain after about five years. As everyone is saying, CS knowledge is timeless, but aside from the basics, it's really not that useful outside of research positions. Most of software development is making CRUD apps, integrating APIs, and other tedious but non-complex stuff like that.

Regarding prestige, most of the time when I'm at a non-techie party, when asked what I do, people have nooo idea what "software engineer" means. :-)

View on HN

Most of software development is making CRUD apps, integrating APIs, and other tedious but non-complex stuff like that.

Isn't that sort of like saying that most of the restaurant business is flipping burgers? Just because something is more common, that doesn't mean you won't be able to move up the food chain a little after 40 years of programming. Companies still have plenty of hard problems to solve in network performance, hard drive performance, UI architecture, cryptography....

If the vast majority of jobs are in burger flipping, and the limited number of elite chef positions are generally filled by a small subset of candidates (e.g. top schoolers) who were on the elite chef track from the get go, then yes, it's exactly like saying that.

You don't really "work your way up" from years and years of CRUD apps and API gluing to hard CS. In fact, if you get a CS degree and don't go straight into hard CS, you will forget most everything you learned in a few years, not to mention miss out on years of focused practice.

I agree with that. I'm personally stuck in one of these positions and it's a black hole that's really hard to get out of. Once you've learned most of what there's to learn about CRUD implementation and gluing them together, you need to get out as soon as possible or a couple of years down the line you'll simply not be qualified enough for any other position in CS.

That or you can write code in whatever spare time you might have from your 8-10 hours a day job. Based on what's said around HN, people putting in 14 hours a day coding are not that uncommon these days, so perhaps it's something programmers are better get used to. Remember to blog, have a rich github portfolio, contribute to OSS and run your own consulting consulting company in the spare time from your full-time job.

Reply on news.ycombinator.com