After going on holiday it’s been hard to get back into writing weeknotes. I’m also frequently unsure whether to continue writing them. I enjoy reading those from other individuals and companies but, after the initial enthusiasm, I haven’t been sure what they’re for in my case.
Other individuals always seem to be doing more varied and interesting projects — the number of things I’m working on in any one week is usually one or none. And writing about processes, problems and ambitions is an interesting insight when it’s about a company, but can seem a little emo when it’s from an individual.
So we’ll see. It could be I don’t try and do this every week. But, to catch up…
The project at Somethin’ Else is nearing its conclusion. The couple of weeks before I went on holiday, and the couple of weeks after, are now a blur of identical days as I worked my way through tickets, tweaking, fixing, adding, updating.
[Incidentally, we’ve been using Lighthouse for issue tracking. It’s been simpler and less annoying than FogBugz — I could never tell who would be notified of issues or updates in that — but not perfect. I keep wanting to combine tickets, which Fogbugz can do, but I don’t think Lighthouse can.]
While I enjoy doing development work — and it’s a large chunk of my work these days, in one form or another — I have realised I put myself in the position solely of making stuff that other people have specced and designed. In some ways this is wonderfully simple — tell me what you want and I’ll make it work — but in others it’s frustrating. I want to be more involved in deciding what to make and why, using more of my experience than my technical skills, such as they are. The concept, the ideas, the design, etc. This is something for me to work on, rather than something that will magically happen.
I have a few more days left on this project over the next month, making changes after more testing has taken place, but, assuming all goes well, we’re in the home straight from my point of view.