Scrum == micromanagement, you can't automate micromanagement.
Agentic SDLC is a complete opposite of Agile/Scrum/SAFE.
For greenfield development / new features use mini-waterfal / Shape Up.
For reactive work use Kanban.
What would you use Scrum's Sprints for? Bin-packing of Jira tickets into sprint cycles less useful when you can implement them fast using AI coding agents.
2.5 hours to explain [a concept somewhat similar to] AoS vs SoA?
Unlike the mainstream OOP, ECS (Entity Component System) is a niche programming model, even Erlang/OTP is probably more OOP-like than ECS. Same with Agents.
AOP always felt like a hack. I used it with C++ early on, and it was a preprocessor inserting ("weaving") aspects in the function entries/exits. Mostly was useful for logging. But that can be somewhat emulated using C++ constructors/destructors.
Maybe it can be also useful for DbC (Design-by-Contract) when sets of functions/methods have common pre/post-conditions and/or invariants.
Colour me surprised that a language which is the practical definition of bolted-on features has an implementation that feels like a bolted-on hack ;)
> early on
Also the "early" AOP was very much focused on a formal definition and a specific approach, further entrenched by how Java did it.
But you don't need to do AOP "by the letter" to do AOP: as long as you have cross-cutting concerns that you sprinkle over your code you're doing AOP, even if you're not calling that pointcut and stuff.
Python decorators, C# attributes, Ruby's whole "monkey patching" (e.g alias method chaining pattern, or simply modules combined with the ancestor system and message passing) are all pretty much variations that fit well with the AOP paradigm.
I'd argue that a lot of people are doing AOP without ever realising it.
It’s based on a social consensus only, the rest (Nakamoto Consensus, PoW, longest chain, difficulty adjustment, block halving, artificial limited supply, decentralization, censorship-resistant P2P network, open source, etc.) is a combination of a Rube Goldberg machine & crypto bros LARPing.
There is a huge scientific merit of the algorithms for reaching a distributed consensus when not all participants can be trusted (including the fact that the Bitcoin paper uses game theory to give evidence why malicious entities attempting to create another fork will by the mere design of the algorithms have a hard time).
What is, of course, social consensus are some aspects about what it "socially" means that there exists this concrete consensus in the blockchain. By the design of the protocol and its data structures, there do exist boundaries concerning possible "social interpretations" of this consensus, but a lot of aspects are up to different interpretations.
> There is a huge scientific merit of the algorithms for reaching a distributed consensus when not all participants can be trusted
Not quite. Distributed consensus had been solved in the 1980's theoretically and the 1990's practically, even in the presence of byzantine nodes. What Nakamoto consensus was first in was to extend this to the permissionless setting (at enormous expense & inefficiency, and with no benefits, in my view; though enabling large scale rule breaking or "censorship resistance", which some see as a benefit).
Bitcoin didn’t solved a forkability and finality problems. Blockchain (or more properly hashchain) is a linked list of hashpointers, and since anyone can create a hashpointer pointing to the head of the hashchain - it means anyone can fork it. And indeed Bitcoin was forked multiple times, and the solution to forks was almost always either centralized and/or social.
IMO PBFT consensus algos have a niche applications anyway, and not required for Electronic Cash implementation, only for decentralized and/or disintermediated Systems-of-Record, but that’s a complete opposite of bearer instruments like electronic cash.
Bitcoin is the OG Birkin Handbag. Valuable for the story. People compete to own a bit of it for that. You can create your own Bitcoin clone and own all of it! But no story, no value.
> Yes, they existed a long time ago and aren't wasteful as a way to generate "value".
Can you give me a literature reference for such a result, because this claim surprises me.
Of course Merkle trees existed long before - but they are just "cryptographically signed data structures", and thus don't solve the distributed consensus problem.
Of course eCash existed long before - but it depended on some central authority.
Of course distributed consensus algorithms existed long before - but they depended on the fact that all participants are trustable.
Thus, in my opinion Satoshi Nakamoto indeed made a really important scientific contribution for a quite specific algorithmic problem.
> Of course distributed consensus algorithms existed long before - but they depended on the fact that all participants are trustable.
No. They depended on the fact that all participants were known (in other words, the permissioned setting). Among those known ones, some (less than n/3) could go bonkers, all the way byzantine, and the honest nodes would still be guaranteed to find consensus (with consistency and availability).
Depending on the networking assumptions, of course there is. That's the whole point of SMR: under certain assumptions, you can attain availability and consistency.
The basic results of SMR theory are as follows, where "sync", "async" and "partially sync" refer to specific network models; PKI is public key infrastructure (that is, each node knows all the other nodes and has their public keys); "f" is the number of failed/dishonest/byzantine nodes (out of n total nodes); and only deterministic protocols are considered.
1) Permissioned, Sync, PKI: SMR possible, any f (!), Dolev-Strong (1983, [-5])
2) Permissioned, Sync, no PKI: SMR impossible if f >= n/3, PSL (1980), FLM (1985) (the hexagon proof, [-4])
3) Permissioned, Async: SMR impossible even with f=1 (!), FLP (1985) ("endless bivalent", [-3])
4) Permissioned, partially sync: SMR with "eventual availability" impossible if f >= n/3 [-2], possible otherwise (eg Tendermint [-1], Byzantine Paxos, PBFT)
In setting 4), PBFT-type protocols such as Tendermint guarantee consistency (among the "honest" nodes following the protocol as intended - you can't make any guarantees wrt to faulty or byzantine nodes) and eventual availability (that is, all requests sent by clients will "sooner or later" be dealt with) once network functionality is resumed.
That is consensus, for all intents and purposes, given that more consensus isn't really possible due to 2), 3). And arguably better consensus than Nakamoto consensus, which improves the boundary in 4) to n/2 (without selfish mining) at the cost of being stochastic, not deterministic, but replaces "consistency always, availability eventually" with "consistency eventually, availability always", arguably the wrong choice for financial applications.
Yes, but no. The Rube Goldberg of PoW isn't just for show, it's a protection from Sybil attack (not that it makes the economics of it any less of a disaster).
You cherry picked one thing from the list, and even there made a mistake.
In Bitcoin PoW used as a method for leader election of the node composing the list of validated transactions on the ledger (aka block), or even an empty list of transactions (aka Nakamoto-style Consensus).
But without all the Rube Goldbergian nonsense it’s simply an illegal/unlicensed lottery where the participants pay with electricity for the right to earn records on the longest chain (aka UTXO with mining block rewards).
> The Rube Goldberg of PoW isn't just for show, it's a protection from Sybil attack
he cherry picked PoW
no, Nakamoto-style consensus is not the same thing as PoW, or even PoW+LCR, not even the same thing as Bitcoin consensus.
Nakamoto-style consensus simply means that we're doing a leader election, and the leader does the transaction validation (aka mining a block in Bitcoin-speak).
The novelty of Nakamoto-style consensus is how we're doing this leader election, i.e. using PoW, PoW+LCR, PoS, PoET, PoA, Proof-of-X, etc.
> 5. Nakamoto consensus refers to the pairing of longest-chain consensus with proof-of-work
sybil-resistance.
> 6. Lecture 8 shows that the only ingredient missing from a permissionless version of
longest-chain consensus with provable consistency and liveness guarantees is a permissionless node selection subroutine that selects honest nodes more frequently than
Byzantine ones.
Fair enough, this is just one definition. There are others. Some even piling the entire bitcoin protocol under Nakamoto Consensus umbrella (including 21M BTC cap).
I was talking about Nakamoto-style Consensus not specific to Bitcoin, more like in (6).
That "rube goldberg machine" is what makes social consensus possible in a distributed system where everyone is anonymous and there's no single centralized authority.
How could it? PBFT is an algorithm, not a problem to be solved. Bitcoin is byzantine fault tolerant though.
> Bitcoin didn’t solved a forkability and finality problems.
There's no such thing as a "forkability problem" and Bitcoin solves finality through PoW.
> And indeed Bitcoin was forked multiple times, and the solution to forks was almost always either centralized and/or social.
That's wrong. The vast majority of forks are resolved algorithmically. There were only 2 or 3 unintentional hard forks in the early days that were due to bugs. This hasn't happened since 2013.
The only real "social" aspect of Bitcoin is what value people decide to assign to the coins.
I was at Bitcoin scene since 2011, I think that I can distinguish LARPing from the real thing. It's not me who created a dychotomy between fiat and crypto, between HODLers/coiners and noicoiners, between Traditional Finance and Crypro Finance, between CeFi and DeFi, between IPOs and ICOs, etc. Crypto always looked like a Pinoccio who want to become a "real boy".
> "it’s simply an illegal/unlicensed lottery"
yes, the PoW-based mining is litterally called a puzzle solving or a lottery. How do you call a game where everyone buys a ticket with electricity, but only one at a time wins a block reward?
> How could it? PBFT is an algorithm, not a problem to be solved. Bitcoin is byzantine fault tolerant though.
OK, BFT (not PBFT algo) is a class of problems with many proposed solutions, but none is good enough if you need scalability. Bitcoin is a partital solution under multiple constraints, even 1/3 of malicious nodes can undermine it. Internet backbone (BGP) should be trusted. Governments should allow it. etc.
> There's no such thing as a "forkability problem" and Bitcoin solves finality through PoW.
the on-chain Bitcoin transactions are never final. Everyone have their own heuristic how many blocks to count depending on the amount transacted. Protocol only defines how many blocks gamblers (miners) need to wait before they can spend their lottery winnings (block rewards).
> That's wrong. The vast majority of forks are resolved algorithmically. There were only 2 or 3 unintentional hard forks in the early days that were due to bugs. This hasn't happened since 2013.
There were many more than 2-3 both intentional and bugs, but why argue? Even 2-3 hard forks are enough to show that it's bad design. Forks should be impossible by design.
> The only real "social" aspect of Bitcoin is what value people decide to assign to the coins.
IMO there are many more social aspects here beside price discovery of UTXO records and social consensus. Bitcoin core governance, Mining centralization in China. Cypherpunks. LARPing.
> Bitcoin is a partial solution under multiple constraints, even 1/3 of malicious nodes can undermine it. Internet backbone (BGP) should be trusted. Governments should allow it. etc.
This is wrong on multiple counts. Bitcoin's security model does not assume BGP is trustworthy, nor does it rely on government permission. And the claim that 1/3 malicious nodes can undermine it misapplies BFT theory. Bitcoin doesn't use a quorum-based consensus like PBFT, so thresholds like 1/3 aren't the relevant failure mode. Instead, the attack vector is hashrate-based, and even a 51% attack doesn't let you rewrite history arbitrarily, just temporarily reorder recent blocks.
> The on-chain Bitcoin transactions are never final.
This is misleading. Bitcoin finality is probabilistic, like nearly everything in cryptography. It's final in the same sense that cryptographic signatures are unforgeable: with extremely high probability. The six-confirmation rule of thumb reflects the difficulty of deep chain reorgs which have never exceeded two blocks in practice on Bitcoin mainnet.
> There were many more than 2-3 [hard forks]... even 2-3 are enough to show it's bad design.
This conflates implementation bugs with protocol design flaws. The forks were caused by programming errors, not bad design.
> Bitcoin is a lottery.
You could argue that Bitcoin mining is because it's is probabilistic and there's a reward. But unlike a lottery, it serves an important role: securing the Bitcoin network.
Honestly, your critique reads more like cope than a technical argument.
> Bitcoin finality is probabilistic, like nearly everything in cryptography.
Yes, Bitcoin finality is probabilistic, and practically good enough after half a day or so (though 20 blocks were rolled back on at least 2 occasions).
However, many things in cryptography are not probabilistic. And in BFT-type consensus, every block is immediately final; the question of finality doesn't even arise (which is why the concept only gained prominence with Nakamoto consensus).
Regarding forks, there was BCH, BSV, etc. - those were not programming errors.
> though 20 blocks were rolled back on at least 2 occasions
Do you mean because of the bugs mentioned earlier or during the normal course of operations? Curious to read more about that.
> Regarding forks, there was BCH, BSV, etc. - those were not programming errors.
That's a different kind of "fork" though and those are arguably not Bitcoin. They're basically just competing cryptocurrencies that happened to use an existing blockchain to get started.
What's incredibly pedantic is insisting that Bitcoin is based on "social consensus." That’s only true in the most superficial or tautological sense - like saying anything people agree to use is based on "social consensus". It doesn't explain at all how the Bitcoin protocol actually achieves consensus (proof of work).
Calling it social consensus isn't an attempt to describe how the protocol works because you are talking about two different things. The consensus on which protocol to use, and the workings of the protocol itself.
You're response to me was to just verbatim repeat yourself while putting "no" in front of what I said. Incredibly pedantic discussion.
1. 1/3 malicious nodes under some conditions and BGP
This is backed by academic papers. Ask google or GhatGPT. You may argue that these papers are wrong or outdated, but then you need to tell this to the researchers who wrote them, not to me.
2. finality is binary, probabilistic finality is an oxymoron
3. > This conflates implementation bugs with protocol design flaws.
there is no formal spec for Bitcoin, there is a short informal whitepaper and a reference C++ implementation. Anyway the paper named "Bitcoin: A Peer-to-Peer Electronic Cash System", and for this specific purpose design is flawed, without regards to bugs.
4. > Bitcoin is a lottery.
Now you're hallucinating quotes I never wrote.
> Honestly, your critique reads more like cope than a technical argument.*
Pretty much all your comments here amount to twisting definitions, misapplying technical concepts, and nitpicking in search of "gotchas." Not to mention all the "LARPing" comments. It screams how to cope with having missed out, which, to your credit, you more or less admitted.
Crypto per se isn’t an asset class, it’s merely a form, not a substance. It can anything: from currency, to debt, to security, to derivatives, and anything hybrid or in between. Similarly like paper can be used for banknotes, cheques, stock certificates, bonds, etc.
In the past for every subject I researched I created a slide deck, and after some time I started noticing common patterns across different even remote disciplines.
Interlinking slides is hard, so Obsidian is ideal for this.
The important part is not to be religious or too pedantic about it, or else it will become a Second Job instead of a Second Brain;) Dump/capture what you can, if it’s really important - it will resurface later.
Lastly, with GenAI the value of these tools as a Knowledge Management goes down, but they’re more like a Workspace with the work logs and pointers/references to the actual knowledge in GenAI tools.
> Dan is a congressman, and what journalist Helen really wants from him is information. She’s particularly interested in a “dirty bomb”—particularly, whether the rumors of one exploding in New Orleans are real, or merely fabricated to advance a war between America and Iran. Dan doesn’t answer, instead choosing to leave. It’s all vague, but it gives the viewer a chance to piece some details together: It was likely the bomb and the escalation of a war between America and Iran that led to the creation of the silos.
IRGC isn’t a sovereign country, it’s a designated terrorist organization
You forgot that IRGC already directly attacked Israel twice in 2024 [1,2], and that’s not including countless proxy attacks and terrorist acts, culminating in October 7th massacres & atrocities
You got it wrong: IRGC attacked and Israel retaliated
US is just helped a little bit their ally
> This stuff isn't OK.
UN, ICC, ICG, etc. all became a $hit show, they don’t work. For 40 years IRGC threatened with Genocide of Jews, and they did nothing. Now when Jews retaliated: * This stuff isn't OK.* ;)
Pedantic rule-based systems are easy to circumvent with loopholes and lacunas. That’s why we should look at the substance and not merely a [legal] form
Examples:
- form: a cryptocurrency, but substance: an unregistered security
- “medical alcohol” during dry laws / Prohibition
- “medical marijuana” & patients vs drug users
- etc.
—-
Was Third Reich[1] a “sovereign government” or a front for The National Socialist German Workers' Party?
Was USSR a “sovereign government” or a front for a Communist Party?
Is Islamic Republic of Iran (IRI) a “sovereign government” or merely a front for IRGC[2]?
And wasn’t Iran/Persia already a “sovereign government” before IRGC staged a coup d'état (aka “revolution”)?
—-
> "De facto" and "de jure" are Latin terms used to distinguish between what exists in reality and what is legally recognized. "De facto" refers to something that exists in practice or reality, even if not officially established or legally recognized. "De jure" refers to something that is legally recognized or officially established
If any entity threatens u: u have 3 options: fight back, surrender, or self-destruct
In the first case, u have 2 more options: strike pre-emptively, or wait for them to strike & then retaliate
It doesn't matter what the entity is, it only matters whether they are enemy or not
——
> So China is not a sovereign state because it is a front for the CPP and can be bombed at will...?
I don't see the logical connection here. I never wrote that countries controlled by terrorist or authoritarian entities should be bombed at will. I wrote that some countries are highjacked by them, & if they attack or declare their intention to attack u, u may as well do it first
Agentic SDLC is a complete opposite of Agile/Scrum/SAFE.
For greenfield development / new features use mini-waterfal / Shape Up.
For reactive work use Kanban.
What would you use Scrum's Sprints for? Bin-packing of Jira tickets into sprint cycles less useful when you can implement them fast using AI coding agents.
reply