Since that's impossible, we simulate this by a network of nodes (humans) linked using a very low bandwidth communications channel (speech and it's representations). Each node has finite capacity and can only bear in mind a certain number of considerations. There are a number of well known failure modes. For example:
One node is delegated a decision affecting matters they don't understand (HR person has to buy computers for Devs)
To render the financial situation comprehensible to central nodes, it is simplified by binning costs into budgets. For example, HR budget pays for laptops, engineering budget pays Dev salaries. Decisions are made to optimize each budget separately, so HR budget is optimised by buying cheap laptops, without reference to the fact that this makes engineering less efficient.
For instance, some developers have a 40 minute build process. You'd imagine that if you spent a week making that 40 minute build process a 10 minute build process you could get that time back in a few weeks.
The first response you might get if you bring the issue up is that we only work on tickets that have a direct benefit to the customer. If you stop for a moment to be articulate about it you can say "the customer wants to get features more quickly" and "we can cut three months off the schedule by speeding up the build process."
That's an argument that people will listen to.
Say you get paid $100,000 a year. Something that makes you 10% more productive saves $10,000 a year. $2000 of hardware pays for itself in about two months!
You can go from "talk to the hand" to getting what you want if you can explain just what a good investment better hardware is for the business.
The CFO/CTO is looking at the macro picture. You are a subset of that organization. If your engineering director wants more powerful laptops, it should be up to him or her to work through the CFO/CTO to do it.
Also some companies have a policy where the less the executives spend, the more money they get in bonuses. It's effective for management, but it sucks for you.
Edited to add:
Increased performance is a "soft" metric, in that it's hard to quantify. Costs are a "hard" metric, in that it's easy to quantify. Which do you think the CFO is going to look at when making a business decision?
Fury. Rage. Tempest. The sound of my soul dying. Where's the fucking grenade?
Forgive me for being so complicit. $100/hr was a lot of money then.
Watching those poor coders clicking around and typing was just painful. Multiple seconds to respond to any input.
Madness.
Where I work now, we do issue developers better laptops than the usual we give out, however they are all the same make and model with no one offs.
It makes keeping track of equipment and inventory easier, and if ever someone needs a new one we just load up one with a pre-built image we made with all the programs and settings pre-installed, and its good to go with little hassle. My guess is other companies have similar reasons, except maybe they want a standard laptop model used by all employees who need one, regardless of role. Sometimes its because an IT department may have only a shoestring budget to work off of due to execs wanting to save money.
It doesn't make sense to save 0.2-1.0% of the fully loaded cost of a developer. Just making them happy and reducing churn by a tiny amount would more than pay for itself.
Not arguing that's enough, but it is probably better than the average customer laptop. So if you do get a much higher-end machine, it's worth making sure the app runs okay on something less capable than that.
As I said many times over here: If you have a terrible manager/lead, if you are drowned in useless time consuming scrum rituals and can't get work done, if you are asked to work more hours you're paid for, if you're not happy with your salary or anything similar to this and you can't see this changing in the short term, just find a new job. If you already have a job as a developer it will take you almost no time to find something else.
Right, your next company might have some of these problems as well. F*ck them too and keep searching until you find something you like. There are a LOT of great companies to work for out there, but it takes time and research effort to find them.
I've left companies just after 2 months because I've given crappy laptops and forced to use tools (such as local editors as crazy as "Scite") because the CTO was a fanboi of it.
I've left companies after 2 or 3 months because they were scrumb-by-the-book extremist who didn't had a clue what they were doing but scrum was good because the book the PM read said so.
I've left companies because after 2 years was earning almost the same salary than when I joined while my market value was a lot higher (now I'm earning about 2.5X).
So are you in a crappy company? They don't want to change their bad ways? Good luck to them, I'm not working there.
- we buy every year about 10,000 laptops. Not one model because some are not available on all continents, but a small number of models.
- we buy less than 400 laptops/year for IT people, that is 4% of the total
- out of the IT people, over 80% are using the laptops just for emails, Excel and PowerPoint, so regular computers are fine.
- the rest of ~100 laptops/year out of 10,000/year means just 1% of the total. The guys in charge of equipment purchasing are measured on cost savings, they could not care less about the 1% with special needs
- out of the 100/year, the smart ones don't do heavy lifting on their laptops, but on servers or special use desktops (ex: Threadripper machines) that are very adequate for their needs. The less smart ones get what is called "engineering laptops" with more CPU cores and RAM and larger screens, but the thermal limits in the laptops are still there, so the problem is just partially solved at a high cost.
In the past I worked in an engineering department where the dept manager took care that everyone had equipment matching their needs. That was a great manager and this is how this should work, but in modern companies mid-level managers are mostly a bunch of politruks and I am saying this as a long-time IT manager working with many external parties.
Most of the time, I don't need a huge amount of power. I'm not rebuilding the Linux core, every time I compile; usually an app.
For my server work, all I really need, is an FTP connection, a browser, and a text editor.
The reason that I prefer laptops, is that, every now and then, I need to take the show on the road, and it is very convenient to just yank my main device out of the dock, and drop it into a backpack, without worrying about syncing. I tend to do native Apple work, in Swift, using Xcode, so it is important to have a lot of local files. I can't really do the work remotely, on a cloud.
When I was still in my "day job," the company issued me a laptop (because I was a manager, and traveled a lot). I brought a laptop for my own work, because that was all done in "nights and weekends." I often threw my personal laptop in with my work laptop, when I traveled.
Nowadays, I have an M1Max 14-inch MacBook Pro. It is pretty much maxxed. Every bit as powerful as any desktop I've ever used. Xcode is still fairly klunky on it, because the code in Xcode is ... classic. I don't think a Mac Pro would be any real help.
But when I'm docked (which is most of the time), I'm running on an LG Ultrawide (49-inch, 5120 X 1440) monitor. Even the 16-inch can't hold a candle to that, so the 14-inch is better for me.
But that's me, and my workflow. YMMV.
Saving money is pretty much the only thing I can come up with. I certainly don't agree with any of it. The laptop piece might be a bit of DR (everyone has their work PC with them, so we don't need an emergency office).
Everyone in our company gets Threadripper workstations these days. Currently we are handing out Thinkstation P620s. We don't play games with bullshit dev machines anymore. All of that frustration is reserved for our cloud vendors.
Running the corporate OS however is a whole different story:
- Symantec Endpoint Protection with SONAR enabled, scanning at every file access
- CarbonBlack Response Sensor
- Hive Streaming
- Riverbed Steelhead Mobile
- BeyondTrust Defendpoint
- Nexthink sensor that were installed because people were (are) having performance issues
- Probably other stuff I've missed
Kernel times are through the roof when I look at Task Manager.
Suffice to say, this computer is plenty fast and does its job better when booting Windows from an external harddrive than it does on its internal NVME SSD running the corporate install. Everything is faster, from running git to running builds and automated testing.
Same with "the meeting should be an email" type of thing, meetings are expensive but they cannot see the costs.
I had to go into a long discussion explaining that we need to run a whole bunch of development tools besides running the application and therefore need much more powerful computer. I also explained that, if he makes developers that will by the hour, work deliberately slower, it will cost him more in the end. I think it was this final argument that won him over.
There is sooooooo much work out there looking for devops people; that, for me, it's a numbers game. And for the companies; a struggle to provide such an environment.
So far so good, and I'm having a blast. It's amazing what a difference having a nice dev experience / setup can make in you day to day work.
Edit: The actual day to day experience is not so bad with vscode and the right plugins.
1) they are cheap
2) they don't like you and have given you the crap machine
3) they want you to create stuff that runs on a machine similar to the target audience of your product. So you'll build stuff that works on less speedy machines
of all of those options its mostly 1, then two, and very very unlikely 3
I guess it's something like cost vs average needs. If most people can do most things without too much difficulty then you're mostly good?