The Perfect Development Environment
This is a reply to http://thinkvitamin.com/dev/the-perfect-development-environment/
I prefer to be alone, with no one walking around, having conversations on the phone or asking questions. And yes, barking dogs are bad while you try to focus on source code^^
If people can not keep their mouth shut, loud music helps a lot. Use the headphones, whenever other people are around.
If you do an on-site consulting job, better not keep the client from asking questions though: This is what he (or she) pays for! Same is true, if you happen to be in the role of a lead developer. There is no way to hide behind your screen(s). Not matter how many you have.
Desk & Chair
I prefer a simple chair. All the fancy furniture didn’t work for me:
And a desk made of real wood, not that crappy and cheap IKEA stuff made of plastic and particle board. No dinning room table, those are usually too high (76cm). Remember that the keyboard/notebook has a certain height too. The perfect desk is 73cm high. I agree it should be simple, without “cubby holes, drawers and cord hiders”.
As a freelance developer, I need a lot of space on my desk to draw diagrams and sign my invoices. Or just to put the Amazon Kindle. It’s a good replacement for the obligatory PDF readers or word processors that are open in the background and hold the customer requirements.
Mouse & Keyboard
I normally have to use the keyboard built into my ThinkPad, which does it’s job quite well. The best keyboard I ever had was a Cherry G80-3000 with MX gold crosspoint technology and without Windows keys. Those times are gone forever. Everything has to be flat in this century and you can get used to it.
As a PHP/JS/C/Perl developer, you will be happy with a US layout. As a consultant not living in the States, you might want to use a local layout, so that you can easily access non-ascii chars while writing your important business documents.
The best mouse I found so far is the Logitech Basic mouse and it is very cheap at the same time. It is available in gray and black. Perfect.
I usually outperform other developers, even those with 3 screens, not because I am cool, but because I don’t use Windows when not working on some Office document. This reduces the times when I have to explain my customer or co-worker that “it does not work and I don’t know why”. Also it’s easy to get rid of 3D effects, playful window borders and desktop widgets that distract you. Skype looks less like a computer game too, but works equally well. The UMTS modem works every time, not not just every second time (if it fails, you will see a meaningful error message). There is no need to think a lot about which applications to use and there is a standard way for pretty much everything. Last but not least most servers run Unix too, so you don’t experience those strange “file not found” problems after the code was deployed to the production environment. Windows isn’t case sensitive.
System Shortcuts & Project Management
You normally have 3 or 4 windows open that matter:
- the console (to run the unit tests and do svn/git commits)
- the text editor (gedit)
- the Web browser (2 tabs, one with the app and one with google open to search for documentation)
- and maybe GIMP (if you work on graphics too) or Skype for talking with other people about the project
Remember that we outsourced requirements documents to the Kindle or real paper where you can scratch around.
Those windows fit into any task bar, even on small screens. You don’t want to see your desktop wallpaper, while you’re working. Maximize your windows and use the full space available (Mac users will complain now, as far as I remember).
Tortoise SVN is crap, but the best you can get on Windows, I guess. Better use the command line applications on Unix. If you do Open Source or want to be cool, you use git and tell all your friends that svn is bad.
IDE & Other Programs
Most editors fail when working on large projects. Eclipse (also known as Aptana, Zend Studio, PDT) used to have a CSS editor that was so slow, that it took several minutes to open large CSS files. The memory management did not work really well – eventually I found a garbage collection plugin, which added small trash button in the bottom right corner that I had to press every time, the memory usage went to high (WTF!?). Just today I enabled the option “insert spaces for tabs”, pressed the tab key and it inserted a… tab. Crap.
Besides those annoyances, the Eclipse file/folder tree does not update automatically and the SVN plugin (there are many with different bugs to chose from, right?) seems as waste of time compared to the straight forward usage of the default command line tools.
Therefore my recommendation is to use gedit, the default editor that comes with Gnome. It’s only downside is that it can not save files on SMB shares (VirtualBox shared folders) because of a bug, and that really is the only reason for me to use Aptana from time to time.
gedit’s major features:
- It is stable
- You see the character on the screen, directly after you pressed a key (no delay)
- You write nice looking code that is readable, even without additional tools, filters and beautifiers
- The file/folder tree updates automatically
- Automatic indentation
- UTF-8 is default – you never accidentally break the encoding again and get hurt by your co-workers for this
- Low memory usage
- The save button works every time (not true for Eclipse, as I had to find out painfully)
- It doesn’t occupy a lot of the valuable space on the screen
And yes, it can use plug-ins and you can write your own, if you feel something is missing. I am happy with how it is.
I don’t know.