This is me. I have an easier time reading the plays and movements of players in real life thanks to my video game days growing up. I don't really game anymore but I do spend almost as much time in the gym and playing sports now than I did playing games. My brain is still just as quick and now I'm in great shape and cut.

What a failure your statue of liberty was...french made.

Well that is not how one does agile in a team environment. The scrum master changes all the time, all he does is ensure the scrum meetings are smooth and concise.

Manual! http://www.1000bit.it/support/manuali/commodore/vic20/A_Beginners_Guide_to_Real_Programming_Discover_your_VIC-20.pdf

I had a commodore VIC-20 and learned from the manual. Whatever I coded in basic was saved to CASSETTE tape hehe. Ahhh the memories.

Yes, even my old game company was doing some game engines using it.

Since when is code review part of agile?

So instead of billions of solar systems like ours, there are just millions. And in at least thousands of those millions, there is probably some poor shmuck like myself posting from their parents basement!

It doesn't solve every problem but it can darn well replace the old waterfall development practice which is/was used for pretty much every project. If agile works for making AAAA games as well as a wide variety of projects involved in game development, HR systems, IT, finance, etc...why wouldn't it work for your projects?

Why do I keep seeing the notion that agile speeds up coding? That is simply not true! All it does is releases certain features sooner so the client can approve of them instead of releasing everything at the end and having an "oh shit, he changed his mind" moment when it's too late. As for the documentation aspect, we had several tasks in our iterations to document code, use cases, etc. The team lead or project manager usually took care of obtaining the specs from the clients and writing the documentation for it.

Well you are doing it wrong. In my experience (I worked in one of the top 3 video game companies in the world) it worked like it claims to do. A different team member was the scrum master every week, assured that the daily meetings were short and concise. We had our iteration planning done properly and our death mortem meetings at the end of each iteration to discuss improvements and fails. Once your team gets into the groove, your team velocity is calculable and improvable...maybe you guys were just lazy?

All agile does is to make the client more involved in the shorten development cycle, the work more accountable (as in changes and implementations are done earlier), and the team members better team players. Agile has nothing to do with workplace problems.

I own a Samsung Galaxy S1 and a HTC Windows Phone (bought around the same time 3 years ago give or take). To be fair my android phone is riddled with reboots, performance issues and such while my windows phone is as snappy as ever. I do use my android more every day but my WP7 is where I code on, develop apps and push it to its limits more.

The trick is how he created the earth without spin...his light must have rotated around the earth to create night.

So god was toying when he gave the earth initial spin since he knew he was going to create the sun later. That is how for 2 days the earth had artificial light from him thus creating day (and the spin of the earth creating night)? Ah I see, got it!