This week has been a busy one.

I’ve finished my week on triage and am back on the project I’ve been working on for well over a year now. This week I’ve been working on part of a Blazor front end and have learned how to use a background service to dynamically update a component in the UI. I didn’t know it was possible to do that so I’m really chuffed I got it working (and it looks good thanks to some guidance from another team member) I feel a techy post may be in the pipeline to celebrate this small win…

Pair programming with another dev has been a great way to talk through problems and I found it to be more helpful than talking to the A Team*, especially as they’re hibernating somewhere in the “to be sorted” boxes (I moved house a few months ago and had no idea just how much stuff I had acquired over the years).

My weekly catch up re. design patterns focused on the factory method and SOLID principles this week. Being able to talk through SOLID has helped me get my head around them – I’d read so many different articles and quite a few were really bamboozling, but we got there in the end.

I spent Friday morning at a careers fair as part of a TechUPWomen celebration event. TechUPWomen supports women and non-binary people aged 18-40 from underserved communities in the North of England who want to start a career in tech. Waterstons are a programme partner and as such we are able to get involved in various ways, for example mentoring, reviewing CVs, running mock interviews and giving industry speaker talks. Friday evening was their celebration event for their first cohort of the year and the ceilidh band I’m in was lucky enough to be invited to play! I have no pictures as yet so you’ll have to take my word for it that I was there.

*AKA rubber ducking. The premise is to explain what you’re trying to achieve to a rubber duck. You then walk it through the code, line by line, and at some point you should realise where you’ve gone wrong.