4 ms·

> I don’t understand why folks default to laptops for development. I think there's a lot of cost/benefit that comes down to: depends on what you are building.

> I don’t understand why folks default to laptops for development. I think there's a lot of cost/benefit that comes down to: depends on what you are building. I had lunch with a VR dev last week. He needed a big machine for huge MS builds. I do a lot of web and network programming, and a $1200 LG Gram (i7/32GB, 17" screen) is way more than adequate. The important thing is that employers understand that slow computers cost them a lot of money when they hobble developers with them.

vsareto 4y ago
>The important thing is that employers understand that slow computers cost them a lot of money when they hobble developers with them. Sadly, that's not going to fly these days with those same employers thinking people slack off more often remotely vs. in the office.
- gjm11 4y ago
  If people are slacking off more when working remotely, then measures that make doing the job less frustrating seem likely to have outsized positive effects, by reducing that slacking-off. (Maybe I'm assuming I'm more typical than I really am. I know that when the work I'm supposed to be doing is frustrating and annoying I feel much more temptation to do other things instead.)
  - vsareto 4y ago
    I'm saying they're not going to see the logic of saving time with better equipment when they're complaining about people slacking off remotely.
raxxorraxor 4y ago
True, employment costs out-compete costs for hardware very quickly. If your employee takes 10 minutes per day waiting on tasks because the system is too slow, you can instead buy a pretty decent rig every year.
- ThunderSizzle 4y ago
  How do you truly report that in a corporation? I haven't seen a way to disclose that a good amount of my time in a project is waiting on thr crappy system they've constructed. It's almost like the just assume the costs or pretend like it doesn't exist.
  - indymike 4y ago
    Don't make the problem be about people or process, just show the exact problem and how you could get more done if you had a way to continue working during a build. Put the problem on trial, and not people (don't call anyone in IT stupid, don't blame anyone for sucky processes, and do not under any circumstance indict the choice of tooling). Take your slow laptop to lunch with your manager. Explain that you are starting a task you have to do three-four times a day that prevents you from working because your computer is maxed, compiling. At the end of lunch, let the manager know when the build stopped, and then discuss getting a faster or a second machine so you can work while building.

vsareto 4y ago

>The important thing is that employers understand that slow computers cost them a lot of money when they hobble developers with them. Sadly, that's not going to fly these days with those same employers thinking people slack off more often remotely vs. in the office.

gjm11 4y ago
If people are slacking off more when working remotely, then measures that make doing the job less frustrating seem likely to have outsized positive effects, by reducing that slacking-off. (Maybe I'm assuming I'm more typical than I really am. I know that when the work I'm supposed to be doing is frustrating and annoying I feel much more temptation to do other things instead.)
- vsareto 4y ago
  I'm saying they're not going to see the logic of saving time with better equipment when they're complaining about people slacking off remotely.

raxxorraxor 4y ago

True, employment costs out-compete costs for hardware very quickly. If your employee takes 10 minutes per day waiting on tasks because the system is too slow, you can instead buy a pretty decent rig every year.

ThunderSizzle 4y ago
How do you truly report that in a corporation? I haven't seen a way to disclose that a good amount of my time in a project is waiting on thr crappy system they've constructed. It's almost like the just assume the costs or pretend like it doesn't exist.
- indymike 4y ago
  Don't make the problem be about people or process, just show the exact problem and how you could get more done if you had a way to continue working during a build. Put the problem on trial, and not people (don't call anyone in IT stupid, don't blame anyone for sucky processes, and do not under any circumstance indict the choice of tooling). Take your slow laptop to lunch with your manager. Explain that you are starting a task you have to do three-four times a day that prevents you from working because your computer is maxed, compiling. At the end of lunch, let the manager know when the build stopped, and then discuss getting a faster or a second machine so you can work while building.