skysight-inc/HackerNews huggingface dataset:
If I had to summarize lean startup, it would be: speed is magic, speed is expensive.

It's hard to convey to someone who's not had the epiphany just how much speed magically solves so many different problems in so many different domains for free, it's kind of amazing. But every incremental gain in speed is pretty expensive which is why people so often shy away from pressing on the gas pedal and dick around.

As an example, the OP brings up that most founders are non-technical and it would cost them $50,000 to build an MVP. His conclusion from this is that MVPs are not worth it. Instead, the correct conclusion is that if building an MVP costs $50,000 and a few weeks of project management, you should instead invest your time in learning just enough prototyping skills so you can bring that down to a week and $200. And then you should invest another big chunk of your time in bringing that down again to 4 hours and $0.

Is that hard and scary and look like it will take a lot of time? Yes. That's why so few entrepreneurs are successful, they want to believe there's an easy path to success which allows them to shy away from hard and scary things. The successful entrepreneurs are the ones who just put on their boots and attack the mountain until it's worn down.
I'm switching to IceCat. It's a GNU maintained fork, but is a few versions behind. I trust GNU more than Mozilla, but you still have to trust Mozilla to some extent if you use any Firefox fork.
Why was it closed 40 years ago?
I've done development both with and without an IDE and I find debugging vastly easier with an IDE. How do developers who don't use IDEs do debugging other than with print to console statements? Do they all use tools like gdb and lldb?

I've pondered learning how to use a tool like gdb or lldb and then using SublimeText for editing the code, but it looks like a lot more work than just clicking to set a breakpoint in an IDE. I'm curious to hear what non-IDE developers are using for debugging.
Not at all - Redis Labs Enterprise Cluster is a downloadable software that makes running Redis clusters a breeze. It is by no means a managed service like Redis Cloud, although much of the underlying tech is the same :)
Here's a better assessment from one of the leaders in the field: https://mkirschenbaum.wordpress.com/2011/01/22/what-is-digit...

It is something of an understatement to say that DH pays a generous amount of attention to its own roots and limits... At this point it is basically a cliche to ask "what is DH?"
I've found a diplomatic critique to be more effective than a fiery polemic. Also, I've been making the same objection to that guy for many years and I'm a bit tired of it.
> I hope you weren't expecting to find anything in your codebase using grep.

This is what nimgrep [1] and nimsuggest [2] are for.

That said, it is still expected to use a consistent style within your codebase. The feature exists so that third-party libraries with a non-standard style can be used without style changes in your codebase.

[1] http://nim-lang.org/docs/nimgrep.html

[2] http://nim-lang.org/docs/nimsuggest.html
One of the problems with doing this is the "recovered" memories are not exactly reliable.

One of the good things about my memory is if I remember something it accurate. I used to win lots of bets (for drinks mostly) by exploiting this - people would tell me X happened and I would say no it was Y and would they like to bet on it. I was always amazed at how many people would accept these bets even after losing to me many times - it seemed they forgot that I had an accurate memory :)
Your model of "randomness" is unrelated to the argument that is being made here. No one--absolutely no one--is saying anything to suggest that a random selection of people could win an NBA championship. They are saying that randomness has an important role to play in the creation of a winning team, along with talent and hard work.

Given that the world is full of talented people who are working hard--and it is--the difference between those who make it and those who don't is very often due to luck. Persistence and courage are two things that really do make a difference because they give luck the most time and largest field on which to operate, but nothing can eliminate luck entirely.

Almost everyone who succeeds is talented and works hard. That is completely unrelated to the claim that everyone who is talented and works hard succeeds. The belief that winners and losers are separated primarily by talent and effort is not very plausible, given the number of "near misses" in the world: people who make it most of the way to success and get derailed by one bad choice (which was not an obviously bad choice at the time) or some other piece of bad luck.
If you've ever wondered why newlines are sometimes CR and other times CR+LF, I think Gary is part of that answer.
That's fantastic to know. I might just switch back to rust because of this.
>Adding proper mutexes to some of our code in production slowed things down so much it was actually better to just run the service under daemontools and let the service crash/restart.

Can the author explain this bit some more? If adding mutexes slows down your code to the point where you would rather just deal with data corruption/races it seems to me that there are issues with your code, not the language.
K&R "The C Programming Language" is a classic. If you're serious about learning C this book should definitely be in your collection. It's the book most C programmers have cut their teeth on over the past several decades, written by the guys who wrote the language itself. (Though go for the most-current ANSI version). If you already know basics of programming methods from Python or JS, you'll be able to handle this book. Make sure to do the exercises!

Beyond that, it would depend what you're hoping to do with C. Eg, Linux kernel hacking? Optimized Python numpy routines?

There also are some recent books that focus on writing 'modern' and also safer C code, particularly with regard to usage of pointers. There are some links on Amazon and O'Reilly that may be helpful (I haven't read any so can't give recommendations)
A flip side of that: if the IBM/Microsoft deal had been made, the PC clone industry might not have succeeded, so PC might have meant exclusively "IBM PC". Forget about all the products that Microsoft crowded out; what would have happened to the hardware and software industry if a dozen competing "PC" manufacturers didn't spring up?
Building a Realtime API with RethinkDB and Pushpin
The effects of supplements (primarily methylfolate and methylcobalamin) seems to depend on which mutation C677T, A1298, or both, and whether the person is homozygous or heterozygous.

However, the biggest difference is having an answer, instead of doctors guessing and prescribing thyroxine or antidepressants (which can make life so much worse).
And the year the month is in.
Are you crazy? What are you going to suggest next? Blinds?!
Google will tell you when its driverless car crash
Writing a blog post can have many correlations to how a person works in a company/team.

This post has no time put into it at all. The author may be lazy or not committed to any work/quality.

The blog post has no effort at all put into explaining the circumstances, making it convoluted. The author cannot clearly communicate context, making it painful to work with the author on a team that shares complex ideas (such as algorithms, or system wide changes).

There has clearly been no editing on this post. The author is sloppy, and does not research what goes into good work.

The story is poorly written, even around simple details. The author cannot communicate simple ideas clearly.

That this article got through any sort of PR shield at all (likely they have none?) is strange enough, but it may also imply the author does not care/seek out team feedback, and may not be willing to entertain the ideas of colleagues.

It actually seems like typical founder writing (and behavior). A quick, efficient one-off, with just enough information to get by.
The problem with this view is that fear of failure is a strong demotivator for many people. Want to avoid failure? Never do anything interesting.

It's a mistake to think that fear of failure is the only or even the best motivator, and I would be extremely leary of betting on anyone who was primarily motivated by fear of failure. I want to back someone who desires success above all else, not who fears failure. They are quite different things.
My argument can't be aimed at fast food because most people find that it tastes nice. You could indeed make a different argument based on price and health against it. The point of my argument is that you don't need to choose between healthy and fast (Soylent), or tasty and fast (fast food), or healthy and tasty (elaborate home cooking). With just a little bit of know-how and practice you can have all three.

I'm not talking about making this for lunch, but for dinner. Which lunch is available to you of course depends on where you work (though even in that case you can take something with you, like muesli+yogurt+fruit or a sandwich, but I can understand why some people might prefer Soylent in that case). Unless you eat 100% Soylent you are not going to save much time on grocery shopping because you have to go to the supermarket anyway, so you might as well take a few packages of vegetables with you. If I understand it correctly then Soylent requires washing a blender and a glass, not much different than washing a wok and a plate (and you don't even need the plate).
Sure he did. He just wasn't CEO when he (and the four other founders) started it.
That only makes sense if you're taking time off work to cook, which most people aren't. Otherwise you weren't getting paid for that hour anyway.
If you look at a sample of people who started companies and find a few repeat winners, you probably will have found repeat winners produced by chance. But if you look at a repeat winner who keeps producing wins after you've started watching them, the same argument doesn't apply -- odds are overwhelmingly against the hypothesis that they continue winning randomly.
Or because it does satisfy much of the Kay criteria for OO and encourages such programming styles.
The first business mentioned in that article certainly did structure their transactions with the intent of avoiding reporting regulations, under the advice of their accountant:

Convenience-store distribution is a cash-intensive business, and Hirsch said his accountant advised him that he should keep the company's deposits below $10,000 because banks didn't like the paperwork involved with Currency Transaction Reports.

The article states But there was no evidence of criminal activity, not that there was no evidence of intent (as the section I quoted makes clear, the intent was obvious).

Please note that I'm not making statements in favor of the law in these comments, just characterizing the facts as I see them.

ETA: as I keep reading, the second business was also intentionally avoiding the reporting requirements (after a teller told them how). The third one does not directly state that they were trying to avoid the reporting requirements.
Name: Dayswork

Pitch: Good software estimates are hard, get time estimates from real industry experts. Submit your brief (we also help you refine it etc.), choose how many estimates you'd like (2, 4, or 6), and then view & compare your project time estimates results from our experts.

Target(s): Non tech peeps wanting a "ballpark" dev. time estimate. Or, devs/agencies wanting to sanity check an estimate they have already done.

Stage: MVP - Solo founder.

Love to get feedback on this... The main idea behind it is: Estimates are hard, some other opinions would be good. Properly defining & communicating requirements is also super hard - so the submission workflow goes deep into that (with clear examples etc).

Would love feedback on pricing... How much would you pay to get 2 time estimates on a software project (from experts, familiar with the tech etc.)?
Cameron's "experiments" (torture) seemed to revolve more around sensory depravation and electric shock therapy (one of the major side effects of electro-shock is serious memory loss).

This does bring up an idea I had from years ago where instead of making prisons as boring as possible we make them amazingly interesting places where the prisoners have to use their brains constantly all day. The idea being that all this information will slowly push out the ideas and thoughts of the old person to be replaced with a new ideas and memories that make the person less likely to commit crime once released. The person should come out of prison a better person than they went in.
Yes, the CC list will subscribe you to email notifications about the bug, and does not really indicate support, only interest in receiving email notifications about the bug.
... most of these are intertwined. Is there more significance to your comment, or is it just a nitpick?
Of course, there's plenty of people in their 40s experiencing the struggles you describe. But, as a matter of fact, I've met as many of them in the 20s and 30s range with the same problems (maybe not so tired, but troubled and egomaniac nonetheless).

In the context of entrepreneurship, however, I find that those traits are much less prominent, regardless of the age.

In my case, today I just sold my part of the company I founded 10 years ago to my cofounding partner. Not a big, glorious exit, BTW. Just the opportunity to try again, and get better results this time.

Being 46, I do feel much more aware now that I felt 10 years ago. Aware of my strengths and aware of my limits. And aware of my motivations.

However, I must confess that, ten years ago, I had the same image that you describe about fortysomethings. That's why I decided to start my own company then, to avoid becoming one of them.
Isn't that what SoMa is? No (or significantly lesser) height restrictions, where the Salesforce tower is going up, and bordered by Bart, Caltrain, and the Embarcadero line.
I thought this was why people carry around phones - why remember anything when you can just ask siri?
HN was the same about Node too. In a year we will see the same articles about Rust.
I've been doing iOS development on a PC for years.
There are a lot of risk reduction reasons and also a lot of ethical and moral reasons. These are all legitimate and worth considering, and hopefully another commenter or two can elaborate and point you to resources.

But I want to take a moment to highlight the legitimacy of sentimental reasons in this case.

Humanity is an important and closely guarded trait, for reasons that some have characterized as "self-evident". One could characterize "civilization" largely as a mechanism for preserving humanness and helping it flourish. When it comes to deciding the genetic fate of the species, these rather sentimental ideals about what makes life worth living are perhaps one of the most important decision criterion.
Sodium needs vary by person; some people require a low-sodium diet, some average, and some higher than average.

While I find the current Soylent interesting, I'm also looking forward to a future Soylent 2.0 that's customized to a specific person's nutrient needs.
As I said, different perspectives on the power relationship between USG and megacorps.

It's like someone used a security bug in NT to load a hypervisor. You could say that NT was still "the kernel", but most of the important stuff goes on outside of it.
To elaborate a bit on the sibling comment here, Rust makes things a bit more explicit than Go does. A Go interface type is actually a pointer (of sorts), since you don't generally want to store things of different types and sizes in a single array. For example, if you have:

type StructOne struct {
field uint32
}

type StructTwo struct {
field uint64
}

It's pretty clear that these structures are of different size. Now, if both of these structures implement the "Foo" interface, we can't simply make an array like []Foo, since we'd have no practical method to index into the array. Go solves this by making []Foo actually be an array of pointers.

However, Rust's philosophy is, AFAIK, "be explicit about the cost you pay". So, if you want to make an "array of things that implement Foo", you need to explicitly put the "things" behind a pointer, or a Box<>. So, you get:

struct MyStruct {
arr: Vec<Box<Foo>>,
}

Which makes it explicit that you're storing a "list of pointers to things that implement Foo". Of course, the nice part is that you can use generic syntax to make an array that doesn't use pointers, like so:

struct MyStruct2<T: Foo> {
arr: Vec<T>,
}

In the above, you can only store items of a single type in the `arr` field, and the generics constrain that to be only types `T` that implement Foo. The upside is, however, that you don't have any pointer indirection (and the compiler monomorphizes - i.e. generates new code for each generic implementation), so your code is probably faster / easier for LLVM to optimize.
What is "Single User Git"?
Google takes search outside the box
You'll have to create a backup service to periodically export your annotations.
Front End Developer Opportunity  Remitly [pdf]
This sounds like a god damn nightmare. Are there people that want this?

Didn't we just go through this the other day with Torvold's latest rant? Don't make me sit here and remember half the spec and precedence for operations. That SLOWS development speed, not increases it.
“Science, Technology, and Exaltation,” Keynote Speech by Ralph Merkle
You can buy a Tesla but you can not match the beauty and 'statement' this babe[1] makes when entering the scene. Accordingly, you'll probably be wearing something like this [2] instead of ugly digital watch.

Well put, people who can afford a Rolex, a Breguet, etc. Don't give a damn about some silly digital toy.

[1] http://www.astonmartin.com/en/heritage/past-models/db5

[2] http://www.breguet.com/en/timepieces/classique/5140
Software Development Engineer  Remitly – Mobile [pdf]
Not an American and have never seen it live, but in the picture I see a beautiful building and not a monstrosity.
HFS/HFS+ are very very similar to the BeOS filesystem.

Dominic Giampaolo developed that, so I assume that's what's being referred to.

There's a great writeup of the file system here: http://www.nobius.org/~dbg/practical-file-system-design.pdf

In particular, the labels and how they worked in BeOS are a big part of HFS, when Finder says it's "indexing" it's indexing all those extended attributes (among other things).
I tried MREs for a while - they are fine for camping but too high in sugar and salt for regular eating. They are also very bulky (two of these per day - http://usarmy.vo.llnwd.net/e2/c/images/2013/05/30/298090/siz...) and leave behind a lot of trash.
This one contains some solid insights, mostly about doing a better job of proving demand: https://medium.com/@michalbohanes/seven-lessons-i-learned-fr...

But...

There is no business idea I cannot kill using a sufficiently cold and objective evaluation. I can show the demand is not there, that it doesn't solve a customer pain-point, that the price is too high, that the model won't work in this market, that the technology won't scale...

At the end of WWII Vannevar Bush, the head of the American military rocketry program, said that human beings would never go to the Moon because you'd have to take a rocket the size of a battleship, stand it up on end, and launch it into space, and this was obviously impossible.

Prediction is hard, especially about the future. Entreprenuership is fundamentally about courage, because you've got to jump off that ledge knowing the odds are you'll fail. If you dig too deeply or look too closely at the problem you may never start, because the risk is always going to be unacceptably high to any sane person.

So it's important for entrepreneurs to balance their optimism against reality, rather than just giving in to realism and sticking with the day job.
C# has had excellent concurrency support for quite some time, and is most definitely a utilitarian language.

Of course, the elephant in the room is needing a windows-based infrastructure ... but if that's not a huge barrier, it's not an unreasonable choice.
Business success is nothing like winning a sporting championship. Sports are specifically constructed to let talent and skill shine through and impress the audience. Business is practically the opposite of that.

You don't know all the skills you need in advance.

You don't have thousands of hours of live and taped competition directly between the best in the world to study.

Progress towards those skills and a championship/success isn't directly measurable.

The ground may shift out from under you overnight (few pro sports rule changes have caused players or teams to go bust or lose all hope of winning... compare that to any widely-felt economic event).

The environment facing an entrepreneur is far, far more chaotic, which is why a first-time founder without deep personal reserves is going to be far more at the mercy of luck than Lebron James or Russell Wilson.

(And even then, there are fierce debates over the role of luck when it comes to individual's career accomplishments. Drop Lebron onto MJ's Bulls, and how many titles does he win? Drop MJ onto the mid-2000's Cavs, and how many does he win?)

(Edit for fixing inconsistency between which directions I was making the comparison in.)
As I understand it, GO makes it so you can use both a pointer or the object itself to access it methods.

And when you define an object method (or I don't know how it's called when you do this:)

func (*string) uppercase(){

// make uppercase

}

Then by saying you use a pointer means you will modify the value when you do this: mystring.uppercase()

So it's not really pointers, it's more an idea of pointers.
Excellent points - you changed my thinking =)
So frustrating! I want to make a blacklist of companies that do this sort of crap and then expose an API to it.
In some ways, this is correct. Go is much more simple and consistent than Ruby or Java, has a better deployment story, and better tooling in some ways.

As a language, it's much less enjoyable to write. Yes, the concurrency primitives are much better, and that's a good programming tool. But to a developer coming from Ruby, code is often needlessly repetitive and obtuse to write. It ends up being overly verbose, full of copypasta, and much less expressive.

It's got it's niche – I've found it useful for writing small command-line utilities, and it's been surprisingly helpful at putting together a good deploy story for some work I've done on the Raspberry Pi (with the benefit of being well-structured and reasonably performant).

But I wouldn't like to use if full-time – mostly because it's just so weirdly irritating to write.
> That's how it should be, but is it in practice?

Regardless they end up back in society.
> notably Dominic Giampaolo

His book on file system design is still a must-read, imo.

http://www.nobius.org/~dbg/practical-file-system-design.pdf
I don't tend to have butter (or margarine spread) in the house. Not to mention I would have to cook them and clean the dishes :)

I've tried them buttered, steamed, roasted, in a casserole, mixed into Mac&Cheese, and 1,000 different methods my mother tried to sneak green beans into my diet as a child. I struggle to stomach them no matter how they are prepared.

I have little concern for trying foods I dislike. I make an attempt to revisit them every few years (ie. I hated sushi as a child, I absolutely love it as an adult) but don't actively try different recipes or "force myself to like it".

The few foods I eat actively, I eat because I enjoy. The other foods I eat because I guilt trip myself into eating healthy. I'd live off nothing but rigatoni with old-school traditional Ragu sauce day in and day out if I could. But I limit that to once-a-week and figure out more balanced and healthy meals the other 6 days (if I eat at all).

Soylent would likely do wonders for my dietary health.