News for hackers. Stuff that matters.
Re:Kotlin creator's new language: a formal way to talk to LL... by onion2k on Thursday March 12, 2026 @11:51AM (#47352595)
Models aren't deterministic - every time you would try to re-apply you'd likely get different output (without feeding the current code into the re-apply and let it just recommend changes)

If the result is always provably correct it doesn't matter whether or not it's different at the code level. People interested in systems like this believe that the outcome of what the code does is infinity more important than the code itself.

Re:Kotlin creator's new language: a formal way to talk to LL... by dsr_ on Thursday March 12, 2026 @12:16PM (#47353115)
Let's rephrase:

Since nobody involved actually cares whether the code works or not, it doesn't matter whether it's a different wrong thing each time.

Re:Kotlin creator's new language: a formal way to talk to LL... by brabel on Thursday March 12, 2026 @02:45PM (#47355331)
You got it completely backwards. The claim is that if the code does exactly what the spec says (which generated tests are supposed to "prove") then the actual code does not matter, even if it's different each time.
Re:Kotlin creator's new language: a formal way to talk to LL... by ModernMech on Thursday March 12, 2026 @03:47PM (#47356106)
The point they are making is the tests are neither necessary nor sufficient alone to prove the code does exactly what the spec says. Looking at the tests isn't enough to prove anything; as an extreme example, if no one involved looks at the code, then the tests can just be static always passing and you wouldn't know either way whether or not the code matches the spec or not.

If anyone cared enough they could look at the code and see the problem immediately and with little effort, but we're encouraging a world where no one cares enough to put even that baseline effort because *gestures at* the tests are passing. Who cares how wrong the code is and in what ways if all the lights are green?

Re:Kotlin creator's new language: a formal way to talk to LL... by SpaceNoodled on Thursday March 12, 2026 @11:52AM (#47352619)
That's a huge "if."
Re:Kotlin creator's new language: a formal way to talk to LL... by gentooflux on Thursday March 12, 2026 @12:06PM (#47352899)
I usually invert those to reduce nesting
Re:Kotlin creator's new language: a formal way to talk to LL... by __loam on Thursday March 12, 2026 @12:14PM (#47353072)
The code is what the code does.
Re:Kotlin creator's new language: a formal way to talk to LL... by kennywinker on Thursday March 12, 2026 @12:43PM (#47353602)
The shoe is what the shoe does.

Except one shoe is made by children in a fire-trap sweatshop with no breaks, and the other was made by a well paid adult in good working conditions.

The ends don’t justify the means. The process of making impacts the output in ways that are subtle and important, but even holding the output as a fixed thing - the process of making still matters, at least to the people making it.

Re:Kotlin creator's new language: a formal way to talk to LL... by raw_anon_1111 on Thursday March 12, 2026 @12:54PM (#47353766)
The end is whether the code meets the functional and non functional requirements.

And guess how much shoe companies make who manufacture shoes in sweatshop conditions versus the ones who make artisanal handcrafted shoes?

Re:Kotlin creator's new language: a formal way to talk to LL... by kennywinker on Thursday March 12, 2026 @12:56PM (#47353801)
Ah yes - we should all strive to maximize shareholder value - triangle shirtwaist be damnned.

Btw in my metaphor, we - the programmers - are the kids in the sweatshop.

Re:Kotlin creator's new language: a formal way to talk to LL... by raw_anon_1111 on Thursday March 12, 2026 @01:13PM (#47354093)
If you are a “programmer” you are going to be the kids in the sweatshop. On the enterprise dev side where most developers work, it’s been headed in that direction for at least a decade where it was easy enough to become a “good enough” generic full stack/mobile/web etc dev.

Even on the BigTech side being able to reverse a btree on the whiteboard and having on your resume that you were a mid level developer isn’t enough either anymore

If you look at the comp on that side, it’s also stagnated for decade. AI has just accelerated that trend.

While my job has been at various percentages to produce code for 30 years, it’s been well over a decade since I had to sell myself on “I codez real gud”. I sell myself as a “software engineer” who can go from ambiguous business and technical requirements, deal with politics, XYProblems, etc

Re:Kotlin creator's new language: a formal way to talk to LL... by pjmlp on Thursday March 12, 2026 @01:22PM (#47354223)
What do you think programmers in offshoring consulting shops are? Sadly.
Re:Kotlin creator's new language: a formal way to talk to LL... by raw_anon_1111 on Thursday March 12, 2026 @01:41PM (#47354513)
Exactly. I work in a consulting company as a customer facing staff consultant - highest level - specializing in cloud + app dev. We don’t hire anyone less than staff in the US. Anything lower is hired out of the country.

That’s exactly my point. “Programming” was clearly becoming commoditized a decade ago.

Re:Kotlin creator's new language: a formal way to talk to LL... by kennywinker on Thursday March 12, 2026 @06:06PM (#47357915)
Ah, so you’re happy with the sweatshop existing - and you look down on those who work there. Good to know.
Re:Kotlin creator's new language: a formal way to talk to LL... by raw_anon_1111 on Thursday March 12, 2026 @06:30PM (#47358167)
I said nothing about looking down on them - I assure you developers in other countries don’t see themselves in sweatshop conditions.

But while you are clutching your pearls, where do you think your computer, clothes etc are being made?

Re:Kotlin creator's new language: a formal way to talk to LL... by bdangubic on Thursday March 12, 2026 @06:37PM (#47358230)
I worked with developers from 6 other countries (the “america first” slogan of the ruling part is missing a fine print that should read “americans last”) and not only are they not in sweatshop conditions, most of them live like kings on salaries they are making and are more “white collar” in their country than most SWEs here
Re:Kotlin creator's new language: a formal way to talk to LL... by raw_anon_1111 on Thursday March 12, 2026 @07:09PM (#47358522)
Isn’t that what I just said?
Re:Kotlin creator's new language: a formal way to talk to LL... by bdangubic on Thursday March 12, 2026 @07:42PM (#47358849)
ya, was just adding to it :)
Re:Kotlin creator's new language: a formal way to talk to LL... by uoaei on Thursday March 12, 2026 @02:12PM (#47354954)
Functional requirements are known knowns.

Out of bounds behavior is sometimes a known unknown, but in the era of generated code is exclusively unknown unknowns.

Good luck speccing out all the unanticipated side effects and undefined behaviors. Perhaps you can prompt the agent in a loop a bnumber of times but it's hard to believe that the brute-force throw-more-tokens-at-it approach has the same level of return as a more attentive audit by human eyeballs.

Re:Kotlin creator's new language: a formal way to talk to LL... by raw_anon_1111 on Thursday March 12, 2026 @02:44PM (#47355324)
Are you as a developer 100% able to trust that you didn’t miss anything? Your team if you are a team lead who delegates tasks to other developers? If you outsource non business things like Salesforce integrations etc do you know all of the code they wrote? Your library dependencies? Your infrastructure providers?
Re:Kotlin creator's new language: a formal way to talk to LL... by xpe on Thursday March 12, 2026 @03:37PM (#47355973)
It seems like ^ and ^^ agree to me. Am I missing something?
Re:Kotlin creator's new language: a formal way to talk to LL... by raw_anon_1111 on Thursday March 12, 2026 @04:12PM (#47356381)
I don’t know. I’m making a point that the only people whose sole responsibility is code that they personally write are mid level ticket takers.

I don’t review every line of code by everyone whose output I’m responsible for, I ask them to explain how they did things and care about their testing, the functional and non functional requirements and hotspots like concurrency, data access patterns, architectural issues etc.

For instance, I haven’t done web development since 2002 except for a little copy and paste work. I completely vibe coded three internal web admin sites for separate projects and used Amazon Cognito for authentication. I didn’t look at a line of code that AI generated any more than I would have looked at a line of code for a website I delegated to the web developer. I cared about functionality and UX.

Re:Kotlin creator's new language: a formal way to talk to LL... by uoaei on Friday March 13, 2026 @06:48PM (#47371028)
The difference is that you have theory of mind of your human counterparts -- you can trust that their reasoned explanations are consistent with what you know about them.

I have not encountered an agent yet that I can trust in the same way.

Re:Kotlin creator's new language: a formal way to talk to LL... by raw_anon_1111 on Friday March 13, 2026 @11:15PM (#47372959)
You give way too much credit to mid level developers and outsourced contractors….
Re:Kotlin creator's new language: a formal way to talk to LL... by pjmlp on Thursday March 12, 2026 @01:21PM (#47354207)
Yet the people voting with their wallets seem to go with cheaper option, regardless of what hides behind it.

Being shoes, offshoring, Webwidgets or AI generated code.

Re:Kotlin creator's new language: a formal way to talk to LL... by kennywinker on Thursday March 12, 2026 @05:01PM (#47357045)
Sure. People go for the cheapest option that fits their requirements, mostly.

But we’re the shoemakers, not the consumers. It’s actually our job to preserve our own and our peers quality of life.

Cheapest good option possible doesn’t have to be the sweatshop - tho the shareholders of nike or zara would have you believe that - the labor movements of the 19th century proved that’s not the case.

Re:Kotlin creator's new language: a formal way to talk to LL... by pjmlp on Friday March 13, 2026 @02:14AM (#47361227)
It is our job to keep our job, or leave if we don't agree with management, assuming to be lucky when there is an option to walk out and start anew right on the other side of the street.
Re:Kotlin creator's new language: a formal way to talk to LL... by kennywinker on Friday March 13, 2026 @12:45PM (#47366725)
This is what is sometimes called a “crabs in a bucket” mentality. It’s how you go from a middle class weaver, to an impoverished sweatshop worker in a generation.
Re:Kotlin creator's new language: a formal way to talk to LL... by jrm4 on Thursday March 12, 2026 @12:00PM (#47352782)
I would be very comfortable with - re-run 100 times with different seeds. If the outcome is the same every time, you're reliably good to go.
Re:Kotlin creator's new language: a formal way to talk to LL... by SpaceNoodled on Thursday March 12, 2026 @04:36PM (#47356713)
Even when it's wrong each time?
Re:Kotlin creator's new language: a formal way to talk to LL... by onion2k on Thursday March 12, 2026 @04:49PM (#47356889)
If it's wrong then it's not provably correct (for any value of 'proof').

How you define your proof is up to you. It might be a simple test, or an exhaustive suite of tests, or a formal proof. It doesn't matter. If the output of the code is correct by your definition, then it doesn't matter what the underlying code actually is.

Re:Kotlin creator's new language: a formal way to talk to LL... by FrankRay78 on Thursday March 12, 2026 @12:55PM (#47353784)
Sure, but where are the formal acceptance tests to validate against?
Re:Kotlin creator's new language: a formal way to talk to LL... by tomtomtom777 on Thursday March 12, 2026 @12:58PM (#47353836)
> If the result is always provably correct it doesn't matter whether or not it's different at the code level. People interested in systems like this believe that the outcome of what the code does is infinity more important than the code itself.

If the spec is so complete that it covers everything, you might as well write the code.

The benefit of writing a spec and having the LLM code it, is that the LLM will fill in a lot of blanks. And it is this filling in of blanks that is non-deterministic.

Re:Kotlin creator's new language: a formal way to talk to LL... by pjmlp on Thursday March 12, 2026 @01:19PM (#47354183)
> If the spec is so complete that it covers everything, you might as well write the code.

Welcome to the usual offshoring experience.

Re:Kotlin creator's new language: a formal way to talk to LL... by sensanaty on Thursday March 12, 2026 @01:32PM (#47354377)
That if at the beginning of your sentence is doing a whole lot of work. Indeed, if we could formally and provably (another extremely loaded word) generate good code that'd be one thing, but proving correctness is one of those basically impossible tasks.
Re:Kotlin creator's new language: a formal way to talk to LL... by xpe on Thursday March 12, 2026 @03:25PM (#47355823)
> but proving correctness is one of those basically impossible tasks.

To aim for a meeting of the minds... Would you help me out and unpack what you mean so there is less ambiguity? This might be minor terminological confusion. It is possible we have different takes, though -- that's what I'm trying to figure out.

There are at least two senses of 'correctness' that people sometimes mean: (a) correctness relative to a formal spec: this is expensive but doable*; (b) confidence that a spec matches human intent: IMO, usually a messy decision involving governance, organizational priorities, and resource constraints.

Sometimes people refer to software correctness problems in a very general sense, but I find it hard to parse those. I'm familiar with particular theoretical results such as Rice's theorem and the halting problem that pertain to arbitrary programs.

* With tools like {Lean, Dafny, Verus, Coq} and in projects like {CompCert, sel4}.

Re:Kotlin creator's new language: a formal way to talk to LL... by 0-_-0 on Thursday March 12, 2026 @01:40PM (#47354491)
Besides, you can deterministically generate bad code, and not deterministically generate good code.