Live data from Hacker News

How to avoid the software salary ceiling

thinkfaster.co

31–40 of 84 posts

Re: How to avoid the software salary ceiling

#31
Moneyquote: "Now I understand why older programmers complain about rampant ageism in Tech. Younger workers are cheaper, and programmer productivity is notoriously difficult to measure, so most companies opt for the cheaper option."

Wow that is so spot on, as a "generic" programmer asking $150K versus a "generic" programmer asking $75K ? Easy choice, we'll get two and double our productivity and halve the sick days! I noted that in the medical profession "General Practitioners" made the least, while specialists made the most. They were all doctors.

Specialist software categories:

Embedded Software - bringing up code without an OS, understanding hardware function and tools.

Graphics Programmer - these days understanding 3D programming with Shaders and other features common in todays GPUs

Kernel programmer - understanding the insides of the kernel and how to write code that works there.

Networking software - understanding all of the intricacies of how packets get from point A to point B, and what interferes with that and what facilitates that.

Security specialist - someone who understands what makes programs and systems break and can program fixes for them or ways to spot attempts at exploiting them.

Storage specialist - someone who understands file systems and disk drives and getting data to and from programs reliably.

Re: How to avoid the software salary ceiling

#32
post #14

The other thing that's somewhat related to this is the old "X years of experience means this range salary". Nothing like that cold, hard statement to remind you that the person across from you sees you as nothing but a cog or entry in a balance sheet. It immediately puts everything you've done, no matter how incredible/complicated/significant, down as if it's irrelevant.

That's capitalism. The sooner you stop thinking of your boss as your buddy and start thinking of the employer/employee relationship as a business transaction of hopefully mutual benefit, the better.

Re: How to avoid the software salary ceiling

#34
post #22
post #9

Earlier quoted context omitted.

Build / release engineering.

Could you elaborate, please?

Many enterprise organizations have a build/deployment process that is archaic, error prone, and takes lots of time.(in terms of man hours, and deployment latency.) A build or release engineer comes in and takes that process and transforms it into the press of button. Basically just build/deployment automation.

But the benefits to an org are vast for just a couple of months of the build engineers time. -Deploys much faster deployment, shortening the feedback loop between end users and development -Is far less error prone. The manager doesn't have to explain to his boss why development started deploying last night at 6pm but now it's 10 am the next day and the software still doesn't work. -No longer has to pay someone to sit there and baby sits builds all the time.

I've worked with a couple of release experts and they've always been extremely valuable.

Re: How to avoid the software salary ceiling

#35
post #22

Earlier quoted context omitted.

Could you elaborate, please?

Many enterprise organizations have a build/deployment process that is archaic, error prone, and takes lots of time.(in terms of man hours, and deployment latency.) A build or release engineer comes in and takes that process and transforms it into the press of button. Basically just build/deployment automation. But the benefits to an org are vast for just a couple of months of the build engineers time. -Deploys much f…

Now that you say it, it is both something I always missed and would love to do.

Especially, if you work with Rails, deployment / release times can be really slow.

What about the operations aspect of the job? What is the state-of-the-art nowadays?

Re: How to avoid the software salary ceiling

#36
post #22
post #9

Earlier quoted context omitted.

Build / release engineering.

Could you elaborate, please?

Not the original person, but in any organization with a non trivial amount of code needs someone that is really on top of managing how the applications build and how dependencies mesh together. There's many tools to learn and leverage (in java you have ant/ivy, maven, gradle) and can easily take up a fairly large amount of time to organize. If done properly it can also prevent certain project failure.

Re: How to avoid the software salary ceiling

#38
post #25
post #21

Earlier quoted context omitted.

I agree with the general idea. You can remain a "simple" developer and still ask for more money if you specialize and bring significant value. I disagree with the idea that moving to a management position means that you get "unstuck", especially financially. To me, becoming a manager is pivoting or branching out, not specializing. And as I stated, a manager should not necessarily make more money than the people they…

> And as I stated, a manager should not necessarily make more money than the people they manage. "Should not" is very different than "does not". In reality, managers almost always make more

Agreed. Mostly because managers are in charge of hiring and they would not hire someone reporting to them and making more than them.

Re: How to avoid the software salary ceiling

#39
post #2

"Many people reach senior software engineer, and then they get stuck. They’ll still be a “senior” level developer 5 or 10 years later. For many, getting stuck is just fine. They like coding, and they don’t want to manage people, and the money is pretty good." I have a problem with this part. Basically, being a developer and not making it to a managing position is "getting stuck". I strongly disagree with that. Develo…

Regardless of salary numbers, becoming a manager is not a promotion. It is changing career tracks. It just so happens that the lowest rung on that ladder is somewhat reachable from the highest rung of the software ladder.

The problem in many companies is that the positions into which a senior developer may be promoted do not exist. Other positions with greater pay and prestige are on other career tracks. Positions like lead software developer, software architect, technical complexity organizer, software developer supreme (with tomato and sour cream), or historical catastrophe repetition avoider might not be available, or not available to internal hires.

They could exist. Several people here could probably argue a very convincing case for them. But they don't.

And the reason is because certain people still don't see business software resources as anything but costs to be managed down. Just yesterday, a member of my own household wanted to extract an image from a PDF, crop out the whitespace, and post it as a JPEG to a website. This non-technical person could have spent a whole day--or more--figuring this particular problem out. Having a technically knowledgeable person on hand shortened that time considerably. (I could have done it myself in seconds, but I didn't want to assume responsibility for doing that on demand for the rest of my life.)

The sad thing is that I got no credit for the time saved. I instead got grief for not being instantly helpful. I wasted someone else's time, because I didn't anticipate the need, so that SumatraPDF and Paint.NET or GIMP would be installed on their computer already. I wasted someone else's time because I didn't drop what I was doing immediately, so that they wouldn't have to wait for me to finish eating, or, horror of horrors, actually spend a few minutes to try to figure it out on their own.

That's the problem. The whole party complains, "Why didn't you just call on the Eagles again, Gandalf? We could have been done in three days!" And then when Radagast explains about the dearth of giant fish in the magical appropriations budget, no one listens to a word he says.

The people with control of the money don't quite seem to grasp that software is yet another product, among many, where you get what you pay for. No matter how magical it may seem, you have to put more money into it to get more value out of it. People get "stuck" at senior because too many companies have determined that threshold is as much software talent as they need, and that paying for more would be wasteful.

Re: How to avoid the software salary ceiling

#40

We should have a discussion about default SQL connectivity limits and the problems with using persistent connections. There seems to be a ripe opportunity to make something similar to Amazon RDS, except with automatic scaling. The current version of RDS presents the user with different instance sizes and doesn't automatically scale during high CPU loads.

I believe your comment is for https://news.ycombinator.com/item?id=9845820 ?
Post reply on HN