software development

now browsing by tag

 
 

Presentation on FreedomBox and Pokemon Go at ActivateTO

On 17 October 2016, I gave a presentation at ActivateTO, a Toronto-based non-profit that hosts a speaker series. It was located at Toronto City Hall which is a very nice venue, very organized with great audio/visual gear (projectors and mics). My presentation included FreedomBox. The topic that night was PokemonRead 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

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

The Software Estimation Struggle

Software estimation research is … improving estimation techniques so that sophisticated organizations can achieve project results +-5% of estimate results… …the typical software organization is not struggling to improve its estimates from +-10% to +-5% accuracy. The typical software organization is struggling to avoid estimates that are incorrect by 100%Read More

AngularJS: testing services that use $resource

when you’re writing services that interact with the backend, you may need to break your service into two services to avoid mock objects. And this is okay!

The GNU Coding Standards need an update

There was some discussion a while ago on the Libreplanet mailing list about creating a wiki called the GNU Developer Network, somewhat similar to the MDN (Mozilla Developer Network) and the MSDN (Microsoft Developer Network). I think it’s a great idea, free/open source developers need a wiki for more discussionsRead More

Systems Past: the only 8 software innovations we actually use

Systems Past: the only 8 software innovations we actually use Interesting post and he makes a good point: I find that all the significant concepts in software systems were invented/discovered in the 15 years between 1955 and 1970. What have we been doing since then? Mostly making things faster, cheaper,Read More

The Chaos Report: a non-existent software crisis?

The Non-Existent Software Crisis: Debunking the Chaos Report I don’t agree with the article and the survey questions to me are flawed, however I cannot respond to it yet until I’ve finished reading Software Development FailuresĀ šŸ˜‰

How to be a Programmer: A Short, Comprehensive, and Personal Summary

How to be a Programmer: A Short, Comprehensive, and Personal Summary Lots of good stuff in here.

Managing Software Engineers – Philip Greenspun 2002

Managing Software Engineers – Philip Greenspun 2002 I submitted this article a long time to reddit, and it still has lots of great advice in it. Some great quotes in there: Negative reinforcement can work if the organization is extremely tightly managed, if the consequences are small and immediate (usuallyRead More