> Many programmers have flexible work hours they can use. You don't need to be in Silicon valley or have a pile of cash to work in a flexible work environment.
Yes and no.
Many programmers can start work when they want, and end work 8-10 hours after that. One segment.
Only the very well off or upper management are able to truly work flexibly. Show up in the morning for a few hours, take off and go to the gym or home, show up later and work for a few more hours. No problem for the founder of Twitter.
(The blog was posted 4 hours ago and it's already dropped to the 4th page; people don't like Docker?)
I would really like to see the Docker provider for Vagrant happen. Vagrant is so easy to manage, and it would make Chef/Puppet provisioning easy. It also makes cross-platform and EC2/DigitalOcean deployment easy with their respective providers. (i.e. you can deploy an image to EC2 that then runs Docker containers)
I would really like to see the Docker provider for Vagrant happen. Vagrant is so easy to manage, and it would make Chef/Puppet provisioning easy. It also makes cross-platform and EC2/DigitalOcean deployment easy with their respective providers. (i.e. you can deploy an image to EC2 that then runs Docker containers)
These dating/find-a-friend services that require Facebook show up often on HN, and like clockwork are berated because they are Facebook-only (and the privacy issues that go along with it).
Yet people keep making them. Am I correct to deduce they are popular and there is market for them, and that it's only HN that hates them?
> I think maybe each bug could have a pot where people could to put an amount, and if a developer fixed that bug and enough people agreed he would get that pot.
Except leave out this part:
> That way developers could pick the bugs where people are willing to put their money where their mouth is.
Instead, completely hide showing how much money was donated to a bug. From everyone. When a developer fixes a bug, they may get a nice surprise for their contributions, that may further encourage them to work on issues.
A little like GitTip, but you're tipping whoever solves an issue, ahead of time. And because it's invisible, it doesn't make your hobby feel like a job because you don't know which issues are worth the most. (although it may be possible to guess by issue popularity)
Great article, I've read many like it, BUT what I can't find is information pertinent to how one should host their API. I submitted an "Ask HN" (https://news.ycombinator.com/item?id=5820761) earlier, but could some folks please advise me on the hosting side of "Designing a Pragmatic RESTful API"?
> So yeah, if you need a box to run your webserver 24/7/365, you can find a better deal elsewhere. But that's really never been what EC2 is for.
What Amazon offering is? This is AWS we're talking about. They have a service solution for nearly everything. You're saying in 2013 they still don't have a service for 24/7/365 website hosting?