100k

"Most people use passwords. Some people use passphrases. Bruce Schneier uses an epic passpoem, detailing the life and works of seven mythical Norse heroes."

http://www.schneierfacts.com/fact/27

Is there a one-liner you can use from the shell that preserves order?

I used to do this, but now I use jq. The thing about the Python version is that Python doesn't have ordered dictionaries, so the output isn't in the same order as the raw JSON. jq doesn't have that issue which is nice.

Or it will extend to the previous generation, like in this Portlandia skit: http://m.youtube.com/watch?v=BLW0MnqH0r8

Orson Scott Card borrowed the name from Ursula K, LeGuin. You should check out The Dispossesed (about the inventor of the ansible). It's a great book.

Thanks. I was wondering about that, but had never heard of a split in a private company.

Can anyone who's been though an IPO comment on what happened to the early employees with their 0.1% stake (of the original 10 million shares)? Everyone understands that they'll get diluted with new rounds, but when I read that Dorsey's giving away 40,000,000 shares I wonder what happened to the poor sap who started with 10,000. Do companies typically issue more options or RSUs to existing employees? How many?

Ha. Thanks for the note. I'm reading on Mobile Safari, so without it, I would have thought Dorsey's message was just a single, ambiguous tweet.

Another excellent reason to write your own query parser instead of using Lucene's. Lucene's query parser is way too powerful to expose to end users.

I'd never heard of hellburner ships, but I _have_ read C.J. Cherryh's novel Hellburner (https://en.wikipedia.org/wiki/Devil_to_the_Belt). I wonder if that's where she got the name.

Yegge's "It's not software" from 2004 has a nice bit about microservices -- pretty ahead of the hype curve on that one:

> What if every "API call" were hosted by a different server? Well, you'd have a lot of flexibility in fixing any given call without needing to impact clients that don't use it. And it'd be easier to distribute it over multiple machines — it seems like it'd be a better design than the BEA WebLogic design, which is to run a few copies of your MonolithService on each of a handful of machines. There would be new problems to solve, but who's to say it wouldn't be a better design overall? We won't know unless we ask the question.

https://sites.google.com/site/steveyegge2/its-not-software

This looks really nice. The resources linked to are also cool:

http://www.daveliepmann.com/tufte-css/

http://sachsmc.github.io/tufterhandout/

Stripe is worth $5 billion. I don't think they hired the wrong people.

Sure there are tons of languages, with different strengths and weaknesses. The part that is important is that the early engineers need to be productive in the language.

Choose boring (to you) technology.

Only if the early engineers could write in a language that they were as productive in as Ruby. Getting Stripe launched was the key thing Stripe needed to accomplish. Everything else follows from that.

Pretty sure it was a standard list of questions - perhaps emailed.

Still, she is one of my favorite writers so it's interesting to read what she likes reading.

Sometimes they are. I really like it. I was selected to speak at a Ruby conference with a blind submission process. I remember feeling pretty good when one of the people who was a frequent speaker at Ruby conferences was whining on Twitter that their talk wasn't selected.

It's the future!

http://blog.circleci.com/its-the-future/

I liked looking through my parents' photos as a kid, but there was a couple of photo books at most. I can't imagine my (hypothetical) grandkids sorting through 60 years worth of digital photos unless software has gotten a lot better.

The busy work and stress of dealing with digital photos has actually caused me to take fewer photos. I have a preservationist bent and I just don't want to deal with organizing them.

Perhaps folks working at also-ran startups are not there because they are bad at picking but bad at getting hired[1] at more successful companies.

[1] This doesn't mean they're bad -- they could have trouble interviewing, or be subject to conscious or unconscious discrimination.

The rest of the site is a helpful database of tech companies considered to be "breaking out" which would look good on your resume/teach you a lot/maybe make you some money.

Very interesting!

Direct link: http://www.cosmographica.com/spaceart/pluto-predicted.html

You can do that: https://pinboard.in/faq/#filter_by_tags

The post ends with "Please don't forget to make backups!"

I love Maciej's sense of humor and honesty.

Now, to download my bookmarks...

You're right, but I think if an early stage company has "developers get quiet working conditions" in its DNA, it's more likely to persist as the company grows.

Having a quiet office is a big plus for me. I would definitely consider that when choosing a company to apply to.

This Immortal is terrific. And Zelazany in general. Dune and Lord of Light (https://en.m.wikipedia.org/wiki/Lord_of_Light) are a few of the only SF books I re-read on a regular basis.

Was looking for this comment.

Also ignores HOA dues (if the home is a condo).

I really enjoy reading how organizations have implemented continuous deployment.

One question I have which is not addressed by the article is how to deal with database changes. Every database has difficulty with schema migrations to one degree or another, but MySQL (which IIRC is what GitHub uses) is particularly bad. In my organization, we are VERY careful with any deploy that contains a migration.

(I suppose this is where GitHub's staging environments with real world datasets come in.)

One workaround I've considered is automatically deploying code that doesn't contain a migration (which is the vast majority) and forcing a more manual approach to database migrations, to make sure people are on hand to roll it back if necessary.

Tell that to DHH.