When you're torn between 'Software Engineer' and 'Software Developer', just remember: Titles are just syntax, it's the logic of your passion and skills that truly compiles.

Of course, in practice these terms are used interchangeably more often than not.

I’ve never known these labels to be anything but interchangeable. My best guess at an answer is: an excuse to write a blog post.

There's absolutely no meaningful, practical, distinction between those terms pretty much anywhere in the world.

In Germany, the term "Engineer" is protected by law. You need an Informatics (or some other engineery field) university degree to call yourself one. There are many IT professionals that do not have one, but have one of the state-approved 3-year apprenticeships instead, and can not call themselves engineers.

What's seperates an engineer is:

1) Problem identification. They don't simple problem solve. They solve the right problems.

2) Intentional. An engineer is intentional about decisions about and implementation of solutions. Below the engineering level solitions are random or simply the first thing that comes to mind.

3) Humility. Paraphrasing and supplementing a comment in another HN thread (about junior devs): "Dunning Kruger as a spectrum within engineering. The less self awareness the dev has, the more jr they are." Engineers understand they have blindspots, and what those blindspots are.

4) What is vs what will be. Engineers understand there is a future and that biz needs can and do evolve. Budget might restrict them from a more future-proof solution but they are at least aware it will happen. Devs are far more short sighted about such things.