Over a million developers have joined DZone.

Are You an Engineer or a Developer?

DZone's Guide to

Are You an Engineer or a Developer?

What's the difference between an engineer and a developer? According to Tim Spann, it has a lot to do with how people in these two positions deal with projects.

· Agile Zone ·
Free Resource

Adopting a DevOps practice starts with understanding where you are in the implementation journey. Download the DevOps Transformation Roadmap. Brought to you in partnership with Techtown.

Did you know that software engineers make $13,000 per year more than software developers on average? It’s even more than that (a $22,000 difference) in California.

Same job, right? You build software. Get some specs, build some software, make it work. But the market clearly believes there’s a difference.

It took 18 months, but I think I finally understand the difference. There’s a binary question you can answer to see if you’re a software engineer or a software developer.

Let’s roleplay!

Manager Bob: Our business has a problem. We spend a lot of money on acquiring users, but they drop out of onboarding before their ah-ha moment. We’ve identified three drop-off points where we lose 50% of our users. Our design and product people came up with a new onboarding flow that aims to fix this problem. It took weeks to design, and we think it’s really good.

You: Uh-oh.

Manager Bob: We tried to reuse old components as much as possible, but the overall onboarding experience is completely new. We also changed some business processes to facilitate these improvements and get rid of unnecessary steps. That might have implications beyond onboarding.

You: Oh yeah, it definitely will. How did you reuse components exactly?

Manager Bob: We used the same semantics as before and tweaked the design to fit our new flow. That’s not hard to build, is it? To be honest, you’ll just have to figure it out anyway. This needs to happen. We can’t keep wasting ad spend like this.

You: Right, yeah. No, we can’t.

Manager Bob: How can we get this out as soon as possible?

I have yet to meet a coder-at-heart who wouldn’t break a sweat in this situation. My initial reaction is always something like “You want to do what? Holy sh*t.”

You get an amorphous blob of a project. What you do next defines you as an engineer or a developer. If you can take the amorphous blob and turn it into:

  • Action steps
  • Sub-projects
  • A staggered delivery plan (perhaps)
  • Opportunities for work in parallel
  • A clear Thing To Do First
  • A well-defined Thing That Says You’re Done

…then you are an engineer. If somebody else has to do that, then you’re a developer.

Or maybe the difference lies in the size of that amorphous blob you can begin with.

P.S. - This is what an engineer looks like per Wikipedia. It’s a shame that software engineers don’t get slide rules.

You should follow me on twitter here.

Leave your email and over the next few weeks, I will send you the best material I've written since 2010.

Take Agile to the next level with DevOps. Learn practical tools and techniques in the three-day DevOps Implementation Boot Camp. Brought to you in partnership with Techtown.

software engineers ,work ,engineers ,software developers ,experience ,points

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}