1
I read an article recently (can't find it at the moment) around how story points can be improperly used as a measure of time which turns into a way of non-technical leadership imposing unrealistic timelines upon engineers.
It's a story as old as the industry itself: non-technical management not fully understanding the nature of the work at hand, which leads to distrust, overly-optimistic estimates, and burn out.
How should story points and velocity be used? How do you deal with this aspect of agile development with your leadership? Book recommendations?
I've primarily used Macs as a data engineer, but recently switched to Windows since that is what the rest of my team uses at my current job. The company I work for does support macs, but it is a small percentage of engineers.
I know this is a very nuanced conversation. In an ideal world, you should be able to choose which ever OS works best for you.
That said, I've typically taken the approach of "use whichever OS the rest of the team is using" since it isn't worth the battle of rewriting all the team-specific setup scripts for your given tech stack and development OS.
I wouldn't say Windows has been a "terrible" experience thanks to WSL2, but it has prevented me from using my standard suite of tools (clipboard manager, note taking app, etc.) that I am used to using.
I'll likely prioritize macOS over Windows going forward in my career due to my most recent experience but wouldn't go as far as calling it a dealbreaker.
I should probably reiterate: my goal of this post is to discuss "is primary OS a deal breaker for you" and not "which OS is the best."