This is a computer made for the engineers who’ve already “made it,” who are making that $500k a year and are looking for a Porsche over a Corvette.
This is a computer made for the engineers who’ve already “made it,” who are making that $500k a year and are looking for a Porsche over a Corvette.
I don't even want a 1TB SSD in it, the 256 is perfect to hold the OS, a few DAWs, and all the plugins I could ever want. Everything else gets saved to drives in a toaster anyway. A rackmountable unit with a ton of PCI slots for HDX/Dante cards was on my Christmas list, and I'm not alone- there's a reason they made a point of showing how many HDX cards it can fit in their presentation.
It also looks like an amazing workstation for video editors. I really don't think it's designed for software engineers who make 500k a year.
Alternatively, forget hotswap and use a Thunderbolt DAS with RAID6. Burn your projects from your DAS to a portable SSD when you want to pass them over. Only takes a minute or two.
"A good craftsman doesn't blame his tools" isn't a warning against complaining. It's a warning about picking bad tools in the first place and scapegoating them instead of accepting that it was your decision all along.
What reason should I have for trusting anonymous self-reported data in a category where people are known to exaggerate?
[1]: https://theblog.okcupid.com/the-big-lies-people-tell-in-onli...
Maybe some people are lying, but that seems about right to me for actual senior people (leading projects, maybe managing people).
My last year at Google, my W2 income was in the area of $300,000. I was a "level 5" with good performance reviews, and the scale goes up to 9. I sold all my stock the second it was issued ("autosale"), so the W2 income is pretty close to the amount of cash I got.
Programmers focused on the right task are worth their weight in gold. There are very few fields where an hour of time put in can save society as a whole thousands of hours. Software engineering is one of those, and we get to skim off a little bit of that value we created in the form of cash.
I don’t know why people are like that, but anonymity thins out the middle group of semi-/socially-truthful people by providing an opportunity to be much more honest or much less honest than is normally possible.
$500k is achievable total compensation at a few companies for some people, though.
Is this what "Pro" means now?
What about an EV such as a Tesla?
Instead I took umbrage with the idea that a $3000 laptop which is our primary tool is a luxury item. I think it's one of many signs that we're a bunch of cheapskates. Other industries have different perspectives on this.
From an overall productivity standpoint, because the biggest bottleneck to programmer productivity is mental and physical health, data would imply that I should spend more on exercise equipment, a better chair that keeps me from getting injured than on a laptop that gets maybe another 10% faster compile of already less than 30 seconds (incremental compilation anyone?) for the $1k difference between a 15" Macbook Pro and a 13" Macbook Air. No amount of money I dump into any hardware or software will make AWS provision its resources everything faster either, and that's what I sit and wait on the most for feedback rather than direct code compiles. And a fat CI / CD server is not run on my laptop unless I'm running Jenkins locally or Concourse.
So if you couldn't get anything out of a better tool, I'd start asking uncomfortable questions about you.
Do I think I as a developer could leverage a Mac Pro to speed up my code-build-test cycle? If the whole team had them, then I'd absolutely tune our tools to use the extra cores, monitors, etc. We are better at troubleshooting when the feedback loop is shorter.
But to me the Mac Pro is more of a tool for designers. If a designer is turning in the same work on a 1k machine I would ask about our process first, the designer second, and the tool third.
On a serious note: why doesn't Apple do any modern container/virtualization?
For example, why can't you set up containers for different versions of xcode and build your code in the appropriate one? or farm it out?