81–90 of 164 posts
Earlier quoted context omitted.
Maybe I'm not a decent programmer but I definitely don't want multiple screens. I would perceive such a set-up as unergonomic and creating too many distractions. Nothing against the rest, though.
That's your workflow. Some prefer two monitors. I prefer to have two computers and two screens instead of two monitors and one computer. (double the keyboards)
why people complain about their tools instead of programming? Well, tools are important... I like to wait less time to see my program compile and I want a good keyboard so I keep RSI under control. These are relevant parts of my profesional life that, yes, are not exactly programming...
Sure, people like to argue about these things because everyone have an ass and an opinion about chair and non Swift developer don't have a lot to say about Swift, and sometimes too much...
But this is pretty much a textbook example of a straw man argument...
Earlier quoted context omitted.
In addition to that, I fail to see the relation between people who like to talk about programming through whatever medium ('metaprogrammers') and people who like to have decent tools to work with. Literally every developer I have ever met wants to have a decent computer, multiple screens, fast internet, and access to the proper software tools required to work efficiently. It strikes me as an incredibly stupid argumen…
Maybe I'm not a decent programmer but I definitely don't want multiple screens. I would perceive such a set-up as unergonomic and creating too many distractions. Nothing against the rest, though.
Earlier quoted context omitted.
Maybe I'm not a decent programmer but I definitely don't want multiple screens. I would perceive such a set-up as unergonomic and creating too many distractions. Nothing against the rest, though.
That's your workflow. Some prefer two monitors. I prefer to have two computers and two screens instead of two monitors and one computer. (double the keyboards)
This is funny because no-one bats an eyelid at an "executive" demanding a corner office, an expense account, a company Mercedes, to fly first class... But God forbid a humble worker should beg for scraps.
> "You post an article about a new programming language, you'll get 10 replies." A quick search pulls up results that would contradict that statement. https://news.ycombinator.com/item?id=7436401 https://news.ycombinator.com/item?id=10901054 https://news.ycombinator.com/item?id=8735892 https://news.ycombinator.com/item?id=10177716 I realize four search results isn't enough to completely debunk the author's statement,…
Most of the consequences of choosing a particular programming language or technique will only come out months or years later, and often those results will have a very muddy connection between cause and effect. I'm way less likely to go on a forum and talk confidently when I would have needed to do multiple projects taking years to have a definitive answer.
On the other hand give me a keyboard for a day and I'll happily wade into an argument about it after typing a few thousand letters on it.
"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.
> As time goes on (16 years as a dev now) I find myself a lot less concerned about this stuff.
That's the point, we shouldn't be concerned, and it's best achieved by giving us equipment that lets us take this stuff off our minds
Some people I've worked with switch between vim, emacs, Sublime and back again, for weeks at a clip, and can rattle off the finer points of each. To each their own, I suppose. And those damn clacky keyboards of course. Not a real programmer if you don't have one of those.