You should have seen some of the Flash sites people made in the mid 90s early aughts. They all seemed to be straight up screenshots of the desired website and then buttons stapled on random portions.
They were an accessibility nightmare, but you use what you got. I tried so hard as a kid to understand flash, but had to settle on MS Frontpage to publish my first RPG page.
Ah I interpreted it as 'of course they can't stop distillation if they couldn't stop a model from escaping its sandbox'
I can see how there's a big leap there, but I agree somewhat. If they are aware these are happening and can detect it as it is happening why are they not stopping them? What do you do there? It'll be cat and mouse for a while. Thinking of reasons they wouldn't try and stop it is just a lot of speculation in my brain.
It's probably a way harder problem than I think it is, but they are aware of them now, so I assume they are going to get more aggressive about it.
Let's say then that they can't detect them near real time or even a bit after, maybe they do have a big observabilty gap that no one has solved adequately.
The speed which they add features I've needed for governance is pretty close to the speed I 'manually' write those for my company. To me personally we are all just going fast and breaking everything and not having enough time to set up safe environments. I'm sure it's in the backlog.
I remember watching GigaOm on Revision3 back in the day, I think I stumbled upon it via Diggnation... nope I think it was CrankyGeeks actually.
It was the first newsletter I actually subscribed to back in the day! Sad to hear about his passing, his appearances on podcasts introduced me to the more business side of tech where I was just a hobbyist teen at the time.
I haven't had time to read the whole article, but I really appreciate the cross section of the world that reads HackerNews and plays STS2. STS1 and STS2 are my favorite games and to see this pop up here brought a big smile on my face. Thanks for sharing.
I have this same attitude. I've been a linux user for 24 some years I don't need to know why Linux broke, just fix x and move on.
I used to spend hours debugging video card issues and other modifications I've liked to make over the years and being able to describe my ideal system admin setup I could get onto what I actually wanted to do.
Heh, thinking about it now, I broke a MBR on a Windows install as a kid and if I would have had these tools I would have been able to fix it immediately, but back then it took me using enough Linux booted off live cds to learn debugging techniques to fix the MBR. And debugging is one of my best skills.
Seeing subagents working in Claude last summer, I saw it and told myself my job is going to be different and I can automate the hell out of my workflow
This read like poetry to me. Thank you for sharing it.
I have a linguistics background and a lot of my philosophizing lately has been on whether or not the emergent abilities of the LLMs is deep down a similar mechanism that creates our consciousness.
For a little bit I was working on having linguistics based evals for a kaggle competition. My challenge was whether or not I could mask things well enough to not trigger its internal state of certain phenomena, and that sent me down a rabbit hole that I'm still exploring.
This story resonated with a lot of questions that can come out of figuring a good solid answer to the what is consciousness question. The one I triggered for me is: Is our perception of time just a slow thread in the giant GPU we are running the universe on? Or more generally, what is time? That's a fun YouTube rabbit hole if you ever need one.
I have it record a series of gifs or videos that I look over. If something looks off I'll dig into it, but I break down work into very very small chunks that are usually easily verifiable or don't require multiple steps.
Another thing I have in the general sdlc process is having it add enough logging to verify features are turned on, configured as we expected, and that becomes enough feedback for most of my features.
I've been mostly focusing on being able to replicate this across stacks greater than 3 projects so far (with the eventual goal of having an agent be able to orchestrate our complete infra stack, and this being a large component of a DR plan to rebuild).
None of this is really new for us, I'm just the most knowledgeable in my group in how the different products across teams glue together so I've been creating these rube goldbergs as a prototype, and then having it iterate on codifying the parts that don't need a constant LLM. We were blessed to have an engineer a decade ago build out tooling for local container automation that matches 95% of the deployed infra stack. That last 5% sucks when you fall into it, but that's always been a truth. I've added and expanded the tool over the years with making it act more like the deployed environment networking wise, but a lot of things don't end up working well in docker containers on M series macs when most of our complicated virtualization in our private cloud can't run on them yet...
This is where most of my productivity gains have come, I have a special harness I move from project to project now that does my testing orchestration, lots of my work day is setting up a prompt or two early and just letting them loop till they return evidence that the feature is working having gone through the big QA loop.
I've slowly been optimizing for token use through the stack and Claude ends up making very tight for loops for most of the process and keeping token count even lower. It's been nice. A lot of my toil at work is just gone.
I have also been finding the MCP auth story to be really lacking was excited to see OAuth 2 support until I tried to get it to work at work and realized our idp implementation didn't support 2.1, and went into the spec and started wondering if anyone had a good experience yet. Luckily most of our environment can settle on a OAuth token env var standard until that's all in order.
Exactly, and for a given task you don't need to recall what your friend's brother's name is to do a git commit and push. There's a pull for more context to make these things better, but also the pull to make these execute in such a small context effectively when appropriate.
I'm more on team small tasks because of my love of unix piping, I keep telling folks, as a old Linux dude, seeing subagents work together for the first time felt like I was learning to pipe sed and awk for the first time. I realized how powerful these could be, and we still seem to be going that direction.
I kept reading about how bad Android Auto was for years but we finally bought a more modern used car and I can't believe they would ship that experience to customers. I had a week where I just had to unpair and re-pair Everytime I got in the car.
I would love to read about why that stuff is the way it is from the engineers, hmm that might be a good spelunking. I really must be missing something that makes it harder than I think it really should be.
Hah same exact setup one brick two ports and it charges everything even my laptop! I've been eyeing some of the ones with built in batteries, but I get a lot of mileage of one brick in the bag.
The steam deck forced me to finally pay attention to the usb-c ecosystem and I can only imagine how some non tech people might get with mysteriously bad or slow charging.
I find it crazy that Apple went back to magsafe in the m4 (maybe earlier but that's the machine I have at work). But at least you can still charge over usb-c.
When I've been working on stuff that requires a SSO login, I noticed that it makes, what I considered, hostile anti-user choices in defaulting to tracking pieces of information I didn't want to track and hadn't mentioned.
Fair that I didn't instruct it explicitly to make more pro-user choices, it just seemed to think slurping as much information into the backend was an default intention. Wasted a few more tokens to iterate on it to remove things, but it was IMO interesting enough that I finally submitted feedback around what I imagine is an interesting training problem.
I'm just a dev, but I appreciate the insights from other professionals.