Coding Quickly; How?
nostrademons: You still consult Google and the language reference, but much less frequently.  Generally, if you want to get feature release time down to hours instead of days, you'll need to have the "core" of the language in memory.  That usually includes language syntax, string methods, data structures API, whatever basic IO library you're using (files/database/network), and various other simple utilities.  You'll know when you see them, because you see them repeatedly.The other point that I haven't seen brought up here is to have a clear goal in mind.  Know what you're building, because you can't build it otherwise.  Unfortunately, this is often kinda tough if you're developing a new product, because your initial ideas for what makes a good product are almost always wrong, and you tend to discover that as you start implementing.   So I've found it helps to think of your code as temporary: I know what I'm building this iteration, and I'll just go code it up and see how it works, but it's assumed that I'll have to throw it away anyway and build something better next iteration.