215 karma · joined March 2, 2011
I use a Mac for development because its closer to our production environment then a PC would be, and because, for me personally, using *nix on the desktop is painful.
If you prefer to work on Ubuntu, then more power to you. If it didn't bother me, I'd do the same as it would be even closer dev <-> production.
If you're looking for information on non-technical position hiring, this is probably not the place to gather it.
The idea that you could do so (unique, strong passwords per site) without a password manager is ludicrous.
I'd previously done the same on a spreadsheet but its nice to have this tool instead.
Services like wufoo and formstack are for non-technical users, not developers.
* http://departments.risd.edu/registrar/web/1112cat.pdf (a number of classes focus on grid systems. this is one of the most respected design programs in the country)
* http://graphicdesigntheory.net/Images/DT/Armstrong_GDTsyllabus.pdf
* http://pacificgraphicdesign.wordpress.com/courses/graphic-design-ii-2/graphic-design-ii-syllabus/But where is the benefit to a thinner desktop? Does it give off less heat? Does the thinness otherwise benefit it somehow? Its 8 lbs lighter - great, but I don't think I've moved my desktop iMac since I've set it up, other then to clean under it.
It feels like amazon is both late to the party and underdressed at this point. The only place it competes is price -- its about half the price of dropbox unless you count the referral space @ dropbox then its not quite half.
In my opinion, the lack of features isn't worth dealing with to save a few dollars. I'm interested to see how fast they make it more dropbox-like, and if they go that direction at all.
In a rewrite you'll find your self relearning about edge cases already solved, you'll lose features and business requirements you didn't even know about. You'll end up with a more maintainable (for you) but worse product in most cases.
Going forward you should have good documentation for key things regarding your system. If its not part of someone's job now, you should explain to your boss(es) why it needs to be someone's job in the future. Documentation is not time poorly spent.
Moving the site to a EC2 large completely removed the problem.
I realize this is completely anecdotal without much detail (well I know the softlayer box runs about $200 a month, so it can't be their worst thing) but it does make me wonder.
Most of them are pretty good. "Erik Spiekermann’s Typo Tips" are some rules that you can apply to what you're doing almost immediately and see improvements, but really -- read them all.
And in 30 seconds I have no clue what your project is, does, or what problem it solves.
Oh and your README isn't IN the README. Seriously?!
Experience and type of work matter, as does actual ability - and good luck polling on that. Company size is also a factor (actual ability seems to affect pay less as the company gets larger, in my experience).
A good developer will Just Get Things Done. Thats a much more valuable skill then having memorized how to write an insertion sort.
Which car would you buy:
* (a) The new Zappino is slick, good-looking, and modern.
* (b) The new Zappino: Women will find you irrestible and Men will be jealous.
Your landing page is (a).
Edit: as an added note, I was so un-thrilled by your landing page that I just noticed there's more information to be had, on my third look.