I just came to say thank you, Beej! Your guide helped me learn networking and network programming. I love learning by example. Your guide was instrumental in my learning.
You typically do a 302 redirect AFTER the POST authentication. This feels more of a publicity stunt more than anything. It might affect very few use-cases. Bulk of the requests on the web are GETs anyway.
I agree. Facebook redirects a successful login POST with a 302, which then results in a GET to '/'. This is an extremely common pattern. Once you're making GETs, 'fresh' resources can be served from cache without revalidation [1]. This is basically the whole point of the fresh vs. stale distinction.
I am sorry if I come off a little rough. It is interesting how you made a data driven decision. However, it is common knowledge that Toyota, Honda are the most reliable cars. That common knowledge is derived from "crowd sourced" data. So while it was nice of you to confirm it with your analysis, it wasn't a necessary step and you would've saved some time and used it instead to look for deals focusing only on those Makes.
Also, next time you have graphs please use colors that are easy to distinguish - purple, pink, violet makes it hard to read the lines. Of course I should probably blame my low quality TN panel for it.
I would recommend learning a language and becoming an expert at it. Right now JS is positioned to be a great language for the web - for two reasons. It's the only, defacto language that can be used in the browser (dart is on it's way but right now it's not here.) Also with Node.js gaining popularity, you can use JS to build server side applications. It's a win-win situation if you know Javascript.
Are you kidding me? The number of tests has nothing to do with the quality of "testing" being done. You could have 5 billion tests and still miss obvious bugs. You're one of those who use LoC as a measure of productivity.
