Our highest priority is ideas with value, and long-term value is greater than short-term value.
Software is a collection of ideas, formulated in a consistent manner that e.g. computers can parse and execute.
On a universal scale most products ever created have zero value--they will not even be possible to use fifty years from now, and the same goes for a lot of the software written for these products.
A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.
I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.
I'd love comments and suggestions about any of these.
I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.
I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".
| app.js |
| function Track(src, spriteLength, audioLead) { | |
| var track = this, | |
| audio = document.createElement('audio'); | |
| audio.src = src; | |
| audio.autobuffer = true; | |
| audio.load(); | |
| audio.muted = true; // makes no difference on iOS :( | |
| /* This is the magic. Since we can't preload, and loading requires a user's | |
| input. So we bind a touch event to the body, and fingers crossed, the |
