"Isn't this just a Boolean flag? If X else y?"
I've saved a great many man months by doing just this. Sometimes work just vanishes. And it's not just the juniors that do it, sometimes the senior / tech lead types just miss a crucial point to make the solution trivial.
But juniors are often used to wanting to make work, rather than solve a problem.
1. Do nothing, bad state remains 2. Surgically restore to world before bad state 3. Remove all bad state (even if it wasn't caused by the incident)
I'm omitting some details, but I think this strategy can be effective.
How configurable should X be? We have one customer who wants it to be configured like this. All other customers want it configured like that.
We can make X maximally configurable which would allow future customers to have a custom setup - how likely is that?
If it's not likely, here's an alternative...
I could be way off base here, but I'd bet a lot of junior devs are just trying to stand out. They want respect, raises, promotions, and new job offers. Invisible good solutions don't bring those.
solutions are only invisible due to a lack of sufficient documentation and communication.
boring solutions are part of the job. they can be fun if the goal is shifted from implementing to automating.
none of this to say you are wrong, but a junior dev that succeeds at such peacocking efforts is signaling the poor health of their surrounding team as much as their eagerness to impress. where was the manager or senior dev to say “great! have you considered a boolean?”
Yup. And that by definition is a junior colleague ;)
That's genius. I'm going to borrow (read: steal) that.
Even then, I find it increasingly hard to argue people out of the nonsense they pick up on blogs and conferences.
Especially for newer techniques that are not yet proven to be inefficient, such as using micro services in the wrong context, one has to resort to arguments by authority. Some junior and senior devs are not very susceptible to that.
For areas such as web development for user interfaces, or taking in enormous dependency trees with package managers, the problem is even worse. Here, an entire industry had standardised on suboptimal methods. One can argue that this is wrong, but there is no viable alternative.
In the latter case, guiding only one junior developer does not improve things. One has to educate the entire industry.
Thanks for this bit. As I gain more experience, I grow less and less patient with many blogs and conference talks. Often authors are just very excited about a topic, and my general impression is that they tend to propose ideas that are not seriously battle-tested in production.
Just also make sure from time to time that you’re on the same side. Don’t hesitate to laugh at your own mistakes openly. Sprinkle in some sympathetic, honest remarks. Target the thing, the mistakes, never the person.
Bottom line: laugh together at the expense of human fallibility and not a particular person.
Of course, the deployment team would have to be informed about this change, so some documentation was required as well, but that was exactly the part of the process where most effort was saved.
Note that all this was used for a system that would be deployed only at one customer, and the feature would always be on. Yes, a boolean flag would have been a better solution for this.
My cynicism is probably not the best approach to change the world for the better, so any hint on how to teach younger colleagues to stop snacking micro service candy is much appreciated.