skysight-inc/HackerNews huggingface dataset:
The application I work on most of the time is largely monolithic and usually I have no problems with that. Some parts have been extracted to their own codebases and are deployed separately because of performance reasons.

We also separated the main backend/API codebase from the frontend mostly because the frontend devs work prefer to work within the Node ecosystem instead of Python/Django and so that we don't have to think too much about synchronizing deployments. The tests for the backend code take quite long to run as well compared to the frontend tests, so having this separation is nice for the frontend devs that way too.

What I some times would like to have better infrastructure support for though is throwaway prototypes/projects that can live in their own codebases and have access to all the regular databases, blob storage and so on, as well as databases that are private to the prototype that I can do whatever with with no risk of doing something bad to the important databases/storage.

I would also like these prototypes to be able to register themselves with the load balancer to take care of everything under `/halloween-experiment/` for example and have the load balancer add headers like `X-UserEmail`, `X-UserID`, `X-IsEmployee`, and so on so that I don't have to implement authentication/authorization in every prototype.

Today these types of prototypes need to live next to the "important" code so that they can use the same CI pipeline and easily be made public or visible to employees and use real data.

I'm following projects like https://getkong.org/ with interest, and together with everything happening around Docker such as EC2 container service or Kubernetes, as well as projects for service discover/configuration like etcd or Consul, it feels like we're getting there. There are just so many projects to keep track of, and you need to figure out how to make them all part of your CI pipeline. :)
If I learned one thing in Software Engineering it's "modularization matters most". And microservices seem to be the epitome of this concept.

If you have to work with different people, you need a way to minimize dependencies between them.

Also, the more encapsulated things are, the less the starting skill of a person matters. You just need people who get things done. Later you can switch out the bad modules easily. Which is a huge economic factor.

I can't count the hours I spent with fixing horrible monoliths and the years it took to replace them.

But if there is a horrible microservice, you can do this in a fraction of time.
And most sites (cant speak for these ) mostly do it alreadyly. Try saying that eg:wage gap doesn' exist and link some articles by economists - 9 out of 10 times such comments get "moderated".
Nice work, one suggestion. The "Account Details" is missing a close button. In trial mode you're trapped after hitting the button.
Seems to me like the only concern with tiny modules on npm are development related. npm could improve the workflow here by specifying a single path to look up (autolink?) additional development dependencies rather than having to link them in each project one by one.

edit: And it seems like someone already thought of that and wrote a module for it ;) https://www.npmjs.com/package/npm-autolink
Pretty similar to what the big IaaS and PaaS like MS and Amazon already do with their regions.
Not just for D.C., no. It's one of the larger/more expensive real estate markets in the U.S., but it's covered by "nationwide" listing tools.

I'm asking for this to be made half in jest, although D.C. traffic is atrocious, and this sort of data fusion looks fantastic. Your concept looks great. =)
Growth Hack the Narendra Modi Way
Very cool, what technologies you are using in your backend?

For commute times are you using the SBB data during rush hour times? My commute is way longer if I don't go to work during rush hour as there are no 'Schnellzüge' outside of those times.
They can't be deployed separately. There's no point in splitting them up. Testing and development aren't affected.
Are they allowed to refuse to cancel your subscription if you don't provide sufficiently valid reasoning for whatever counter-question they throw at you, or something?

Why'd you even answer the second question/offer, let alone get into an argument about it?

"No thanks. I want to cancel my subscription, please."

If they continue to ask "but why?", I'd just start coming up with increasingly unlikely reasons.

"Doctor's orders."

"Lost a bet."

"Religious reasons."

"Sacrilegious reasons."

"I'm gluten-free so I quit computers and phones."

"I literally have no money."
Well, in my days I read "is optimized for Mozilla 1024x603" as "I am not savvy enough to make IE align my stuff correctly but I am an armchair open standard freedom fighter condescending enough to stick my W3C-validate logo in the face".
This is great, I've been considering writing something similar for London taking account cycling distance/time.
Writing a fuzzy receipt parser in Python
Chilli Peppers Beneficial for Health?
That this kind of risk is zero-sum. If higher rates are charged to people who meet these criteria, those of us who don't will get better rates from competitive lenders.
Cool stuff. There's something similar for London too: http://property.mapumental.com/
Meh. I'm putting it on Reddit, I'd rather they profit from it than Buzzfeed.
Any ToS that contain "unexpected" or "surprising" clauses are automatically null and void under EU law. Even if the user agrees with them.
They should finish the monorail to the airport. I'm sure the reason that it hasn't been finished is all politics.
It's not at all similar. Camlistore is your private datastore for life with sharing-capabilities, YouTransfer is an on-premise WeTransfer.
No problem, this is very interesting and I suspect I'll buy the song just as an excuse to play with ethereum. Haven't had a chance to look at it before.
The problem is that there is no reason to believe that is more likely than the opposite case of
"You have something you really want (everyone has different goals). Right when you think you are about to fail to reach your goal, it is achieved (because of something clever you did in the past; everyone has done something clever at one point). This is why unchecked data collection is good"
But Michael Bloomberg is just like us!
In my view, there are two sides of the coin.

Experts (people who have the experience) should always explain, we tried this and this and that is why it have failed.

On the other hand, creative people should be able to justify why the situation or their solution is now different compared to what was tried before.

The rejection seems to happen if this kind of communication doesn't happen. And it cuts both ways - just like there are experts who reject creativity there are creative people who reject expertise. (Typically this is a generational conflict.)
Canva Raises $15m Series A backed by Owen Wilson and Woody Harrelson
As others have already pointed out, you don't need microservices to achieve a good modularization of your code. Then have each team work on a different module, with clearly defined APIs between them. No need to separate them with HTTP calls.
And this is why I only watch content with access to fast froward button. No TV for me.
Because the bigger companies were established long ago, when the US had the much bigger market.

Nowadays that's not true but the US startup VC is a lot stronger in the US for a bunch of reasons, so new startups tend to be established there much more often (with the financial tech field being the exception I believe). If you're making a new company you're going to make it where you live just out of sheer convenience.
9.5-year-old Reddit account here, so perhaps my view is atypical, but I see this as Reddit's answer to the new Digg, and to the broader trend of editorial curation as a counterpart (not necessarily a competitor) to aggregation.

Reddit has web aggregation and communities pretty much sewn up as a market. How can they grow? By leveraging their insight into that traffic to create their own publication. I think they see their audience for Upvoted as people who know what Reddit is, and perhaps use it, but aren't power users and just like to have interesting and entertaining stuff presented to them.

Best of luck to them, I certainly don't think Upvoted's success is written in stone (especially given Reddit's history of half-delivering on their initiatives).
The concept of Winner’s curse
No, this is terrible.

These countries are demanding we run our services in their countries. This is a money grab.

Note that these same countries expect the United States to act as World Police, and do not contribute as much money as they should. They want the US to know about attacks ahead of time. I wonder how the US could possibly know about attacks ahead of time?

I deplore mass surveillance. I really do. But I think wiretapping with a warrant is a necessary tool for fighting crime, and terror, and bad state actors.

There's a part of me that desperately hopes all major internet services just shut off Europe entirely. Welcome back to the Stone Age.
The chances are just as good - not necessarily 50/50, but close to population baseline - that the person you met actually was a nice guy and "the machine" assumes you hang around with good people.

If your chances are actually higher than population average to hang around with bad people, the machine is probably correct for assigning you a higher risk.

Which all misses the point that as soon as he walked into the party, your own ocular implants would have performed the same recognition and you would have known to stay away from him.
5 Things from the 90s Tech World No One Misses
Thanks, that makes sense. I remember the original model m's were real power hogs, to the point that USB->PS/2 converters rarely worked with them.

Now I wonder if they're just using the original circuit with a tacked on converter... might have to open it up to check.
Rubbo Swingo
Even if we adopted identical laws, the government would just ignore them. We're a nation of criminals.
Google Glass specifically, yes. There will be other products with the same form factor that don't have the same restriction. And you can always just take your chances with sideloading an app even if Google themselves aren't willing to distribute it.
Thanks for the feedback. I think the post has much to be improved, but the idea was to get an idea of how that would be useful for other developers --

As for the `next()` and `consume()` approaches, yes, that would basically combine multiple generators in one and not block on any of them.

I will update the post with more information and also take into consideration all the work that has been done on asyncio module for Python3.4.
Thanks for picking this up, I've pushed out an update to fix this issue.
Which is funny since US "national security" is what prompted the ECJ to invalidate the safe harbor provision.
> I was replying to a comment about how to know how much to produce.

Not really. My post, which you replied to, made no mention of "knowing how much to produce". It's not as simple as that. The problem is knowing what to produce, at which quantities, when to invest in capital goods, when to invest in research, when to save money for the future. And this has to be expanded to every agent in an economy. How will a consumer know how to allocate his resources if the economic is not possible?

What you're describing is a nightmare world. Guard against over-consumption? Who decides what is considered over-consumption and what is "normal" consumption? How many smartphones can a family have? How many trips a year is "over-consumption"? Pray not to have a diarrhea or you might over-consume toilet paper! What if I want to eat caviar every day? Do I get it for free? Have you even considered scarcity?

By the way, who produces those smartphones in such a moneyless economy? On what incentive? Who builds the airplanes?

So the central planner will "just" monitor available resources and then what? Order that more must produced? Whose second/third/etc order goods will be used to produce consumer goods? Do you expect people to invest and innovate in exchange for a rice quota?

It's very easy to just claim "collaboration" and not have to care about how it actually works in practice.
Porsche Chooses CarPlay Over Android Auto Due to Google's Data Collection Policy
Reminds me of a less readable Yahoo! circa 1997
So I did ctrl+f for "coherence time" and found this:

A marked improvement in coherence times has been observed by defining the quantum dots in silicon, which can be isotopically purified, such that quantum dots with single-spin fidelities above the threshold of surface codes can be realized

Meaning they get a bit less than a 10% error per operation.

the thing that will make quantum computing practical is quantum error correction. I describe it as "the hospital problem". Suppose there's a car accident. An ambulance gets sent to pick up the survivors and fix it. But an ambulance is also a vehicle and so there is a chance it will also get in an accident. You can send more ambulances to fix the situation, but those ambulances are also vehicles and could also get into accidents. The layout of the roads, frequency of hospitals, and probability of accident per meter will determine on average how many problems get fixed per ambulance. If on average an ambulance gets into less than one accident then it is worth it. Otherwise ambulances cause more accidents than they fix. The point where ambulances fix exactly as many accidents as they create is called the threshold. Once you pass the threshold, with sufficient hospitals you can make the expected number of accidents arbitrarily low (aka the probability of successful computation arbitrarily high).

When people talk about surface codes, they mean the broad class of error correction schemes which look a bit like the toric code. The toric code has a threshold value around 10% which is great! However it is literally a lattice of atoms (or other spin systems) embedded on a torus. Construction is difficult. It also doesn't scale. A toric code with a few dozen qubits works as well as one with a few hundred. In fact several no-go theorems show that any transitionally invariant lattice in less than four dimensions won't scale. My research is actually in getting around these theorems by throwing out the lattice idea entirely.

This research is important, but the real Chicago Pile of QC will be passing the threshold of an easy to implement correction scheme.
Google Takes Stake in Messaging Startup Symphony Communication Services
I'm also curious about the commute time estimation.
I've been playing with the app around the Geneva area where I live and work and I think the commute times are a bit too optimistic.

Nice idea, in any case!
Good question.
* This mail client is hackable which can lead to many plugins created on this.
* It is open source and if they embed the sync part in the app will ensure your data are safe.
* And its design belongs to 2015.
>When was the last time you bought a CD or a record?

August 2015. Is that a trick question?
New Release Lightworks 12.5: Test Drive on Linux
What about free baseband?

http://bb.osmocom.org/trac/
You don't need to buy out every university. You just need to buy out enough to "create a debate."
Can You Be Arrested for Running a Tor Exit Node in Canada?
Facebook Unveils New Second Screen Tools for Broadcasters
Thanks :-)
The stack is based on:

* A Javascript based SPA with handlebars for template and leaflet.js for map

* Django + Postgres for the API

* Simple Vertex-Edge model of the train system, with shortest-path to estimate travel times (including walking distance)

-This is on our to-do list to improve, but we do this since querying all pairwise travel times from SBB/google would be too heavy.

* Numpy/Scipy for the machine learning
Have you tried pressing the delete button (on your keyboard)?
Works in Firefox on Linux.
This. This is so often overlooked. Getting your architecture to roughly align with your team structure can do wonders, even if there's only a hallway dividing people. When a small team can iterate and evolve a chunk of code independent of anyone outside the team, it really unshackles them.

There are obviously patterns for doing this in monoliths (or, say, mobile clients - another type of monolith), but at some point you are bound by the dependencies inherent in a single runtime.
The article is a little weak, but well worth the read.

I love the microservices concept, but fair warning: as bad as OO has gotten over the past 20-30 years, microservices promise to be even uglier.

Why? Because not only are you mucking around in the code, you're also mucking around in how everything connects to everything else in your cloud.

Just like we saw vendors come out with click-and-drag ways to create new classes, now we're seeing vendors start to sell "pre-finished" microservices. Get the disk out of the box, boot it up, fill out a couple of forms, and voila! Now you have microservices.

That worries the living crap out of me because microservices are the architecture of the future. You just can't get from here to there using a magic bullet. Learn you some pure FP, make everything composable using the Unix Philosophy, and keep your LOC to a bare minimum. Toss off every damn thing you don't need.

As much as I know they are the way forward, I have a bad feeling that consultants will have plenty of billable time coming up straightening out a lot of messes.
Well, he is a (wildly successful) fintech entrepreneur!
My view is that the ones, who first hand know will succeed are the founders and co. (even if they sometime doubt)... Investors, etc..., on the other hand, once they invest will always put the right spin and word to fullfill the prophecy. Before they invest, most of of them have no clue, hence invest in large numbers of startup projects with the hope, at least one of each portfolio will make boom for the entire portfolio.

"Prediction is very difficult, especially if it's about the future." dixit Niels Bohr.

Good interview from Sam though.
*buries the lede
With sufficient data, you can narrow down the NYC crowd population quite a bit too. Whose smartphones are known to be nearby vs whose are known to be far away probably already gets you 90% of the way there.
How much inequality is a problem can be an opinion, but what we have is a trend to growing inequality.

At least that you are OK with total inequality (or with a systemic collapse) we should start to look at this carefully.

And this is what the article deal with, what is saying is: "the trend is going to reverse because it was born from demographics, nothing to do with the Washington Consensus, the dismantling of worker protections and other small details."
Some of the weaknesses can be tempered by not using HTTP to communicate between the microservices:

- "slowdowns on the order of 1000%"

- " bunch of code necessary to marshal/unmarshal data [...] there are always dragons in there.

And also problems of versioning, data integrity, etc.

I've had those problems in a microservices architecture. That's things that are solved by protobuf[0]. Your servers exchange small, efficient structured data and you get tons of other benefits ({un,}marshaling for free, integrity, versioning, ...).

Potential downside: a language you want to use having no protobuf API.

Finally, I see another downside to the microservices architecture: it may be decided that the smaller, decoupled code bases should be stored in multiple CVS repos. Which turns into a nightmare: a single bugfix may span across multiple repos and there is no clean built-in way to links commits across them, you still should sync the interfaces (e.g. with git submodules), etc. This is a thing I've witnessed firsthand, and proposals to merge the repos were dismissed since "We [were] using a microservices architecture". Yes, it's a mistaken implementation of the microservices paradigm, but it still happens.

edit: I recommend protobuf not by preference over other equivalent solutions, but because it's the only one I know and have used. Alternatives are evoked below.

0: https://developers.google.com/protocol-buffers/
I think it's bullshit too, but most people online just want Cable TV With Hyperlinks. Reddit is actually raw and unfiltered to those users.

Everything else on their radar is an editorial outlet, the home shopping network or the classifieds section. The closest they get to interacting with real people is Twitter and Facebook. Which appeal to the user's vanity, and following mechanics keep them in some approximation of the social bubbles they're in offline.

But Reddit has pseudonymous randos, with too many different names for a user to meaningfully fit in their brain, so it becomes a single voice to them. And they have ideas that aren't carefully crafted for palatability before presenting them. So reddit becomes "id."
But w/o a gray background.
Sounds like a boring half-measure. Let's shoot for full-scale personal holography. Look however you want, whenever you want.
But "occasionally, someone can interest a TV show" isn't a replacement for regulation :-)
Thanks for the awesome points.

I don't have a mac handy so I will need to look into the keycodes for Command instead of control as well as the mac delete key keycode. I think at the moment backspace will delete elements on a mac.

I've updated the app so that the account details can now be closed.

Thanks again for your valuable feedback!

Edit: Delete should now work as expected on a mac.

Edit2: Copy + Paste should now work as expected on the mac
Legal action clearly didn't work against MS. They're now bundling the same basics (integrated search, Cortana etc) in Windows 10
Ship.io is shutting down
IMO, this rant highlights very well what's wrong with Google's Material design: the whole interface is jelly-like and does not feel very functional.
Even the current directive likely doesn't require satisfying all nations separately; since the various schemes are supposed to be compatible (i.e. conceptually safe harbor, though it's not called that, does apply within the EU), if a business hosted its data in one country and served others from there, they'd likely be safe.

There might be some bureaucracy to ensure that you really count as being hosted there (e.g. possibly ensuring that the parent company cannot access said data - which would be problematic for some companies), but AFAIK (IANAL) there's no legal distinction between EU and non-EU companies in this kind of rule.
"Disruption" is an overused term, not an overused idea. True disruption, following Christensen's model, must involve a higher barrier for incumbents than just sprouting a new product line. If their expertise, infrastructure, and/or market position allows them to do that, they will . . . and they will probably win. Even most of Christensen's own examples fail to work the way true disruption must.

True disruption does occur, when a fundamentally different and fundamentally better way of doing something comes along, but it's a lot rarer than people suppose or pretend. It's barely more common than creating a whole new industry. 99% of the time when people talk about disruption they really mean nothing more than basic product/service differentiation.
I think we can have the idea of improving genetics in a high-tech way without all of the Nazi baggage like Social Darwinism, racism, etc. that comes with 'eugenics'.
Reddit is not the world, and it's not unfiltered. It's the same comments being upvoted and downvoted in similar patterns again and again and again. 4chan is much more unfiltered because it's anonymous and there's no voting mechanism to filter unpopular opinions. 4chan is still not the world though, it's mostly white American men.
Ideally I'd also want also to have cycling+train - since that is also a feasible option for some people. E.g. I live 1km away from a train station that is well connected to my workplace, so I can bike to the train station and commute the rest.
I really don't believe that anyone has "control" of our public schools-- unless their intent is to simply run them into the ground by failure.