There's a date system in computers that uses a single 32-bit integer to count the number of milliseconds since January 1, 1970. I believe that counter runs out in 2036 or so.
To get around this, that 32-bit integer is being changed to a 64-bit integer.
But you know how these things go. There will likely be systems that don't get updated.
Would you trust an LLM to write code to handle date calculations in this environment?
Would I trust any random to write #vibecode to change the date?
No.
Would I trust a skilled operator?
Yes.
Folks, especially folks who can't use #Ai tech ascribe magical, mythological properties to #LLM
Vibecode produces deterministic code that can be tested 6 ways till sunday
Plus when you learned how to effectively vibecode, there are checks and balances as you code.
The wood folk think you rattle the tin until dice fall out.
Which is kida sweet in its naivete.
Most programmers out there are still learning how to #vibecode, there were some spectacular failures (AWS, Clownflare) where vibecode got pushed to prod with no testing.
The curve of competency decreases with the time using #Ai assistant.
The most ignorant vibecode commentary is from the folks who have never "written" anything with Ai.
Would you pay heed to a practitioner who does not practice in field?
Nonsense like "Debugging vibecode is hard", Vibecode is random, and our learned OP, "vibecode will keep programmers busy for generations"
Don't need programmers for my projects 😁
Tofu Golem
Lily Star
Wulfy—Speaker to the machines
Vladyslav