71–80 of 244 posts
Earlier quoted context omitted.
This. I see too many older developers who complain about ageism, but what's really going on is that they're essentially the same developer they were 2-3 years into their career. If you've been working in the industry for over 20 years, employers can and should expect that you've made the most of it. Those developers have very few problems with ageism. It's the ones that have become comfortable and stagnated that have…
I'm not a programmer anymore, so I don't have a horse in this race, but I cringe when people exhort older programmers to "stay current." If you're spending your free time learning about distributed databases, machine learning, cryptography--fields that existed in the 1990's but are more relevant and developed today because of the web--you're becoming a better programmer. If you're figuring out the latest "compile to…
Shouldn't having the knowledge of what you could do in 1994 make you that much better suited to doing it in 2015 even if you have to spend a few days learning the faddish way of expressing the concepts?
When I was a young man, a slightly older associate told me that "programming is a trap". What he meant is that if you are relatively smart, you can get a CS degree, get good at it, and go earn a fantastic income right out of school. I heard the words. I understood the words. I agreed with the words. Even now, 30 years later, I keep asking "is this a trap that I choose to remain in?" I still love programming, but it i…
You should quit now, and try working a multitude of other jobs. Come back to us and see if your definition of 'trap' has changed, or expanded. Software engineering is such an entitled world, it is ridiculous. As someone who has seen the world of menial work, I will never, ever leave it. I feel blessed. You should too. You just don't know it.
I am 55 and have been programming computers since 1975 when I was 15 years old. Do the math, I have been programming now for 40 years. Recently, I had a conversation with someone else about this topic and I told them that I have never been so excited about my career, the field of computer science, and most importantly the opportunities that exist today in the field of technology. The excitement surrounding too many t…
Maybe I should do a graybeards Meetup group or something. Get some reverse-discrimination going...
Earlier quoted context omitted.
I don't think it's the developers being myopic. For the most part, it's management that views development as a young person's game and encourages people to move out of the technical track and into the management track. If companies viewed programming as a long term career, they would put the pay scales in place to treat it as such. It's only a "trap" in the respect that in many (not all) places your pay maxes out as…
I thought this was a problem of managers for the longest time, but recently I read an argument once that convinced me of the opposite. Tu quoque: the "my boss doesn't understand" problem in companies basically comes from people working for people with lower IQ than them. It's not a skillset gap, it's a pattern-recognition gap. In the military, the best soldiers become officers, and the best officers become generals—e…
This isn't true in any modern military.
I'm not saying that people don't get tired/slower as they get older (I struggle with it), but I don't think it's inevitable.
Earlier quoted context omitted.
As someone in their late twenties who is just starting a career in programming, it makes me very, very happy to hear things like this.
Hahah don't jump to conclusions, and don't trust anyone over 30.
Earlier quoted context omitted.
A trap, compared to what? Is plumbing a trap? Is finance a trap? Is hairstyling a trap?
I get your point and agree with it. I've said it many times myself. But people don't think in terms of mastering a craft and spending a productive life practicing it. In the modern world if you're not on a trajectory toward the 1% you're losing. In that sense most engineering fields are "traps" because if you stay an engineer you aren't going any further up the ladder. I'm a craftsperson, and I still practice the cra…
And what, exactly, is it that you're losing? You can have a pretty damn fine life without getting anywhere near the 1%.
Earlier quoted context omitted.
I guess I might as well pile on. Turned 50 last year. Got my first paycheck for writing code junior year of high school (writing BASIC code on a Commodore PET!) Working on my fifth startup now.
I can't imagine all the technologies and skills you guys have acquired. If I may derail the conversation a little bit, may I ask if/how you use the things you've learned today? I mean, is it things like paradigms that have stuck with you like OOP/functional/w\e, or do you always structure your exception handling in a certain way, no matter the language? Are there skills/technologies you've been using since you've sta…
There's plenty of languages I've used over the years that I have no use for today, or hardly even remember: Basic, FORTRAN, assembler, Pascal. None of those languages even had exception handling, so it's hard to say that it influenced my thinking on the subject, except by forcing me to be familiar with the alternatives.
Today it's C++ and C# that pay the bills, with as much Python as I can sneak in. Next up in the queue is Javascript, for which I'm admittedly overdue, but that one's entirely on my own time.