The iota enumerator in Golang is elegant and unique. Writing idiomatic Golang code is so implicit in the language itself that I've been able to easily read almost any Go code I find.
Slashdot videos: Now with more Slashdot!
If you're building services that still require "regular maintenance windows" in 2014, you're doing it wrong.
This is a really nice sentiment but is in fact somewhat disconnected from reality.
In the web world, building zero downtime services that don't require maintenance is doable. In many enterprise IT environments with legacy or bloated software (hospitals, education, government) it's a non-starter. The staff do not have the skill, the applications don't have the support, and the political will within the organization is not there. Database migrations alone can be a major source of downtime, and that's largely true even for web services.
Puppet is a great tool for automation but does not solve problems like patching and rebooting systems without downtime.
Yup. Very dependent on the business, the application, the usage patterns, etc.
The right answer to this is to have redundant systems so you can do the work during the day without impacting business operations.
Yep, pretty much this. For me it was a bit later - 1980 - but we had a C64 in the house and my Dad was in a club that talked about them. He showed me some simple BASIC and set me on the track at an early age.
Come up with a few simple programming projects that students can run through. There's something magical about writing code and seeing the computer execute exactly what you told it to do. Write a Ruby Sinatra or Python Flask app and show how to access it from the command line. This will teach them what a web server is and how to write simple code at the same time.
This android app (currently under development for iOS) is open source (github.com/surespot) and gaining momentum. "Exceptional encryption for everyone."
Disclaimer: I know the developer.
Where are my mod points when I need them?
Valve addresses this very question in the Handbook for New Employees:
Q: If all this stuff has worked well for us, why doesn’t every company
work this way?
A: Well, it’s really hard. Mainly because, from day one, it requires a
commitment to hiring in a way that’s very different from the way most
companies hire. It also requires the discipline to make the design of
the company more important than any one short-term business goal.
And it requires a great deal of freedom from outside pressure—being
self-funded was key. And having a founder who was confident enough
to build this kind of place is rare, indeed.
Another reason that it’s hard to run a company this way is that it
requires vigilance. It’s a one-way trip if the core values change, and
maintaining them requires the full commitment of everyone—
especially those who’ve been here the longest. For “senior” people
at most companies, accumulating more power and/or money over
time happens by adopting a more hierarchical culture.
Completely agreed. How did samzenpus decide this of all submissions should make the cut? The submitter is clearly quite uninformed and the question is far out of line with the thinking of the Slashdot community, even if it were reasonably formulated.
The FAA Reauthorization Act, which President Obama is expected to sign, also orders the Federal Aviation Administration to develop regulations for the testing and licensing of commercial drones by 2015.
Privacy advocates say the measure will lead to widespread use of drones for electronic surveillance by police agencies across the country and eventually by private companies as well.
Link to Original Source
I used it exclusively. For me it was the best place to find torrents that where properly categorized with many seeders and, most importantly, ratings and comments so that you could be confident in the files you were downloading. It was an aggregator of other sites so it had an extensive database. I had been using it since it's inception in 2005. I'll miss it dearly.
Personally I don't understand all the animosity around "the cloud" moniker. We need an easy way to refer to a paradigm shift in serving computing resources. The cloud is an accurate representation of that shift. What's the problem?
That's why I got the TNT 2. Hah. I think I still have it somewhere.