218 karma · joined March 20, 2024
Mistakes are a cost of doing business with engineering, even the kinda sorta engineering programming looks like. An environment that helps to prevent mistakes from making it through testing and review should be the focus, but I guess there is value in identifying an individual as being especially mistake prone.
So all of a sudden all focus is on the word "determinism", and before even going down this route you have to agree on what aspect of the subject are you declaring to be "deterministic?"
Its sort of like chatting with libertarians, as soon as you agree that taxation is theft and democracy is tyranny then all problems melt away!
Now there are still obviously holes everywhere remaining in my bot slaves cell that still need to be closed off, like syscalls, inline asm, taking address of, calling anonymous functions all that mess, I mean how can you make c secure against fundamentally insecure input like web server contact forms, or llm outputs?
So sure, c sucks but I'm still into it so why not just give the llm access to parts of c required for what I want done? Why not just write a "pass through" for a small subset of c that looks more like the old timey pascal but with curly brackets instead of begin / ends?
Sort of like what they did with javascript, because fundamentally your web browser javascript engine is tasked with running unsecure input.
Being a now hobbyist programmer, AI is just fun for me chatting with it, throwing structs and snippets at each other, but boy am I reading some horror stories about what it does for jobs, working conditions and code quality. The thing is, its just humans making great inventions and then as usual, fucking everything up with them.
Once I ditched the library idea and just coded to the spec things went much nicer lol it turned out to be a relatively normal socket coding project. Just hobby code tho.
"what happened year 1867 japan no social rules"