[conflicted_dev]

Heh. It took me a few months to be put into my proverbial place, but now I understand just how amazing some engineers are. I read that post a while back too. A few of my colleagues have actually done client work for Google (even though they clearly never had to go through their interviewing process).

The thing is, I'm trying to figure out whether if it is really worth my time to continue the grind. Are there other roles that I might be both more excited about and better equipped for? Perhaps. This thread is essentially the beginning of my research process.

[mikekchar]

I'll take a young developer who understands where they are over someone who can solve tricky algorithm problems any day. You've got a good attitude and it will serve you well.

Here is my litmus test for developers. Writing software is a boring job that requires you to obsess about details and to concentrate heavily on minutia far beyond the tolerances of most people. It is also a thankless job. Users will hate you for the bugs. Management will hate your for how slow you are. Nobody will appreciate the effort you put in, all believing that what you do is trivial. Even your own team mates will view your work and universally declare it to be crap. Every time you try something new, someone else will tell you that you are doing it wrong and imply that you are an idiot. Every time you discover something truly complex that requires years of experimentation to even come close to getting good at it, someone will laugh at you and direct you to an ill considered blog post or framework that purports (and fails) to solve your problem. To be blunt, you will be criticised for virtually every keystroke you make for the next 45 years.

There are easier ways to make a living. But if programming still seems awesome after you have read the above, welcome to the club. Never give up.

[Koshkin]

Judging from my own experience, none of this is true or correct. In particular, programming is by far the easiest way to make a (good) living. The apparent fact that programming is not for everybody does not change that a bit. A lot of people who work as software engineers hate it and/or are not good at what they do, but if coding were taught in K-12, I am sure many more people would have liked it - simply because coding would have been a second nature, just like reading, writing, and counting.

[omarish]

And then there's manual labor...

All sarcasm aside, I don't think there is anything "exceptional" about being a programmer, just like how there is nothing exceptional about being a management consultant. I wouldn't say it's the most thankless job, nor would I say it's the job where you get the most praise. It's a spectrum.

Often times, when I have thoughts like these, exuding confidence that my job is the most in any dimension, I realize that they might be more about me than the field of software engineering. Put differently, I'd probably have the same thoughts about welding if I was a welder, or the same thoughts about monetary policy if I worked at the Federal Reserve.

[20years]

Have you considered getting a software or web dev job in a non tech company? They generally don't put you through the algorithm tests and tend to have interesting problems to solve. Completely different vibe vs tech companies though but may appeal to you more.

Examples:

Warehouse shipping companies that have a need for shipping software, barcoding software, always need reports, etc.

Mail order or e-commerce companies who rely heavily on inbound orders and who need automation/streamlining.

Advertising agencies tend to need web devs too. Pay is generally lower but you get the opportunity to work on all types of projects.

[analog31]

This is an excellent point. I work at one of those companies. Actually, it qualifies as a tech company, but our main revenue source is not software. I think that the pace of work at a multidisciplinary company isn't as frenetic as a pure software shop, just because it can't be. And we don't conduct coding interviews.

I had a conversation with one of our developers recently. He could have been you. He told me that he had interviewed at the big software shops, and had flunked the coding interviews. Yet I know that he's a very bright and productive engineer, who is also a pleasure to work with. I asked him: After those interviews, would you really have wanted to work at one of those shops? He said that he wouldn't.

And I know that I wouldn't survive that atmosphere either. So you're in good company.