Introductions00:01:38 On’s first exposure to tech00:06:04 Game development adventures00:11:12 The difference between university and real-world experiences00:17:43 A context switch question00:24:41 Points of frustration00:30:53 Build versus Buy complications00:32:06 Code reviews00:39:58 Quality of code00:45:12 Using callouts for the right reasons00:49:57 Code reviews can be too late sometimes00:52:11 Using social interaction as pre-review orientation00:57:03 How not to use code reviews01:01:35 Where Wilco helps programmers learn01:09:11 Working in Wilco01:11:49 FarewellsResources mentioned in this episode:Links:On Freund:Linkedin: https://www.linkedin.com/in/onfreundWilco:Website: https://www.trywilco.com/Twitter: https://twitter.com/trywilcoLinkedin: https://www.linkedin.com/company/trywilco References:Micro-Adventure:https://en.wikipedia.org/wiki/Micro_Adventure If you’ve enjoyed this episode, you can listen to more on Programming Throwdown’s website: https://www.programmingthrowdown.com/ Reach out to us via email: [email protected] You can also follow Programming Throwdown on Facebook | Apple Podcasts | Spotify | Player.FM Join the discussion on our DiscordHelp support Programming Throwdown through our Patreon

Programming Throwdown

Code Reviews

Code Review

Mortal Kombat vs. Minecraft

Do Computer Science Degrees Prepare You for the Job?

Bradley: The preparedness of programmers for jobs

How to get your first job after university

Working on a semiconductor manufacturing machine

How to Get Out of the Infirmary

What Came Next After Working At WeWork

Build vs. Buy in the Home Automation Market

Code Review

What are Code Reviews and Do They Matter?

Code Review is a Shared Ownership

Code Review: A Pet Peeve

Code Review: Tailoring it to the Needs

Code Reviews: Why They're so important

Should We Have Made Wilco?

Inventing the Future of Software

How to Write a World-Class Quest on Wilco

Wilco Hiring: Open to Experienced Developers

Pun of the Day