I think this situation would've happened regardless of advice vs permission. So it's not really talking directly towards the article, but yeah, bad actors are terrible to deal with especially when they hold power on like a PR review.
I think this situation would've happened regardless of advice vs permission. So it's not really talking directly towards the article, but yeah, bad actors are terrible to deal with especially when they hold power on like a PR review.
It's much nicer to deal with overly enthusiastic junior developers that want to rewrite one out of the company's 30 typescript microservices in rust (because they read somewhere it's cool).
In my experience, it's much worse to deal with enthusiastic juniors.
Another especially bad take coming from the same company is 'move fast and break things', which is one of the most destructive pieces of advice in our industry.
We got Boeing software defects costing lives, SolarWind pwnages, the npm crashes, we got the Cloudstrike fiasco, Tesla self driving bugs, and who knows how many failures of software engineering. And we, the software engineers wanna be moving faster and breaking things? What happened to writing correct and reliable programs?
We want to somehow pretend we live in a world where junior devs' ideas are some hot takes that nobody has ever thought of before and encourage them to do things first and ask their team later? You guys do you, then.
Nobody suggested that. And nobody suggested using junior devs' code in critical components.
But I would much rather work with people who want to learn and aren't afraid to change things than old farts who prevent any improvement with the excuse that there's a non-zero chance that it will temporarily break something. It's so tedious.
The whole idea that juniors are somehow the people who know what improvements need to be made, and the seniors are the gatekeepers stopping them, is hilarious.
Juniors:
- don't know the domain
- juniors don't know why the existing ecosystem is how it is
- juniors probably can't even ascertain as good as a senior whether there is really a problem that actually needs solving
- hell, juniors don't even know half the capabilities of the language/framework/infrastructure you are using
Imagine that you are a teacher in school, and you find that somebody wrote a book "Whatever your teacher says, don't listen, just do what you feel like" and is actively pushing it to your students. That's what this BS "Ask advice, not permission" advice does to junior developers.
> It's so tedious.
It's tedious to have 3 junior engineers in a typescript/react shop, each from a different team, one wanting to rewrite everything in rust, one wanting to switch to deno, and one wanting to rewrite everything in vue, while there is no actual problem to solve.
This is a real situation that happened to somebody I know. And he, the senior, was the old fart, gatekeeping the great and always-learning juniors from all that potential rust greatness.
What if I come to your team and want to rewrite everything you have in Lua, and then complain when you "gatekeep" me?
There is seniority in software engineering, and in companies in general, so somebody can stop stupid ideas from proliferating and occupying the whole company's time. Sure, there is a problem of bureaucratic middle management that doesn't allow good ideas to come to fruition, but to not acknowledge that a huge percentage of ideas coming from juniors belong to the waste bin, that's just pure hypocrisy.
> What if I come to your team and want to rewrite everything you have in Lua, and then complain when you "gatekeep" me?
I would say "what's the benefit of that?" and if you can convince me then I would let you try rewriting part of it as an experiment. No gatekeeping.
But no junior devs I've worked with have suggested anything like that anyway.
And I'd say:
"There's no other scripting language that makes it as easy to add scripting abilities to native applications.
It is lightweight, simple, easy to learn, and not that hard to master. You can use it for anything: as a substitute for ini or json files, or to code entire games in it. Just like JS, just easier to embed and easier to use.
LuaJIT, in the hands of a skilled programmer, is a marvel when it comes to performance."
(Taken from reddit, by the way)
At the end, we'd go over some things that are probably not okay in typescript and Lua does better, but we'd be missing the point. The whole idea that it's not worth to rewrite whole systems in Lua just because you don't like some syntactic sugar's absence in typescript is totally lost on a junior dev. You can convince them, of course, but probably not to a full extent, and you'd still be considered a gatekeeper.
> and if you can convince me then I would let you try rewriting part of it as an experiment
What's wrong with a straight up opinion and saying: "this is probably not a good idea, considering we have 30 repositories, all using typescript, and no in-house knowledge of Lua"? Why do we have to endlessly coddle people and mislead them?
Imagine this scenario: somebody asking you to do something ludicrous and you enabling them, multiplied by the number of junior developers you have, month after month, busy with new experiments. Eventually, you'd have to allow some of these proofs of concepts into the codebase, or they’ll realize you’re just leading them on, right? Congratulations, your 30 repo react/typescript codebase is now 15 different versions of react, vue and angular, Lua, python and rust rewrites, and they are deployed (or are they) randomly on all your major cloud providers.
This is how, by being afraid to assert authority and not wanting to appear as a “gatekeeper,” you end up on a slippery slope, allowing junior developers to do whatever they want and dragging the quality of the codebase and the velocity of your team with it. How many competing experiments can your teams juggle?
If the junior devs want to learn, they should do so on existing systems, trying to understand and improve them, rather than we all pretending they are god's gift to humanity and giving them entire systems to develop from scratch and wasting months of work on experimentation.
You are doing the junior devs a disservice by leading them on like this, imo it's much better to coach them why existing systems are how they are, and help them improve along the way.
I’m not sure about moving fast in a safe environment. In general it might be good for the individual devs to have initiative. A safety critical code requires a safe process, which should not rely too much on the prudence of an individual developer. Have really good devs is not a plan, right?
But I didn't want to be the guy who "once the project was about to be deployed they suddenly became very opinionated and critical of each and every tiny detail". (Even now I remember how annoying that guy felt when I was a junior dev!) So I let it go forwards with too little scrutiny of what might go wrong. Now I hope I've learned my lesson, and insist on doing things safely even if it might make me seem annoying or obstructive in the moment.
I'm not sure you have learned the right lesson - you already admitted that you let the change go forward, so it isn't a case of junior vs senior. You both made a mistake.
The correct lesson to draw from something like that is that you didn't have enough systems in place to prevent a mistake.
If that doesn't suit your character, as it can be, than you can discuss with your team how to come up with a better process. Perhaps someone else has no problem with that, or you rotate the responsibility, etc.
New lesson learned: They don't like you questioning everything and being super thorough either. And no matter how politely[1] you say it, they think you're difficult to work with too. The decision to rewrite, or do something a certain way was made by someone that is "in the decision room", and they'll play along with you for a while, but you best eventually acquiesce to the way they want it done.
Being a bit more meta about it: I'd say the real problem is that the tech field has ridiculous levels of "flat hierarchy". In this case it means that simultaneous everyone and no one has a say in any one particular decision. And even if there is a title for whatever responsibility or area you are to have final say in, there is always the room for suggestion and criticism, which means you have to "consider it". Thus opening the flood gates of all this non-sense.
[1]. I don't even know the word to use here. Politely doesn't do it justice to how much I have to bend over backwards to be considerate, calm, and appreciative of everyone.
Can be a cultural thing. Here in the Netherlands, it's expected that you give honest feedback. In other cultures Dutch people are known to be blunt or impolite because of this trait.
In general you can ask beforehand; "Would you like some feedback on your proposal? I have some thoughts about it I'd like to share".
> Thus opening the flood gates of all this non-sense.
Am I misunderstanding you? It seems here you call suggestions and criticism non-sense. Where earlier you say that when you give suggestions and criticism, you hate it when it's viewed as non-sense.
I'd say that if there is so much negativity regarding feedback, you need a process to structure it. This at the very least stops it from 'hanging in the air' all the time.
Sounds like they're right. That attitude is difficult to work with.
> no assumption unquestioned
That's just unhelpful and a hindrance. Assumptions are good! They are huge time savers. Occasionally they are wrong and that can lead to bad things but questioning every assumption is just pointless and going to piss everyone off.
People have told you you're difficult to work with, and you can't really argue with that anymore than you can argue with someone saying they don't like you. You can't say "yes you do!".
> there is always the room for suggestion and criticism, which means you have to "consider it".
Erm yeah! Why would you not want to consider people's suggestions?
Maybe instead of complaining about people finding you difficult to work with you could try and change your attitude so that they don't?
> Erm yeah! Why would you not want to consider people's suggestions?
This was in the context of a lack of definitive authority and a flat-hierarchy. People that work with me know I genuinely consider everyone's opinion, and everyone always gets a clean slate with me.
I've picked a strategy at times where I will say that something is a bad idea for the reasons X, Y and Z, and then when they still want to go on with it, I'll let them, so it would be possible to win some trust with them so I don't have to spend so much energy again on explaining why something should not be done. I will refrain from "I told you so", hoping that it allows to build some confidence to move on quicker next time.
But then at some point people rotate and I have to start building that trust all over again.
I guess with other engineers I just hate it when someone is really enthusiastic about something and I think the idea is truly impractical and will do more harm than good. I have to kind of find a way to direct them to do something else without hurting the enthusiasm.
If you made things clearer for both of you, you can feel good about what you did. You helped the other person make better choices. Now this still can be something different than your choice. But if it's their responsibility, then that's fine.
In situations where I don't agree with my boss or colleague I focus on two parts:
First; do we fully understand each other? Are we aiming for the same thing, and do we agree that X, Y, Z are risks? Are there other aspects you perhaps didn't know that are important for the other to weigh, etc.
Second; what is the earliest we can test who's right on the important part where we differ. You can suggest a short brainstorm for a proof of concept, etc.
I would actually rather not work on something like this, but it pays more than anything else I could currently get.
I don't think so. If you have a process in place where everyone can and should be heard during the design process and once the design is approved it is owned by everyone and everyone is obligated to fully commit to it, you prevent the sociopaths within your ranks from weaseling out and throw anyone under the bus. You eliminate the motivation to steer people in your team down a bad path to afterwards portray yourself as the only sane, competent guy in the ranks, because you have to explicitly sign off on the project. Once you sign off on the project, any extraordinary miraculous epiphany that happens after the fact is something that you must be held liable for, because it becomes obvious that you were never acting on behalf of the team's best interests. Therefore this sociopath move is no longer something that benefits you, and so the perverse incentives to screw over your team members is no longer there.