@_SamWilsn_@MicahZoltu Native targets and JavaScript, too. The multiplatform targets (with common codebases in the overlap and platform-agnostic interfaces), relatively elegant multithreading with coroutines, and the fact that it drove Java out of complacency are worth a tier. :)
@mikkopiippo This is a privileged view, to be certain, but I prefer when that's not strictly a career decision. I was lucky to be able to study philosophy, already having tech skills. Doing so made me a better thinker and enhanced my love of data, dev patterns and careful reasoning.
@tgwilson DSM 5 has loose enough diagnostic criteria for that to point to a great many things. DSM 6 should have one for obsessive patch compulsion. Key criteria include this and how many Git branches one has with varying attempts to optimally resolve Node dependencies.
@SimoAhava@ReaktorNow Much yes. Leadership jobs are mostly roles in service of those you lead. (And that mindset benefits the organization far more than short-term thinking about service to the org itself. Organizations are organized people.)
@mikkopiippo There's enough data out there that is and can be collected respectfully to not bother with this, even if you figured out some iron-clad justification for it.
Quality is an aspect of culture that must infuse the organization. Standardized mandated process wont get you that. You need people at the top who instill a culture of quality. It ultimately comes down to personal values. Teams can realize quality in ways that make sense to them.
next time you are about to explain something to someone who knows more about it than you, try taking a cue from the whales and not speaking for your entire life