TDD does not take extra time. Writing tests _first_ is not overhead because they force you to think through the problem and partition it properly. You’d have to do that thinking anyway.
Testing after the fact IS overhead because you did all that thinking already.
"This is the hardest team in the world to make for a reason. With our group and how competitive it is, if you're top 3 in the U.S., you have a real shot to get a medal." – @TrevorBassitt30
The @ashlandeagles_ is headed to @WCHoregon22
Full interview: https://t.co/wpJ0ALgCwE
"Every now and then you just have to throw your hands up in the air and appreciate how much better some people are at running than you. I’m just happy to watch."
-@TheRealMerb sums up running quite succinctly here, folks
You could argue @goashlandeagles is the best track and field collegiate success and post collegiate success in @NCAADII.
When I say track & field I mean all events, across the board success. Top of my head I can list greats in PV, SP, 400h, 400m, 800m (all diff people)
(On going out hard and dying)
Cycling: What an incredibly brave performance! He rode heroically for 150km and his team will be proud of the way he attacked the climbs. The strength of the peloton was too much but so much promise for this young rider
Running: Wow very dumb idiot
"I don't have time to write tests".
Do you have time to:
1. Run the app manually after each change
2. Investigate and fix broken builds
3. Investigate and fix QA errors
4. Investigate and fix production errors
Add all that up. Writing automated tests *saves* time.
Morgan Stanley’s model for US economic re-open, via @sameepa:
MAY: Peak of new cases
JUNE: Serology testing widely available, 1st wave of people return to work
SEPT: Schools open
OCT: Potential vaccine for health care workers
MARCH 2021: Vaccine potentially widely available