▲ | esafak 10 hours ago | ||||||||||||||||||||||||||||||||||||||||||||||||||||
No-one is going to spend $8K out of pocket to A/B test this on themselves. Of all the things you could be doing to improve your productivity, this is some high hanging fruit. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
▲ | Veserv 9 hours ago | parent [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
If you have a US employer who is unwilling to spend 8 k$ on software engineering productivity then they are pennywise, pound foolish. It literally costs 10x that for a single junior engineer. And, as I pointed out, the net productivity improvement you need to see to justify that expense is miniscule. If your employer really is skeptical, then they can run a A/B test over a small group of engineers to prove out changes in productivity. But not even being willing to run that test when it is so cheap is just management incompetence. Engineers are ridiculously expensive. In electrical engineering, where the engineers are generally less well-paid than in software, employers routinely spend multiple hundreds of thousands of dollars per engineer per year in tooling. Not being willing to spend 8 k$ on a test of well known technology and attempting to identify mere single digit percentage improvements is just stupid. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|