We’re back with part 16 of Overheard in Product—a series where we round up all of the tantalizing conversations from product folks that you may have missed on the web last week.
This week, we talk about non-goals, advice for new coders, email as culture, and why your software project is scoped wrong.
Let’s get to it.
That’s always been a non-goal of mine
Gwen Betts, Director UX & Product Design at Rapid7, added to Sunhail’s tweet about the importance of non-goals.
Food for thought: The term biggerism was coined by the late visionary designer Charles Thacker, who often argued against it and preferred to keep his designs simple. How can you rail against biggerism in your work?
Guide and seek
Glitch said asked the world for some guidance to pass along to new coders.
Our favorite pieces of advice include being kind to folks—yourself included, to share your ideas, and that depth is more important than breadth.
Attachment issues
Trevor McKendrick, Chief of Staff at Lambda School, made an observation about email.
Food for thought: What language and value system are you participating in when emailing?
Bonus: Ship it real good
Erik Bernhardsson, CTO at Better.com, wrote an incredible article (and statistical model) about why we’re so bad at predicting how long software projects will take.
Erik’s thesis is that developers are actually pretty good at identifying the median time a project will take—it’s the mean that’s a more accurate predictor.
.png)
.png)