3,388 karma · joined August 5, 2009
[ my public key: https://keybase.io/kmarekspartz; my proof: https://keybase.io/kmarekspartz/sigs/lAuti1mlFpdPEev0ARi4yG2scPClzuqROymp-BEAtUc ]
There are compounding incentives for this. I see this as the most likely outcome, though it will likely be stepwise rather than gradual.
If there is an AI bust, we will have a glut of surplus hardware.
Unsure about integrating it with Pocketbase but I imagine it is reasonable to do.
jsonformat -> jq
running -> pgrep
Hmm, I don't think any of these were true with non-AI software. Commonly held beliefs, sure.
If anything, I am glad AI is helping us revisit these assumptions.
- Software vulnerabilities are caused by mistakes in the code
Setting aside social engineering, mistake implies these were knowable in advance. Was the lack of TLS in the initial HTTP spec a mistake?
- Bugs in the code can be found by carefully analysing the code
If this was the case, why do people reach for rewriting buggy code they don't understand?
- Once a bug is fixed, it won’t come back again
Too many counter examples to this one in my lived experience.
- Every time you run the code, the same thing happens
Setting aside seeding PRNGs, there's the issue of running the code on different hardware. Or failing hardware.
- If you give specifications beforehand, you can get software that meets those specifications
I have never seen this work without needing to revise the specification during implementation.
I chuckled at this one because I consider most modern languages to be homomorphic to Algol-68.
> int partition_branchless(int* arr, int low, int high) {... for (int j = low; j < high; j++) { ... }... }
That for loop is just a sugared while loop which is just a sugared cmp and jmp
Instead, I would point to the physical trauma of a concussion as the differentiating factor.