nickabe
Joined 1 month ago
Joined 1 month ago
Ultimately, you spec out these tests and create deterministic code around them - but that doesn't mean that the tests didn't drift from the intended spec.
I think I agree with the author in that what you were TRYING to achieve is much more important than what you actually achieved (in code or tests) and actually using the product is your best defense to see if code / spec has drifted.
Basically every large company has gone all in on AI, and as a result the number of bots has (likely, I have no proof) exploded. Then as a result of that, they crack down on "potential bots" by banning them. Of course, all they care about is what % of bots they cracked down on now what % of real people. Then because they've gone all in on AI, you can't get an actual human to help you... just a bot they trained to always say no.
My current experiences in these arena: - Opened a Meta for Business account to try and buy ads. Immediate lifetime ban before taking even a single action. Most likely thing that looks like a bot? Opening a new account. - Got bot farmed on a Google Ads campaign, delivered definitive proof of it to Google. Never got a real human, just went back and forth with a bot who was told to acknowledge everything I said without admitting fault. End result - no refund, the bot farm still operates, and I have to be super careful when buying Google Ads. - Tried to open an account to post stuff on Reddit, every post gets instantly banned because I don't have enough karma. Try to start posting comments to get karma, same thing. IN fairness, this did eventually start to work - where I could post on certain subreddits and comment in others.
Overall the experience always has the same shape - something super opaque to the end user, no resolution options, and really you are left with no alternatives because every big tech firm is doing this.
So then the same AIs that create the problem recommend you try and get media articles published about it to draw attention to the plights of the real human caused by AI bots.
The natural response is to assume that corporation will be more efficient, and there the consumer will get a better end result. And, again, that was probably true for some period of time. The problem is in a corporate world you need to grow your profits by 3-5% a year (minimum) in order to be considered a "viable" investment. So what happens when your customer base isn't growing at 3-5%? Well you cut costs to improve your profits or you raise prices or both.
End result is the consumer ends up worse off, they got a one-time efficiency gain by switching from government to corporate - but then pay for that over decades.
Anything software related they will end up being "in", in some form or another. Why? They are already selling to enterprises and have their trust. The selling motion for Project Management software may be slightly different than Enterprise AI - but it's close enough to rhyme.
They will probably also end up in anything consulting related. Why? Well again most consulting comes from Enterprise or Government. They are already selling to both. Probably Enterprise moves away from Accenture / Deloitte / McKinsey towards Anthropic / OpenAI faster than Government - but still the point remains.
Selling plumbing services? Probably not.
Yes it all started with "natural language", but even AI has an understanding that you need more structure than natural language when you want deterministic results.
Like what matters is: - Does it do the thing it's supposed to do - Does it do it with a reasonable amount of resources - Does it do it without any obvious security flaws
Yeah, if they were nuclear codes you'd want to be really really sure and you'd probably want to check every line yourself. But if you're making a habit tracker or 95% of apps out there, it really doesn't matter.
There is definitely some skill in piloting the LLM, where you have an advantage if you understand what "good" is - but I'd argue it really isn't that necessary in most cases. McDonald's has had a lot of success selling food that most chefs would say isn't that great, but it fills that need at that moment.
One thing that has helped me make the LLM more consistent on scoring is deduction based rubrics. Start everything at perfect and deduct points for specific things (ie style, missed facts, etc). It gives much tighter final scores under these conditions (for me) than giving rubrics + samples.
Hyper focusing on detecting bots without thinking about the humans you're blocking is making the Internet a crappier place.
After that it still did it on various different views but it was much faster.
I think AI also has a lot of internal conversation - you can see it in the reasoning phase - where it will invent shortforms as it talks to itself. This also makes it really hard to follow AI text because it will often invent its own jargon.
Beyond that though, a really good way of testing is actually using the product you've asked it to build. In a pre-AI world that was the biggest beef I had with real developers. They would say "hey I built this thing" and never actually test it inside the app at all. I appreciate most people are going to say "those are bad devs" - but it was shockingly common. The view was always that this was something QA or the PM should do, but you never learn more than by actually using your own product (or code in this case).
No actions / no posts. I guess they determined the way we opened the account was too bot like. Sucks because we're real people that were trying to buy Meta ads.
But maybe doing something like this allows them to ease those restrictions, and then by charging for posts they have an ability to determine bots from non-bots in a more robust way. I'm doubtful it will actually work - because bots are exactly the type of thing that can and will try to open dozens of accounts to get around the 2 posts per month limit.
A simple system would be something like: - accuracy is most important - if tied on accuracy (ie both got 8/10) then tie break is done on speed
In general, across a lot of games - winning is a big determinant in who comes back. Right now it might be very difficult to beat JEV with the way your scoring is setup.
For my game in particular it's like a 47% chance that a winning player returns versus just 10% for non-winners.
If you limit the sample size, you end up finding more. For example, on my project when I tested 350 strings at once it failed to find 15 strings with "ai slop" that testing 10 strings at a time did find.
So, "gerrymandering" the districts to make it so the least popular "party" wins is the objective of the game. What's maybe not clear about the game is that each dot represents one animal and not say another mini district.