If they're handling it as “website, don't care” (because they're training on everything online) they won't know.
If they're treating it specifically on “code forge” (because they're after coding use cases), there's lots of interesting information that you won't get by just cloning a repo.
It's not just the current state of the repo, or all commits (and their messages). It's the initial issue (and discussion) that lead to a pull request (and review comments) that eventually gets squashed into a single commit.
The way you code with an agent is a lot more similar to the: issue, comments, change, review, refinement sequence; that you get by slurping the website.
What I find perplexing is the very respectful people that pay those subscriptions to produce clearly sub-par work I'm sure they wouldn't have done themselves.
And when pressed on “this doesn't make sense, are you sure this works?” they ask the model to answer, it gets it wrong, and they leave it at that.
I mostly read those signs as “don't go there unless you already know you can” which as a “tourist” I just assume can't (unless I'm a local, and figure it out).
What I've recently found troubling is the places that use similar signs for emissions controls. With a rental you usually have a recent enough car that you can ignore those.
Being able to distinguish between “low emissions zone, but any car from this decade can go in” and “local traffic only, you need to live in this neighborhood to enter” in a foreign language, bit me a couple of times while traveling.
That was probably done by fiber[1] the code specifically took the param from it in the function passed to the Get(path string, handlers ...Handler) Router function. c is the *fiber.Ctx passed by fiber to the handler. My code took the string from c.Param("name") passed it to url.QueryUnescape then another function which had a mutex around setting the key/value in the map. I got the hint it was slices and something modifying the keys when I found truncated keys in the key list.
My guess is fiber used the same string for the param to avoid allocations. The fix for it is just to create a copy of the string with strings.Clone() to ensure it does not get mutated when it is used as a key. I understand it was an issue with my code, it just wasn't something I expected to be the case so it took several hours and using the debugger to find the root cause. Probably didn't help that a lot of the code was generated by Grok-4-Code/Sonic as a vibe coding test when I decided to go back a few months later and try and fix some of the issues I had myself.
And… I actually don't have an issue with it to be honest. I've done the same myself.
But this mutability should never escape. I'd never persist in using a library that would let it escape. But apparently… it's intentional: https://github.com/gofiber/fiber/issues/185
Oh well. You get what you ask for. Please don't complain about maps if you're using a broken library.
Considering Google Classrooms is used by a significant percentage of public schools, I have no idea why you think Portugal is special here.
Also, given the frequency of families having issues with the Cuco MDM used to lock out the Windows computers they handed to kids during COVID, and what kids do which such computers, I'm doubly unsure it was a smart idea to offer shitty Windows laptops vs. shitty Chromebooks.
Schools around the world give kids Chromebooks (or iPads) because they're harder to fuck and easier to unfuck. Windows still sucks at this, and no one came up with a coherent — locked down — Linux platform to achieve the same.
I am Portuguese, have family ties with teachers still into the active, I guess.
That kind of stuff is mostly US school system, schools in countries that go with USA into G7 meetings, or wealthy enough for that kind of stuff maybe.
Not every country has the pleasure to enjoy a school system swimming in money to offer computers to kids, in every single school.
Not even during COVID was every Portuguese family granted the pleasure to have a device offered to them, some lucky ones did, a large majority only saw them on the news, and as usual the burden was on the family to come up with a solution to all their kids attending the various school levels.
And lets not even go to such great stuff like Magalhães, e-escola, and who got to profit from it.
I'm writing from personal experience in a middle of the table public school, with a single IT guy helping out around 1000 pupils, who regularly get their computers locked with said MDM.
It's possible other school districts with a less diligent, but similarly overworked, IT guy just give up and don't even hand out the computers anymore, especially if they don't have enough of them, after being on their second or third kid.
Those are certainly above 6 grade, because I am aware of few schools, whose desktop computers, with luck get to a have a visit from some local computer store, on demand after lots back and forth with the regional ministerium office regarding how it gets paid.
None of them has hardly an IT guy, or girl on site, and as usual "em casa de ferreiro espeto de pau", acquaitances have been invited to have a look at their computers.
The IT guy is the TIC professor, who does it in excess of work. The guy is the son of the former TIC professor. And of course, I was roped in to help for my kids’ classes.
And yes, it includes kids from at least 2nd grade. My COVID kids got their laptop on 1st grade, but that's no longer the case.
I actually hate AI in my core, to the point that if it gets too much more advanced I'll likely be in existential crisis, so don't attack me on those grounds. Given it exists, I'm going to find what's good about it though. I do think the problem of AI existing has to be confronted. Maybe one solution is what the human does is produce specs like the HTML 5 one, and what the AI does is implement it in software.
Yes, in the only successful OSS project that I “maintain.”
Fully vibe coded, which at least they admitted. And when I pointed out the thing is off by an order of magnitude, and as such doesn't implement said feature — at all — we get pressed on our AI policy, so as to not waste their time.
I don't have an AI policy, like I don't have an IDE policy, but things get ridiculous fast with vibe coding.
If they're treating it specifically on “code forge” (because they're after coding use cases), there's lots of interesting information that you won't get by just cloning a repo.
It's not just the current state of the repo, or all commits (and their messages). It's the initial issue (and discussion) that lead to a pull request (and review comments) that eventually gets squashed into a single commit.
The way you code with an agent is a lot more similar to the: issue, comments, change, review, refinement sequence; that you get by slurping the website.
reply