Daniel Whitenack: Something that I’m kind of getting in what you’re saying as well, which I know is often a misconception that I run into when I’m either doing workshops, or working hands-on with people with generative models, is there’s typically this misconception that you need to package everything into a single prompt, and then output your final result as a sort of one-step thing. I’m getting the sense that your workflow, for one, it probably involves multiple calls throughout the codebase, because of the context size; I would assume it’s partly because of that. But then also, you mentioned this kind of iterative element, where - hey, there’s kind of big rocks that you can move, that are the sort of worst offending areas, so there’s hierarchy in that respect… Bt also, it seems like - let’s just assume; I know it’s not a good assumption, but if we assume that a person’s codebase is fully tested, integration tests, unit tests, it seems like this is something you could just loop over and over and over again to get increasing optimizations, probably with diminishing return. Could you speak a little bit to how you as a team think about that chaining element, I guess would be the way to say it? And then also, maybe iterative element.

Drew Marshall: Exactly. You buy a really nice 4k or 8k UltraHD TV, and you plug your aerial into it, and you wonder why it is that it doesn’t look very good. Well, you have to make sure that your network is aligned with the hardware you’re running it on. That’s just how it is.

So in terms of a home internet connection - and these days, home working, and home internet, and all the rest of it are now in one big melting pot. So my first question would be “So how important is the internet to you?” If the answer is “Well, actually, I run my business on it. I run my life on it. Actually, I want this to be as near as is reasonably possible 100% up”, then I would say you’ve gotta be really looking at two connections, like you have, ideally from two different providers, because that covers off “What happens if the network goes bad? What happens if something bad happens?” And actually, we’ve covered you off – so not only are you with Vodafone and Trunk Networks, but actually… Vodafone is with CityFibre, so that is a different physical cable in the streets, that’s to a different physical aggregation point, that’s plugged into a different physical bit of network, in Vodafone. And then we’ve given you an Openreach circuit, which is why it’s asymmetric, not symmetrical like CityFibre would be… But that’s then on a separate piece of fiber, taking a separate route, in separate ducts, different bits of road, that will go back to the BT exchange, and then over a different backhaul, onto us as a different network… So if any one of us, and if any one of those components goes bad on you - give or take, 30 seconds, you’ll fail over - your life will continue, and depending on what you’re doing, you may not even notice. That’s kind of where I believe people should be. We can fail over transit providers. We can have a major BNG failure he says touching which hoping that doesn’t happen, but… We can suffer those things; we’ve got more than one of them. Customers simply end up disconnecting and reconnecting somewhere else. And although that may not be completely seamless, hopefully within 30 seconds to a minute your router has done its thing, our network’s done its thing, you’re back connected, we’re all online, everybody’s happy again.

Alex Ellis: Yeah… I can think of about half a dozen software maintainers in the industry that I know quite well, and I think we all feel like we’re in the same boat, which is that being a maintainer and leading a project can be a very thankless task, where people will expect much from you and very high standards, and they’ll potentially just taking until you burn out. So one of the things that I think people learn - certainly that I learned very early on - is to try and set boundaries.

My wife has helped a lot with cooking meals when I still had a day job, doing most of that kind of stuff, so that I could spend those extra 2-3 hours working through issues, or helping users, or whatever it may be.

It’s also meeting with the end users… Working late into the evening, meeting with BT, or Minio, or whoever it would be at the time, who had reached out very excited about the project, and kind of had this expectation that a big company was behind it, with a lot of money and a lot of resources; the actual fact - it takes a lot of energy to keep something like that afloat.