4 ms·
Having worked as an indie dev for a decade and a manager of 150+ developers for a decade, I find this comment misguided. Here's "how it works out" for me. I w
by Terretta 15y ago
Having worked as an indie dev for a decade and a manager of 150+ developers for a decade, I find this comment misguided. Here's "how it works out" for me.
I wrote code as fast on an Apple //c as on this late-2010 MacBook Pro 17". I'd argue faster, as context switching to something unproductive was actually a chore. For writing, Appleworks 2 on the //c was, if anything, more efficient than the latest MS Word, for the same reasons some hardcore devs prefer EMACS over Visual Studio.
In my experience, the single most meaningful programming productivity boost in the past 25 years is a second screen.
Running PageMaker on an SE/30 with an external Radius Pivot, for example, ran productivity circles around working the built-in screen alone.
But before second screens, devs managed to get by. In the Apple II coding days, an Imagewriter printout of code thus far taped to the wall behind the monitor served as the "second" screen, and physical books lying open around the desk served as reference tools. In many ways, I'd argue the simplicity and thoughtfulness of that approach was more efficient. It's as though the mind can keep separate threads for each type and physical location of media.
For horsepower, as the rest of the comments here point out, a team does want a source code and build system that screams, but each developer workstation could arguably be a text terminal provided it can handle a few windows.
The psychology of latest toys contributing to job satisfaction contributing to productivity is a separate argument. I have found giving dev groups machines tuned for LAN parties (latest graphics, high GHz CPUs) more relevant to productivity than providing machines tuned for compiling (striped raptor HDs, quad xeons).
- mahyarm 15y agoIt really depends on your build and testing times. If you have to wait another fucking 15 minutes so the entire build system can compile the project, or 30 minutes to run through all of the tests before you can compile, it does kick you out of coding.
- regularfry 15y agoI find it's not the 15 or 30 minute builds that are a problem; I can usefully context switch to something else, get it done and come back in that time. It's the 5 minute builds that are the problem. If I know something is going to take between 2 and 5 minutes, chances are I'll crack open Chrome, hit "news.y<enter>" and lose the next 30 minutes until noprocrast kicks in.
- rbanffy 15y agoMy Apple II development workstation was actually two Apple II's - a II+ where I edited the code (because it had a Videx keyboard enhancer and 80-column board attached via a soft-switch to a 14-inch white-phosphor monitor I had to convince a CCTV company to build for me), and a IIe enhanced with a 12-inch green screen to run and test what I built (moved via floppies). That and a pretty-printed listing. The II+ motherboard video out was also piped to a 16-inch color TV via composite. I wrote a couple programs that used both the Videx 80-column text and the motherboard video at the same time. My dual-headed Apple II+ was something to behold.
- Terretta 15y agoThat's fantastic! Btw, do you know if that Videx board is what the Korean Apple ][+ clones used to make it do upper/lowercase? The Korean clones had that before Apple IIe came out.
- rbanffy 15y agoLower case could be done with a proper keyboard. The II used a 7-bit parallel ASCII keyboard and IIRC the II+ could use it. The Videx keyboard thingie would be overkill.