Live data from Hacker News

Programmers: Before you turn 40, get a plan B (2009)

improvingsoftware.com

271–280 of 446 posts

Re: Programmers: Before you turn 40, get a plan B (2009)

#271

Earlier quoted context omitted.

If it takes 30-45 minutes something is wrong. I hated standups as well until I worked with right people.

you misunderstood, the standup happens 30-45 minutes into the workday.

Show up 5 minutes before standup, or 5 minutes into it, then. Problem solved. ;)

On a more serious note, read email, get a drink, and plan your day. You’ll be talking about the plan in less than an hour, anyway.

Re: Programmers: Before you turn 40, get a plan B (2009)

#272
I think the entrepreneurial route is the most realistic route in the long term. The idea is to use your experience and knowledge to build a software product that a niche market needs, and sell it.

If you live outside the main city centers like Silicon Valley, New York, Los Angeles etc. its not hard to make a full-time income online.

A key thing to understand is that, as an employee working for someone else, your revenue will always be capped to the rate associated to the job market of that profession. There might be a 10% difference between jobs, but that's it.

While if working as an entrepreneur, your revenue cap is the one of the market you are on, whatever that is.

Re: Programmers: Before you turn 40, get a plan B (2009)

#273
post #46

I'm not sure I'm buying that. The JVM ? Still rocking it 20 years after. Memory allocations pattern ? Still there. The network stack ? Well, doesn't seem to have changed a lot. The older guys, they seem like they had the time to correctly learn the unix network tools, the jvm debugging ones, the memory inspection ones. I've known older devs for which I have the utmost respect because I felt like they can just debug t…

Yeah, you hear all these horror stories about how developers have a "shelf life." In the meantime, though, every single older developer I've met has been extremely knowledgeable and frankly much better at the craft than myself. Look at any hobby -- say, guitar playing. The difference between someone who's been doing it for 4 years and someone who's been doing it 20 years is ridiculous. They're so much better. I feel…

I am at a startup just now and they are complaining about frontend devs as - they don't hang around - they don't want to touch the old frontend written in Dojo, just the React stuff.

I'll do whatever (I am officially a 80% backend dev who can do enough frontend when needed). The Dojo way of writing things actually seems a lot nicer than React, but it ain't cool.

Re: Programmers: Before you turn 40, get a plan B (2009)

#274

Earlier quoted context omitted.

I don't have a problem with standups. I actually like having ticket tracking systems (how else are you supposed to know what is high priority to work on?). But, open offices are objectively terrible. Research shows it, people here complain about it all the time, and yet companies keep building them. Where I'm at, the floor is divided in such a way that teams sitting together can sometimes have their own little "bull…

I hate standups with a fucking passion. All a standup to me is an interruption 30-45 minutes into the day which causes me to lose an hour or more of time every single day. I basically just fart around with things that don't need much focus until the standup happens. The worst part is that I suggested instead of standups we just send what we we would have said in the standup via slack. That lasted 3 days. The reason n…

Sounds like your team might be doing standups wrong. Firstly they should be 3-8 mins tops. Secondly, I consistently find that when someone mentions what they're working on, more days than not, someone shares something useful (hey, we did something similar last year . . .) and when someone is blocked, someone agrees to get them going again. It's also just nice to have a sense what the whole team is working on.

[EDIT] I also misread length of standup. And agreed, it's tough to have an interruption 30-45 mins is as you lose that time. Wonder if you'd be better with middle or day standups or something so at least it was between worthwhile chunks of time?

Re: Programmers: Before you turn 40, get a plan B (2009)

#275
post #261

Earlier quoted context omitted.

I think you miss the point about 'shelf life' The shelf life is due to a business decision, where the knowledge the older person has is deemed insufficient to justify the compensation they've grown used to. Sure, you love working with them and it's better for engineering, but the business wants college grads they can pay less, even if they don't do the same quality work. Importantly, this doesn't have to be logical o…

It's not just quality, it's capability. As I'm fond of saying, I may cost twice as much as an entry level engineer, but I can do things that two entry level engineers can't do.

I have a similar expression. My daily price might be higher, but they will cost you more.

Re: Programmers: Before you turn 40, get a plan B (2009)

#276

Earlier quoted context omitted.

I'm pretty sure you have misused the word literally.

Try to update a one year old npm project and you will find that literally 75% of the code in node_modules changes, and also that the app no longer works.

And then it was yarn. And then npm again.

Re: Programmers: Before you turn 40, get a plan B (2009)

#277
post #19

Earlier quoted context omitted.

Literally everywhere outside of Silicon Valley you can get great jobs in Software that move at a reasonable pace. SV is very different from the rest of US

Not to mention the great overall quality of life that a regular 9 to 5 job as a software developer provides in the rest of the country outside of SF/NY/SEA/LA/BO. Be a median software developer, pair up with a spouse making the national full-time median, now you've got a $160,000 household income (which doesn't sound special in SV). Married that's $115k-$125k in take-home pay in most of the country. $160,000 family i…

You're absolutely correct, and it's something so many people do not realize.

Re: Programmers: Before you turn 40, get a plan B (2009)

#278

Earlier quoted context omitted.

> the actual work of being a developer/programmer in a professional setting is a really shitty job and sad life The thing is, it doesn't have to be and, until relatively recently, honestly wasn't. It's a shitty job and a sad life because we have open offices, ticket-tracking systems and daily standups. There was a time when programming was exciting and rewarding.

>open offices Noise-cancelling headphones are mankind's greatest weapon in the hopeless war against braindead management practices.

Surely evidence of the declining mind share of unions.

Re: Programmers: Before you turn 40, get a plan B (2009)

#279

Earlier quoted context omitted.

The thing is, it doesn't have to be and, until relatively recently, honestly wasn't. Indeed. It's almost as if it's a bad idea to take people working in a field where creativity and careful thought are fundamental and a wide variety of experience with different but related ideas is often helpful and then try to turn them into interchangeable commodities with the whole process dumbed down to the level of the least com…

Yup. Gray-haired contracting life is a different beast altogether compared to being an employee.

How did you start?.. the fear of not being able to acquire work is what's stopping me.
Post reply on HN