phil
🐡 @pjc | Ξ¦L | design fumes (and sundry extra-curriculars) β†’ Ζ’(🧠):πŸ’¦ β†’ trust/time 🌳 https://github.com/philcockfield 🧫 https://jsr.io/@sys
Phil Cockfield pfp

@pjc

0 reply
0 recast
4 reactions
Phil Cockfield pfp

@pjc

And now for something worse than "technical debt" πŸ₯ "cognitive debt" - a new peril β€œCognitive debt accumulates when AI writes code that humans lose shared understanding of” β€” Margaret-Anne Storey ref: https://www.youtube.com/watch?v=Tk0hIOAwf6M AI Cognitive Debt: The Crisis Nobody Sees Coming β€” Imran Gardezi
2 replies
0 recast
8 reactions
Phil Cockfield pfp

@pjc

βœŠπŸ»πŸ’― | Q
0 reply
0 recast
2 reactions
Phil Cockfield pfp

@pjc

"turn the universe into a parameter"
1 reply
0 recast
3 reactions
Phil Cockfield pfp

@pjc

β€œThe world no longer needs to pay for software the way it currently pays for software.” πŸ‘
1 reply
0 recast
3 reactions
Phil Cockfield pfp

@pjc

ref: Q | βœŠπŸ»πŸ’―
1 reply
0 recast
8 reactions
Phil Cockfield pfp

@pjc

ref: (@v, @dwr) β†’ https://tempo.xyz Stable Coins
0 reply
0 recast
1 reaction
Phil Cockfield pfp

@pjc

I bet there is some kind of "dunbar number" adjacent-equivalent thing going on with a ceiling on how many agents an engineer can run (as in how many parallel disciplined, human owned, responsible for the code in production, you can mentally manage) before which it all just gets away on you, and it moves into a new level of dangerous/lossy unexamined abstraction ("someone else's code, not understood, either architecture or syntax").
6 replies
3 recasts
21 reactions
Phil Cockfield pfp

@pjc

tools == "the harness is the product"
1 reply
0 recast
2 reactions
Phil Cockfield pfp

@pjc

Getting into a shit-fight with the US defence dept (ministry of war) sure is some all out seat-of-your-pants, high-stakes marketing manoeuvring. (not for the feint of heart)
0 reply
0 recast
3 reactions
Phil Cockfield pfp

@pjc

There are so many layers of "miracle" going on right now. Sutton’s β€œbitter lesson” is the gospel (β€œgood news”)β€”if you take it from a non-sunk-cost place.
0 reply
0 recast
3 reactions
Phil Cockfield pfp

@pjc

1. dev's own their code in production 2. practice observability driven development 3. test in production 4. seperate `deploys` from `releases` 5. CI/CD (continuous integration)
0 reply
0 recast
0 reaction
Phil Cockfield pfp

@pjc

ref: farcaster etymology https://farcaster.xyz/july/0x0fa51fc4
0 reply
0 recast
3 reactions
Phil Cockfield pfp

@pjc

"test in prod or live a lie"
1 reply
0 recast
3 reactions
Phil Cockfield pfp

@pjc

ref: "The Unreasonable Effectiveness Of Plain Text" https://www.youtube.com/watch?v=WgV6M1LyfNY
0 reply
0 recast
1 reaction