08 May 2017
Quick notes, but notes nontheless:
- On Selworthy, I wrapped up work on our latest export format and got that deployed to production. I also did battle with handling video with non-square pixels correctly. That was an adventure – and a pile of learning to do – but we got somewhere good in the end.
- On Gisborough, we committed our final content changes before a second round of testing. I also spent some time porting the application from “a directory full of PHP files” to a self-hosting Sinatra application, mainly to make it easier to host on PAASes like Heroku. This didn’t take very long, but gosh, Apache and
mod_phpis a pretty handy prototyping environment and some days I miss its easy availability.
- On Longcrag, my correct set of front panels arrived from Eurocircuits, and I built up the remaining test boards. So far, so good: I identified two mistakes on the boards (simple component values) that can be solved through corrections in the build document. I ordered the replacement parts, and next week, kitting up begins in earnest.
03 May 2017
The notes continue to be brief in proportion to the busyness of the week!
- I spent most of my time on Selworthy writing export tools for another broadcast subtitle format; challenging, but making lots of headway and understanding the format better the longer I spend with it.
- On Gisborough, we wrapped up a second pass of the content, started to brief an animator, and planned the final push on the project.
- Longcrag is paused whilst I wait for the replacement panels to arrive from Eurocircuits.
However, two prototypes for future Longcrag projects arrived, so I built them up. One was an entirely new board – albeit based on two other existing products – and it worked first time, and also confirmed that the idea for the product was a good one. So that’s something that might move up the production schedule depending on how the first batch of products go.
The other was a second iteration of something I’d made earlier – now ported entirely to surface-mount technology, and fixing a bug in the layout that meant the output voltages weren’t high enough. It works entirely correctly, and is quite exciting – unlike the other Longcrag products, which are my own take on existing ideas or concepts, this one is an invention, and it seems to work well. I built up two of them, and have sent one to a pianist for beta-testing, and to see how another musician responds to it.
Fair motoring, and rolling reasonable well through all the inevitable context-switching.
04 April 2017
- Gisborough marched on: we finished up a set of revisions to the previous week’s work, and started thinking about how best to illustrate it all.
- I spent some time on Selworthy cranking on a finishing up a particularly challenging file exporter. Despite an initial working prototype, I spent some time tidying up the code and making it much more compartmentalised: easier to test, and also easier to extend in future. I also spent some time trying to fix some strange import errors from other tools, when we tried to load these files into them. I compared ‘golden’ output from another tool with our own, and comparing notes as to what might lead to the issues we’re seeing. By the end of the week, I’d tidied up a lot of my own output and had improved our export files no end – but the inexplicable import errors were still to be dealt with
- With all the components for the first of the Longcrag products here, I fixed them up in their production packaging. The good news is the packaging works well and looks good. With the first 20 products packaged, I spent some time starting work on building a website about the products, and ordering various pieces of merchandise and collateral. The final few components arrived from various distributors, so once the final PCBs arrive, we’re into packaging up some kits – the products are self-assembly – and making sure our documentation is good to go. Exciting, and a little nerve-wracking, to see it all coming to life!
29 March 2017
Another busy week, so time for more codename confetti:
- Over on Gisborough I cranked out some HTML prototypes ready to be tested, as well as taking a quick second check at the language in the second prototype. Later in the week, I went over those tests with the team and we began to plan what would be coming next and taking stock a bit.
- On Selworthy, I spent some time remembering how useful integration tests are for testing complex workflow; Capybara really does make life a lot easier. This helped test some of the new code I’d been writing around sending alerts to our Slack channel when specific criteria are met. I also spent some time working with our new tech lead who’ll be taking over from me in due course.
- Components started arriving for Longcrag, some with attendant customs bills – I’ve learned a few lessons about shipping companies this week. I laser-cut some panels for a new prototype, and ordered the first production PCBs for one of the products.
- Finally, I tightened a few screws on Walbury all ready for a second round of tests.
And we’re out!
20 March 2017
Lots going on, so more bullet-point weeknotes:
- Gisborough begins to take shape. Alex, our content designer, has been working with me on picking some topics and then asking me questions to find both the stories we want to tell, and the way we want to tell them. That’s been challenging in all the best ways, and by the end of the week, she’d found an angle and an arc, and we were shaping up for our first prototype and test.
- Over on Selworthy, I finished up rebuilding our developer tools. I also spent some time working on our internal administration tools: adding some more detailed metrics and notifications for administrative users, and starting to touch on the beginnings of some Slack integration.
- The first of two deliveries from China for Longcrag arrived – 200 cables with a male end and a female end – and I cut them all in half. The packaging also arrived, and a quick packaging test felt and looked good. Onwards.
- I spent an afternoon with Erica fettling the Empathy Deck – aka Holmfell – and discussing some new features I’d add in due course.
- And finally, Wapley had its first test in the wild. It sounded from Richard like it went well; as a result of that, I wrote some quick additions to improve the user experience and make debugging it in the field easier.