You are viewing a single thread.
View all comments
104 points
*

Funny enough, I probably did more software engineering as a web dev than I did as a software engineer at some companies.

In the UK, at least, the only difference typically between a web developer and a software engineer is £15-20k in salary. Frankly, we’re all software engineers…

permalink
report
reply
12 points

What are dev/engineer salaries like in the UK? Been considering places to move to…

permalink
report
parent
reply
24 points
*

About half of the equivalent in the US, often less. It’s exceedingly rare to make 100k here even in a senior position, although it does exist. Median is 40-50k (pounds, so times that by 1.2 for USD).

permalink
report
parent
reply
4 points

Holy crap. That’d be a pretty substantial cut for me, but I guess that said, is the COL a lot less?

permalink
report
parent
reply
2 points

You made that as a senior software dev in Finance more than a decade ago, more now (mainly because the pound went down versus other main currencies), especially if you’re working in the Front Office (i.e. directly with business, such as Traders and Analysts)

However breaking into Front Office IT in Finance without previous experience in your CV working in banking or similar is pretty though.

permalink
report
parent
reply
6 points
*

Varies heavily dependent on industry, but typically less than US devs. Also if you live outside London it’s going to be a lot less.

You average non-junior dev will probably make about 50-60k £ in london but about 25-35k £ outside london.

Senior developer can vary heavily. in london I’ve seen 60-120k depending on language and industry.

permalink
report
parent
reply
3 points

Wait so it’s possible a Senior Dev outside of London would make $35k??

permalink
report
parent
reply
1 point

Holy shit, that’s nothing outside of London. At that point be a restaurant server.

One thing in the US that has been encouraging is the very lowest earners are getting big jumps in pay, while people like devs are stagnating

permalink
report
parent
reply
-19 points

I still wouldn’t say software engineering is actual engineering.

permalink
report
parent
reply
26 points

You mean you wouldn’t expect a software engineer to understand the coefficient of thermal expansion of tungsten carbide in a gas lubricated piston/cylinder pneumatic deadweight calibration system?

Yeah, me either. But I would expect one to know how to research the documentation to find out what it meant.

permalink
report
parent
reply
5 points

Even though my job title has “engineer” in it, I don’t agree that it should be considered an area of engineering.

Yeah, me either. But I would expect one to know how to research the documentation to find out what it meant.

I wouldn’t even expect most of them to this kind of research, no. On top of that, I see “engineering” also carrying some type of accountability and responsibility. For example, civil engineering, there are often regulatory bodies, codes, and standards that engineers must adhere to, and they are legally responsible for the safety and integrity of their projects. While in the software side of things, standards and best practices are more loose. Unless you’re working in safety critical industries (automotive, aviation, etc…), the “accountability structure” is completely different, if existent at all. Calling themselves Software developer or some derivate would make much more from my point of view.

permalink
report
parent
reply
11 points

And software development isn’t actually development. They don’t build houses!

permalink
report
parent
reply
3 points

Did you mean to say software architecture?

permalink
report
parent
reply
8 points

I think the idea is, most people could build a doghouse with no training, but you need planning and education to plan/build a skyscraper. If you want to write your own app at home, maybe no software planning is really required. Keep nailing in workarounds. But if you want to build a huge system, you need to do a bit more than workarounds. You need a good plan from the start to make it all efficient and in a manner others can contribute to the code base.

That said, I feel like just having workarounds is really common even in large industry settings. Maybe I’m wrong though. I’m more of a home doghouse builder type myself.

permalink
report
parent
reply
6 points

Anyone can build a bridge. Only an engineer can build a bridge that barely stands.

In the same way, the fact that one built a large online platform, that doesn’t necessarily mean it was built with minimal ressources and without taking past or future risk.

Engineering is, as a profession, specifically the application of scientific principles to solve problems the right way, the first time, that is to say efficiently, and with minimal risk.

The fact that one codes, or wields a wrench, or operates a C&C machine does not mean one is applying science to solve problems efficiently and managing risk. These are entirely different skills and professions.

permalink
report
parent
reply
3 points

Why? Excited to hear another internet hot take

permalink
report
parent
reply

Programmer Humor

!programmer_humor@programming.dev

Create post

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

  • Keep content in english
  • No advertisements
  • Posts must be related to programming or programmer topics

Community stats

  • 3.4K

    Monthly active users

  • 1K

    Posts

  • 38K

    Comments