I was in the middle of writing a script to pull down all the metadata from a GitHub repository when I stumbled upon their Migrations API[1]. Designed for moving organizations to GitHub enterprise, this feature creates an archive with everything in a set of repos: issues, pull requests, git repo, wiki, comments, attachments to comments, milestones, etc. It's in preview with no UI, and afaik no existing client library supports it, so I hacked together a quick tool to make it easy to use.
There are a whole range of options, if we have enough warning and invest in the technology[1]. My personal favourite is the gravity tractor:
> One more alternative to explosive deflection is to move the asteroid slowly over a time. Tiny constant thrust accumulates to deviate an object sufficiently from its predicted course. Edward T. Lu and Stanley G. Love have proposed using a large heavy unmanned spacecraft hovering over an asteroid to gravitationally pull the latter into a non-threatening orbit.
And the same technology could be used to actively "capture" asteroids for fun and profit
Agreed. I'm extremely impressed by the quality of that video. Reminds me of the original Surface teaser[1] in that it's surprisingly ambitious and self-confident marketing, for Microsoft.
Great product idea. I was quite taken aback by how similar the UI and UX is to Airbnb's though [1]. Of course that's not necessarily a bad thing - it's a much nicer interface than most hotel comparison sites - but it's extreme to the point of brand confusion. My first instinct was to check if this was a spin-off business!
ServiceFrame - Dublin, Ireland - Full Stack Software Engineer
ServiceFrame improves the quality of outsourcing relationships. Outsourcing brings together two organisations in an unusual alliance to deliver a set of services. Objectives are misaligned, cultures and sometimes languages differ. Until now, this has resulted in fractured communication between the two organisations, and eventually in failure. ServiceFrame establishes clear and consistent communication between the two organisations, better control for the customer, better margins for the supplier and a higher success rate for both.
We're looking for full stack product developers; people who are as happy designing and implementing new UI features as they are building out distributed data integration systems in AWS. Self-starters who can own the development of features from day one. People who are passionate about quality and can deliver. People who are brave enough to fight their corner and big enough to know when they are wrong. People who like to put themselves in our customers shoes and who are able to think big. People who are innovative and also able to simplify.
We currently use technologies like C#, CoffeeScript, io.js, Docker, AWS, MongoDB, PostgreSQL, Handlebars, Stylus. We believe in functional programming, SOLID principles, DRY, testing, continuous deployment, REST. We don't care if you know our specific stack already: the right kind of developer will pick it up quickly, and show us how we can improve it (Haskell, React and etcd would be easy sells, for example). Our development process relies heavily on GitHub, Slack and emoji.
nearForm[1] sell node.js consulting and software to enterprises like Condé Nast, Universal, Intel and Qualcomm. They organize NodeConf Europe[2]. They're bootstrapped with 100% year on year growth so far and projecting 200% growth this year (according to the article).
One of the interesting things here is that they're Irish, but instead of setting up in Dublin (home to the EU headquarters of Google, Facebook, Microsoft, Airbnb, Intercom, etc) they've decided to set themselves up in a small town in Waterford, a county with a population of 114,000.
Absolutely agree. I cringe every time I see a long blog post with a self-effacing "tl;dr" block, especially when it's placed at the end of the article. Just follow this "journalistic" style instead and you'll be doing the reader a big favour.
The feature is opt-in, requires a somewhat formal process to turn on, and all users will be notified "via Slack that the feature is active and that their private messages are subject to export". They don't make it clear if it'll be made sufficiently obvious to a new user who joins after it's turned on, but I'd guess so.
Also quite nice that "Compliance Exports are not retroactive and do not apply to past private conversations before the feature is enabled"
> when you start having multiple clients connecting to the database
If you assume that will happen, then all the things you suggest are true: the schema is indeed the best documentation, and clients will have to pay close attention to versioning since you can really only have one version of a fixed schema at a time. You'll probably also want to move business logic into the database in the form of foreign key constraints, triggers and the like. Getting that right is really important to protect against a broken client corrupting data.
But that isn't the only strategy. You can instead have clients connect to an API, with the API implementation being the only thing that connects to the database. The API becomes the documentation. It can handle versioning. It handles business logic. In this world, the database schema is much less important, and you can safely use schemaless databases.
Both designs have their advantages, and multiple clients connecting directly to the database may well be a better choice in many circumstances, but it's not inevitable.
> It is well established that prices RyanAir advertises are not prices passengers pay.
Not true. An EU regulation in force since 2008 makes that illegal [1]. Ryanair, for all its other faults, abides by the law.
[1] Article 23, Regulation No 1008/2008. PDF: http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2...
"The final price to be paid shall at all times be indicated and shall include the applicable air fare or air rate as well as all applicable taxes, and charges, surcharges and fees which are unavoidable and foreseeable at the time of publication."
> The homicide division doesn't prevent murders, they solve them.
I don't think larrys was suggesting otherwise, just that it'd be interesting to know if the homicide division was reduced in line with the homicide rate. Similarly, what has happened to the percentage of cases being solved and successfully prosecuted?
> 'community policing' [...] turns out to be more effective at stopping crime
It's known as "policing by consent" by the British, where officers are meant to follow the "Peelian Principles" from 1829 [1]
Of particular relevance here:
2. The ability of the police to perform their duties is dependent upon public approval of police actions.
3. Police must secure the willing co-operation of the public in voluntary observance of the law to be able to secure and maintain the respect of the public.
4. The degree of co-operation of the public that can be secured diminishes proportionately to the necessity of the use of physical force.
9. The test of police efficiency is the absence of crime and disorder, not the visible evidence of police action in dealing with it.
I spoke too soon: seems like https://github.com/octokit/octokit.rb supports it