Posts tagged as selworthy (page 3)

In haste:

• 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!

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!

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.

A short week, after returning from a short vacation, but lots of progress in a few areas.

• Some work on developer provisioning on Selworthy – wrapped up the work of using our existing Ansible scripts, with minor modifications, to provision a development environment inside Vagrant. Should make it much easier for new developers to come on board. Oh, and we shipped a small, useful addition to the internal metrics tools.
• Started working with our content designer on Gisborough; this ended up with me trying to narrate the journey through the OSI Stack when you POST a form, to work out how to explain this more plainly. That was a deep dive of “remembering all the stuff that’s really going on”!
• Longcrag started its journey into reality, with ordering packaging and also some key parts from overseas; I also spent some time filling out forms and paying customs invoices, wearing a learning smile throughout.
• Finally, I broke ground proper on Wapley, a new tiny project with Richard that takes some of the work we explored in Rubato and pivots it into an interesting direction. After some simple prototypes in earlier weeks, a few hours of staring down some node code got us an exciting alpha.

No wonder I feel a little like I have whiplash. Aaaand breath out.

Week 218

Week 218 began with a Chinese PCB manufacturer sending me a picture of boards about to be DHLed to London. I was testing out overseas manufacture for Longcrag, and seeing what the process would be like.

They arrived later in the week. I’ll be honest and admit I was disappointed, but my disappointment was behind a learning smile: the manufacturer had made everything to the tolerances they specified. What I hadn’t twigged is that they were much lower than the tolerances of my US prototype manufacturer. It turns out that OSHpark boards are ridiculously high-quality, in terms of the precision of the silkscreen. Given these boards are for DIY assembly, and the silkscreen needs to be clear, they weren’t going to be good enough.

So that led to two conclusions: firstly, spending a bit more on the boards, and manufacturing them in Europe, at a supplier friends have had good experiences with; and secondly, reading each manufacturers’ tolerances better. I redesigned the silkscreen on all the Longcrag products to be much more legible, and within tolerance. Fingers crossed!

Over on Selworthy, I continued wrestling the SCC format to the ground; it’s a difficult challenge compounded by the challenge of testing it. At some point, I should possibly write this up, or extract it to a library. But for now, just getting the output files right is the correct challenge.

And Gisborough metamorphosed into a slightly different project, that should begin in earnest in week 219.

Week 219

A short week this week.

Selworthy saw me spending the afternoon with a new colleague to start the process of handing the project over to a new lead. That’s right: after nearly two years, of the little-five-week-project-that-could, I’m planning to move on.

I really should write the whole thing up.

Anyhow, we spent the afternoon trying to build up a development environment, and this time around, decided to make use of all our Ansible collateral, rather than building a complex environment by hand. This was perhaps not the pace that was expected, but I’m sticking to my guns that it’ll be good in the long run. Sometimes, communicating the dreariest kind of technical debt – things that are only going to be debt if we have to do them again. When that’s unlikely, but not impossible, it doesn’t always feel like the most obvious investment, so you have to hold fast to the knowledge that all it takes is one unknown in the future to change your perspective. I’m hopefully going to wrap up this process in Week 220 and then we can get back to the land of features and fixes.

Gisborough mk2 kicked off, with some thinking and writing and talking and it feels like it’s moved to a reasonably natural place; next week, I start talking to a content designer about heavily involving them in the concept and giving them what they need to start thinking through it.

And Longcrag saw some big developments. Firstly, I spent some timing costing up production runs over on Eurocircuits. Eurocircuits are good value, though more expensive than the Chinese manufacturers I looked at; they primarily manufacture in Hungary and Germany. However, their tooling for uploading, configuring, and pricing boards is excellent, and hugely confidence-inspiring; it’ll make it easier to order repeats in the future. So I’m thinking of going with them, if only for the quality and speed of service; it’ll impact my costs a little, but better than the risk of longer turnarounds and more unknowns in the process.

A new prototype under the Longcrag umbreall arrived this week, and I quickly built it up – to be pleasantly surprised that it all worked as expected first time. Which felt like a big deal: a custom PCB containing a microcontroller chip alongside other circuitry, and an in-system programming header, flashed with my own code, and all behaving itself. And more importantly – it wasn’t just working, it was exciting – the possibilities for it as an instrument revealed themselves quite quickly. I’m going to try to get a couple of prototypes to other musicians soon, to see how they feel about it, but this one feels good.

And finally: I received an order for some Longcrag kits. A small order to begin with, but it’s going to entail kits for 5 different products going on sale from a retailer, and means I’m putting this stuff into the world. Shipping (unassembled) hardware! Blimey. Long list of things to do around all the other projects. It’s going to be a busy few weeks.

But for now: week 219 ended early, and I headed out for a long weekend; a small break to top up the energy reserves, before heading into a crunchy month or two. It’s going to be exciting.

A busy couple of weeks, which is why I appear to be writing them for two weeks, not one. Ah well.

Selworthy saw a deployment that integrated and released a pile of new features – that was good to get out, and thorny, given it involved changing some of how we stored data on it. I also started working on a new export format for the application, which is probably the most painfully difficult file format I’ve ever worked with. We’ve certainly had an ‘interesting’ time testing it – it turns out the edge cases are very badly documented, so that’s been a lot of publish/test/fix going on.

menting it; it turns out the edge cases are very badly documented.

Over on Longcrag, I made another spreadsheet. Not a BOM this time: instead, a burndown chart of all the products in the range and what’s left to do on all of them. It’s… only moderately intimidating. I’m concerned some of the later tickboxes actually hide a lot of work, but for now, the goal is to get BOMs, PCBs and panels all completed so that I’m ready to send a large order to Elecrow.

That is, if they prove satisfactory. So to test them, I ordered a set of prototype boards from Elecrow: a baby step towards manufacturing in Asia. We’ll see how they turn out. Finally, I sent some emails inquiring about wholesaling the products, which is the other big GO/NO GO step for the project – hopefully we’ll hear about that soon. But a GO from a wholesaler and a quality board from manufacture means three or four products are probably ready to go.

I also took the sketch I made the previous weekend and built it up on a breadboard and microcontroller. The MCU code I wrote on the sofa worked first time, and led to a huge grin as I realised quite what this thing could be. So I continued to bash out a first pass at a front panel and get to a circuit board that could be made. A slight digression from the products I should be focusing on, but it’s very exciting, and good to have things in the pipeline. By the end of Week 217, a prototype of this was ordered up, and a few friends I showed initial footage to seemed excited by it.

Gisborough hit a bit of a speed bump; some things that felt clearly defined turned out not to be, which has led to me taking a step back briefly whilst the project refocuses itself – more to come in the near future, I’m sure.

And to cap it all, I failed to do weeknotes last week. So a fortnight’s worth this week, and let’s get back on the wagon next week.

Continuing the theme of doing weeknotes for a single week almost on-time:

• A few days on Gisborough with dotEveryone, carrying out some research trips, sharing our findings, and trying to creep up on the project from a variety of angles. I’ve been reminded that when I get stuck, I probably need to make things, even if all I’m making is words. Writing-to-explain has been one way out of holes, as has making hypothetical posters. Better to have something to disagree with than nothing at all.

• On Selworthy, I liased with another developer about merging our two strands of work, and also about changes to the data we’re storing that’ll require transforming everything in the system. It’ll enable a nice chunk of new functionality, but definitely something to measure several times and cut once. Also lots of UI finessing and research, although my time on this was curtailed at the end of the week by slight illness.

• On Longcrag, I revised the two prototypes with minor bugs from the week before. One took a good half hour of prodding and staring at the oscilloscope until I found the glaringly obvious problem: an output connection normalised to ground that shouldn’t be. When the normalised connection was broken, everything behaved itself. So a single change to the schematic and board, and that one’s good to go. The other board needed a more comprehensive redesign, it turned out, which I breadboarded up and confirmed worked well; I quickly laid the thing out and ordered a second pass of it from OSHPark.

  And finally, at the weekend, I sketched out some code for a new Longcrag idea that came to me in the shower at the weekend. It should be a really interesting device – I can see lots of fun applications for it.

Friday finished early as head-cold and winter lurgy did for me, so a largely quiet weekend in order to prepare for another busy week. Onwards!