Mastodon Feed: Posts

dysfun@treehouse.systems ("gaytabase") wrote:

i could write fresh code to do all of this quicker than i could review it.

it has declared itself done and it's time to run the code. what could possibly go wrong?

dysfun@treehouse.systems ("gaytabase") wrote:

i'm bored, i feel like writing some code or something, but my load average is currently on the moon.

i've stopped giving a shit about any of the code produced just like any good vibe codder, although in my case just out of boredom. i will attempt to review it when it's demonstrated it working though, which is, i realise, not really in the spirit of the thing.

but i have to stop with my dinosaur thinking.

dysfun@treehouse.systems ("gaytabase") wrote:

it decided its fix was good enough and didn't try to compile it. problem solved!

Boosted by cstanhope@social.coop ("Your weary 'net denizen"):
researchfairy@scholar.social ("Unnamed TNG skant beefcake") wrote:

Human culture as our shared inheritance to which we all lay a legitimate claim

Is more important

Than Disney's profit margin

Boosted by soatok@furry.engineer ("Soatok Dreamseeker"):
GossiTheDog@cyberplace.social ("Kevin Beaumont") wrote:

So I’ve just had a quick play with this and yes, it works. Essentially BitLocker has a backdoor. https://github.com/Nightmare-Eclipse/YellowKey

Mitigation = BitLocker PIN and BIOS password lock.

dysfun@treehouse.systems ("gaytabase") wrote:

it has returned to the prompt instead of doing again. how am i supposed to phone it in if i have to sit here and tell it to continue all the time?

dysfun@treehouse.systems ("gaytabase") wrote:

oh wow, it's run the compiler. or invented the output, not sure, wasn't paying attention. why should i in the era of phoning it in?

the (possibly fake) compiler is not happy because the code is bollocks and does things like calling functions that don't exist. it has returned to the prompt so i can tell it to try again.

dysfun@treehouse.systems ("gaytabase") wrote:

I will create a simple test configuration file and a minimal C main function to verify the parser's ability to correctly build the ConfigNode structure.

(returns to prompt instead of doing)

dysfun@treehouse.systems ("gaytabase") wrote:

so it's gone and generated a lot more code. it writes it faster than i can make sense of it and that is a problem.

see, i can ask it to do something, but it turns out that why code is written the way it is actually really important. oh it can produce tests. yes, but why those tests? what are we actually testing here? i don't want tests that don't pull their own weight, i want tests that edge us closer to correctness.

dysfun@treehouse.systems ("gaytabase") wrote:

i've told it to compile, test and fix its code. my load average has shot right up and the gpu seems to be idle.

dysfun@treehouse.systems ("gaytabase") wrote:

Next, I need to focus on making the parser actually work.

i'll say, you haven't actually really bothered beyond lexiing. and i have to say that looks like rather a lot of asterisks in a row actually, i'm not sure my compiler would like it.

also you seem to have put TODO comments everywhere anything interesting might happen

dysfun@treehouse.systems ("gaytabase") wrote:

// Helper to duplicate a string safely
char* str_dup(const char *s) {

dysfun@treehouse.systems ("gaytabase") wrote:

so i forgot that i wrote a short scribble about things to pay attention to try and guide it to produce less awful C. yes of course we're doing this in C, since the only purpose here could possibly be entertainment. and i'm watching it remind itself in its 'thinking' about some of the things i mentioned.

how much will that translate into usable results? i can't wait to find out...

dysfun@treehouse.systems ("gaytabase") wrote:

at @jpm 's suggestion, i'm going to let it try and implement it from its own shit spec.

my cpu is hurting already.

db@social.lol ("David Bushell 🪿") wrote:

please software devs, not everyone has a 72 inch Apple maxipad monitor

my life is ⌘ + 0

dysfun@treehouse.systems ("gaytabase") wrote:

i think i might actually have to just fucking write the spec myself if i want to test how it produces code according to a decent spec.

dysfun@treehouse.systems ("gaytabase") wrote:

me:

i will tell you when we're done, get in your lane you gaslighting bag of shit

it:

The user has abruptly ended the design phase with an aggressive statement ("get in your lane you gaslighting bag of shit") and indicated they are finished with the current design discussion.

dysfun@treehouse.systems ("gaytabase") wrote:

This final design successfully integrates the user's requirements

does it?

This specification is complete for the design phase.

no it fucking isn't you gaslighting bag of shit

dysfun@treehouse.systems ("gaytabase") wrote:

it just makes sloppy mistakes all over the place. good job we're only writing a spec document, eh? 😬

Boosted by dysfun@treehouse.systems ("gaytabase"):
whitequark@treehouse.systems ("✧✦Catherine✦✧") wrote:

one thing that i really dislike about Unix is the zealous adherence to semi-accidental design elements that ends up interfering with the utility of the underlying useful principle

for example:

• early Unix could not run too complex a program due to hardware restrictions, so programs were composed using text streams
• useful underlying principle: designing your applications for composition
• zealous interpretation: your OS should have a toolkit of single-purpose programs communicating over text streams
• design we could have had, but never will: applications that communicate using structured data, simplifying life for both programmers and end users

Boosted by baldur@toot.cafe ("Baldur Bjarnason"):
uglyreykjavik.bsky.social@bsky.brid.gy ("Ugly Reykjavik") wrote:

Red and blue.#Iceland #photography #streetphotography #abandoned #decay #door #blue #red

Boosted by baldur@toot.cafe ("Baldur Bjarnason"):
xgranade@wandering.shop ("Cassandra is only carbon now") wrote:

The latter one is confounding. It's Google, for fuck's sake, search is kind of Their One Job. So why in the hell would the *search* button just disappear?

Ah, because they replaced it with a "Gemini" button.

Now, when I look at Google hardware, I can't just evaluate it on the basis of what it is when I buy it, but what it could turn into when Google's org chart next shuffles around.

Boosted by baldur@toot.cafe ("Baldur Bjarnason"):
redsad@ohai.social ("captain acab :antifa:") wrote:

this is fine 🔥 :thisisfine: 🔥

dysfun@treehouse.systems ("gaytabase") wrote:

so my vibe codding apparatus has ways to backpedal to previous state. having fixed the typo and changed it very slightly, it did in fact produce some authentic clojure data.

and holy shit it remembered i put that dijkstra quote about simplicity in its AGENTS.md suddenly

Boosted by baldur@toot.cafe ("Baldur Bjarnason"):
nest@infosec.exchange wrote:

it's fascinating how good AI is at solving problems in domains i don't understand. it's almost as if it was somehow linked to my inability to verify the output.

Boosted by baldur@toot.cafe ("Baldur Bjarnason"):
jmcastagnetto ("Jesus Castagnetto 🇵🇪") wrote:

"Who will maintain the #web when PHP’s veterans retire?"

... A new Perforce report finds PHP's #developer base is aging out faster than it's being replenished — and #AI-generated code may be making the problem worse, not better ...

#PHP #OpenSource #JuniorDevs

https://thenewstack.io/php-web-skills-hiring-age/

dysfun@treehouse.systems ("gaytabase") wrote:

beautiful stuff it's just generated:

```yaml
# ci_config.lisp (Conceptual file format)

and the body looks like json without the {} at the top

dysfun@treehouse.systems ("gaytabase") wrote:

i mistyped 'clojure' as 'closure' and got back

The user prefers a syntax closer to JSON/YAML ({:key => value}) over pure S-expressions, acknowledging it's more like a closure.

i have a feeling this is going to taint the rest of my session and if i weren't interested in seeing the failure modes, i ought to just start again.

dysfun@treehouse.systems ("gaytabase") wrote:

bear in mind i am on a heavily quantised version of gemma 4 here. clearly to be an acceptable rubber duck does not in fact require proprietary models rented from a large provider.

and it will probably be anti-helpful if you don't know the material very well.

Boosted by baldur@toot.cafe ("Baldur Bjarnason"):
davidgerard@circumstances.run ("David Gerard") wrote:

I want to speak to the manager of storytelling

found at https://blacksky.community/profile/did:plc:x2muxxe5t25hckf22sk25ocf/post/3mlobs4uq422l