@jonathoda For images, flipping between one and the other makes the eye notice the differences – it's good at focusing on movement. Maybe the same would work for tables if changes are per cell. Probably not much help for large-scale changes to the structure of the table.
@davefarley77 ... I can remember the exact instant when I realised that a large part of my life from then on was going to be spent in finding mistakes in my own programs."
– Maurice Wilkes, 1949
2/2
Thanks for all the kind words & shares of my radio doc, Becoming German. I'm thrilled it was pick of the week in the Sunday Times, Observer & Radio Times.
It's being repeated today on @BBCRadio4 at 3pm and is now on BBC Sounds.
Danke meine Freunde.
https://t.co/3Z0WIy1vXA
I'll be at @extremetuesday club on Tuesday 16th July. We're hosting it at #FordDigital...
An Open Space evening meetup, covering all things in and around #agile software development, leaning towards #extremeprogramming...
Sign up for free here:
https://t.co/4QPwryd63d
Digital and IT services are now core to keeping a government running smoothly, like transport and other infrastructure. Personally I would bring *more* IT in-house. A large team with lots of experience of digital service would allow better management of outsourced projects, imo.
One thing a new UK government needs to do is sort out the various disastrous IT projects.
Here's the goods transit system having a risky big bang upgrade on a Monday
Hey systems research folks! My team at @neo4j will be hiring for postdoc positions on some very cool next-gen database runtime stuff.
If you're PhD-ish and want to build kick-ass systems, ping me.
reminder that there's still alpha in Rob Pike's 1989 article on recursively composable window systems based on concurrent processes communicating with synchronous channels
An experiment for devs to try. I started keeping a "dev diary" while working on @breezbook . It was prompted by a statement by Stuart Ervine when I asked how others keep broader context of decisions behind code that are not visible in code, tests or comments.
I wanted to start simple, so it's just one long markdown file. My partner on breez, Metehan Altuntekin, suggested that a tool like Obsidian or similar might be more appropriate. But I'm happy I stayed with a simple text file. I can edit it in my code editor, while I'm coding, without breaking flow.
It's a good sounding board when I'm working on my own. I can write down my doubts and concerns, and just the act of getting them down helps me think them through better.
And I can feed it to an LLM and ask questions, like: remind me why I decided on @inngest for messaging? Or why might the location_id field on service be optional instead of mandatory.
I consider this a worthwhile experiment to try on dev teams. Yes, ADRs, but consider this as an alternative or complement.
And Stuart Ervine, if you have any experience reports to share, I'd be all ears.
The dev diary is here btw - https://t.co/U146ke1ybR
@MattStopa @_mostlyunknown @ThePrimeagen @thedevdad_ You need a backend web framework that does both routing and reverse routing. If the framework only does routing, managing links is tedious and error-prone. If the framework also does reverse routing, HATEOAS is straightforward.