Idle thought: maybe the world would be a better place if the de facto ‘learn to code’ tutorial was not a todo list (individual productivity) but a simple group poll (collective decision-making).
  • Read: Doughnut Economics
  • Reflecting back and seeing them published on my website, I realise my work notes each day are a little mundane.
    • I imagine most people aren’t that interested to see them.
    • But, I do like the fact that they stimulate me to publish to the garden even on days where outside of work I have little time for it.
    • And I find them a helpful piece of reflection.
    • So I think I’ll experiment with putting them off in links from the main journal post. So people can read them if they want, but they won’t be right up in your face with visual noise.
  • Reading:
    • I like the emphasis on an economics that is distributive by design and regenerative by design.
    • Also like the occasional references to . Not convinced yet how applicable to economics it is – but I just have a general interest in it from days.
  • Listened:
  • Today at work I:
    • Responded to a personal message from a community member.
      • We have a community and friends within it, and sometimes personal messages come via my work channels.
    • Scheduled in some things for when I’m away.
    • Did the daily inbox trawl.
    • Looks good. Only skimmed it, but they mention as one of the positions held.
  • Today at work I:
    • Did the daily inbox trawl.
      • A lot of the emails are automatic alerts that take up a lot of my time checking. I kind of need to see them though.
      • I wonder if there’s a way of flipping it so I only see them if something has gone wrong.
      • The trouble then, though, is you don’t realise if the alert itself has stopped sending.
    • Responded to questions from the team on Slack.
      • Schedule tasks/actions in as a result.
      • Either as ‘unplanned’ work for the day if it needed doing today.
      • Or for a future date if not urgent.
    • Quickly added a cache around a slow endpoint.
      • It was (a) meaning some automatic tests were very slow to run.
      • (b) possibly crashing the app when the tests were running.
      • I patched it quickly in on live (naughty, but needed) and now need to properly add it into the repo.
    • Tested app-to-app connection between app and WP site API as part of migration tests.
      • I always app-to-app connections and APIs. Prefer them to user interfaces 😀
    • Attended team meeting.
    • Did some layout/content tweaks to our main website.
      • Fiddling around with CSS and layout is not top on my list of fun things to do. Always takes longer than you expect.
      • Some yak shaving to be done based on npm install failing. Haven’t got the time to shave that yak right now.
    • Do some quick estimates of how long potential pieces of work should take.
    • Cross-posted a social post on Mastodon.
    • Kicked off a new sprint in Jira (late, as I was off on leave when it technically started).