The end result is that developers are spending more time upgrading their software to ensure that it continues to work with web APIs they’ve integrated with, and less time adding the features and refinements that would really benefit their customers.

This is true, but there is no alternative.

1. These integrations add value to the software for customers.
2. There is no “standing still” for technical platforms.

Everyone understands how platforms evolve and change over time, but the converse is also true. A platform that isn’t moving forward is falling behind in such a way that it’s effectively moving backward; dying.

Looks like some great new stuff in here – I see digesting, prototyping and testing in my future.

The only thing left with any color of consequence it the obscenely red subscribe button in the top left, which in keeping with the spirit of prioritizing the exactly wrong thing — you don’t even need to use very often.

Reminds me of the famous Ralph Waldo Emerson quote:

A foolish consistency is the hobgoblin of little minds[…]

Consistency in interface design, applied correctly, is very useful. It helps someone leverage existing knowledge and past experience to more easily use something new. Just making things look the same without regard to each thing’s features and functionality is exactly what you shouldn’t do.

A pretty thorough overview.

Thank diety, well-executed iOS support for Mute. I still content that the BlackBerry Gmail app is the most efficient Gmail interface I’ve used. Largely because of the keyboard commands and the fact there is always a selected message (e, m, delete, e, e, return, etc.).

Seriously, if you’re writing JavaScript as part of your job then you definitely owe it to future maintainers of your code to learning JS properly.

Some nice tips here, check out part 2 as well.

Many newcomers to git make the mistake of not taking the time to understand what git does, treating git like their old centralized source control system, and getting frustrated by the number of commands they have to remember to work with new concepts like the index (staging area), their local repo, and remote repos.

If you create a model in your head of what git is doing, you’ll be quickly on your way to mastery. Understanding what’s happening under the hood relieves you of the burden of having to memorize commands that seemingly make no sense at the outset. It’s like understanding how a formula is derived instead of memorizing the formula. Once you understand the model, it will become second nature to work with the various parts of your git repository.

Getting the mental model is the key factor when using any version control system.

This post is part of the thread: Version Control – an ongoing story on this site. View the thread timeline for more context on this post.

In reality, replacing Carp with Fielder nets you maybe three or four WAR, and unfortunately, this roster is not three or four wins away from being a legitimate contender. The M’s need to add something like +10 to +15 WAR this winter – a very tall order, and one that’s basically impossible if you throw your entire budget at one player.

Incremental upgrades at multiple positions insulates you from injury better as well.

WANT!