As well as a reminder for those not good at staying on task, it sounds worth considering for those who spend their day satisfying constant small ad hoc requests who later get asked "What have you been doing all day?"
Hopefully it has a "same as last time" button, I doubt this has the same cognitive distraction level as fielding a question from a colleague as well. I.e. understand their question, think of the context, etc etc
I think there's often a leeway given to the full stack dev that they have strengths and limitations. I haven't got to the point where I could compete with the true / good front end dev with my skills.
Even at the backend you have the application backend (c# or whatever) and then sql/rdbms. If you are that good perhaps you deserve thrice the pay by this logic ;).
Jokes aside, at the last good company I worked for where I knew other people's pay, I was compensated for the entirety of my skills compared to the good front end dev. We earned the same, and I was quite happy with that.
Bear in mind the tutorial is prefixed "Relearn..."
Though I'd class myself as a "full stack developer" css for a long time was the 2nd class citizen, with most of my time spent on learning to use front end frameworks in their idiomatic way, the "it depends" peculiarities of SQL and RDBMSs and making inroads on the vast tomb that represents architectuliary sound back ends.
So an article focussed on improving my "it's only css but it works" knowledge is one of the best things I've seen on HN in quite some time :)
This could put off anyone who thinks they could be acquired by such companies from using your software as well. How can anyone know who is going to make it onto the blacklist for the next version etc. Seems quite the can of worms.
"At some point, I bet someone in a design meeting said "Hey, I think this might compromise security, can we study that before implementing it?"
And the decision to implement it without that study, or despite it, was made."
Because we should assume all your past missteps were due to willful negligence? Yeah, let's not just start making shit up to support the group think outrage.
Not so much being a bad participant, but something I've found are developers who propose a solution to a problem outside of a meeting, but when it's then thrown out to the group for suggestions they remain quiet. Hard to know what advice to give for building confidence.