Things I'll Apply Next Time After Using a Dev Laptop for 3 Years

The laptop I bought in 2022 is starting to struggle, so I figured I'd write down what I've learned. These are the points I regretted in real-world use after looking only at specs when choosing a laptop.

1. Get at least 32GB of RAM, no question

I bought 16GB, but running Docker + 20 browser tabs + an IDE causes swapping. For a developer, 16GB of RAM is genuinely not enough.

2. Weight and battery vs. performance

At first I prioritized performance, but the weight hit 1.8kg, making it hard to carry to cafes. In the end, I often just left it plugged in.

3. Screen aspect ratio matters more than you'd think

16:10 is much more comfortable vertically than 16:9. You scroll less when reading code.

4. Keyboards and trackpads don't show up on spec sheets

This makes a huge difference in practice. You really need to try it in a store before buying.

5. Number of Thunderbolt ports

Even connecting just one monitor takes up half of them, so you should get plenty.

The conclusion: rather than benchmark scores, choose based on what kind of work you actually do for long stretches.

by 코딩하는곰400

6 answers

For real, 32GB of RAM is just the developer standard now lol. I held out with 16, went through swap hell, and switched right away.

by 밤샘코더237 · ▲0

I really agree with the point about weight. I also bought a 1.9kg one and carried it around for the first month, but ended up just leaving it at home. After that, I concluded that 'portability = ultimately meaningless if you don't carry it around,' so I only look at models under 1.3kg. Covering performance with the desktop at home ended up being cheaper overall, too.

by 지나가던행인751 · ▲0

Well, I think 'always 32GB' is a bit of an overgeneralization. If you're only doing frontend work or light backend work, there are plenty of people for whom 16GB is enough. Docker + IDE + 20 tabs just means your workload is heavy, not that the RAM baseline is wrong... I agree with the conclusion that you should look at your own work patterns first, but I think point 1 is case-by-case.

by 스타트업러196 · ▲0

16:10, this is right. That 100px difference in vertical space makes a huge difference when coding.

by 궁금한사람710 · ▲0

The keyboard/trackpad are the parts that really don't show up on spec sheets, so I spend about 30 minutes at the store typing something code-like before buying. And when I read reviews, just searching for 'key feel' brings up all the chronic issues with a given model (stuck keys, trackpad play). For reference, with Thunderbolt, buying one good hub may be more important than the number of ports. If you use a hub that handles two monitors + Ethernet + charging at once, two ports are enough.

by 밤샘코더72 · ▲0

I agree with the conclusion. If you buy something with high benchmark scores but it's so heavy that you don't actually carry it around, what's the point? There's no source, but since it's written from experience, it feels even more trustworthy.

by AI덕후123 · ▲0