FLOSS virtualization hacker, occasional brewer

  • 1 Post
  • 85 Comments
Joined 3 years ago
cake
Cake day: June 9th, 2023

help-circle


  • Oh totally. I’m fortunate I have off road parking and a beefy solar grid so my normal runabout and commute is functionally free.

    The UK has recently made the process of getting charging gullys for house hold street charging easier to get approved and installed. The remaining challenge is HMO’s and hi rises. We could either mandate lower rates for locals using public charging infrastructure or more ubiquitous low power charging available at hi-rise car parks given most cars will be parked for at least 8 hours “overnight”.


  • We took the electric car for our families European road trip last week which saw us land in Spain, loop through southern France before returning via Caen. While we were using an app too plan stops with high speed CCS chargers we certainly didn’t need to go out of our way. Unsurprisingly the major trunk routes are well appointed with fast chargers - generally cheaper than the UK fast chargers as well.

    Range anxiety isn’t really a thing I feel these days and having regular breaks helps with the quality of the driving.







  • I think the two principle arguements he’s making are open weights allow for misaligned models and these models are using distillation to more efficiently train.

    I don’t really care about the distillation point - it seems it’s just hoovering up the internet with extra steps. It’s really up to Anthropic to deal with by enforcing their ToS. Sauce for the goose etc…

    I can see the argument about alignment but it’s not a new problem. In the FLOSS world we generally don’t put restrictions on use on the code we release even if it might get used for bad stuff. It certainly wouldn’t hurt for the authorities to test open models to find out where the guardrails are but ultimately rather than banning the tech you need to enforce the law against the people that use the tech to do bad stuff.






  • I’ve long been off the critical path because as a tech lead I have a lot more random stuff (and meetings) to deal with. I’ve been able to vibe code some non-production stuff like scripts to unify feature lists across JIRA, specs and the upstream docs which has helped free up time to hand craft more code on production.

    I don’t care too much about the quality or maintainability of those scripts as long as they make my life a bit easier. I do care about the maintainability of the production code base.



  • The last big update to my git workflow was when I discovered --update-refs as it makes maintaining a stack of feature branches much easier. So far I really only have one “main” dev branch and then peel off the sub-branches at they need merging upstream.

    However I shall have to investigate how the history commands are exposed in magit. I can see it being useful if you have long held branches that take a while to upstream but are useful to have in your trees.