More from The Web Witch's Blog
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 :)
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?
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.
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?
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.
More in programming
Helping Scout focus and remember
tl;dr: the Explorer Pattern is one individual or team building a functional implementation that minimizes cross-team and cross-functional impacts as much as humanly possible, and then reconciling the details with other teams after that prototype is completed, accepting that this approach can require very substantial rework to that initial development. Why write this? Imprint previously called this the “Tech-led” or “Engineering-led” development model, but it’s pretty unclear to folks what that means. This writeup provides a more defined term, the “Explorer Pattern”, and explains in more detail how this works. Why do we need to adjust the way we work? Before 2026: Code is expensive, and we design process to minimize implementation and rework In and after 2026: Writing software is extremely cheap, but it’s a wider phenomenon: generating output is effectively-free across many dimensions. Code is nearly free — if we have appropriate constraints. Designs are nearly free — if they follow patterns. Analysis is nearly free — if we’ve instrumented things properly Reworking software is extremely cheap. Historically industry has optimized around avoiding engineering rework because engineering was the highest cost / narrowest constraint. In many companies this was interpreted as writing code being the constraint, which was never true, but many common practices were designed as if that were true (e.g. bringing engineering into problem-solving late “to protect their time”) Working on the system is much more effective than historically if we get automated integration and feedback loops right, e.g. not improving a one-off design but improving the design system. Any place where improving the higher-leverage process is slower than solving the one-off is a bug in our process Explorer Pattern: primary-and-replicas metaphor The easiest metaphor to think about the Explorer Pattern is database replication. Databases like MySQL and PostgreSQL have a primary database, where writes are performed. Every write is verified at that point, and once it’s verified, you know that the writes will flow downstream to various secondary replicas. Those downstream replicas can be delayed but they can’t be wrong because writes are verified upstream. (I’ve resisted the desire to talk about the CAP theorem.) A different model for database design is that used by Dynamo or Cassandra (or MongoDB to a certain extent), where you have a replica set, and have to get an acknowledgement from the majority of the replica set for a write to be strongly consistent. This is a very reliable setup, because it means you can tolerate losing a node, but it also introduces inconsistencies, and on a fixed amount of hardware they tend to be much, much slower than running a primary-secondary setup (or rely on bad performance metrics that don’t fsync to disk to create the illusion of throughput). The Explorer Pattern is the former primary-secondary model, where the vast majority of the work is done by the working individual or team. This makes all work internally consistent because it’s passed through the same small group. It doesn’t, however, mean that the work is perfect. For example, you can always insert data that meets the table’s requirements but is still inherently wrong (e.g. 200 is a valid integer, but it doesn’t mean that my credit limit was supposed to be 200, that depends on the surrounding application logic). Other teams become aware of the changes downstream, not synchronously upfront, and it’s instead the working group’s responsibility to both rationalize approach and create visibility into their work for other teams to engage in a non-blocking fashion. Example: Support for Financial Aggregators A concrete example of this practice at Imprint was rolling out financial aggregator support, e.g. allowing folks to connect to their Imprint powered accounts via Plaid. This has always been something folks want, but it’s particularly important in the realm of agentic commerce where more folks’ agents are analyzing their financial state for them. For this project, one of our engineering leaders (Ron), built the first pass of the feature at a low-burn while understanding the shape of the problem in a private alpha. He chatted through some of the details periodically to keep other teams aware, but it was a bit of a side project. However, once he found the full shape of the problem and had implemented a full solution, we cut the replica-lag across teams down to near-zero, identified and ran through the small number of remaining issues, and shipped it. Like many of our projects this year, it was never officially on a roadmap, and shipped a quality feature that our members have wanted for some time. How to follow the Explorer pattern The rough rules for following the Explorer pattern: Know your goal and sponsor: every initiative ultimately has to have a specific outcome it’s pursuing and a sponsor who’s bankrolling that pursuit. This doesn’t always need to be explicit, especially for smaller projects, but once a project goes beyond ~3 weeks of effort, if you can’t very explicitly identify who the stakeholder is sponsoring your project and they would not enthusiastically agree, then you are likely closer to “lost” than “exploring” Small working group is small: at most 5 people, and preferably smaller. Everyone in the group has to keep the entire project in their head for as long as possible to detect problems and opportunities Small working group is flexible: folks in small working groups have to “find a way to yes” rather than “find a way to no”. Exploring is about uncovering the fundamental shape of a problem rather than pretending we know the fundamental shape Publish progress in a public channel: explorers have to report home with the progress they are making so others are aware. This is both a Linear Project and a Slack channel. Make the narrowest viable changes to what already exists: when we introduce unnecessary changes, we invalidate others’ mental models about how the world works. When we haven’t made those changes with care, we’re not only invalidating others’ mental model, we are creating the expectation that we’ve done it very intentionally for a good reason, which has a chilling effect on others improving them later, which is very expensive, whereas the Explorer pattern depends on being as inexpensive as possible Exercise good judgment to identify reasonable hypotheses: discard bad ideas immediately, and then filter the rest by trying to implement them as quickly as possible. Once you see the shape of the implementation, you can figure out which of the remainders are interesting Hold assumptions constant to avoid getting stuck: the only way to navigate complex ambiguous problems is to hold things constant, even when you know they are imperfect. For example, to do headcount planning we have to know our revenue, to know our revenue we have to forecast it, to forecast it we have to know the day that partners will go live next year. We don’t truly know any of those things, so just anchoring on a plausible guess to unblock us is much more valuable than trying to get them accurate. A little prework is useful, but a lot is just artificial precision that’s a distraction from progress Hold space for being totally wrong: when we move fast, with low information, we always find the way out, but often it’s not the way out we anticipated when we got started. Being open to throwing it all away, and starting a second, third, fourth time Ship all the way to production behind a feature flag: features and products move fast when we get the pieces working every step from frontend to backend to data pulls. This is the first step of exploration. Just make sure it’s behind a feature flag that’s only enabled for internal folks!
Comparing two different ways of work and working environments.
I own an old, cheap TV. It has no Internet connection, no fancy smart features that make you want to install a Pi-hole, and no ask-me-again-later updates. However, it is connected to my own desktop computer through an HDMI cable, so I can watch movies and TV series from the couch. Setting it up used […] The post Making a dumb TV just smart enough appeared first on Quentin Santos.
Five days and 540km on a bike across Kyushu, without a laptop. Notes on the peace of riding all day, convenience store dinners, and Japan's emptying countryside.