22 April 2019
Lots of meetings at Highrigg, across a range of projects; some good time thinking through design interactions with colleagues, and then, around that, spelunking an API I’m coding against.
At the same time, forcing my brain through the React mincer possibly faster than is ideal. I am finding getting up-to-speed with React challenging, and often end up frustrated.
Learning new things is hard, yes, and it’s of course sometimes the work of a technologist to stay up-to-date. What I’m finding hard is the gulf between the basic tutorials and guide (which I’ve completed and re-read a few times) and the real-world project I have to operate in. I know this means I haven’t fully internalised the information - going from knowing to knowing - but it’s a while since I’ve felt like this. It doesn’t help that it feels like something I ought to have some faculty with, as a former front-end developer.
Why am I putting myself through this? Because I think it’s important even if I’m spelunking or prototyping to work in the platform other colleagues are most familiar with, and inside a React+Typescript shop, I think it’s reasonable to work with those. (They also, lack of familiarity aside, seem like highly reasonably technology choices). There’s real internal value to playing ball, especially in a larger organisation, and so a balance between ‘output from prototyping’ and ‘lasting value of prototype’ needs to be trod.
We’ll get there. But a frustrating few hours trying to achieve things I know I could do in other platforms or languages, and resisting the urge to chuck in the towel.
On Thursday, I found that Fedex had failed to deliver parts for a Foxfield run, so delayed that until next week. I spent some time in CAD and lasercutting, wrapping up a prototype panel, and then finishing the electronics of the prototype I’ve been working on. This went well: my workflow from panel to cutter is much tighter now, and a single iteration got things spot on. The prototype is working well, too. Time to make a decision about that prototype soon.
And then, a long weekend. Back Tuesday for a four-day week 329.