-
Chiron Codex: helping software engineers become centaurs. APPropriate Behaviour
The book about all the things software writers do that aren't writing software.
FSF
Author Archives: Graham
My current host name scheme at home is characters from the film Tron. So I have: Laptop: flynn (programmer, formerly at Encom, and arcade owner) Desktop: yori (programmer at Encom) TV box: dumont (runs the I/O terminal) Watch: bit (a … Continue reading
On UML
A little context: I got introduced to UML in around 2008, at an employer who had a site licence for Enterprise Architect. I was sent on a training course run by a company that no longer exists called Sun Microsystems: … Continue reading
Posted in agile, architecture of sorts, design, software-engineering, sunw, tool-support
Tagged History of Software Engineering
2 Comments
I don’t use version control when I’m writing
Or rather, I do use version control when I’m writing, and it isn’t helpful. I’m currently studying a PhD, and I have around 113k words of notes in a git repository. I also have countless words of notes in a … Continue reading
By doing it and helping others do it
We are uncovering better ways of developing software by doing it and helping others do it. It’s been 20 years since those words were published in the manifesto for agile software development, and capital-A Agile methods haven’t really been supplanted. … Continue reading
What Xamarin.Forms taught me about data bindings
I’ve spent about a year working on an app for a group in the University where I work, that needed to be available on both Android and iOS. I’ve got a bit of experience working with the Apple-supplied SDKs on … Continue reading
Posted in mono, msft
5 Comments
Whoever “wins”, software freedom loses
I’d like to start by recapping the three distinct categories of interest in software freedom. This is definitely my categorisation, though only the third is novel and the first two have long histories of common recognition so this is hardly … Continue reading
Posted in FLOSS, freesoftware, fsf, GNU
1 Comment
One person per task
One of the least teamy things I see with software teams is limiting the maximum and minimum number of items of work in process – tasks, stories, whatever you call them – both to the number of developers on the … Continue reading
Posted in team
4 Comments
The Vizzini Effect
A bunch of the topics I wanted to discuss all turned out to have a common basis, so I’m going to write the post about the commonality using a couple of examples from the specific topics for illumination. Maybe I’ll … Continue reading
Posted in whatevs
Leave a comment
“Best practice” is less of a scam than claimed
Another day, another developer explaining that they don’t follow some popular practice. And their reason? Nothing more than because other people do the thing. “Best practices don’t exist,” they airily intone. “They’re really mediocre practices”. In one sense, they’re correct. … Continue reading
Posted in whatevs
Leave a comment
