There is a great little book - Daily Rituals [0] - that goes into many artists' and scientists' daily habits. The habits are very much along the same lines as your thought - they are workflows for how the individual tends to think best.
I'd love to see someone put together a website or book that did that in the context of software engineers' workflows. Does someone know if a resource like that already exists?
[0] https://www.goodreads.com/book/show/15799151-daily-rituals
-edited for grammar.
How did you juggle acquiring skills for both roles? Also, where there times you had to struggle between the two mindsets on a task?
I get your complaint; my father is a fully qualified and slightly/weirdly eminent electronics engineer (and IEEE member), so from a young age I've been made aware of the sanctity of the term in that context.
But the term has been used in other contexts for a long time, and most people understand the distinction.
It's not a hill worth dying on. Best save your energy for more important battles.
Furthermore, tons of experienced working engineers outside of software don't have PEs. They're just not needed in a lot of contexts.
Edit: I'm referring mostly to the US. Licensing bodies in some places (perhaps including some US states) may say that only licensed engineers can be called/are engineers although the degree to which such strictures are followed will almost certainly vary. (I was told this was the case in Texas but there's no shortage of people in Texas who call themselves engineers but aren't PEs.)
Why should they get to do that? What do they know that I don’t?
I have a Master of Engineering degree but I’m not chartered - I’m still going to call myself an engineer no matter what anyone else thinks about it.
> You don't call yourself admiral right?
Because I’m not commanding a fleet. If I ever came to command a fleet I’d start calling myself admiral and as long as I’m actually doing that it’d be fine. If you’re doing engineering then you’re an engineer. Some of the best software engineers in the world have no professional qualification.
However, if I were to start practicing medicine in anything other than a first aid context or if I were to mislead people into thinking I was a certified medical professional, that's not allowed legally.
By contrast, while PEs are required especially for signing off on certain documents in civil engineering, there is not in general any requirement to have one to practice engineering in the general case. In fact, there's no requirement for an undergraduate degree.
> just anybody can call themselves engineer?
> It's not about titles.
It was about titles!
What you cant do is profess capital ‘E’ engineering work without running afoul of the law. That’s akin to practicing medicine without aboard certification, even if you claim to be a doctor because that’s what your degree says.
Degrees and licensed are related, but different in terms of the profession.
I honestly think that software "engineers" should be legally liable for the lives at stake though.
I'm not an accredited engineer, so I feel I have no right to the title.
It really annoys me that some manages at work call themselves Release Train Engineers.
Generally I think an engineer as someone that does design. Key part of that is some sort of analysis. That can be ad hoc, standards based, or formal.
Most of the time software feels like craft to me not engineering. Otherwise I'm more on the side that a license an engineer doesn't make. There are engineers without degrees designing and there are fat fuck PE's that just sign their name over and over for $300/hr.
[1] https://www.nspe.org/resources/pe-magazine/may-2018/ncees-en...
Added: So, basically the grandparent registered on HN so they could leave comments about how people without PEs shouldn't be allowed to call themselves engineers.
Shout out to the people that don't really bother because they're good enough to adapt to any setup. :)
There are two issues here:
a) Designers trying to simplify everything beyond usefulness is a good instinct gone haywire. Simplification helps, but without an understanding of accidental complexity versus essential complexity, one is bound to end up painted into a corner with no flexibility left in the app. Few designers understand this, and those who do got it the long way round — by working on products that have a lot of essential complexity, like AdWords, and by repeatedly fighting those battles
b) An engineer's operating environment, OS, IDE, shell, terminal, is a reflection of the inside of his or her mind writ large. Like every Jedi has to build their own lightsaber, every engineer has to go through this pain of building out their weapon, because one's workflow is how one thinks, how you look at the problems at hand. No UI designer can help with that.
[0] (Because it's relevant to the context: ex-Google, ex-Facebook as professional experience)