Notices by James Broadhead (jbo@mastodon.social), page 2

@Eramdam I don't have a good handle on what their business plan is

@Eramdam it's for the advertisers. They pay for 'authenticity', they fear brand confusion

@aolgrandpa oh wow, I see what you mean. You could play the two on top of each other

@bagder thank you! Loved my iRiver 😁

@shipp @GrapheneOS it's really great if your car supports it

@offset___cyan @soc I've never seen a good counter to this take
It's weird to compare it with the elegance of something like nix

@grobmeier it had heart! I hope the new one is as good

@HayleyMulch we can only hope

@markgrieveson 7 😅

@markgrieveson augh! The colors switch randomly depending on the day! I regret having followed the link on this toot!

I worked Helpdesk for 10 years and it made me who I am. Your disrespect is a signal you don’t really understand what it takes. What being accountable for every second of your work on the line with someone who needs you to succeed entails. It is a filter. I am better because I had to be.

It's useful to remember that it doesn't "learn" as the conversation goes on. It merely has a smaller set of token paths to explore. It's a statistically constrained GPT, but the underlying model's unchanged.

Refining the actual model can cost $millions.

I’m very adamant about using “toot” instead of “post”. I’ll die on this hill, but hopefully not today because I have lots of errands to run, like buying stamps at the toot office.

@danhon oh man, I can just see it now. One made of fire-steel, the other with a saw-wire

@bornach @andrewnorthrocks @jhpot YES

@mcc it's kind of a miracle that we can get them to do anything

@falun all good - thanks for messaging 😀

^[2] maybe with some kind of rotation system, so that embeds get a chance to work on large initiatives and get 'refreshes' on culture and practises

Looking ahead - how to structure an org; centralise knowledge and responsibilties "the SRE team" / "the Frontend team" versus embeds & guilds. I lean towards having a Core Team with ownership, with embeds who distribute knowledge and ensure standards are followed.

Still trying to figure out what I think about patterns where the same codebase is deployed into multiple roles.
I think it avoids some of the problems with microservices, but risk the code-entwining of monoliths.