skysight-inc/HackerNews huggingface dataset:
And this identity is Wired from the late 1990s.
Not far off: https://www.mozilla.org/en-US/internet-health/ from: http://www.joeyskaggs.com/works/stop-biopeep/skaggs-stopbiop...
Thanks for the shoutout! We definitely see huge value in letting your users post & vote on feature requests:

- You know what your users want most

- People feel like their voice is heard

- It builds a community around your product

Try it out!
The most poignant line is near the end: "It's really tough to ask these [questions] without sounding obsessed with money, which feels unseemly, but you have to do it anyway."

Basic due diligence on a startup offer is asking for # of shares outstanding, last company valuation, strike price. Advanced due diligence is talking about things like extended exercise windows, secondary sales, and liquidation preferences.

Unfortunately, basic due diligence is rare enough that if you do ask a potential employer the latter kind of question, there is a risk of coming off as overly mercenary.

The way of talking to potential employers that I've seen work is to ask questions in increasing complexity, sharing your conclusions along the way, and signalling why you're asking these questions.

After you ask the basic due diligence questions, you can share the math you're doing on stock value various exit scenarios (a good base assumption is to assume an exit at the current valuation).

That typically lays good groundwork for having "advanced" due diligence conversations about an extended exercise window and shows you're serious. In contrast, if the company isn't willing to share valuation or total share numbers, this is a huge red flag as it prevents you from doing the basic math.

This is a tool I built giving engineers the questions they need to ask, in order to do that basic math on what their stock is worth: http://www.optionvalue.io/
Just because we're the one usually excluded from photos encouraging diversity, since for some reason we're oppressing, even though we've driven the tech ecosystem for ages. And by driving, I mean, working our asses off, hoping for help, no matter what color, gender, sex, etc.
Indent 4 spaces for code.

Here's another way to do this in Go:

func f(obj interface{}) {
switch obj := obj.(type) {
case Foo:
// Do stuff with obj.x
case Bar:
// Do stuff with obj.y
default:
return fmt.Errorf("obj is of unexpected type: %T", obj)
}
}
The implementation of PostgreSQL is complex, no doubt about that. But if you need strong data consistency and durability guarantees, it provides a rock-solid foundation.

SQL might take some getting used, but it is also not rocket science. It shouldn't take more than a week's study to master the basics. There is of course a lot of awful SQL code out there, exactly because most programmers don't even know the basics. You can do incredibly powerful things in it that would take 10x the code in an OO/procedural language. In my opinion dumping an ORM on top is also not the best way to leverage the strengths of an RDBM.

It is slightly ironic that you bring up security malpractice in the context of PostgreSQL, when in the next sentence you advocate Redis as a far easier alternative. As was recently in the news the Redis defaults were for a long time insecure (google for Fairware ransomware).
Why Bitcoin Scares Society
> all the way up the call stack, discarding useful context that should be reported (like remove /tmp/nonexist: above).

It's simple. With exceptions, we got used to "errors" that are, by default, debugable. But Go got rid of default debugable errors, and programmers are lazy.
Or still yet, a robot-care business staffed by ever more populous and longer living Japanese. Because Japan!
but different people = oppression /s
Well, considering the energy put in by US and Russia to divide European union, I will not be surprised... Divide and rule, isn't it?
And if Bison's scheme to take over the world worked the Bison dollars would make you totally rich.
> So don't pardon Snowden. Commute the charges against him.

Commutation is reduction of sentence, it can only happen after conviction.

> Like 97% of the cases that go to prosecution in this country, let him plea to a lesser crime

Is there any indication that Snowden has any interest in pleading guilty to anything?
>But especially here, where we're talking about reducing complexity, it feels off to me. PostgreSQL and MySQL seem to me like incredibly complex packages. SQL, the language, is not easy to master either; most programmers I meet know mostly basics. On top of that, there's a long ongoing history of security malpractice.

PostgreSQL and MySQL are very complex, but the complexity is entirely contained. Both are well-tested and reliable, so developers can deploy them without worrying much about them.

I would disagree about SQL being difficult to master. The basics are all most people need, and are not at all difficult to learn. The more advanced stuff (e.g. CROSS APPLY) is not necessarily standard across implementations, and can usually be replaced with application code.

>When talking about reducing complexity, CouchDB and Redis are far easier alternatives, in my humble opinion, though they go slightly against 'use the tools developers know'.

I can't say I'm that familiar with CouchDB, but Redis is entirely inappropriate for most SQL use cases. It's a key value store, and is not meant to do any sort of advanced queries.
Virtual Reality: still not quite there, again
Yeah, if I use "dog" to mean "cat", that's incorrect, since it goes against consensus and nobody would understand it.

"Beg the question" is fine: it means what 99% of native English speakers believe it means, and everybody understands it.
Chrome uses green for the DV lock, though, which is a bad idea. EV certs taught users that green means good, and then Chrome decided to use it for DV certs too. So users are taught that green is good, and when they go to a DV site they see green text and it says "Secure", so they think they're safe. This is absolutely terrible design on Google's part.
This is exactly what we do at my startup: our options are early-exercisable, we pay a bonus equal to the strike price, and we set up the 83(b) paperwork for you. (We don't gross up the bonus, so you will owe taxes on the strike price, but so far that hasn't been a problem for anyone; early-stage strike prices are manageable.) Are other companies doing this as well? It does seem like the sane approach.
Unfortunately, there is no consensus algorithm to prove him wrong on this point.

Upset? I think he's doing just fine btw.
How do they know their kid wouldn't be the one who would have solved climate change?

The way I see it every new human expands our global hive mind super computer and it's also a lottery ticket at getting a new Einstein. All you need is one genius to advance a science to the next level.
I love that this made it to the report in the "React Boilerplates": https://github.com/tj/frontend-boilerplate

> A boilerplate of things that mostly shouldn't exist.
Somewhat off-topic, though it may be relevant.

Is it that much more difficult/complicated to have a server side rendered app with pure JavaScript sprinkled in versus SPA vs. no JavaScript?

The situation I'm thinking about is the following:

firstApp.domain.com

secondApp.domain.com

If you have an SPA then you literally can just have separate SPAs for each sub domain served statically. You could also have everything rendered server side using whatever back-end you're using. Finally, you can have server-side rendering and add JavaScript when necessary, but this seems to add complexity as your team would now need to know whatever templating language your server-side framework uses plus the front-end framework. Am I missing anything?
Give this game a try :-)
http://howmuchsugar.in

Also if you want to increase transparency for nutrition, consider contributing to Open Food Facts (we need Perl, Android, iOS volunteers and barcode scanners to help)
https://world.openfoodfacts.org
https://github.com/openfoodfacts
It looks..interesting. WIRED got it right, though. I feel as if grandpa Mozilla got on iFunny and found some memes.
I liked it repeated several times. It sorta made a point. (In fact I thought it was made on purpose).
Most unicorns disallow this nowadays to prevent the headache Facebook had when IPOing (very explicit you cannot transfer shares without the companies consent clauses in contracts). Some do controlled tender offers which allow employees to sell some shares, but these happen at the behest of the company, not the employee.
This seems to remain the best way to motivate employees from the founders' eyes. Everyone loves the idea of striking it rich, especially young workers just out of college, even if it's unlikely to happen.
Every country but the US has had very bad luck with Mars landings. Its a non-trivial problem to solve and even the US's expertise and funding leads to failure sometimes.

https://en.wikipedia.org/wiki/List_of_missions_to_Mars

The idea that there's a conspiracy at work is ridiculous. We're not exactly at the "Star Trek" stage of humanity here. Landing on Mars is still risky.
They seem to be going the "internet hipster mememaster" route.
Building a Firewall with Linux and IPTables
"There are more or less advanced plans or propositions in many EU countries."

Citation needed.
> Test results should be cached too: if none of the inputs to a test have changed, then usually there is no need to rerun the test. This will make it very cheap to run “all tests” when little or nothing has changed.

I'll be curious to see how this pans out, because it sounds like a very deep rabbit hole. Is there any precedent for this in other language toolchains? I've seen some mondo test suites in Java that could desperately use it.
Extremely. You'd take ten seconds to say what you had to say. Sometimes you'd say "I need help with SQL", say, and someone would say "I'll help", and you'd be done.

But we had a real agile guru on the team. We didn't do "Agile Methodology" exactly; we did Extreme Programming, and we kept tweaking it. Sometimes he'd say "let's try changing our approach in this way for the next two iterations, and see how it works out". We'd do the experiment, and keep the changes or not. We kept hacking and experimenting with the process, in a controlled way, but never in a "this is how it's done" way.

So if you have an "Agile is the one right way" person trying to run your team with big-A Agile, and he/she wants to do 30-person standups, you're probably in trouble...
> so you can add new interface implementers later and not have to go fix-up old type-switches.

Or, rephrased: the compiler doesn't help you find the old type-switches that need new branches.

As you say, being closed gives exhaustiveness checks, and this is often a good thing: it's harder to accidentally not handle new cases in existing code (or not handle existing cases, when writing new code), and it makes refactoring much easier. For some code the flexibility of being open isn't the right choice, just like for some code, it is.

> First-to-match pattern matching complects order with dispatch

This seems orthogonal to ADTs: one can retain retain behaviour like Go's current switch, and only allow switching on the variant, not doing more detailed pattern matching. This retains order independence.

> Relying on positional fields causes two classes of problems

Again, totally irrelevant: one can pattern-match using the names of fields.
The Nidaros Cathedral in Trondheim has this interesting feature as well: https://radiojente.files.wordpress.com/2011/07/nidarosdomen-...

The story behind that were something along the lines of, according to legend, if Nidaros Cathedral ever were finished, Trondheim would be swept into the ocean by clay/land-slide, hence, there's a missing brick that'll never be laid.
> I really don't miss having invisible control flow for expected conditions blowing up my programs with long stack traces.

As opposed to panics? Checked exceptions don't blow up in your face, you have to handle them. Nil errors and type errors might yet these also happen to Go. I see no difference with Java here. Go isn't better when it comes to error handling, in fact Go is extremely tedious when it comes to error handling.

> (And FWIW, Go does have exceptions, it just calls them panics, and has a culture not using them for "known knowns" error conditions.)

So Go has both(unchecked exceptions and errors as "value"), how does it make things better? it doesn't. If it did, the blog wouldn't be talking about people "handling errors the wrong way".
The numbers in the article and the numbers in your spreadsheet differ. The article contains analysis and categorization that your spreadsheet lacks. The data in your spreadsheet come from a public dataset, as I'm sure the data from the article do. Github stars are not a novel metric. I don't see why the author would need to cite you.
You're going against the narrative there ... no amount of progress is worth sea level rise.
That would have been completely impossible.
I find that the boundary creates operational headaches. A function call won't time out, deliver a 502 error, have authentication/authorization issues, require load balancing, etc. etc.

A REST API will.

Plus, once you've debugged a problem that involves crossing 5 microservice boundaries you'll start to wonder if it was all worth it.

Monolith is also a wrong (and somewhat derogatory) word to describe a non-microservice architecture. There's nothing monolithic about loosely coupled code running on the same machine.

I really think that microservices are a hack to deal with conway's law in large corporations. Operationally it's inefficient but it fixes a nexus of technical and political problems when the correct boundary is picked.
Fine, let's have it your way.

If up was down, up would be down... But why is that point made? Sure, the statement based on the false premise is true, but there's nothing to be gleaned from it whatsoever, because it is never the case.

I accept the 2 step logic. I don't accept that it conveys any relevant information, because it is based on a premise that will never be true.

So why is "the point" made?
Couldn't they have just generated this dataset themselves? Why do you think they used yours?
There's a conservative backlash going on as people see an effort to make the world more inclusive as a racist attack on their own priviledged position.

For the record I didn't see any Polynesian, Micronesian, Melanesian, or Jewish people. I also didn't see any Black Men, Asian Women, Transgender, etc.

I saw a White woman and a White man with a VR head set though.
> you can't make any type error when unwrapping the enum

This is also true in Go with type switches:

switch y := x.(type)
case MyStruct:

And with type assertions:

y, ok := x.(MyInterface)

In both cases, y is of the correct type. The ok is optional, if omitted and the assertion fails, you'll get a runtime panic.
Logic 101. :)

> I never claimed that we have no way of determining whether something is true or false

Everything can be cast as a declarative statement.

Matches(givenStatement, actualIntention).
The trend states so.
This is a bad analogy. Nobody calls themselves a "toothologist". The reason is pertinent as well: dentists are basically toned down surgeons, and (in North America) you're not allowed to practice as a dentist without the training because of the harm you can cause. You're not going to get HIV/Hepatitis from a nutritionist, you can from a shitty dentist.

Edit: a good analogy would probably be a licensed counselor/therapist vs and unlicensed one.
Magnet links are perfectly fine for popular content, but because of the dependency on BEP 009 (Metadata exchange) for very long tail content it's often better to get the torrent file directly.

For example, to get information about torrents that are on life support (e.g. have a couple seeds that show up for a few minutes a day), having the torrent file downloadable is invaluable, as it includes info like the size and the file names, etc. In many cases it's even possible to bring a torrent /back to life/ if you have the torrent file and got the content that was in it out of band.

If you just have the magnet link you cannot do any of this.
I'm not sure why you would call it cheating -- it seems like a very principled engineering decision to me.

Even if you never deploy, it's not like Python processes will run forever if you have have GC on. Big deployments usually recycle their processes regularly. Why wouldn't you? There's no downside once you have a big enough cluster.

I recall hearing that YouTube also runs with GC off, but I don't have a source for that.
Thanks for the formatting help!
> Such a big decision should have been a two thirds majority

Two-thirds majority may not have been reached this referendum but it would have been eventually. Euro-scepticism has been festering in the UK for some time and is surging in France [1]

Most of the British public believe that immigration controls need to be tightened [2] something that is not possible when being a member of the EU.

[1] - http://cdn.yougov.com/cumulus_uploads/inlineimage/2014-05-10...

[2] - https://d25d2506sfb94s.cloudfront.net/cumulus_uploads/inline...
I've seen Jira tickets about creating Jira tickets :)

In large lines I agree with this comment. Micromanagement of Agile teams is detrimental.
Implicitly, the message is that managers should leave their teams to work in peace?

The question I have: assume you are that manager. You have 5 agile teams working on 5 client projects. One team seems to get work done much slower than the other teams. What do you do? (And how does one actually track progress of an agile team to begin with? Story points can vary wildly across teams).
DocuSign hires new CEO, in latest sign it's headed for an IPO
Also, don't forget that the food pyramid is defined by the Department of Agriculture (whose job it is to sell food and maintain food surplus) and not the Department of Health and Human Services (whose job it is to pay for all the trillions in health issues resulting from the billions in subsidies).

The calorie is a calorie argument is old and dumb. It ignores insulin which is a BIG deal. It also ignores that high blood sugar can cause a temporary endorphin rush. Ever hear anyone talk about a "protein high" or "fat high"?
There are two things that have to happen in tandem:

1) Mitigating the effects

2) Minimizing the effects

Going all in on one or the other is a fools' errand.

The appropriate solution, IMO, is a substantial carbon tax, with some proportion of it going to funding mitigation and the rest going toward a citizens' dividend.

A pro of this arrangement: to the degree that it's easy to cut down on carbon pollution, it will drive people in that direction. And in the areas where it's really hard to cut down on carbon pollution, it'll act as an economically efficient tax that's passed on to consumers and then rebated to the people. There're almost no losers (except for the many people who disproportionately benefit right now from offloading their carbon pollution onto other people).
Done and Done! Let's talk.

There is a body of evidence that correlates CO2 to Temperature. Where I think this falls down is the causality.

There is evidence that CO2 is caused by higher temperatures, rather than is the cause of them. We see lags of a thousand years in ice core samples, where temperature goes up, and 500 to 1000 years later, CO2 goes up. This is waved away as "due to solar variability", but when solar variability is used by non AGW proponents, they are ridiculed. This is obviously cherry picking of data.
I winced.
I put "good" in quotes for a reason. I never said "hire the best"; that isn't a requirement for anything that was stated.

There shouldn't really be a measurable overhead of running a distributed system, at least in the context of microservices. I strongly disagree with the sentiment that a distributed system isn't "worth it" at smaller organizations. I'm part of one, and it helps keep things flexible while increasing reliability of the "overall" system(s).

But that's neither here nor there. One shoe size won't fit everyone, but OP ran down a gambit of things and seemed to have issue with each one. It is exceedingly unlikely they are doing anything eccentric enough to the point of proclaiming CI is just a bandaid on the broken concept of microservices. I will contend that the source of OP's insights are... misappointed, and by breaking down efficiencies and flexibility they're merely masking certain underlying problems.

What's more probable? An organization hired some wrong people, or a generic list of strongly supported practices over the course of two to three decades are to blame for an organization's failings? I guess that's my take on it.
I worked at Apple from 2014 to 2016 and the iPhone, iPad, etc. teams I was working with were in offices, one or two to an office, up until a big move to an open office in early 2016. They appeared to have been in offices for years.

Apple is sufficiently secretive that indeed some other teams might have been in open offices. Not the ones that I saw or interacted with. I was working on a key part of the iPhone and iPad technology.
Thank you for writing this. Us white males have to start standing up against this agenda. It started with the senseless addition of people of other races (even if they never contributed to a certain cause) and now we see the next step: white males being removed completely, despite being a crushing majority in all tech projects.

Stand up!
The perceived upfront cost is lower with Vue. You can just put it on the page and voila, you have observables, computed properties, templates, everything. No webpack, no transpiling, no modules, no npm.

This is also how angular got popular. The tutorial said: Just add this one JS to the page and start making SPAs! Here is a 10 line example with everything in it explained, and it works!

Same with mongodb - their 10 step interactive tutorial website was extremely convincing

Not many people know you can get started the same with react by putting react, mobx and mobx-react on the page https://jsfiddle.net/ugh2xhfg/. Thats because its not advertised. You will still need babel / compilation though. JSX is still a major barrier to entry.

There is no easier way to make a project become popular than to offer an unrealistic-for-production getting started page that will get you rolling by doing almost nothing!
https://bazel.build/ supports this. Bazel is Google’s build system, open-sourced.
How is it a threat to the US GPS infrastructure? Does it not add another potential layer of redundancy for positioning systems? Assuming that the EU/NATO is still our ally...
The problem isn't the methodology. Its the library support. I (for my employee) wrote a library a few years ago (~go 1.1) with "errs.New" and "errs.Append(err, ..work like fmt..)" that generates error that look like:

main.go:13 main.main(): highest level error;
Details: foo.go:8 foo.ExportedMethod(): mid level error;
Details: foo.go:42 foo.innerMethod(): low level error!

It provides handy helpers like GetRootErr and PanicToError too. I hope we can opensource it in the next month or two.
Interesting definition. Do you have a source for it. It seems ambiguous.

From the Wikipedia article on relational databases, subsection relational model.
"This model organizes data into one or more tables (or "relations") of columns and rows, with a unique key identifying each row. Rows are also called records or tuples."
"The company can choose not to buy back your unexercised options at par-value for as long as it wants."

That's usually not right for incentive options. Check your option agreement. Most will say that the stock option automatically expires or converts to a non-qualified option if not exercised within 90 days of termination without the company having to decide to do anything.

What you are describing is more commonly associated with restricted stock, where the employee "owns" the shares, subject to the company's right to buy them back at par in certain situations.