Ironically, HN is probably the most egerious example of wide columns
Write thin to write fast
71–80 of 146 posts
Re: Write thin to write fast
#72I can see the logic in this. You seek less.
Re: Write thin to write fast
#73Interesting, I wonder if screen writing came to a similar format for the same reasons.
Re: Write thin to write fast
#74I one time read book that had 4 columns on every page. It was the hardest thing I read. It was a Amazon createspace for some out of print Modernist work (Tarr by Wyndham Lewis), get the Oxford Classics edition which you can now buy on Amazon.
Re: Write thin to write fast
#75On a related note: At one point I switched to working exclusively on a laptop and after a while realized that the smaller screen had forced me to write better code. I wrote smaller methods, made smaller files, kept my concepts together, the whole nine yards. I even wrote better tests since that helped me keep my work small. It didn't last; I'm writing this on a 27" monitor, but I think that has more to do with bad la…
I see some coworkers with ridiculous setups. Three monitors, one vertical, one ultrawide and curved. I don't see why you need that much screen to write code... when pressed they say it's for having references, Slack, etc. up on other screens but then you just end up moving your head around a lot (what a pain in the neck!) I do everything on a single 27" monitor.
Re: Write thin to write fast
#76On a related note: At one point I switched to working exclusively on a laptop and after a while realized that the smaller screen had forced me to write better code. I wrote smaller methods, made smaller files, kept my concepts together, the whole nine yards. I even wrote better tests since that helped me keep my work small. It didn't last; I'm writing this on a 27" monitor, but I think that has more to do with bad la…
I see some coworkers with ridiculous setups. Three monitors, one vertical, one ultrawide and curved. I don't see why you need that much screen to write code... when pressed they say it's for having references, Slack, etc. up on other screens but then you just end up moving your head around a lot (what a pain in the neck!) I do everything on a single 27" monitor.
It's almost as if people have different preferences in working environment, isn't it?
I used to prefer dual 24" monitors. I felt the physical separation let me better organize my tools.
Now I prefer my 34" widescreen. More flexible, less distracting.
Re: Write thin to write fast
#77On a related note: At one point I switched to working exclusively on a laptop and after a while realized that the smaller screen had forced me to write better code. I wrote smaller methods, made smaller files, kept my concepts together, the whole nine yards. I even wrote better tests since that helped me keep my work small. It didn't last; I'm writing this on a 27" monitor, but I think that has more to do with bad la…
I see some coworkers with ridiculous setups. Three monitors, one vertical, one ultrawide and curved. I don't see why you need that much screen to write code... when pressed they say it's for having references, Slack, etc. up on other screens but then you just end up moving your head around a lot (what a pain in the neck!) I do everything on a single 27" monitor.
I'm writing an operating system, its build system, a verifier for it, and writing docs, usually switching often between them. I wish I had that much screen space.
Everyone has their own workflows.
Re: Write thin to write fast
#78On a related note: At one point I switched to working exclusively on a laptop and after a while realized that the smaller screen had forced me to write better code. I wrote smaller methods, made smaller files, kept my concepts together, the whole nine yards. I even wrote better tests since that helped me keep my work small. It didn't last; I'm writing this on a 27" monitor, but I think that has more to do with bad la…
Split your screen.
I never write code in a full screen window. Either code on two sides or a terminal on one side, etc.
Long horizontal lines really mess with comprehension and attention.
I typically go 13" laptop, but when docked on a 4k screen, I use screen splits to achieve a similar effect.
Re: Write thin to write fast
#79On a related note: At one point I switched to working exclusively on a laptop and after a while realized that the smaller screen had forced me to write better code. I wrote smaller methods, made smaller files, kept my concepts together, the whole nine yards. I even wrote better tests since that helped me keep my work small. It didn't last; I'm writing this on a 27" monitor, but I think that has more to do with bad la…
I see some coworkers with ridiculous setups. Three monitors, one vertical, one ultrawide and curved. I don't see why you need that much screen to write code... when pressed they say it's for having references, Slack, etc. up on other screens but then you just end up moving your head around a lot (what a pain in the neck!) I do everything on a single 27" monitor.
> but then you just end up moving your head around a lot (what a pain in the neck!)
If moving your head causes you neck pain, you should get that looked after ASAP!
Generally, a static posture over a long time is really bad for your health. Make sure to stretch, fidget, move around, change your posture a lot when working with a screen.
Re: Write thin to write fast
#80Anyone know of a vim or NeoVim setting or add-on to do this?
For neovim: https://github.com/Pocco81/TrueZen.nvim