a pale slim ghost

asymptotes (1) barbican (1) blogging about blogging (3) bracken house (1) burnout (3) camping (3) chess (1) choir (5) climbing (1) films (4) floorp (1) games (2) greenbelt (1) holiday (1) hospital (1) inlaws (1) kettricken (2) keyboards (1) lasers (1) leicester (1) london (1) meetings (1) melting (1) metal gear (1) minecraft (2) modular (5) music (4) musical (1) need for speed (1) operation mincemeat (1) origami (2) ourple (1) peak district (1) photos (1) platforms (1) secrets (1) sick (1) skin (1) supercars (1) synth repair (1) tech lead (2) theatre (1) tool kit (1) weeknotes (22) work (5)

Tag: tech lead

  • weeknotes #3: business horoscopes

    content warning: wild animal injury

    1. been watching the Fast & Furious films with friends

    • once a week, on a sunday afternoon
    • we sync up the films, hit play, and pretend we’re mst3k via Slack
    • they’re actually pretty good, even the bad ones
    • also i’m spotting how much of an influence they had on the Need For Speed franchise in the early 00s
    • speaking of which:

    2. i’ve been playing a lot of Need For Speed: Most Wanted (2005)

    Read more…

  • weeknotes #1: fried liver attack

    1. WOW I HAVEN’T BLOGGED IN A WHILE

    • hahaha funny ironic meta blogging joke

    2. okay so i’m the Tech Lead of the FT.com Platforms Team now, what’s up with that

    • my(!) team solves common developer problems so every other team can spend time doing not that
    • we own a lot of stuff, like seventy repositories out of the three hundred ish in the Customer Products group
    • we’re a fairly new team, there were predecessor teams but basically none of the knowledge about what we own has survived
    • we’ve got a lot of catching up to do! we started rewriting our documentation last year and we have a hitlist of what knowledge we’re missing
    • but also we’ve jumped in the deep end with a beeg rewrite of the FT.com developer tooling
      • the line i use in presentations is “they’re used literally every day by literally every developer in Customer Products, and they’re broken”
      • they’re actually public, that’s odd
      • this week is the second “mob programming” week we’ve done on this project
        • we cancelled all our meetings
        • we set some goals
        • we worked on VS Code Live Share (for a couple of hours at a time! pairing is exhausting, remote pairing is gggggggggggg)
        • we’ve written more than a thousand fucking lines of code with three developers in one week, what the heck
      • find out next time on dragonball z
    Read more…