Joke is more about the fact that quite a lot of 30 under 30 end up serving prison time - mostly because they think they are smarter than everyone and that they can BS and get away with such things like one from TFA.
There is still a lot of engineering to be done with LLMs. Maybe not exactly writing code but I think a lot of optimization problems will be there no matter what.
Some people treat toilet as magic hole where they throw stuff in flush and think it is fine.
If you throw garbage in you will at some point have problems.
We are in stage where people think it is fine to drop everything into LLM but then they will see the bill for usage and might be surprised that they burned money and the result was not exactly what they expected.
Yep. I hate to predict the future but I’m betting on small, open models, used as tools here and there. Which is great, you can get 90% of the speed up with 5-10% of the cost once you account for the full costs in both time and money.
The economics and security model on full agents running in loops all day may come home to roost faster than expertise rot.
If I am writing backend code I am mostly in a single IDE window moving tabs with code files to other screens is working but is inconvenient.
When I work on frontend I much rather have preview on second screen and most likely reference next to it.
When writing documentation or requirements I cannot imagine working on a single screen as essentially I am integrating multiple data sources into one, like I need to see how app looks now and before release, what changed and still have my working space for draft.
Switching windows to quickly look up documentation is fine but when creating requirements having time to understand what needs to be in which place how it has to evolve I need to have it right there so that my imagination doesn’t runaway.
I would argue that „doing shit” should be done by dummy automations. AI should be used to help build that automations or step in when dummy automation breaks.
For now too many people will use AI for stuff that deterministic stupid code would be much more efficient.
Doing barrel roll, twist and speed up - radio to airliner „see buddy can you do that?”
Airliner „wait a moment” - some time passes nothing happens - airliner „hey buddy you seen that?” - f16 „what? Nothing happened” - airliner „I went to toilet on the back, took dump, made myself a coffee and strolled back to cockpit”.
Yeah, it’s not a great name. But it originates from the government. When somebody without a security clearance needs to go to a secure area, they must be escorted by somebody.
When the blog post mentioned Hegseth and “digital escort” in the same sentence, I was surprised to learn it wasn’t about his OnlyFans habit at his work desktop.
Your bank doesn’t depend only on cryptography. It would be still a lot of effort to simply make transfer from a bank account. Quantum computer will not magically give an answer for a password of a hash you don’t have. TLS is moving to post quantum as we speak.
For crypto currency you have all the data you need to break whole system ready in your hands as you will be able to produce private key from public keys of wallets. Cryptocurrency depends only on cryptography.
2. Deriving the private key(s) from the public key(s)
3. Creating and broadcasting its own transaction using the stolen keypairs before the original transaction confirms (presumably with a higher fee to win the confirmation race).
Please correct me if I'm wrong.
EDIT: correction: every transaction completely spends any selected UTXO of an associated keypair, not all of the "source keypairs' funds". Thus the attack vector also includes being able to steal from any keypair that has ever made a transaction and also has UTXOs.
The newest transaction mechanism (taproot; P2TR) exposes the public key of the receiver as part of the transaction. If it becomes more commonly used, the supply of bitcoins with exposed public keys would start going up again. See figure 5 of https://arxiv.org/pdf/2603.28846#page=14 .
reply