News for hackers. Stuff that matters.
Re:The Metaprogrammer by V-2 on Wednesday September 07, 2016 @06:47AM (#12442197)
"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 waste waiting for it to complete is not worth whatever money they cleverly save by supplying me a "CP/M from '78"

"To insult a new hire by providing only a single 4:3 monitor? I can't work like this."

I can work like this, but I prefer two monitors. How much does a monitor cost anyway? Having two displays is much more convenient.

I can program sitting on a kitchen chair, but I prefer an ergonomic office chair, because I spend a large part of my life at work and I see no reason why it should feel uncomfortable.

Oh, how pampered I am!

"- You were lucky to have a LAKE! There were a hundred and sixty of us living in a small shoebox in the middle of the road.

- Cardboard box?

- Aye.

- You were lucky. We lived for three months in a brown paper bag in a septic tank."

etc.

Re:The Metaprogrammer by pjc50 on Wednesday September 07, 2016 @10:09AM (#12443487)
The single 4:3 monitor is rather like the famous Van Halen rider about "no brown M&Ms": it's an opportunity to red-flag the employer.

Monitors are cheap, at most one or two developer-days of salary. If you can't get a monitor, what happens when you need to buy some more specific piece of equipment?

A previous employer had an extremely liberal policy on letting us just buy anything that cost <£100. Obviously we recognised this was a privilege that would be taken away if abused, so we didn't use it much, but it was tremendously liberating. Want an evaluation board? Need a cable? Or a book? Done!

Previously I've had to do a PO for a box of M5 bolts. That's the morale-draining opposite, especially if you have to sit around wasting several orders of magnitude more than the cost for the paperwork to be done.

(Aerospace people excepted where it's actually required)

Oh, and it is too noisy to concentrate in this open plan office without headphones.

Re:The Metaprogrammer by dev360 on Wednesday September 07, 2016 @10:31AM (#12443691)
That was a funny anecdote about Van Halen, had to read up on it. Here's the link if anybody is interested: http://www.snopes.com/music/artists/vanhalen.asp
Re:The Metaprogrammer by pasbesoin on Wednesday September 07, 2016 @02:20PM (#12445725)
It's also a signal as to who's in control of the development process. (Hint: Not the developers.)
Re:The Metaprogrammer by protomyth on Wednesday September 07, 2016 @10:07AM (#12443471)
>> "To insult a new hire by providing only a single 4:3 monitor? I can't work like this."

> I can work like this, but I prefer two monitors. How much does a monitor cost anyway? Having two displays is much more convenient.

I now prefer a LG 21:9 34". They are fairly cheap, have a good quality screen for long viewing, and the extra width is a real help. I wouldn't buy the thunderbolt version as it really doesn't do the thunderbolt properly.

I think any programmer or manager bitching about developers chairs or screens is a sadist and doesn't really get we have to live with this stuff and it affects our health.

Re:The Metaprogrammer by oz on Wednesday September 07, 2016 @02:04PM (#12445606)
I have an Asus 21:9 29", 2560x1080, not 3440x1440 like the LG you mention (which I've considered). The extra width is nice, and the aspect ratio is perfect when watching movies, but I find I need more vertical pixels.

Instead of the 34", wouldn't make sense to just go 4K (3824x2160) and get it over with? You're getting more vertical AND horizontal pixels. Personally, I'm salivating at the Seiki SM40UNP (40"). Anything smaller at 4K resolution and you'll need display scaling, negating the size gain. I don't think my 2013 ultrabook can drive it at 60Hz, but there are apocryphal reports that I may be able to eke out 50Hz.

Re:The Metaprogrammer by iwintermute on Thursday September 08, 2016 @04:08AM (#12451137)
>> Anything smaller at 4K resolution

I have 32" 16:9 Benq at 4K and it's perfectly usable without scaling. You can think about it this way: 32" is double 16" monitors, and 15,6" monitors (rather popular in notebooks) with 1080p are quite usable. And it took me few days to adapt from previous 27" 1080 monitor.

Re:The Metaprogrammer by protomyth on Wednesday September 07, 2016 @02:44PM (#12445930)
Well, when I bought it before the 4K was available, but LG is supposed to have a 4K equivalent coming in 21:9 which would have the same vertical of 2,160 pixels (giving 5,040 x 2,160). I'll get that when it comes out because I like ultra-wide versus buying 2 monitors.
Re:The Metaprogrammer by smoyer on Wednesday September 07, 2016 @01:07PM (#12445125)
I may be an old-timer and I typed my code into CP/M on a text-only display starting circa 1983 or so. I had to compile the code too and guess what ... it was fast!

But when you've only got 64K RAM there's a limit to how sophisticated a program can be. And when you're writing the type of tools we could write back then, your compilation cycles would be fast too.

Would I go back? Some of my CSS files are bigger than the hand-coded assembly language programs I wrote back then but I still love what computing has become. Many facets of today's systems seem almost unimaginable (except that I was an avid sci-fi reader). So I'll join you in demanding a fast machine so that I'm not waiting for code to compile. And who knows what we'll be building in another 30 years?

Re:The Metaprogrammer by Nursie on Wednesday September 07, 2016 @07:31AM (#12442405)
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 by splatcollision on Wednesday September 07, 2016 @07:34AM (#12442423)
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!)
Re:The Metaprogrammer by V-2 on Wednesday September 07, 2016 @08:36AM (#12442821)
I should be able to run unit tests locally, and have it happen quickly. Added to that, I'm often travelling on the job and sometimes code on the go, massive multicore build machine may be out of my reach

> 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

Re:The Metaprogrammer by Nursie on Wednesday September 07, 2016 @09:48AM (#12443311)
I think the point is that as you gain experience you realise how unimportant your local terminal is.

Engineers tend to grow out of it.

Not that many coders 'often' travel on the job, as a proportion. Most are office-bound.

Re:The Metaprogrammer by falcolas on Wednesday September 07, 2016 @10:19AM (#12443575)
> as you gain experience you realise how unimportant your local terminal is.

If I may be blunt, bullshit. Working on a remote server, especially one not on your local lan, is a lag filled pain in the ass.

Even if you decide to work on a local editor and upload to the cloud, your write-test cycle will be slower, and the best editors will require quite a few CPU cycles themselves to provide (their version of) intellisense, syntax highlighting, and documentation.

And this doesn't even cover ensuring that the computer is capable of handling remote conferencing - a resource drain to end all resource drains on laptops.

I'd go one step further and say that as I gained experience, I realized the value of the productivity gains from low latency and the freedom offered by working locally (I even keep local copies of documentation websites, so I never have to worry about them being down).

> Not that many coders 'often' travel on the job, as a proportion. Most are office-bound.

Internet can still go out in an office. So can power. People travel, work from home, and sometimes work from a conference. Why limit your employees for the sake of saving 1% of a software developer's salary (less, actually, when you consider amortization)?

Re:The Metaprogrammer by jdbernard on Wednesday September 07, 2016 @12:24PM (#12444657)
One more data-point: I've purposefully worked on a thin client. I had an employer that gave us access to powerful machines but not laptop, so I bought a cheap, under-powered laptop and did almost everything on the servers. My experience was that at first it was great and I appreciated the habits the constraints encouraged. Then I took a job where I was given a beefy laptop and immediately noticed a whole bunch of pain points that I had just been living with that disappeared entirely. The good habits from having a low-powered machine can transfer onto a high-powered machine, but there is are a whole lot of little irritations that completely go away when you have more computing power locally available.
Re:The Metaprogrammer by V-2 on Wednesday September 07, 2016 @10:26AM (#12443636)
Well, my experience on the matter aligns with what falcolas says
Re:The Metaprogrammer by koder2016 on Wednesday September 07, 2016 @07:40AM (#12442459)
I guess using some of my 8 logical cores for background static analysis is archaic now?
Re:The Metaprogrammer by gbog on Wednesday September 07, 2016 @09:35AM (#12443225)
Building, editing, testing, all of that is better done remotely with ssh and gnu screen or similar.
Re:The Metaprogrammer by falcolas on Wednesday September 07, 2016 @10:09AM (#12443485)
I personally disagree. That requires that you use vim or emacs, which is not feasable (or even desirable) for many programmers. It also requires a stable and low latency network connection; something which is not always available.

Anecdotally, I had to work this way once for an employer. It worked rather well, but our "development" machines were on-premises, and when they went down, everybody was down. I was also extremely limited in what I could download and run, since the machine was shared with other developers. Not very productive.

Though, I did get really good with Vim, so I am thankful for that.

Re:The Metaprogrammer by gbog on Wednesday September 07, 2016 @11:01AM (#12443955)
Use vim or emacs not feasible? not desirable? If most of the greatest programmers use them, if you're a wannabe programmer how would you not use these tools? It's like willing to be a cowboy but for thanks to the horse and the gun...
Re:The Metaprogrammer by pjc50 on Wednesday September 07, 2016 @11:11AM (#12444033)
If you're writing C# you'll be much faster with intellisense and autocomplete. It's quite amazing how much help it is, especially before you reach expert level.

Occasionally you encounter weird toolchains where some stuff is much more convenient to do from the IDE, so you end up editing files in emacs then having Quartus or Vivado open to look at their reports.

(People should be a bit more specific about their working environment before confidently declaring the best way to do things!)

Re:The Metaprogrammer by falcolas on Wednesday September 07, 2016 @11:58AM (#12444433)
Cowboys have evolved. Many use ATVs and only infrequently have to use a gun. The hat has stuck around, though - great protection against the sun.

I've attempted to write Java using VIM. I've even been moderately successful. But it's still easier to do with Eclipse or Intellij.

Re:The Metaprogrammer by dasmoth on Wednesday September 07, 2016 @10:07AM (#12443476)
Why?

Not all software is designed to run on servers.

In some cases, building locally will give a quicker response cycle.

Editing locally is almost always a better user experience. Especially if your servers aren't in the same building.

And plenty of other reasons (travel, flexibility, ...)

Re:The Metaprogrammer by pjc50 on Wednesday September 07, 2016 @10:12AM (#12443514)
Depends what you're building. Most of my previous embedded work was done on my desk due to needing the proprietary tools to link to the device.
Re:The Metaprogrammer by wtbob on Wednesday September 07, 2016 @10:09AM (#12443491)
> Building, editing, testing, all of that is better done remotely with ssh and gnu screen or similar.

Why? I have a full command line suite running on my laptop, because I'm running Linux. Why would I log in elsewhere, when I can run stuff locally?

Re:The Metaprogrammer by gbog on Wednesday September 07, 2016 @11:09AM (#12444016)
For many reasons. The remote server is in a data center, supposedly better maintained than your PC, it has backups, RAIDx all the stuff. If you automate some tasks, or run long-lasting scripts, it is much more reliable. Also, keeping it in the terminal forces you to use the right tools, e.g. vim/emacs instead of the good old Dreamweaver...
Re:The Metaprogrammer by dasmoth on Wednesday September 07, 2016 @01:33PM (#12445363)
Just because I'm working on my PC doesn't mean my changes aren't pushed elsewhere frequently (admittedly the "trunk based development" crowd seem determined to make this less flexible than it ought to be...)

I'm personally an emacs user for most purposes, but I'm not going to claim it's the right tool for everyone, all the time.

Re:The Metaprogrammer by wtbob on Wednesday September 07, 2016 @08:34PM (#12449275)
> Also, keeping it in the terminal forces you to use the right tools, e.g. vim/emacs instead of the good old Dreamweaver...

I run emacs locally. In X. That way I can browse the web, view PDFs & images, play Tetris in colour &c. I wonder how advanced the nethack mode is these days …