> If I do want to stick this out and turn this team around, I'm going to be working nights and weekends for at least a year - there's just too much to fix.
Is it worth though? For whom are you fixing the issues? For the coworkers who will leave while you're still refactoring? For the charismatic boss? Your own personal pride? Also, is the work worth your overtime? If they staff "idiots", do they deserve your free time on the weekend?
I applaud you for being able to care so much in what you describe is a terrible team.
> We’ve also introduced pruned module graphs in this release. Modules that specify go 1.17 or higher in their go.mod file will have their module graphs include only the immediate dependencies of other Go 1.17 modules, not their full transitive dependencies.
This is a very welcome change and make the go.mod much more obvious to understand. Hooray!
Maybe the Firefox devs will at some point have mercy and undo this change to the tab bar. Maybe they can sell it in version 95 as a "fresh new idea to improve usability".
We actually aim at education and training, the app is kind of a simplified OBS studio with features targeting the needs of educators, normally a session there last for quite some time, and theme can be very divers. Ads revenue is one of the thoughts we have.
Is it worth though? For whom are you fixing the issues? For the coworkers who will leave while you're still refactoring? For the charismatic boss? Your own personal pride? Also, is the work worth your overtime? If they staff "idiots", do they deserve your free time on the weekend?
I applaud you for being able to care so much in what you describe is a terrible team.