Links (12,295 links)

Spend money on tools, basically.

git pull has two problems:

* It merges upstream changes by default, when it's really more polite to rebase over them, unless your collaborators enjoy a commit graph that looks like bedhead. * It only updates the branch you're currently on, which means git push will shout at you for being behind on branches you don't particularly care about right now.

Combines multiple API documentations in a fast, organized, and searchable interface.

Via ttscoff.

Sleep, it turns out, may play a crucial role in our brain’s physiological maintenance. As your body sleeps, your brain is quite actively playing the part of mental janitor: It’s clearing out all of the junk that has accumulated as a result of your daily thinking.

The Node environment seems to have shifted from "use this for your one-off, high performance, I/O dominated real time service" to "hey, you know Javascript, build all your webapps in node, build your command line tools in node, build everything in node, since it's the lingua franca of the web." This latter trend sucks, and results in things that to me seem absolutely bonkers, like the Vows test framework.

Via monospaced.

A portable tool for managing a single set of dotfiles in an organized fashion

M*EAN (*MySQL, Express, Angular, Node) - A Simple, Scalable and Easy starting point for javascript web development with a relational database ORM

The "clunky, insecure but simple and reasonably effective" strategy.

Via monospaced.

[Bookmarklet to] take a selection -- including headlines, links, and images -- and converts it to Markdown using Marky.

EAT LIKE YOU GIVE A FUCK

Via russelldavies.

Via tomtaylor.

Let's say someone's made a pull request from their fork into your repository. Here's how you can check out her changes on your machine and verify that everything is a-okay.

Myth is a postprocessor that lets you write pure CSS without having to worry about slow browser support, or even slow spec approval. It's like a CSS polyfill.

Here's a more nuanced view: speed matters, and you can be really successful developing important, business-critical software by emphasizing speed over quality. If it's a problem domain you're particularly familiar with, especially if you have a lot of tools, frameworks, and libraries to help you, you can get an impressive amount of work done.

As you continue to work, you'll slow down. At some point—about six weeks is my guess—you'll actually be going slower than someone who's focused on quality. They'll speed up over time (asymptotically), and you'll continue to slow down (also asymptotically). You'll still be ahead of them, though, because you got so much done in that initial burst of energy. Your life will start to suck, though, and you'll be looking forward to when the project is done.

Eventually—about three to six months, I'd guess—you'll fall behind. You'll be going so slow that your initial advantage will have been erased. Luckily, you now get to hand the project off and start a new one. Win!

Three to seven years later, your code will be thrown away. It will be so expensive to change that it no longer makes economic sense to maintain. If it's still relevant, it will be rewritten at great expense and even greater opportunity cost.

Well said.

Via jamesholloway.