I have just read Why contracting developers refuse to go permanent. It says:
Working with legacy technology is something the developers I spoke to were not particularly fond of. They explained that these pieces of software are often built using outdated methodologies and poorly documented, if at all.
This is true, but my experience of dealing with several legacy projects which were written by contracting developers is like this:
This one is in Rails from three years ago and is full of CSRFs! This one is in Ember! This one is hard-wired to a five-year-old version of WordPress!
Yeah, it’s definitely the organisations which are the problem.
Today I took my 6 and 2 year olds into town to look around the Bristol Mini Maker Faire. It was really good and highly recommended.
We saw the Nao and Baxter robots from Active8 Robotics, a laser cutter from Just Add Sharks in action making press-out catapults, Raspberry Pi-powered wheel and track robots from Dawn Robotics and plenty of other things.
The kids were particularly taken by a couple who reverse-engineered childrens’ electronic toys like the Furby or basic motor-controlled toys and had them rigged up to simple push buttons to make them work.
They were sadly a bit too young to make their own shonkbot or get a Petduino (needs soldering) but watching the RepRapPro in action was a novelty, and we came away with some printed robot figurines which they treasured!
There was lots of other homebrew displays from people who used the Bristol Hackspace and I’m only sorry I can’t remember the names of their projects, but we all enjoyed it thoroughly!
Here’s looking forward to the next one!
I remember being a new developer and thinking that vertical alignment of code, whilst having some minor upsides, was just too damn ugly to do.
Now I’m much older and the less time I have to spend parsing someone else’s code before I can see if it’s correct or not, the better.
Vertical alignment, the vast majority of the time, does make code vastly easier to read, and although it may have some diff-based downsides, they tend to be one-off rather than perpetual. I know which cost I’d rather bear.
I have started working from home one day a week to help make up the hours I lose by taking my son to school in the mornings.
This week, on my day at home, I wanted to have a remote talk with some people in the office. “Easy”, we all thought, “we’ll just use Google Hangouts”. Wrong.
Laggy, constant dropouts, confusing UI. In the end I hung up in frustration and we IMd to exchange Skype details and used that, which was near-perfect.
It turns out that having more than 10 years experience of running a product does actually make a difference. Who knew?
Warnings and apologies: 6am introspection ahead!
I have a grudging acceptance that being older, and having two kids, but still being interested in Things as well as games, and, y’know occassionally going outside means I have to pick and choose what I spend my time on. I used to spend a lot of time, pre-kid, on taking some new or interesting piece of technology and making a thing. There used to be an XUL interface to this blog, for example.
But the edges are less clear to me now. Or at least the bits-only edges are unclear. There’s obviously a load of really interesting stuff going on with sensors and arduinos and the Raspberry Pi, and, one small step up from that, plenty of programmable toy robots.
I suppose that areas like Web Components are where the current excitement is – an area with a dense spec and, when I last looked, a dearth of examples.
I realised some while ago that I have the theme from Precinct 13 living deep in my subconscious, but it was only today, when Hip Hop On Precinct 13 came on the radio that I realised it was because the previous owner of the Commodore 64 I had as a kid was big into the demoscene and this was the theme track to one of them.
Not only did I have disk after disk full of demos but, amongst all the other disks for my 1541 drive, a copy of Elite and multiple save games which had either been hacked or which the previous owner had spent hundreds of hours building up. Docking was never so much fun as when it was a mere keypress away.
This was the computer, followed by the 286 which I wrote text adventure games on and modified Gorillas on, which got me into programming. I was never a hotshot PEEKer or POKEer, but even the basics, tediously copied in from a printed listing in a magazine, made me feel like a genius.
This August my son will turn five. He loves playing computer games, and with any luck, he’ll love the Kano he’ll be getting. Hopefully in thirty years he’ll be having flashbacks to images and sounds he spent hours exploring on the first computer he could call his own.
So, despite my sterling attempt to delude myself last year it’s been years since I’ve been a developer rather than a manager, and it was about the time of this change in my role that this blog started to die out.
All I have now are opinions and guidance, which the internet is far too full of for me to want to add to (plus I am still very management-naive in a number of ways), but there’s always been room to contribute something new in the form of code.
Off the back of that 57 day coding streak I decided to set myself a few other goals.
I keep a private blog where I write about my kids. Until the beginning of the year I’d posted about once a month and they mostly started with “its been far too long since I last posted, but…” and then detailed just the last few days, because when you’re the dad of a one year old, that’s all you can remember.
So far I’ve made twenty posts this year, including every day in March so far. I’m using an android app for this called goal tracker, although once installed it annoyingly just calls itself “calendar”. It has nice big ticks for each day, and this seems to be working.
This year and the end of last year ha vee also seen big streaks in “one second everyday” and “calorie counter fitness tracker”, the latter of which I use to feed extra data into my fitbit profile.
All of which is to say that I’ve been focusing in rather than out, and making sure I can make a daily commitment to something.
Being able to maintain even this somewhat small but continuous level of creativity (taking a video, writing a blog post, thinking about what I’m eating and where I’m going and how far it is), plus a couple of catalysts at work have helped me to think about the problems (and some more fun non-problems) I could get my teeth into both in and out of work.
Hopefully this will lead to a few more things being shipped to the outside as well as the inside, and can stop being worried that I simply don’t have anything to say anymore.
We have just had a phonebook delivered to the house. The front cover implores me to use the website to find the phone numbers of people and businesses I’m looking for. I’m so confused.
Yesterday, with the return of my family from holiday, I forgot to make changes to any of my projects in GitHub, and broke my commit streak at 57 days.
Initially I’d aimed for making changes on 30 consecutive days, just to try and get some momentum up in making progress on a couple of fairly low-key projects that hadn’t been going anywhere, and although I did cheat a few times (GitHub counts things like opening issues on a repo as ‘activity’ and I have plenty of bugs and features!), the vast majority of my activity was real commits, and I found 30 to be quite easy.
I think this is definitely something I’ll try again, but probably in 30-day chunks (each day only tends to give me ~30 minutes free to do any coding at home!), and probably with a more well-defined plan about what I’m actually expecting myself to ship within that time.
Anyway, despite the fact that I’ve finally broken my run, I’m pleased that I managed to get so much higher than I’d originally aimed for. Onwards!