skysight-inc/HackerNews huggingface dataset:
I see very few people asking what jenny_2’s long term career goals are. If your desire is more entrepreneurial then take a year off and make a decision later as to whether you go back. Things change dramatically in a year (especially in a startup) so if you commit to founders now to stick it out and decide in a year to go back to school so be it. I guarantee you their commitment to you is just as loose given you make it big.

I see this as a much simpler question of whether you are going to take a year off. All the variables for which you base that decision will change over the course of the next year so start with the first step and if you choose to leave let the rest play out over time.

In my own experience leaving school is the right choice for some. I left school for startup in the original 90’s boom and although I’m not a Zuckerberg I have had great experiences with startups successes and failures. I’ve also had no issue growing into an executive role in the valley along with a “seat at the table” where colleagues went the more traditional college route. I will however fully admit I am not the norm.
I don't know if that makes long-term sense.

The OP sounds very entitled: "We'd endorsed Slack to thousands of people on our Twitch.tv streams, and even mentioned it in interviews with the media."

Of course Slack must provide them with free chat rooms in perpetuity, they've even been mentioned in interviews!

It's probably better to be rid of "customers" like this sooner rather than later.
> US Cellular was the brand – I didn’t react to AT&T, Spring or Cellular One towers

...
You found a bug in an unstable version 1.0 compiler (for me, Swift 1.2 is the de facto version 1.0). Great. But the clickbait title lost you a lot of good will.
You realize that this one example actually proves the rule, no? In order for the math to work out in this instance you need a large, tech-focused community that might one day turn into a workforce of engineers that might then bring their Slack preference into new companies. At which point assuming the company isn't already using Slack, which is a very big IFF, you then hope that the coder builds enough clout in the company to evangelize Slack and convince the company to move off of whatever they are currently using.

If I were Slack I would generate migration assistants to get organizations like this OFF of Slack and on to something like Gitter ASAP. Seems like the return on that investment (in purely good will) would be much more predictable and scalable.
Cron in Amazon Web Services
Rainforest QA (YC S12) Is Hiring Full Stack, Ops and Front End, Remote or SF
asciinema dev here. Please read my comment on the topic here: https://github.com/asciinema/asciinema.org/issues/186#issuec...

Btw, the player is already a separate project: https://github.com/asciinema/asciinema-player/tree/next
In fact a lot of financial stuff basically works on eventual consistency, they just don't call it that, wear suits and carry serious expressions. What is double-entry bookkeeping? What is an audit? What is end-of-day? What is end-of-financial-year? What is invoice due date? What is multi-currency accounting? What is a market order on an exchange before you learn what it was sold for? What is a credit card transaction that can be disputed? What is a tax return? ... etc.
This is why i have my ^b mapped to ^\ actually. :)
Using Slack for communities and groups of people who don't know each other is incredibly clunky. It still feels like trying to fit a square peg in a round hole.

Slack is made for teams who communicate furiously. Large communities are typically more passive and casual.
Do you have any source for this correlation, or did you just make it up?
Whatever you may call it, I think the distinction between fixed cost and whatever each unit costs you on top of that is very important when we're talking freebies. The correct term is probably marginal cost.
Not only is the headline tired, it's wrong per the author's own analysis (emphasis mine):

> Finally I checked the optimization flags. The problem seems to be reproducible with code generated without optimization (-Onone) for ARM (because for x86 it is OK). At the same time, result is right with optimized code (-O, -Ounchecked) - this is rather strange to me, I'd expect unoptimized code free of errors like this, rather that optimized one.

That is, there's an outright correctness bug in Swift, or at very least a huge break in the principle of least surprise.
An open response to Taylor Swift's rant against Apple
Would you do that by picking up a copy of K&R or would you have a more modern recommendation?
It's pretty clear that Slack is not, and never will be, built for this use-case. Slack is for teams: small groups where everyone knows one-another by name, can be trusted with one-another's email-addresses and other contact information, can be trusted to only use @everyone triggers for important things, etc. A lot of Slack's features are built to assume this "small group with a shared purpose where everyone can be trusted to fiddle with things" paradigm.

Slack can handle "communities"—effectively groups with a "team"-sized aristocracy and a bunch of rarely-visiting people who mainly interact in a hub-and-spoke fashion with the team. But it's still not built for that.

Slack is emphatically not for societies: groups big enough that people only know a small percentage of others, groups that must create "laws" to prevent random strangers abusing your shared infrastructure, etc.

In fact, very few pieces of software are designed to cope with use by societies. Maybe Usenet (as a whole), IRC (an entire server, not a single channel), and Reddit (the code-base, run on your own server) are for societies.

If I were to come up with a way to host a chat adjacent to a MOOC, though, I'd still probably use Slack; I'd just have one Slack team for each instance of each course. (The one thing I do think Slack is missing, is a way to easily share your "Slack identity" (username, avatar, client display prefs, etc.) between multiple Slack teams you're concurrently logged into. Then you could be in two "classes" and be sure the same person is the same person in both; or Slack could even consolidate their Direct Message threads into a single one shared between both teams.)
He was brought up on a farm in Switzerland in the 1950s before industrial farming took off, so definitely not that.

I suspect it was a psychological thing after having to process chickens by hand.
I'd like to see it correlated to age as well. If the numbers change so quickly in the last decades, it seems to me it would be a generational issue.
> it seems like Apple may not actually have the cash to do this

Maybe they could do a Kickstarter campaign?
Interestingly I'd say a lot of your points are true for the investors here in the UK.

Investors want to see growth, they want a business/marketing plan, ideally they want traction...overall they're simply more cautious than our American cousins.
Oh, that makes sense.

Older servers couldn't handle enough clients for connection related limits to matter.
sqlite is really only appropriate for things like mobile or desktop applications or things with generally low concurrency requirements.

I think what you mean here is low concurrent write requirements.

(Edit in response to below: Isn't sqlite file oriented and read-only opens eschew locking? Thus replication via network filesystems should be adequate, no?)
You won't be so happy when your https connection drops after "/" as you are piping into /bin/sh:

rm -rf /$INSTALLER_TEMP_DIR
That is so true. Primates, not just apes. Here's Sapolsky explaining how stress in an hierarchical social arrangement impacts heart health and life expectancy.

https://www.youtube.com/watch?v=A4UMyTnlaMY
This is the real mystery here. I'm a huge fan of what Slack has done and was a big advocate for it when it was starting up. But it feels off that people with high realtime chat needs don't just use IRC, which has been around for ages, is super stable, and deals with this amount of users easily.
+1 for Python. It dominates the security space in general.

Also good to know are C and Java/JVM.
> because consensus is how all decisions are made

This is the crux of it. All decisions are not made through consensus and I would wager that's true at most companies.
Might be enough to just pretend they did
I agree that IRC would have been a good fit, and with modern IRC clients like LimeChat and Slate, it's not the "legacy" experience a lot of people remember. IRC also would solve all of the problems this guy faced:

* Free. You can hop onto an existing tech-focused server like Freenode, or if you want your own control, throw it on your own server(s) for pennies. If you do the latter, you have full control over all logging.

* Logging. Every client can choose what they want to log, what format the logs are in, where the logs live, etc. No more archived messages. Some IRC clients are smart enough to pull from the log to "back-fill" the messages.

* Modern Clients. Like a said above, LimeChat is a really nice IRC client. It doesn't have all the features of Slack, but do you really need all the features of slack?

* Bot Surplus. There are hundreds of bots written for IRC, in nearly every conceivable language. This was the first "integration" anyone ever used for chatting, and can integrate with anything if you put the time in. You don't get it for free, but for a community focused on programming, that's not the worst thing.
> One thing bugs me. Wonder if Bitcode can fix issues like this automatically. It seems the tool to do the job.

If the bitcode you upload to the App Store is LLVM bitcode and not SIL, then Apple can't fix bugs in the SIL-to-LLVM pipeline this way. From looking at the bug it's not clear whether the bug is in SIL or LLVM, but since SIL optimizations are newer than those of LLVM the odds are that it's a SIL problem.
I kind of think that Gitter is a joke and I'm not convinced they can do better than Slack. I mean their Android app has the balls to ask you to write your GitHub credentials.

Maybe Asana/plain IRC is a better solution.
The lightest Android launcher ever
You'd think a look at employment rates of science and engineering graduates, as seen in your third link, would help, but because of affirmative action that data's kind of spoiled.
It's probably better for most sites to minimize the number of DOM lookups by combining jQuery with the rest of your vendor code in a vendors.js (or similar) file. The chance for a cache hit is very low (and getting lower with the trend away from jQuery).

That said, test the 2 approaches and see which works better for your site.
On the other hand, historically, art hasn't paid very well. I suspect the modern artists-get-rich era started with Elvis. That era may be an aberration and be drawing to a close.

In my own profession, writing compilers, you simply can't sell them anymore. That hasn't deterred me from continuing to do so, I just adapt and find other ways to make a living from the business.
I thought when NAS came around we were gonna get cool, drug-addict symptoms like the black shakes...but headaches and skin-rashes?

Lame.
This is...ugh, I don't want to use the word but gross seems to be most fitting. I really don't understand why anyone would do this. Worst yet if your iOS app is interpreting and executing this from an external source than it's against the Apple ToS for the App Store.
BTW, you should watch his lecture series on the biology of behaviour: https://www.youtube.com/watch?v=NNnIGh9g6fA&list=PL45A5E21EC...

For me one of the best teachers you will find online
Huh, I was under the impression that linear scan was more well-regarded than it is, then. I guess I hang around JIT folks and LLVM hackers too much. :)
IRC servers are easy to start up but managing them is not a piece of cake. Also clients aren't that great and features like chat sync all have to be built on top of IRC and have no standard implementation. It has similar issues to jabber which "supports" group chat but I've yet to come across a client that exposes this into something as nice as IRC/Slack/Hipchat/etc rooms.
Yep, they do have a fantastic conversion rate though - last I read was 15m paying of 60m users [0] - 25% must be among the best for freemium. So in that sense I can see why they probably optimise heavily for more users.

I imagine there are a fair chunk of artists who would take the premium only route if they could too - I guess they want to avoid that.

[0] http://www.theguardian.com/technology/2015/jan/12/spotify-60...
This might be the case if you have one and only one application interacting with the database, and your unit tests include each and every permutation/edge case.

It is very common to have many applications, from different vendors and from different time periods interacting with a database.

It often also happens that data can be modified directly in the database, not via the application. I agree this is not best practice but in larger enterprises it happens.

Once you start implementing foreign keys in the client you are adding a lot of complexity to a problem that most mature relational database system do well enough to be trusted by a lot of traditional financial institutions.
At least intuitively one doesn't think it would cost half a million dollars for a year.
You're framing this from a western perspective, yet people in Papua new guinea also have something called common sense, irrespective of colonization, etc.

Don't always look at things thru a western point of view or experience. Lots of themes which exist in western culture actually also exist elsewhere.
ttyrec is a tiny terminal utility that does this on your terminal. It was released in 2000, it's one of those nice little gems one is glad to discover. It records and playbacks terminal sessions. The recorded files are in kb's. [1]

It's simple to use. 'ttyrec filename' starts recording, ctrl-c to stop recording. 'ttyplay filename' to playback.

Of course with asciinema.org, you get the benefit of an html player for the files, that you can link and playback on your own website.

[1]http://0xcc.net/ttyrec/index.html.en
[2]http://manpages.ubuntu.com/manpages/maverick/man1/ttyrec.1.h...
Ha, I am a TinyCo alum who started his own gaming company. Let me know if you want to get coffee one of these days.

Would highly recommend you have a finished game + some revenue before you hit up institutional investors. In the mean time, find angels who respect you. Believe you are an engineer, so people won't often doubt your ability to produce.
> In step 1 you haven't assumed that you know all the primes up to p_n, and then in step 2, you assume that you do have them. If you don't make step 1 more precise, saying that you know all the primes up to p_n, then when you multiply them all together and add 1, step 3 fails.

Why? We know that the largest prime is p_n, and the numbers from 1 to p_n are finite. Each of them might or might not be prime. It's perfectly legitimate to say "multiply together all the primes between 1 and p_n" without knowing which numbers in particular those happen to be. Since I don't know which numbers I multiplied together, I won't know the numeric value of the number produced in step 3, but I certainly do know that by construction, it is not divisible by any prime <= p_n. (Technically, I know this conditional on the lemma "all prime numbers are greater than one.)

The proof I've given doesn't deal with arbitrary sets of primes at all. There is no point in the proof at which you could multiply 3 and 5 and then add one to produce 16. If 5 is the largest prime, the number (implicitly) computed in step 3 is 2⋅3⋅5 + 1 = 31. Iterating from 2 (but why?), you'd compute 3, then 7, then 211, and then something large. And 2⋅3⋅5⋅7⋅11⋅13 + 1 = 30031 = 59⋅509 isn't a counterexample to the proof I've given, because the conclusion is explicitly "the number constructed must have a prime factor greater than p_n", and p_n in this example is 13. 59 and 509 are both greater than 13.

Where does my proof fail? How is yours more correct? You still seem to think that I'm misstating the proof found in the Elements. You can prove things more than one way.
WTF is Slack???
She seems to be signed with Universal

No, she's signed with an indie label called Big Machine Records. Big Machine Records has a distribution deal with Universal.
Even if they hadn't, the 10k message limit is well publicized and would have forced them into an insanely expensive pricing model.

Slack's pricing model and the ad copy of their website makes it obvious to me that it's a communication tool intended for small teams, not a chat room for thousands of users.
It does seem to be a bad fit. That's too bad for them, I really enjoy using Slack.
One of the people in the story claims the florescent bulbs at the Dollar Store triggered her condition. If that's the case, it should be REALLY easy to verify some of these claims in a laboratory setting.
asciinema is here since 2011 (although it was called ascii.io until 2 years ago).

As for rewinds, you can click on the progress bar to jump to a time you want. Also, the upcoming version of the player supports fast-forward/rewind/jump keyboard shortcuts: https://github.com/asciinema/asciinema-player/blob/next/src/...

As for the playback speed you can set speed, theme, font size etc (embedding docs say this - https://asciinema.org/docs/embedding), and you can append these options to any asciicast URL too, like this: https://asciinema.org/a/21743?speed=5&theme=solarized-dark

Looks like these are not easily discoverable from the player UI, so noting this down. Thanks for bringing this up!
We do break people's bones pretty regularly as part of a medical intervention. The simplest case is just resetting a bone that healed crooked, but there are countless other ways, like in open-heart surgery or an orthodontic procedure that involves breaking the upper or lower jaw.
Yes, agreed, if we are talking about straight concurrency only.

Other things like replication, are also not there, so it's not what I would choose for a website database, but if you can serve all your reads from one server, and don't care about high availability, then go for it.
One downside I see to this is the cost of the host for what will likely be a idling machine for a long time. Ultimately these services end up pinging some API or kickstarting a workflow, and the host itself isn't always super busy.

Looking at other services provided by AWS, Lambda[1] seems like you could easily schedule tasks out of the box, and not pay for the host/capacity unless your script is running. If all you are doing is pinging other services, it won't even be running that long.

[1] http://aws.amazon.com/lambda/

"Scheduled Tasks"

AWS Lambda functions can be triggered by external event timers, so functions can be run during regularly scheduled maintenance times or non-peak hours. For example, you can trigger an AWS Lambda function to perform nightly archive cleanups during non-busy hours.
It's still constructive, you just have to change a word. That you insist on dismissing the method entirely baffles me.

I'm sorry that I didn't remember it off the top of my head.

Factoring is not a huge burden compared to the earlier steps, and also not necessary a lot of the time, especially if your goal is to keep feeding the number back into the system to create numbers made out of new primes.
Related: http://techcrunch.com/2015/05/02/and-c-plus-plus-too/

We fail to learn. Heartbleed. GHOST. The Android 4.3 KeyStore. Etcetera, etcetera, etcetera.

C was and is magnificent, in its way. But we cannot afford its gargantuan, gaping security blind spots any more. It’s long past time to retire and replace it with another language.

[...]

So please, low-level programmers of the world, I beseech you (while, to be clear, also respecting you immensely): for your next project, try Rust rather than C/C++. There is no longer any good reason for today’s software to be as insecure as it is. Those old warhorses have served us well, but today they are cavalry in an era of tanks. Let us put them out to pasture and move on.

(Personally I'm rather neutral on the issue (I don't work with low-level languages), I just think it's good food for thought.)
"But evolution is only a theory!", which is true, it is a theory, it’s good that they say that, I think, it gives you hope, doesn’t it, that - that maybe they feel the same way about the theory of gravity... and they might just float the fuck away. -Tim Minchin
If there is real consensus on what should happen then nobody is managing, things are just happening.

But "managing by consensus" is forcing everyone to say they agree (hah!) about what the manager has already decided on. Depending on how much the manager has bought in it may either be 1) veiled authoritarianism or, worse, 2) a cult where they think this is helpful.

I can work with you without having been forced to agree.
3 months free is a way for Apple to promote its service against its competitors, and they need to do this promotion because they're late-comers. There is nothing to gain for the creators of music in getting more people to use Apple streaming service instead of Spotify or Google, so, why should they finance Apple's promotion?
We have stumbled into the era of machine psychology
Steam allows full refunds within 2 weeks. You're not publishing on steam anymore?

If there was a subscription program for apps, I could see apple introducing a similar trial period.
You can't really use a product outside of it's use case, then complain about it when you reach "outside" it's walls.. I mean you can complain all you want about it, but don't blame it on the product itself. The manual invitation form is clearly designed to discourage mass open ended invitations. A product designed for teams with 500-1000 users in mind, is probably going to get bogged down by 10,000+ users.
The "X considered harmful" snowclone is usually reserved for when X is fundamentally a bad idea. This is a case where X has a bug. Not really the same thing.
So no one will mention the Clasp (Lisp on LLVM developer)? He built a language to build better, albeit not visualize, better molecules.

If you are on this article, you probably will love to watch this guy. I am computer nerd and this guy makes me want to go back and study chemistry.

https://www.youtube.com/watch?v=8X69_42Mj-g
Python, closures, and scopes (2010)
Sure, but I think you need to consider how fast moving blocks of memory can be on modern computers. memcpy feels intuitively slow, but because it's such a ubiquitous operation, it's really really fast. On the other hand, changing pointers sounds fast, until you consider that a pointer read might flush everything out of cache and result in the cpu stalling for hundreds of cycles while the RAM retrieves something.

I'm not suggesting like, never used linked lists or anything. I just think that most computer science is predicated on an abstract machine with predictable memory latency, and naturally people tend to design things with that in mind, while in reality, unless you're processing data sets so large that memory latency is insignificant, an O(1) operation might be way slower than an O(N) operation.
Why not use IRC or some form of XMPP? Heck, just make a channel on Freenode and call it a day. Want integrations? Everything works with IRC already (maybe not all the one-click integrations).
How Do Maize Moisture Meters Work?
I ask coz I want to make a mobile app that maize farmers in East Africa (I'm Kenyan) can use to check for moisture content in their maize, but phones don't come with built in moisture meters the same way they have gyroscopes, accelerometers and so on. I'm thinking of getting the basic electronic component for moisture measurement and moving it's data to a phone via USB where the app does the rest. So like a probe with the meter on one end that you plug into your sample of maize, a USB cable and a phone. I know google is my friend, but if you're already conversant with this, it'd help a great deal.