DillonOpens in new tab, MattOpens in new tab & ScottOpens in new tab record an episode with some semblance of quality.
The gang dove directly into software's hottest topic: AI. We believe in using AI in your day to day job to be more successful.
In this episode we discuss;
- use cases for AI in software development,
- the fun tasks AI has taken away and,
- how to be successful using AI tools.
Listen to us explain navigating writing code in a world where more and more companies are increasingly advocating the usage of AI at your day job.
How do we continue to learn and grow as human while still maintaining fun, creativity and human interaction as an engineer in 2025?
AI is a powerful tool used correctly, however that AI will submit to confirmation bias and your role is to prompt AI to be as unbiased as possible to the best of your ability.
Episode Summary:
In this episode of The Bikeshed Podcast, hosts Scott Kaye, Matt Hamlin, and Dillon Curry discuss the role of AI in software development, sharing their experiences with various AI-powered tools and debating the impact of AI on engineering workflows, learning, and job satisfaction.
Key Topics Discussed:
- AI in Software Development
- The hosts discuss how AI has become integral to software engineering, particularly for writing code and automating tasks.
- Matt introduces the main discussion: how AI is used in development today and the broader implications of its adoption.
- Preferred AI Tools
- Dillon shares that he used Cursor until his company restricted it, forcing him to switch to Copilot, which he finds inferior.
- Scott uses NeoVim with NeoCodium and Avante, but acknowledges their limitations compared to Cursor.
- Matt relies on Cursor at work, noting that his company prefers it over other AI tools.
- AI's Impact on Development
- AI enables developers to work faster but can remove the learning process.
- Over-reliance on AI can lead to shallow understanding of code and a decrease in creativity.
- AI often acts like a junior engineer whose code must be reviewed, making debugging a larger part of the job.
- Using AI can lead to less collaboration with teammates, as developers tend to consult AI over their colleagues.
- Concerns About AI in Software Engineering
- Some engineers feel less engaged with their work as AI handles boilerplate and repetitive tasks.
- AI's agreeable nature can reinforce incorrect assumptions, leading to confirmation bias.
- Companies may use AI to increase efficiency and reduce hiring, raising concerns about job displacement.
- AI vs. Traditional Search (Google)
- Unlike Google, where users must craft precise search queries, AI allows more fluid back-and-forth conversations.
- AI can provide immediate answers but might not always offer the best or most optimized solution.
- The “No AI” Challenge
- The hosts agree to a two-and-a-half-day challenge of coding without AI, to evaluate how it affects their work and problem-solving abilities.
- Game Segment – “Two Takes and a Fake”
- Scott introduces a new segment where Matt and Dillon guess which of three AI-related tweets is fake.
- Matt wins this round, showing a keen eye for spotting AI discourse trends.
- What's New?
- Dillon is learning piano and music theory to slow down and disconnect from work.
- Matt is exploring Cloudflare workers and running Deepseek R1 locally for AI experimentation.
- Scott is focused on improving his Golang skills and debating Cherry Pepsi Zero vs. Cherry Coke Zero.
- Closing Thoughts
- The hosts discuss burnout, learning in tech, and how side projects keep programming fun.
- They tease next week's episode on burnout and side projects.
The episode wraps up with some lighthearted banter and a call for listeners to like, subscribe, and share.