damethos

I personally feel very lucky that I experienced the days were we had to wait for the updated MSDN DVDs to arrive so we can check out the new docs/code samples and make changes to our drivers and docs! Good times.

I am experiencing the same. I have decided that the only way to use these tools (at least for now) and at the same time to avoid the janky crap and understand what's going on with the codebase, is to ask from the model to work in very small committable batches which I can review without my head exploding, commit in branch, repeat. I feel much better now and I catch things fast and early.

Are you implying that there isn't an operational cost for maintaining the infrastructure to support cashless payments or that it's cheaper? Unless I see actual numbers I am not convinced and that 1% you mention sounds completely random to me and not really "the true answer".

Nostalgia activated. I now have to play Grim Fandango! Loved that game!

The article had me at "[...] every new feature is the one that's going to be the one (but certainly not that one that was supposed to be the one during the previous sprint)".

I have fought way too many times the new "the one" feature. Just ship it, it's already good enough, everything else just adds cost, especially psychological cost to the team.

I am not a Fastmail user but I completely doubt this. I have been using Gmail for 20 years and I have never seen a spam mail land in my inbox which has always impressed me. Everything else I have used from time to time does miss a few, which I guess it might be acceptable if you want to move to another host.

I still read programming books, especially if I want to check out a new language and get the gist of its capabilities and how are things are done in that specific environment. Also I prefer to read a book written by an author that I know has the experience and the insight to actually write the book than read random sources on the internet. Or maybe I am just used to it.

Time to re-re-re-re-N-watch this!