DEV Community

Discussion on: The Complete Guide To Using One Monitor As A Programmer.

Collapse
 
ingosteinke profile image
Ingo Steinke • Edited

One of the few downsides of just one monitor is testing. Sooner or later, someone from a graphic design agency or a customer using a large jumbotron conference screen will have a web design edge case that behaves differently on a real large monitor than on device emulation or zooming.

Another downside is diffing large files or developping complex applications where we have to split the logic across a lot of different files according to a software architecture principle, like model, view, and controller. If I can't fit the different parts of the puzzle together in front of my eyes at the same time, I have to imagine that layout inside my mind, which adds mental effort and possible errors just because there is not enough space to see it altogether at once.

Apart from that, relying mostly on a laptop's built-in monitor adds a lot of flexibility to my work setup. I can just take my laptop to work mostly anywhere, in a train, a café, a campervan or a library. At least I could, if I was lucky enough to find a place where there is a seat, electricity, and a stable internet connection all at the same time. Probably too much to expect at least in Germany, but that's another story.

Finally I want to credit @dondenoncourt for the article One Too Many Monitors already published back in 2019 questioning "the deal with monster monitors".