Is the call for "developer focus" a selfish complaint from precious snowflake employees? What right do developers have to ruin the design trend of great-looking open offices where collaboration magically happens? This week, we discuss how we feel about the need for managers to talk to employees at all times vs the need for folks to get work done without interruption.
- Randy has a potential client for Fractional CTO work, meaning a consultant working in a part-time CTO role for their startup
- Don discusses the University of Florida incubators, Sid Martin Bio tech institues, and two buildings off-campus for an innovation hub/co-working space
- Randy mentions that Northwestern University has its own incubator space, called The Garage, which is taking charge of the community they have, energetic students, and supporting them with programs around entreprenuership
- Research at the university level and research in the entreprenuerial community are not all that different, at least in what they aim to produce in the end: products, patents, and licenses
- The ability for any employee to have quiet-time, control of their environment, that does not interrupt their train of thought and work-in-progress
- The ability to chain a number of pieces of work together, along a track of time, without being interrupted by noises, temperature, weather, or other people
- It takes people a chunk of time to regain focus after interruption
- People think that if you increase collaboration, it will help team productivity, but that's questionable logic
- "The trend for open offices is a result of selfish management practices that think their ability to talk to anyone at any given time supersedes those employees' needs to be focused on work"
- "Open offices look great, it looks like work is getting done"
- "The idea that an open office works for everyone is extremely short-sighted."
- "I would bet that a big part of your team's productivity problems are a result of your ability to constantly interrupt folks on your team"
- "Slack is anything but a focus-driven tool. It is synchronous communication for the most part."
- Randy had a lot of respect for a developer that would routinely "go dark" on Slack to get work done
- Slack does have features that allow a person to "look offline" or avoid notifications
- Slack is less intrusive than an open cattle-call office space, but it's not that far off on the alert/notification effect
- The phone was also synchronous, and interruption-based system, but it was easier to avoid
- "Slack is not the reason for the problem. It's not the tools, it's the managers establishing how the team should communicate"
- The need for developer focus is not new. Joel Spolsky blogged a ton about dev focus and had a sales pitch of giving developers a door to close as a perk.
- "A good developer doesn't want an office for status, they want it for focus and productivity"
- "Developers are not asking for privacy and quiet because they are special snowflakes. They are asking for it because they want to meet the deadlines and the needs of the company they work for"
- My team members get to choose how and when they receive alerts, not me. They get to choose how their focus is managed.
- Randy recommends Netlify for static/single page hosting due to their an easy deployment process
- Don recommends a book Red Notice by Bill Browder about one man's attempt to fight back against Russian politics and power
- Clean out your closet of side projects by Don VanDemark
- The new Randy Burgess website
- Using ActiveStorage with UUIDs on Rails 5.2 and PostgreSQL 9+ by Randy Burgess
- Bulldog 100
- UF Sid Martin Biotechnology Institute
- UF Innovate
- iBubble: The first autonomous diving drone that follows you and captures beautiful footage, hands-free.
- The Garage at Northwestern
- Interruption is Not Collaboration by Wailin Wong
- Trello, an asychronus communication tool
- Joel on Software
- Jason Fried on Inc Magazine
- Signal vs Noise
- Remote: Office not required a book by Jason Fried and DHH
- The Calm Company an upcoming book by the folks at Basecamp
- Patreon: CTO Think Podcast is creating Episode Transcripts for Accessiblity
Thanks for listening to the CTO Think Podcast.
Shownotes and previous episodes can be found on our website at www.ctothink.com
Reviews on Apple iTunes are always appreciated and help promote the show.
Patreon contributions help us to produce transcripts, which allow people that are deaf or hard-of-hearing to access the show.
For questions, comments, or things you'd like to hear on future shows, please email us at firstname.lastname@example.org
Voiceover work by MeganVoices.com
You'll hear from us next week!