Ohh I had a similar experience with a quite big open source project (~10k stars on GitHub). Posted an issue, it’s obscure enough even the lead maintainer comes in to help and still got stuck unable to fix the issue.
Ohh I had a similar experience with a quite big open source project (~10k stars on GitHub). Posted an issue, it’s obscure enough even the lead maintainer comes in to help and still got stuck unable to fix the issue.
If you’re competent, a SM is invaluable, however it’s one of the easiest to replace role. As an example, almost all of the engineers in my division has a PSM I certification. So all the SM do is just facilitate meetings. When we started we have around 5 SMs but currently only have 1 because all of the SMs are redundant since the team already know how scrum works.
Teams are just shit like that. Although my company has migrated to 365 for our work apps, the team’s main communication is still Slack. With Slack I’m still able to find old messages easily and be able to link it in relevant context.
It’s bad if you don’t have a design system. If you have a design system it’s :chef’s kiss:
TBH compared to the old versioning system people used to use like SVN and Mercurial. Git is a godsend. Just taking your time in learning and not using a GUI client works wonders in learning how it works. Especially when all the GUI clients are basically a collection of commands being executed so if you fuck things up on CLI you know what happened vs using GUI.
If your work is bleeding edge enough, even ChatGPT won’t be of help since it’s not in their training dataset.