Full Width [alt+shift+f] Shortcuts [alt+shift+k]
Sign Up [alt+shift+s] Log In [alt+shift+l]
1

Personal Sprint Retrospectives

from The Web Witch's Blog [alt+shift+b] in programming

Due to time zone differences, I'm not typically able to attend team sprint retrospectives on Fridays. If you've never done a sprint, a sprint is a set amount of time to complete a specific set of tasks. For example, we work in two week sprints at RapidAPI. I believe we did the same on the Microsoft Edge team but my work was so disconnected from traditional engineering teams, I was rarely ever working in sprints. Work can spill over into other sprints, other randomizing tasks pop up and things get re-prioritized. It happens. But overall your sprint plan sets the goals for the sprint and what tasks you'd like to ideally close out. In a sprint retrospective you go over what went well, what could be improved and what you should do more of in the upcoming sprints. I usually look at the retrospective board that gets shared out and make note of anything relevant to me as product manager, if there's anything and start sprint planning. Why I do my own personal sprint retrospective # Recently, I started doing my own personal sprint retrospective on my own for work. While I can't join the team one unless I stay up until midnight, it gives me an opportunity to reflect on what I thought went well, what can be improved in my own workflow and what I should continue doing. Doing this allows me to close out the sprint in my own way and self reflect. It also allows me to create a routine, which I'm realizing is incredibly important with the way I currently live (lots of travel). This exercise is also helpful as my scope has grown incredibly since my time at Microsoft. I was doing developer relations work but when I would do product feature work, it was just that. A feature in the browser. Now I own 4 products and experiences and the RapidAPI design system. So this allows me to drill down on where I think I can improve from a product management perspective. Example of my personal sprint retrospective # It doesn't have to be super detailed or in-depth. Just observations about what...
21st Oct 2022

Stay updated

Get a weekly newsletter with the top 5 articles worth reading every week.

More from The Web Witch's Blog

A Short Update on Designing for Foldable Devices

And here we are three years after I wrote about the Google Pixel Fold being announced, followed now with the announcement of the iPhone Duo...(I have questions about the naming by the way). Four years ago I was talking about web primitives in the platform for the Surface Duo. My how time flies. There are CSS media features, a Viewport Segments API, a Device Posture API but Chromium based browsers are the only ones currently supporting these things. I haven't been able to find any signal yet on whether Safari will support these things in the web platform as the developer docs focus on application development. If you're interested in trying out the platform features, you can emulate the Surface Duo and Galaxy Z Fold in the developer tools. And if you're thinking, do I really have to have my website adapt to two screens? The answer is no. Adding a design to an application or dual screen makes sense if you have an experience that has two simulataneous contexts that are useful e.g. a list of email messages/inbox on one screen, an open message, email thread or email composer on the other. Here's one of my talks from 2022 if you're interested in learning more about what's available in the browser for dual screen/foldable devices. Happy building :)

24th Sep 2026 • 1 votes
Web Witch's Grimoire: Summer 2026

The year flies by when you're postpartum, sleep-deprived and your little bubba is suddenly on the move and making developmental leaps. Time is this sort of weird compressed experience, not dissimilar to the way I felt about COVID and 2020 (wasn't that just yestersday? No indeed it was not, it was 6 years ago). And I'm a bit discombobulated as September is upon us. Budget planning at work? Didn't I just do budget planning for 2026? I went back to work in June, which has been an adjustment and prompted many an identity crisis, but at the same time I am happy to be back and doing lots of soul-searching. I'm in a better place than the start of the summer. Part of the soul-searching has been prompted by AI and the state of tech that I re-entered into. I still hate how it is being shoved down our throats and the prioritization of data centers, especially in places experieincing drought. Everyone should have access to water and humans should be prioritized over a data center. Full stop. For my current role, it has been extremely helpful in speeding up mundane tasks like compiling reports, and giving me more time to spend on things like design and social media content, which I historically had barely enough time for. But I continue to be baffled by AI and its bubble. The IPO valuations seem wildly ridiculous, and I've seen the salaries offered to people and I wonder how it is even remotely sustainable. I also hate the fearmongering and the polarizing content ("AI is going to replace [your industry of choice here]") to create engagement bait that has come with the commercialization of this technology. It is a horrible and interesting time in tech. I have seen many qualified people laid off because of "cost-cutting", and it's not right. Summer Bits # We survived multiple heatwaves in South East England, and while I'm told there were four, it really felt continous up until a week or two ago. I've kept the windows open and the house chilly in the morning because it is a relief. The first heatwave in May was stressful as hell, with Chloe about to be 5 months and trying to keep her cool while our upstairs rose to 28 C. The number of parents lamenting online about the lack of knowledge sharing in prenatal classes about how to keep a baby cool in hot weather was more than zero. We all knew the safe sleep guidelines said 17-21 C but wtf are you supposed to do when you can't get any part of your house that cool? It was stressful and horrible, but it's over for now. I think. My dog Vogue has had health issues since last October and we have finally got to a point where I have not had to take her to the vet in about a month or so. She's on heart meds and has mitral valve heart disease. Her heart is quite enlarged but we're managing. She rides in the bottom of Chloe's pram for walks so she still gets to go out and about. I love her to bits, I can't believe she's 14 and I cherish the time I have remaining with her. The Patio # While it became increasingly apparent that we will need more space when Chloe is older, I decided to make the most of what we have and asked our landscapers to put a patio in off the back of the house, and they finished it in early July. It has become a daily sanctuary, and I'm sad the nights are getting shorter. There was a good 3-4 weeks when we were outside eating dinner. Yorkshire Coast # We didn't leave the country this year for my birthday. I can't remember why it didn't quite work out, but we took our first overnight trip with Chloe up to the Yorkshire Coast and Whitby. It was beautiful and by the time we eventually found our groove with Chloe and naps and going out to do things, it was already time to leave. I love the sea, and it was lovely to be along the coast for a few nights. Will hopefully make a more permanent move along a coastline at some point. Family coming to visit # My mother came to visit for 3 weeks and help with Chloe which was so lovely for her to get that time bonding with her granddaughter. She also got to see Chloe make some big development leaps even in the short time she was here. Then my sister came and stayed with us for a week. We went to Wrest Park, London and Warwick Castle and Chloe loved it all. I only wish both my mom and sister could have stayed longer. What I've been... # Watching # A lot of reality TV. I've just been hella into Bravo shows more than usual. Ladies of London: The New Reign - It was the best Bravo show I've watched in a long time. Interesting characters who felt more authentic than Real Houswives. I am gutted it was not renewed. I want more of Mark and Martha! The Valley - More reality TV. Oddly comforting as the new season started when I was 3-4 months postpartum and two of the women on the series were also at that stage of postpartum so it made me feel a bit normal and seen. House of the Dragon - Season 3 was way better than 2. Rooster - Love a Steve Carrell show. It was different. I enjoyed it. Dutton Ranch - Ridiculous and outlandish like Yellowstone but entertaining. And it's Premier League season again babyyyy. Though I am extremely sad Arsenal sold Trossard. Boooo. But I'm thrilled there has been so much football on. Reading # Ha - it is taking me months to finish books at this particular moment in time. Glad I read so many last year. I did finish Crescent City #3 House of Flame and Shadow back in April. I started Brimstone (Fae & Alchemy #2) but could not stay engaged, so I DNF. I know book one was ripped apart because of the writing, but I was entertained. I couldn't look past the writing this time. I am currently making my way through the first book of Dungeon Crawler Carl. Other Bits # In this process of soul-searching and finding my identity as a mother, I am back to the state of mind prompting me to ask "why not?" when something comes up. So I bought a Pioneer DDJ-FLX4 to learn how to DJ and have been rediscovering the music I so love at festivals and feeling re-energized about something new. I'm loving mixing and am excited to see where this takes me. I've also decided to go back to school. Not your normal school though. I have become deeply interested in astrology and am going to pursue that for fun. Looking forward to being in a classroom setting again. Because why the hell not?

25th Aug 2026 • 1 votes
Returning to Work After Maternity Leave: Day 1 as a New Mom and Remote Tech Worker

I started work back up again yesterday, June 1, as a remote tech worker for an open source consultancy. My husband started his paternity leave today. I'm only going back part-time for the moment so my rough plan is to work 3 days a week with the exception of this week, as I wanted to open my laptop, clear out my inbox, setup my Notion pages for 2026, change my away message and just try to get a vague sense of what's happened while I've been away. I'll work Monday-Thursday but Monday and Tuesday will be half days. My goal for the day was to get up with Chloe at 6:00 AM like normal. Put her down for her nap at 7:30. Have Jhey take over while I take the dog to the vet for heart scan and then log on for a little bit this afternoon. The universe said, a plan with an almost 5 month old? Nice try. Chloe woke up at 3:00 AM which is unusual for her. I rocked her back to sleep. Put her down. Tried to crawl back into bed. She woke up, rolled onto her tummy, and cried because she can't get onto her back because she's seemingly forgotten how to do so. She started rolling tummy to back weeks ago, but now that she can go back to tummy...that's all she does. Rinse and repeat until 6 AM. So I'm at that shattered level of tired. So much so that when I take my dog Vogue to the vet and they're telling me the results of her heart scan, it's not processing how poorly her heart actually is until I get home and talk to Jhey. She'll be on medication for the rest of her life. She's 14. We'll do another scan in a month to see if the meds help slow the progression of her heart enlargement and then I'll ask for a potential timeline...how much time they think she has left. Jhey goes to the gym and then someone shows up to pick up his special edition Mustang that he's sold. I get Chloe down for her nap and log on at 2:00 PM. I had briefly logged on for a half hour in the morning to just do a quick check and update. My inbox is a disaster as it seems my out of office reply, replied to spam messages that would normally not be in my inbox and I have 100s to delete. I try to be ruthless and delete as much as possible but leave the more company-wide discussions for follow up. I try and skim the chat. But there's too much. By the time it's 5:00 PM I have barely managed to get my Notion pages set back up. I'll try again tomorrow. I remind myself that today was particularly difficult with scheduling and is not indicative of my days going forward. Tomorrow I'll try for more routine. I go over to Jhey's parents' house and chat, we bring Chloe back for her nap, then bath and bedtime routine. I make a quick dinner of shrimp stir fry with a nice veggie stir fry pack from Waitrose. I almost make it to the end of the Euphoria finale but pass out briefly and then go up to bed. Exhausted but accomplished. Day one of this new life and routine and figuring it out is complete.

1st Jun 2026 • 1 votes
Back from maternity leave

Today is my last day of maternity leave. Chloe is down for her morning nap and I'm trying to process the last 5 months and where it has all gone and all these complicated feelings. I want to go back to work and I don't. I am only going back part-time for a few months but it still feels like a massive shift is about to happen. Chloe is on a pretty good routine at the moment and just learned to roll over from her back to front. She is more aware, getting stronger and so damn cute. Her little gummy smile when I get her out of her cot in the morning and after naps fills my heart with such joy. I'm not sleeping particularly well at the moment and it's not necessarily because she wakes up at night. I have a lot of anxiety around sleep at the moment because of how hot it's been in the UK. Somehow despite the broken sleep, I get through the day and have a burst of energy after she goes to bed. I started anti-depressants for postpartum depression around the 3.5 month mark. This can also cause sleep issues and insomnia but I feel a lot better and have no problem saying without medication I'd be struggling to survive. I've even rediscovered my joy for a few hobbies and am excited to start gardening again and have decided our outdoor space needs an upgrade. I'm finding a rhythm again, ever so slowly. When it comes to the web and my career, I feel like I'm coming back at a weird time. AI is wrecking havoc and I continue to be skeptical of how hard it is being pushed. I believe it can be useful and is a tool, but the places where it could have the most impact and be incredibly transformational are not being funded adequately. I also don't believe it can adequately replace entire roles, and I don't believe we should be expecting 10x the output from workers because AI may be automating some tasks for them. We should not be pushing AI generated code to PRs without reviewing it or having some understanding of what has been generated. I fear there's going to be a lot of slop to clean up. I've been approached to create a proposal for a new side project. Details TBD but I'm considering moving ahead with it as it ties into Design for Developers. There's a lot on my mind, but I'm expecting Chloe to wake up any moment so I will eventually share those things on the blog but I will be back from maternity leave tomorrow (June 1) and dipping my toes back into adult life again. I've enjoyed the level of disconnection from online. My screen time is way down as I try to avoid being on my phone when Chloe is in front of me. Priorities have shifted. I've shifted. I feel like a completely different person, but I think it'd be strange if I didn't. How can you not grow after the experience of giving birth and motherhood?

31st May 2026 • 1 votes
And Suddenly Spring

And suddenly it happens one day in March. The sun beams down in a rare cloudless sky. It might be cold as the wind gently blows but The Sun. The Sun beams down and it promises Long nights on the horizon. It promises miserable humid days And lovely warm days. Harsh mid-day light. Dreamy golden evenings. It comes out to announce Winter's end before It once again disappears behind England's cloudy skies. And Suddenly Spring is here and my soul is warmed once again.

20th Mar 2026 • 1 votes

More in programming

Modifications to add a booty to Loops by Kat's Ditto amigurumi

I found a wonderful free crochet pattern for the Pokémon Ditto from Loops by Kat, but I decided I wanted to make a version with more than 3 "leg" blobs like the original pattern had. Specifically, I wanted to add two more smaller blobs in the back to help stabilize Ditto when they're sitting and also add a butt to our favorite transforming blob. Hazel Knits Cadence, a worsted weight superwash merino, in Terrywinkle that I had in my stash (I used about a third of the skein/36 grams/66 yards/60 meters), and I crocheted with a 2.5 mm hook. I make very tightly stitched amigurumi - do whatever is a good fit for you and your yarn! I used two 6 mm round safety eyes, and I embroidered the mouth with scraps of Hazelknits Cadence in Coral, Bloom, and Signature Black. The above photo is more true to color than some of the ones I took where Ditto looks more pink. I made Ditto's 2 additional booty blobs intentionally off-center by embracing the natural lean of crochet stitches - this gives a more animated or "in motion" feel to Ditto. As an added bonus, this simplifies the pattern as everyone's tension will be a little different, and thus everyone's off-centering a little delightfully different, too, but centering it instead wouldn't be the same for everyone! Here's all the information to modify Kat's crochet pattern to create a 5-blobbed Ditto. I use US crochet terminology. This pattern modification is also available as a pdf. Follow Kat's pattern through round 13. At round 14, it's time to start modifying to add the space and shaping for the additional blobs. There are also 3 more rows in this section to better fit the new 5-blob proportions. Modified increases in body, beginning at round 14 (with additional rounds, too): Round 14: 3 sc, 1 inc, 46 sc, 1 inc, 3 sc (56) Round 15: 56 sc (56) Round 16: 2 sc, 1 inc, 2 sc, 1 inc, 44 sc, 1 inc, 2 sc, 1 inc, 2 sc (60) Round 17: 60 sc (60) Round 18: inc, 4 sc, inc, 48 sc, inc, 5 sc (63) Round 19: 63 sc (63) Round 20: dec (through front loop of first stitch and both loops of second stitch), inc, 9 sc, inc, 38 sc, inc, 11 sc (65) At this point, the original pattern suggests placing the safety eyes, but I think it makes more sense to do this after you've made the "butt" and divided the stitches the 3 main "front" "leg" blobs from the original pattern. You'll still have plenty of access to place them then. Roadmap for doing 5 "leg" blobs instead of 3 To make 5 blobs, you use some of the main body's stitches and some created stitches for each. Created stitches are a combination of chains, pickups on the back of chains, pickups in the connections between the chains and the main body, and pickups in the connections between the chains. The "butt" "leg"/mounds are created before the 3 original "legs," and the left "butt" "leg"/mound is made before the right one. 1. Left "butt" "leg"/mound: This is the left "butt" cheek when viewed from the bottom. (While this is really the right butt cheek from Ditto's perspective, I'm calling it left because we're crocheting while viewing from below so it's backwards.) The start of round is the same as the start of round from making the body of the blob, so you can continue as usual. Round 1: 13 sc, chain 11 (24) Round 2: connect chain at previous start of round (skipping 52 stitches) then 24 sc (24) Round 3: (6 sc, dec) x 3 (21) Round 4: (2 sc, dec, 3 sc) x 3 (18) Round 5: (sc, dec) x 6 (12) Round 6: 6 dec (6) Finish off by looping through front loops of all 6 stitches and pull tight, etc. 2. Right "butt" "leg"/mound: This is the right "butt" cheek when viewed from the bottom. The start of round for this "butt" "leg" is 12 stitches before the body/left "butt" leg start of round. This is the second stitch in an increase from the last round of the body. Round 1: 12 sc, 1 dec in the corner of body connected to first "butt" "leg" (pictured below), 4 sc in the bottom loops in the existing chain, chain 7 (24) Round 2: connect chain at start of round for this "butt" "leg" (skipping other blob's additional 7 chains and 40 stitches in the main body) then 24 sc (24) Round 3: (6 sc, dec) x 3 (21) Round 4: (2 sc, dec, 3 sc) x 3 (18) Round 5: (sc, dec) x 6 (12) Round 6: 6 dec (6) Finish off by looping through front loops of all 6 stitches and pull tight, etc. Getting back to the original pattern for the 3 main "legs": After both "butt" "legs"/mounds are done, there are 40 stitches on the original body, 7 chain stitches that can be picked up from each "butt" leg" that haven't been picked up in a second location, which totals the original 54 stitches - this sets you up for the 3 blobs as described in the original pattern. Between each "butt" "leg" and the main body and between the two "butt" "legs" themselves are an additional 3 connections that are also picked up and decreased appropriately to keep the seams between "legs" tight. As a reminder, here's the road map, which shows how to divide up these stitches for the Ditto's main three "legs:" You might find it helpful to visualize this division by temporarily stringing up some scrap yarn to preview the divisions: If you'd like, place stitch markers like I did to delineate the division: Now that you've visualized how you're dividing the main "leg" blobs, it's a good time to place safety eyes if you're using safety eyes for eyes. I placed mine between rows 7 and 8 counted down from the small head blob and left 8 stitches between the eyes. Now you can proceed to make the main legs in the same order as the original pattern. 3. Main "leg" blob 1: This is the left "leg" blob labeled 1 in the original pattern. To start, connect your yarn into the first stitch in the main body after where the main body meets the left "butt" mound. Round 1: 18 sc, chain 9, 1 sc in the 2nd bottom loop in the chain right of the body/left "butt" mound connection, dec through the leftmost bottom loop in the chain on the left "butt" mound and the loop on top of the meeting of the main body/left "butt" mound (pictured below). (29) In the start of the original pattern "leg" 1, here are the two loops in the decrease through the left most chain loop on the left "butt" mound and the loop on top of the meeting of the main body/left "butt" mound. Follow the original pattern's Rounds 19 to 23 and finish off blob "leg" 1 as written. 4. Main "leg" blob 2: This is the right "leg" blob labeled 2 in the original pattern. To start, connect your yarn into 15th stitch from where the main body meets the right "butt" mound - there should be 7 skipped stitches along the front of the Ditto between this start of round and the left "leg" blob's last stitch on the front side of Ditto before the chaining. Round 1: 15 sc, dec through the loop on top of the meeting of the main body/right "butt" mound and the rightmost bottom loop in the chain on the right "butt" mound (pictured below), 4 sc in the bottom loops in the chain on the right "butt" mound, chain 9 (29) In the start of the original pattern "leg" 2, here are the two loops in the decrease through the loop on top of the meeting of the main body/right "butt" mound and the rightmost chain loop on the right "butt" mound. Connect chain at start of round for this blob "leg" at the beginning of round 2's first sc and continue the original pattern's Rounds 2 to 6 for blob "leg" 2 as written. As in the original pattern, now is a good time to stuff your Ditto most of the way! 5. Main "leg" blob 3: This is the center "leg" blob labeled 3 in the original pattern. Round 1: Start in the corner next to left "leg" 1 on the front side (pictured below). 37 sc into the following stitches you pick up: 7 stitches along the main body 1 stitch in the corner of the main body and right "leg" 2 9 stitches in the bottom loops of the chain along right "leg" 2 1 stitch in the corner of right "leg" 2 and the right "butt" mound 2 stitches in the bottom loops of the chain along the right "butt" mound 1 stitch in the corner between the two "butt" mounds 5 stitches in the bottom loops of the chain along the left "butt" mound 1 stitch in the corner of the left "butt" mound and left "leg" 1 9 stitches in the bottom loops of the chain along left "leg" 1 1 stitch in the corner of left "leg" 1 and the main body (37) My lime green running stitch marker indicates the start of round pickup location for making the main blob "leg" 3. To compensate for the extra 5 stitches from those corners, I decreased in the second round at the corresponding locations instead of just single crocheting the whole way around to ensure the end of my round 2 of this section had the specified 32 stitches: Round 2: 6 sc, dec, 8 sc, dec, sc, dec, 4 sc, dec, 8 sc, dec (32) After round 2, I continued with the rest of the original pattern to finish the middle blob "leg" 3. Make the two arms according to the original pattern. I attached them less symmetrically than the original suggested. Finally, embroider a mouth for Ditto. You can either do this in black to match the safety eyes or create a two-toned mouth in red and pink to make a very happy looking Ditto like I did. FYI, this is also documented as a project on Ravelry (though it's a lot harder to follow since photos couldn't be inline).

2 hours ago • 1 votes
Tyding up my side projects

Being focused is about doing less things, and giving more space to the stuff that matters. I am spread out on too many projects and I can’t give enough attention to all of them. It’s time to clearly sort out which one I will keep maintaining and which I should drop entirely. Chuttersnap Mikochi Mikochi is a self-hostable remote file manager I’ve started in 2023. It’s my most successful open source project. I personally use it every day, and thousands of people have adopted it and started using it on their own servers. This year the project has been receiving more and more attention. Maybe it just reached a critical mass of users. In practice, that means a bit more maintenance work, since people have been pointing out bugs and suggesting new features. At the same time, working on Mikochi is fairly enjoyable. It’s a small, self-contained project made with technologies I enjoy working with. I’ve got no complaints about spending some time working on it. Verdict: Keep maintaining Mikochi and actively continue improving it. Itako Itako is an investment portfolio tracking SaaS. I built it for the most part between 2023 and 2025. In terms of scope, it’s the largest project I’ve done entirely by myself. Is it a success? Not really. There are definitely a lot of people who tried Itako, and some who’ve kept using it a bit. But it’s not engaging enough for anyone to consider getting the premium plan. And honestly I don’t find myself using it that much. My view of investing and portfolio management has significantly shifted since I started this project. While I used to think that more sophisticated analysis would lead to better returns, I now realize that the only strategies that consistently make money are honestly stupidly simple. Or maybe it’s a U curve: on one end you’ve got a monkey throwing darts, on the other end you’ve got Jane Street, and everyone in-between fails to beat the market. Anyway, the biggest issue with Itako is how dull working on it is. The interesting parts of the projects are working on statistics and data visualization. But in practice, 90% of the time is spent tediously fixing data, understanding why some German stocks have an exchange labelled XETRA instead of XETR, why some Belgian stocks still have quotes while Euronext shows them as delisted… Verdict: Shut down Itako today. Milou Milou is static site generator for press kits. It started as a fork of presskit.html which was completely abandoned at the time. It’s a very useful tool. At Tsukumogami, it’s part of our Cloudflare pipeline which builds our website in a few minutes whenever we need to change something. It seems like a few other game studios have picked it up, although I rarely get any feedback about it. I’ve not spent too much time working on it in 2026. I think it could be interesting to come back to it and add a feature or two. Better support for multiple languages could be an idea. At least, I need to make sure we don’t fall into the good old Node.js dependency rot. Verdict: Spend some time on Milou. Luluka Earlier this year, I created Luluka. It’s a CLI that allows previewing the output of Ebitengine shaders. I do still think Ebitengine is a great engine and Go is better suited for game development than most people realize. However, after quite a long period of experimentation around it, we’ve decided to remain a Godot studio. On top of having quite a large sunk cost in infrastructure surrounding Godot, the tooling and possibility of doing 3D games still makes it a more attractive engine for our use cases. And I’ve been doing a lot of 3D work lately, so better put those hours to use. Verdict: Archive the project. The rest I’ve had a lot of good ideas that stayed as almost empty repositories in my GitHub. For example, Hakumei was a terminal companion to Mikochi. I made a few commits on this project and never found the time to work on it again. I have to admit I’m probably never going to have the time to work on all those repositories. Time to archive them all!

3 days ago • 1 votes
Not everybody is an AI expert - and that’s fine

This post was previously published through my newsletter on November 9, 2026. From time to time, I will republish newsletter issues on my blog here if I think people (and search engines) might benefit from it. If you want to read everything I’ve written once it is posted, I recommend signing up for the newsletter. If you’re doing anything to stay on top of what is happening in the world of software testing and test automation, like browsing or even posting on LinkedIn, which I stopped doing for the foreseeable future, or reading blog posts - my preferred way of keeping up these days, and I highly recommend Dawid Dylowicz’s excellent Software Testing Weekly aggregator mailing list if you prefer longer-form reading, too you’d be thinking that AI has consumed our entire field, and that everybody (or at least those who post or write in public) is an AI expert these days. The reality, though, is far from that. Yes, some people use a lot of AI, even when I would only call a small fraction of them ‘experts’. I definitely do not classify myself as an ‘AI expert’, by the way. A much larger group uses AI on a less frequent basis, and they’re getting some value out of it. Sometimes more, sometimes less. That’s the group I’m probably in. And then there’s a group of people who haven’t really been using a lot of AI at all so far, beyond maybe the odd prompt to ChatGPT or Claude. I don’t have the actual numbers, but I suspect that this group is a lot larger than you would think from browsing your feed or surfing the blogosphere. You just don’t see them, because they’re typically not the people who do a lot of work in public. A few weeks ago, I started working with a small group of testers to teach them how to use AI in their daily work. This work covers both test automation as well as broader software testing tasks, as some of them contribute to automation on a daily basis, but not all of them do. I’m working with them one day per week, on average, for three months, and we’re making small steps towards making AI a more prominent tool in their tool belt. So, what are we working on right now? I’m pulling ideas from my ‘Valuable Feedback, Fast with AI’ course, and so far, we’ve spent some time setting up Claude, going over some important concepts such as context windows, models, tokens, and (of course!) the probabilistic nature of LLMs, and what that means for the results they provide. We have gone through several initial conversations, using Claude to learn more about and review specific user stories, which was an excellent segue into using talking about MCPs and setting up a connection to both Jira and Confluence using the Atlassian MCP. Last week, we also started experimenting with writing straightforward skills to make it easier for Claude to repeat certain actions in a structured way. These actions ranged from reviewing stories and acceptance criteria to refactoring small chunks of code in their (Robot Framework-based) test automation suite. What I loved about this is the avalanche of ideas that popped up in their heads when they saw how easy it was to use Claude. We made a short to-do list of ideas to try out for the next couple of weeks, and I’m looking forward to seeing them getting more confident around using Claude. One thing I have noticed is that their level of comfort around using AI varies quite a bit. Some of them are naturally quite cautious, which means they’ll ask ‘can we really do this?’ and ‘should we really do this?’ frequently before even submitting a single prompt. This is a good habit, I think, but we’ll have to do some work to get them more comfortable with using LLMs, without losing too much of that caution. Others in the group are the opposite: I need to hold them back a little, because otherwise they’ll create a beautiful mess within days, simply because they see so many opportunities to use Claude in their work. That, too, isn’t inherently bad, but I do want to teach them not just how to get the most out of an LLM, but also (more so) how to use AI prudently. Over the next couple of months, we’ll dive deeper into writing better prompts, creating and structuring skills, better context management, and creating and using agents, and probably a few more things, too. I’m looking forward to seeing these people grow more comfortable around using AI in their daily work, and figuring out where AI genuinely adds value and where it doesn’t in their own context. Is there a deeper message in this newsletter? Maybe not, and I’m just happy to tell you about this project, and how it is a great example of a what I call ‘corporate mentoring’, a very efficient way of teaching a small group of engineers new skills, within their own context. But maybe it’s also to show you that, despite what you might see on the Internet, especially those places featuring a lot of self-congratulation (I’m looking at you, LinkedIn), not everybody out there is an AI expert. At least not yet. So, if you feel like you’re ‘behind’ simply because you’re not running at least 17 agents continuously, creating 5400 merge requests per day, know that you’re not alone. Quite far from it, I would say.

4 days ago • 1 votes
Keyhive 08 · Rain Diagrams

Certflow diagrams laid out in time

5 days ago • 1 votes
Notes from CoRL 2026

(Tuesday)

6 days ago • 1 votes
📚 BoredReading

You seem to be enjoying this.

Join free to unlock everything.

Create free account

Already have an account? Sign in