Can't believe he didn't mention text editors or indentation!
Why would he? I think the general consensus nowadays is that Sublime and tabs is the best option.
I beg to differ ;-) See my own $0.02 sibling comment.
The Metaprogrammer
51–60 of 164 posts
Re: The Metaprogrammer
#52In the audio and electronic music world, this is often called GAS -- Gear Acquisition Syndrome.
Re: The Metaprogrammer
#53Re: The Metaprogrammer
#54> Gotta have that 40" monitor, it's essential, can't work without it And I was thinking I ought to be content with my 27"
I used to be that guy that proclaimed I could not work if I did not have 2 monitors of at least 21 inches in size...
But, 2 * 21" (FHD LCD) became 2 * 24" (FHD IPS), which I upgraded to 2 * 27 (Apple 2560 * 1440), which I now consider to replace by 2 * 42" (4K). Have I became 10x more productive by it? No. Can I work without them? Sure. Do I enjoy working on those huge screens? Hell yes! And since screens are not that expensive anymore, why not? I spend 10+ hours a day in my office, so why not try to make that time the most enjoyable I can?
Re: The Metaprogrammer
#55Reminds me of this: https://xkcd.com/1629/
Sounds like devops
Re: The Metaprogrammer
#56"If they don't have the shiniest Apple MacBook then they can't work. Never mind that their job involves typing letters into a text file, something you could have done on CP/M back in '78" I don't want an Apple at all, but I do want a beefy machine because my job doesn't only involve typing text you see - for instance I also need to build the result of all that typing, and if it takes ages, guess what, the time I wast…
Building on your own desktop? That seems rather archaic. Well-connected and integrated access to a massive multicore build machine seems a little more modern.
As time goes on (16 years as a dev now) I find myself a lot less concerned about this stuff.
Re: The Metaprogrammer
#57I came into this comments section to post about how I didn't actually know any programmers who acted as the author described, but in seeing the other comments I guess I've just been extraordinarily lucky not to have to work with divas.
Of course I and others I know have preferences about chairs, keyboards, and monitors, but not so much that they claim they can't to their jobs. Quite frankly, I wouldn't want to work with somebody like that. Who wants to work with somebody who thinks their skill set gives them licence to bitch and moan? Who wants to work with somebody who bitches and moans, period?
Re: The Metaprogrammer
#58You use the right tools for the job --- and when you're sitting in front of a computer for 8-14 hours a day, why wouldn't you want the best tools? Are you gonna build a new wood-piece with a hand-powered screw-driver?
"You post an article about a new programming language, you'll get 10 replies. But start a discussion on what headphones you wear while you work, and ten-thousand people will rise up from nowhere, pushing the thread ever-skywards on a tower of upvotes"
Not many people care about your new programming language, but everybody understands the importance of a good chair, monitor, or headphones, and when you ask people for an opinion, they'll express it.
IMO, code with whatever you want, but I'll stick to my Herman Miller Embody, a self-modified 45g-uniform Realforce Silenced Keyboard, a 4K 30-inch dell monitor (UP3216Q), and 2 27-inch dells (U2713HM).
Re: The Metaprogrammer
#59That's the way people are about everything. Read many of the comments on HN and you will come to the same conclusion. We like to "bullshit" and tell anecdotes. This is fine for being social but it's a very inefficient way to learn and pass on knowledge.
In all the noise, however, there is a lot to be learned so I decided to extract some of the information on various topics. For example, On the topics of standing desks, keyboards, RSI, etc, I've created some org-mode notes on Github.
Re: The Metaprogrammer
#60"If they don't have the shiniest Apple MacBook then they can't work. Never mind that their job involves typing letters into a text file, something you could have done on CP/M back in '78" I don't want an Apple at all, but I do want a beefy machine because my job doesn't only involve typing text you see - for instance I also need to build the result of all that typing, and if it takes ages, guess what, the time I wast…
Building on your own desktop? That seems rather archaic. Well-connected and integrated access to a massive multicore build machine seems a little more modern. As time goes on (16 years as a dev now) I find myself a lot less concerned about this stuff.
Sometimes once in a rare while you want to be able to work totally offline, or in a low-connectivity environment. For example I'm currently on a commuter train on an hour+ ride into the city, and if I want to do everything locally, I can. Options are good. (PS: ask me about working remotely!)