Viewing profile — hendershot

what the author is talking about in a short rant is classical vs mockist TDD. for better content on the subject: https://martinfowler.com/articles/mocksArentStubs.html https://mart…

Why would you want to? when the same unit test coverage will run under 1 minute, and be smaller easier to understand/change tests and can all be done on your laptop. it all depends…

Integration, E2E, and smoke tests are generally slow, flakey, hard to write. They should not cover/duplicate all the cases your unit tests cover. They are good at letting you know …

I've seen the following from pairing Junior and Senior engineers: * Really talented junior engineers blossom extremely quickly. They will easily be a multiple better after a year v…

Paring with Ping Pong TDD works really well. Improves paring with frequent driver/navigator switches and improves TDD by having the navigator thinking ahead. Been doing it almost e…

The problem often is that scrum (or any iterative process) fails when it's not paired with good XP engineering practices. There's constant learning and change on the product side, …

Yup. Play is built on top of Netty and adds value so my point is why not build it as a re-usable library (or set of libs) vs a Framework, it's really not any more difficult.

I like Play, currently using for a personal project. But ultimately looking forward to the day where frameworks are replaced by mixing and matching libraries where you get just wha…

+1 on keeping things simple and not using a "F"ramework for every concern from the very beginning. >in Java you have to make those architecture choices day 1. That's just not true.…

Sometimes solving the hard problem means jumping into a teamroom in front of a whiteboard and doing some serious brainstorming / design. That is the one thing that is very hard to …