skysight-inc/HackerNews huggingface dataset:
The 'daylight' line is me butchering a quote from Louis Brandeis about transparency, 'sunlight is said to be the best of disinfectants' commonly rendered as 'sunlight is the best disinfectant'. That's what I get for posting from mobile.

I'm neutral on microservices, pro Docker.

What I'm properly alergic to is arcane setups where it's easier for everyone to share a server than it is for anybody to set up a copy of the system that is theirs and theirs alone. In a big enough shop, running all of the microservices you need on your dev box might be possible while running the whole system isn't, because you run out of memory before everything loads.

The bad coders often continue to be bad coders because nobody can 'prove' that it's their fault and so they keep dazzling the managers with bullshit and implying that you are the one with the problem, not them. Isolated, repeatable systems means you have to look at how crazy your architecture is instead of ignoring it, and regarding this conversation, there's a paper trail backing up your version of the story.

When people don't know which solution is better, they tend to back the side that has more trustworthy people on it, where trustworthy is "doesn't make messes, or helps clean them up when they do".

If you make it clear who's the problem and the project management still doesn't intervene, take your skills elsewhere. You're quitting with cause and many managers will value your commitment to sanity.
Programmers are often logical people who neglect the importance of PR. Convincing people and marketing good solutions to them for reasons they don't necessarily understand is a powerful tool.
The only changes made to PIL in Ubuntu in any current release (Precise, Trusty, Xenial) are security fixes:
https://launchpad.net/ubuntu/+source/pillow.

> The main issue is that they're modified at all

Not modifying packages at all would also be a major issue. We'd end up shipping dysfunctional packages, or packages with major bugs, or not fixing bugs during the lifetime of a release.

Distributions do a ton of integration work that I think goes unnoticed by users. We routinely find issues and send them upstream - every development cycle. Users don't notice because they'll also find the bugfixes in upstream releases because we sent them there. But upstream releases don't all happen in lock-step, so we end up having to carry some patches to make everything work with everything else.

In the general case, we can't win. We'll always upset someone, which is why I asked for specifics. In general, we will:

(0) Avoid changing anything in a stable release, so users don't have things changed on them - except for (1).

(1) Fix bugs (including security bugs) as they are reported. Because of (0), this generally means that we cherry-pick fixes, which does cause some divergence from upstream. But if we don't do this, then other users complain either about the bugs or, if we pull everything into a package in an existing stable release, about things being changed under them.

(2) During development of a release we fix for integration issues, since every package in the distribution is expected to work with every other package - and (though with some exceptions) we generally only ship one version of each thing in a release. This means that we sometimes need to patch things (we prefer cherry-picks from upstream, but sometimes we don't get a response from upstream in time for our release schedule) in order to make everything work.

But in the specific case of PIL, we appear to not have had to do any of these things, except for some security fixes.

For urllib3, it looks like we had to make some modifications to fix security issues with regards to TLS and certificate verification in Trusty, and one bug in Xenial related to broken IPv6 square bracket handling, and that's it.

I don't really see how we can do anything different here. Should we have ignored the security issues and shipped vulnerable packages? Or should we have upset many more users of the stable release by bumping behaviour under the feet of existing deployments?
Can I repackage my technical debt and sell it to idiots all across the world?
I really doubt one-size fits all advice is appropriate here.
> I'm surprised an enterprising company hasn't come along that allows you to pick all your own stocks, and allow them to be rolled up in an index. That kind of service shouldn't be too hard to create from a technical point of view, so I'm assuming the issue is with regulation.

This is what Motif does, but it's super expensive, and picking stocks is a terrible idea. Vanguard/Betterment are cheap because everyone owns the same thing and you can trade between customers for free.

https://www.motifinvesting.com
It seems to me that you're advocating changing implementation details (binary query protocol instead of SQL, map-reduce queries instead of sprocs) and claiming that it is somehow fundamentally different. But I don't see how that would be the case.

How is a binary query protocol fundamentally different than calling a sproc?

How is a map-reduce job in Javascript any different on the attributes you mentioned than ad-hoc SQL or a sproc?

Obviously map-reduce is a fundamentally different approach to data processing, but it seems to have similar traits in regards to source control, testability, etc.
> I'm more tempted to trust engineers who's day-to-day job is engineering rather then a Youtuber who ...

Even if those engineers clearly have a financial incentive to make biased claims?
https://kite.com ?
The split-brain scenarios you mention cannot occur, since all the proposals have to go through the leader before they are agreed to by any processes.

Moreover, the leaders are lease-based in the author's proposal, so I believe that what he describes correctly solves consensus. However, his proposal doesn't really give
much of a resilience improvement over the original Paxos, since the system, in the worst case, tolerates only 2 failures (leader + one more process), same as a 5-process Paxos. Nevertheless, an interesting idea, one that I don't think I've seen elsewhere.
walk away
There are a number of reasons beside owning the property outright. They can make a bigger down payment than you can, so the total debt is lower. They bought it at a much lower price many years ago. Their total capitalization is much larger than yours, which drives interest rates toward zero. Their tax basis is different than your tax basis would be.

It is straightforward financial math. If they have more capital than you or a different tax basis, they can have a lower monthly cost basis than you.
Then you can't sell (without taking a financial bath). But you can still live in the condo, and the payments don't go up.

Or you can try to walk away in some fashion and leave the bank with the problem. As you say, that contributes to instability.
There's no way that dude's name is actually "Brogan BamBrogan"...
We already have a safer and less expensive mode of transportation: air travel.

Same speed, cheaper, exists today, no need to build tracks :)
This analogy works quite well. Basically, you have to look at all of the costs of the current edifice. Maybe it costs nothing on paper to keep the ramshackle old house the way it is, but the impression it gives to visitors is a cost. Likewise, if you think of new hires as "visitors" was well. On the other hand, a building that's well designed can have a positive effect on the public perception of an organization and the mental state of the people working within it. The same thing goes for code.
The account on mobile read that shared the jailbreak was called branch delay, so I'm assuming this is the author.
I'm curious about equity splits that are unequal, but not woefully lopsided, eg. Microsoft's 66/33 split, YouTube's roughly 45/45/10 split, or Apple's 45/45/10. Do they have similar problems? It seems like the 45/45/10 split does - Ron Wayne left Apple, and Jawed Karim seems to have been a bit of a loose cannon at YouTube (uploading all the copyrighted content) and hasn't worked with the other YouTube founders since. But then - maybe those partnerships would've foundered anyway? Reddit's equal split between it and Infogami didn't really work out either. Are there any companies out there that have succeeded with 60/40 or 65/35 splits, or 40/30/30 between 3 cofounders?

Honestly, looking at the history of startups, it seems like it really is "growth solves all problems". Startups that have users who desperately want them can survive single founders (PlentyOfFish, Instacart), a 90/10 equity split (Netscape), one founder who screws the others out of equity (Facebook, Microsoft), founders who barely know their cofounders (Parse, Dropbox), founders who break the law (IBM, YouTube, Zenefits, Uber), founders who quit (Apple), founders who bow out (Uber, EBay), all the way up to founders that split shares equally and give a bunch of shares to professors & classmates (Google).
I don't see much benefit. The investment philosophy that goes along with Vanguard is buy-and-hold for the long term, there's little trading that goes on these accounts. And that's a good thing. It's not like it's difficult to trade stocks as it is, no real need to make it easier.
Doing a startup with a spouse sounds like a dangerous situation on 2 levels, 1 you're crossing streams. A bad day at work can lead to a bad day home or vice-versa. The second is you're no longer diversified. If you go bust, you don't just lose 1 income stream, you're down 2.

There's a third point related to the first. If your business expands, and you bring in another decision maker on any level it creates an unfair power dynamic. You have 2 motivations instead of only 1 professional. You may disagree with your wife on a critical decision, and you may be right, but it may behoove you not to dig in your fists to keep your home life happy.
I'm surprised YC hasn't explored Dynamic Equity Splits at all:

https://techcrunch.com/2013/02/09/the-perfect-cap-table/
The problem is that half the servers failing is indistinguishable from a switch connecting two racks being flaky, or anything else which can lead to half the servers being temporarily disconnected from the others.
It can be in a rack-mount for live use but in offhand conversation, it's an audio software / plug-in.

For future reference, the United States Patent and Trademark Office offers a lookup service to quickly check if a planned mark might already be registered.

http://www.uspto.gov/trademarks-application-process/search-t...
I think you're right - it is very much like writing call options. It is still a liability, but of an unknown quantity.
This shows the dangers of hording 0-days. When/if they go public en-masse they can cause serious havoc.
Portfolio work for photographers, illustrators. Loads of musicians working for peanuts or for promises of fame and also building portfolios.

I think lawyers and doctors are abused by working long hours and are not compensated for it as they should. There it is called duty or civil service.

But I do not have any hard example...
Also, the landlord could have bought the property before the price went up. Their mortgage does not necessarily reflect today's price.
That was one engineer disagreeing with a team of managers.
I always wondered why we only have a single election day given how long the candidates spend campaigning. Is there any reason why a 3 day window (or more) couldn't be used?
VeraCrypt on linux uses the linux kernel infrastructure for user data encryption/decryption and hence its performance will be on par with LUKS because it uses the same infrastructure also.

Performance of a VeraCrypt volume will degrade only if you use multiple ciphers.
Air travel is a huge pollutant and is literally destroying ecosystems and life all across the planet Earth. Either airplanes need to get to 0 greenhouse gas emissions, or we need new types of long-distance and fast transportation. The hyperloop is a great concept because it can significantly reduce the demand for high-polluting air travel. There are other ways too, of course - hyperloop isn't some single savior for everything. But you cannot pitch airplanes as an alternative. They are not.
VS Code Intro Videos
I loved the old Model M I somehow got as an impressionable youth, back when PS/2 keyboards were fancy and USB keyboards weren't a thing yet.

Eventually I moved away to USB keyboards and hated the mush feel and looked around for options but balked at the price. Finally I ran into a couple of guys who'd made the jump (not to Das though) and I started looking around. I found the DKs to be really good looking and I really like how they feel (I've got the clickiest switches they offer for the Mac).

I think over $200 for a keyboard is crazy as well, especially if it's because people are getting conned into thinking they're getting more than they really are, but I won't begrudge someone's decision if it came down to, "I know what I'm getting and I'm fine paying this premium because of [insert deciding factor]"

I wouldn't do it, but 10 years ago I wouldn't have spent $120-150 on a keyboard either.
What could be more regressive than ignoring one side of an engineering debate because that speaker doesn't agree with your politics?
It doesn't improve regexp; it improves your code that uses regexp to populate type-checked data. Instead of writing a lot of "if foo is int then ..." type checking code you can just annotate the regexp with types and it either extracts those types for you or throws an error or something.

In general you have the same problem when parsing CSV, command line flags, URL query parameters, JSON, etc.
Automatic voter registration? No. If you aren't informed or concerned enough to register then you ought not be voting. Some significant percentage of Americans can even name the chief justice of the Supreme Court.. Do we actually want those people voting? Kim Kardashian would be President of that we're the case.

We should require an oral civics exam before anyone is allowed to vote. If you don't understand basic government functions, you sure shouldn't be allowed to vote on those functions.

That's like asking the marketing department to debug C. Why should the ignorant be allowed to make decisions that affect everyone's lives unless they care enough to actually understand what they're voting for?

Voting is certainly a right, but that doesn't preclude the responsibility.
First, let me explain why drop-shipping is a popular vector for fraud. Drop-shipping means selling a product which you don't make or hold in stock; instead, when a purchase comes in you go and buy it somewhere else and have it shipped directly to the buyer. You can think of it as a form of arbitrage. They're remarkably efficient businesses: they need to have no assets or physical presence. The flip side of that is that if you were looking to create a legitimate-looking shell business to, say, cash in on stolen credit cards then drop-shipping would be a very plausible cover story. It's hard for us to disprove.

Since Stripe is on the hook if customers don't get their goods or services, we need to be able to ensure that the businesses are legitimate. It's hard for us to reliably do so with drop-shippers. While dropshipping is not Shopify's primary business, they are more specialized in ecommerce, they have more business-specific data, and there are a handful of other properties which let them support these businesses more readily.
There's one thing that keeps bothering me about all the Hyperloop competitions and startups: everyone seems to be using maglev. This does not match up with the original Hyperloop proposal, which used an air compressor to suck up oncoming air and blow it out the bottom, creating a fluid bearing.

Maglev trains have been proposed before; there's nothing particular new or novel about the idea. One of the bigger problems with maglev is that the tracks are very expensive. One of the exciting things about the Hyperloop concept was that the tracks should be much cheaper, since all you need is a steel tube.

Is it really right to call it a Hyperloop if it eschews the original concept in favor of building a maglev train in an evacuated tube? Feels like they're taking a totally different idea and just using the Hyperloop name to generate hype.
A quick read of the comments here gives me the impression a lot of people are unfamiliar with what logic programming is, how it works, and what it might be used for.

I am among them. Really appreciate the post just for inspiring me to learn more about it. Anyone have a favorite go to resource?
Ask HN: When is the next YC Fellowship batch?
Hey guys,

Couldn't find anything about it on the website. Is it an annual or biannual program?

Thanks!
> Do you think if I had a choice, I would have chosen Git? Ugh.

> No, I'm forced to use it as a condition of employment.

And you deem it a valid reason to avoid learning the tool you use? O_o
A few additional notes:

1) Investors do look at equity splits. Or at least my fund does, and I assume we're not an exception. I think uneven splits can be reasonable as long as they're just. For example, I think Reid Hoffman had more equity in LinkedIn than the rest of the large founding team combined, but that made a lot of sense: he already had a great name in the Valley, he self-funded the business for the first year, and so on. It would have been much harder to find a substitute for him than for other founding team members (all of whom were great in their own right).

2) I don't say "always" very often, but you should always have vesting. Always. I've seen friends break up over equity issues because they didn't have vesting. You don't necessarily have to do a 1-year cliff, but it should take years for someone to accumulate 30% or 50% of a company.

3) If you're interested in advice on this topic, the book I always recommend to people is The Founder's Dilemmas (https://www.amazon.com/dp/B007AIXKUM/). The author analyzed data on thousands of founding teams to come up with practical advice for people who are starting companies. There's a chapter on equity splits in the book.
Honestly, this seems like a stretched comparison to me. How many managers understand options? And what is even the underlying for your call option? Why would it be a call option and not a put option?
How is this better than what say Xero does for reconciliation?
I really didn't feel it was cryptic or pretentious. However, if you do, can you help describe what made it difficult for you to understand?

The daylight word worked great for me, since the idea is to have everyone be able to see what's happening when they introduce changes.

If there's just one staging / integration environment where people are building things and patching over one another, and your local environment maybe has deviated a lot from either the staging, production, or even a clean local env, then there's all kinds of unexpected problems that might happen.

Getting more things, including your environment, under version control and requiring people to deploy things via files that live in version control rather than a smattering of deployment or env setup commands that not all of the team has visibility into, helps the entire development process go more smoothly.
Doesn't using bots get your account banned?
Show HN: LAF LLVM Passes – LLVM Passes designed to increase fuzzing coverage
Glad to know auto revenue recognition is useful to you! Not yet, but Braintree is high on our list of integrations to build
To get started on all of this, is there any boiler plates with auth built-in to take a look instead of reimplementing everything from the base up?
I'm the author of the blog post and I now see I didn't make the context clear enough. I wrote that post after leaving a company that 100% pair programmed all the time. I'll update the blog post next time I get a chance.
Even if you were right (air travel is insignificant pollutant contributor compared to, say, cars), you can't sell it on the open market. If air travel is more convenient and cheaper, you can't compete with cleaner technology unless it delivers value somewhere else.
Part of the issue is that the delineation isn't clear, in life or in startup advice.
A bit off topic, I like his JS style [1], almost doesn't look JS..

[1] https://github.com/mcsoto/LogicJS/blob/master/logic.js
A secret is more valuable. The reason why is a secret.
Agreed. Not to put the work down - it's beautiful - but the part where you get into the silicon capsense controller is never attractive and/or easy.

When building glass touchscreens we had anisotropic Z-tape under heat and pressure. Is there some breakthrough in doing this on a wet tattoo applique?
You know what else happens in that situation?

Nobody will volunteer to help you fix an obscure bug that only happens reliably in your version. Because it's too painful for them to shelve their local configuration and grab yours. And once people have that hesitation, 'all hands on deck' emergency fixes become window dressing, because only a few people can actually participate in tracking down and triaging the bug. Everyone else is sitting around waiting to be needed for the two minutes that they can contribute.
Huge yes, but still only about 1-4% of total emissions. It's good to make inroads there, but I'm more worried about cars, power plants, etc. I think the biggest argument to make in favor of the hyperloop is ease of use, speed, and price.

After all, maybe we'll have battery powered airplanes some day or maybe we'll just use gliders for shorter distances though maybe that wouldn't be as great for a reliable transport.
...and once we hopefully eventually be done with TSA nightmarish setup, it will be still manageable in terms of time it takes not only to fly, but to depart and arrive.

As of hyper-loop, even if, arguendo, it works; every other major type of transportation eventually failed. Trains do derail sometimes and planes do fell off the sky even if very rarely. I seen some pretty scary pictures in my life, and once seen a deadly car accident (head-on collision at 80mph) myself where you couldn't distinguish where the dashboard ends and actual human body begins, but I can't imagine how it would feel or look like when a body of tissue organs and blood crashes down after driving 780mph.
If the title tag which denotes that it's sponsored content, as required by another government agency, you can easily assume that yes, a judge will care.
Why didn't Larrabee fail?
40 joins for a classified ad?
The same people who look after Python in Ubuntu also look after Python in Debian (as part of a wider team) and also are active upstream in Python in making Python work well across all distributions.

Ubuntu is hardly on its own here. I recommend that anyone who disagrees with how Python is packaged on Debian and Ubuntu get in touch on the relevant mailing lists. If you think it's wrong, there's probably a use case you're missing, or you'll find that your proposal will badly break some other expected behaviour.
As far as I know it is quite common.
My Text in Your Handwriting
It sounds like he got into it because it piqued his interest so he did a deep dive on the subject. Nothing wrong with that. I will get frustrated with people sometimes for not doing things that they ought to be doing, but I would never sh*t on someone for following their bliss and spending their hobby time on things I personally am not interested in. If this pisses you off then I can't imagine what sort of vitriol you would direct at someone who is into, say, quilting. "Aren't quilts solved problems already?!? You just go down to Target and buy one, WTF people!"
Popular will can be a dangerous thing if the popular will is dominated by ignorance. I personally don't want everyone to vote. Kayne West would end up president.