@lindsay.at :: Projects :: Remix (music) :: API Overview
The Echo Nest Remix API (“Remix,” for short) is an open-source programming framework written in Python. It provides numerous classes and methods to deal with recorded songs, analyze them, inspect and manipulate the resulting analyses, and manipulate audio based on that information.
Related cards:
LÖVE - Free 2D Game Engine
LÖVE is an unquestionably awesome 2D game engine, which allows rapid game development and prototyping in Lua.
JSON APIs: Default design for common features
When you build a JSON API you need to come up with a style to represent attributes, pagination, errors or including associated objects. Instead of reinventing the wheel, you may reuse successful API designs.
JSON API
[JSON:API](https://...
InfoQ: How to Design a Good API & Why it Matters
A well-written API can be a great asset to the organization that wrote it and to all that use it. Given the importance of good API design, surprisingly little has been written on the subject. In this talk (recorded at Javapolis), Java library desi...
gerrit - Project Hosting on Google Code
Gerrit is a web based code review system, facilitating online code reviews for projects using the Git version control system.
cortesi - The impact of language choice on github projects
Are there major differences between projects in different languages? Is it possible to quantify these differences? I decided to try to gather some hard numbers.
Hoptoad and Javascript, Sitting in a Tree, S-E-N-D-I-N-G - GIANT ROBOTS SMASHING INTO OTHER GIANT ROBOTS
We didn’t want to leave front-end developers in the dark when their Javascript throws errors, so we’ve added a Hoptoad notifier for Javascript!
wkhtmltopdf - Project Hosting on Google Code
Simple shell utility to convert html to pdf using the webkit rendering engine, and qt.
The Pragmatic Bookshelf | Tell, Don't Ask
You should endeavor to tell objects what you want them to do; do not ask them questions about their state, make a decision, and then tell them what to do.
Bill de hÓra: Managing large stories on agile projects
I've seen this granularity problem on every project, product or program I've worked on. Often in non-agile methods it comes it up in the form of traceability requirements on top of the actual requirements.