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 .
There is no „stupid” I often write „(this is stupid|are you stupid) fix this”.
And Claude was having in chain of though „user is frustrated” and I wrote to it I am not frustrated just testing prompt optimization where acting like one is frustrated should yield better results.
Feels like you never worked at corporation it goes more like this:
"old employees who know the environment and are in tune with community are playing safe so they don't bring in immediate results, feels like progress stagnates, so they move those people to other tasks"
"new clueless manager joins, has to come up with a brilliant idea (that actually is bad across the board for someone who understands the environment) to get quarterly bonus, then convinces bunch of |out of touch suites| with power point presentation where numbers go up"
"he gets burned by community response, becomes more conservative - next quarters he is moved away or he moves away on his own - new clueless can come into his place"
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.
reply