I'm sure I'll get downvoted for this one, but can we stop using the word engineer in the commercial software and startup sector entirely. It's mostly hacking, fucked up things that make you cry, turds smeared all over stuff, religious factions fighting over faith (marketing) arguments and embarrassing catwalk fashion show bullshit. None of that is engineering . I'm only here because for some insane fucked up reason,…
We don't have senior engineers anymore
61–70 of 127 posts
Re: We don't have senior engineers anymore
#62How the computer works, from electrons to transistors, to CPU, assembly, and high-level programming languages.
How the internet/network works, how you send some information from one computer to another, all OSI 7 Layers.
Engineers who fixate on this kind of detail are useless to most businesses most of the time.
If you structure everything on reducing, and value people only on their ability to reduce, everything to first principles of how electricity works then you're wasting everyone's time.
I want senior engineers to:
Be up to date but pragmatic about patterns and solutions Be able to, within minutes of being asked, map that knowledge to new business needs, explain that thinking across non-technical stakeholders through to junior devs Be able to lead and execute a plan with a level of pragmatism that reflects the fact that businesses aren't playgrounds for indulging in their own fixations
If they're more worried about NAND gates then not only are they failing in their duties, the industry has failed in providing meaningful abstractions so that smart people aren't bogged down in cruft.
Re: We don't have senior engineers anymore
#63Wait till they end up as staff or principal. Along with bad management they hollow out several hundred person orgs.
all titles except for the ones indicating executive or direct reports are meaningless. It is a game, where workers strife to be granted higher and higher titles, just because their peers and the industry does. There is no inherit requirements, I can start a company today and call everyone super duper staff engineer
Re: We don't have senior engineers anymore
#64How you learn doesn't matter -- the results you deliver do. This should be obvious in an engineering discipline. Physicists know better than to turn their noses at mechanical engineers for not studiously considering general relativity in their day to day work. Maybe the more computer science-oriented people in software should follow that example.
Re: We don't have senior engineers anymore
#65Any article that splits people into two groups and says one group cannot inherently be good at something immediately puts me off, sorry.
So you are saying there are those who split people into two groups and those two do not, and the first group is inherently bad at writing articles?
Re: We don't have senior engineers anymore
#66Earlier quoted context omitted.
all titles except for the ones indicating executive or direct reports are meaningless. It is a game, where workers strife to be granted higher and higher titles, just because their peers and the industry does. There is no inherit requirements, I can start a company today and call everyone super duper staff engineer
They're not meaningless. Someone can get a line management role and be terrible technically. In fact that's a good thing to do with someone who's not good technically.
Re: We don't have senior engineers anymore
#67Earlier quoted context omitted.
So you are saying there are those who split people into two groups and those two do not, and the first group is inherently bad at writing articles?
This is the flaw in having an entirely hateful view of splitting, that view is itself an example of splitting. You have to instead believe that there is a time where it is appropriate and useful to split (e.g, war) and times where it isn’t (general thinking)
Re: We don't have senior engineers anymore
#68Lets take the example provided by the author about `Solving a Problem`,
It is always possible, that the engineer fixing the bug might not have a lot of time to spend on it, or the fix does not need to cover all edge cases and a quick fix is good enough based on their own mental map. But to an outsider, it might seems as if the engineer has not taken ample time to `understand the root cause of the error, and which assumptions are wrong in their mental model`, which is a valid thought, but not necessarily true.
Re: We don't have senior engineers anymore
#69If there ever used to be "Senior Engineers", I wonder if it was because before there were so many fewer engineers and those who were engineers were the folks who were most interested in computers. Nowadays the field is lucrative and people do it for money, so the average dev is lower quality. Kind of like an eternal September situation.
So you've gone from a group of people that got into programming because it peaked their interest and their hobby became their occupation to a group of people who look at programming as a way to make a lot of money. I'm not saying these people aren't talented and don't enjoy what they do I just think they are coming from a different angle than us grey beards. I also think the real problem is figuring something out on your own is no longer a thing, if there's a problem you go straight to google for the answer and while efficient it screws with the learning process and it reduces new and novel ideas.
Re: We don't have senior engineers anymore
#70Earlier quoted context omitted.
So you are saying there are those who split people into two groups and those two do not, and the first group is inherently bad at writing articles?
This is the flaw in having an entirely hateful view of splitting, that view is itself an example of splitting. You have to instead believe that there is a time where it is appropriate and useful to split (e.g, war) and times where it isn’t (general thinking)