now browsing by tag


ACM partners with Social Coder: volunteer software development

The Association for Computing Machinery (ACM) has announced that they will be partnering with Social Coder, a site where software developers can volunteer their skills and time to help charities and non-profits of various types. Social Coder aims to match software developers with charities that are working on causes thatRead More

4 Things To Know About Teamwork

Here are the four things to know about teamwork: When the situation is tense, call a timeout, it’s the only thing that will work Information needs to be as close as possible to the team members that can make use of it Be aware of the message you’re sending asRead More

Quoted in “The Secrets Behind Great One-on-One Meetings”

I was recently quoted in the free ebook from O’Reilly, “The Secrets Behind Great One-on-One Meetings”.¬†As an aspiring interview coach for software developers, it feels great to offer advice especially on the subject of one-on-one meetings. It’s a great short ebook and very useful for those wanting to see theRead More

Setting Clear Priorities

To be a tech leader, rather than just a manager, you have to set clear priorities. There are two ways to do this and they apply in different situations.

How to apply cause and effect diagrams in IT and Software Development

Cause and effect diagrams, also known as Ishikawa diagrams, are one of 7 basic tools of quality. You won’t see them used very often in software development or IT projects though they should be. So today we’re going through what cause and effect diagrams are, why they’re useful, an exampleRead More

Culture Eats Strategy For Breakfast

SEMAT Kernel Example – walking through a small task

I’ve been reading the SEMAT Kernel book, The Essence of Software Engineering: Applying the SEMAT Kernel, and it provides a new way of managing software development projects. It’s supposed to make it easy to check the health of a project by classifying the major components, known as Alpha states inRead More

About Workplace Anarchy

The blog of Guile co-maintainer, Andy Wingo, has a series of blog posts detailing how the Igalia workers’ co-operative works: no master but that would be anarchy! time for money This is a very interesting subject as there are few workers’ co-operatives in existence…or maybe there are a lot ofRead More

Seven signs of dysfunctional engineering teams

Seven signs of dysfunctional engineering teams Preference for process over tools Excessive deference to the leader or worse, founder Unwillingness to confront technical debt Not invented here syndrome Disinterest in sustaining a Just Culture Monoculture

Effective Technical Leadership

Effective Technical Leadership Attributes of an effective technical lead: Knowledge Speed Awareness Activities: Block Unblock Redirect Decide Show Some key actions: Help create and stack rank project priorities Define best practices for issue tracking Coach other engineers Review code in detail and provide useful feedback Shield engineers from management whenRead More