When I used to go to conferences regularly, I’d invariably post “95% white male, 4% non-white, 1% female”
First impressions at #BrightonRuby 10% female, 15% non-white
CTO @ | https://www.Collabor8Online.co.uk |
Nottingham Forest FC Podcast | http://eighteensixtyfive.football |
The Art && Science of Ruby | https://theartandscienceofruby.com/ |
When I used to go to conferences regularly, I’d invariably post “95% white male, 4% non-white, 1% female”
First impressions at #BrightonRuby 10% female, 15% non-white
It’s here!
Our interview with the actual Son of God - Forest legend and top-scorer Nigel Clough. Talking about working for the great man, how good that side was and being cheated out of European football.
Have a listen here https://podcasts.apple.com/gb/podcast/1865-the-nottingham-forest-podcast/id1151210661?i=1000713372417 or wherever you get your podcasts
@collin Another British cultural difference.
Food at football is terrible and they put no effort in - because no one spends any time in the stadium.
Pub before, arrive at the ground ten minutes before kick off, grab a pint during the 15 minutes at half time, then leave (inevitably disappointed) after the final whistle.
(Also it’s a chip cob where I come from)
Recently listened to a podcast (maybe @robbyrussell ?) with Evan Phoenix - where he said programming is a trade, like plumbing.
Because you learn by doing.
Therefore we should have apprentices.
I’ve often thought we should have apprentices but never realised why. Evan explains it perfectly.
A guy I hired, after about 6 months of working with me, said “oh, I get it now - this way of doing things is really useful”
When he left to get a (better-paid corporate) job he said “I’d never have got this without you” which is one of the things I’m most proud of, work-wise. https://mastodon.cloud/@jasongorman/114680599464493539
I've been watching developers learn TDD for 25 years, and I have a reasonable ballpark on what it takes. Roughly 1,000 red-green-refactor-commit cycles for the "rules" to become habits, and to scale the learning curve enough to make TDD work in practice on everyday code bases. If you progress from regular practice (e.g., 2 hours a week) to TDD-ing on most of your code (10-15 hours a week, apparently), you're looking at 4-6 months. And that, folks, is why "We tried TDD and it didn't work"