
Live-Ale 🇩🇴 🇺🇲
6.5K posts

Live-Ale 🇩🇴 🇺🇲
@LiveAleRedacted
kaio-ken x10


Delve accused of misleading customers with ‘fake compliance’ techcrunch.com/2026/03/21/del…




An article from the 90s explaining how in the 1980s, personal computers changed the dynamic of college vs high school workers. College grads learned how to use PCs and grew wages faster Mind you, this was when interest rates were 15pct, white collar unemployment was the highest it’s been any non covid year, general unemployment was 10pct, there was a recession, 18pct mortgages, and the start of the savings and loan industry collapse. The economy was a mess. Except it was the start of the “digital revolution “ which lead to change. Here we are at the early days of the AI revolution. I think it will be very analogous to what happened back then. If you think learning how to use Clause seems daunting, imagine being 50 yrs old in 1983, not knowing how to type, using a 1.0 key adding machine with a tape roll to do all your work as an analyst and realizing you had to figure out how your brand new IBM PC and lotus 1-2-3 worked. Or having only used a typewriter your entire career , then having to learn the new PC and WordStar. Trust me. WordStar key combinations were far harder to learn than telling Claude what you want done Lots of people couldn’t figure it out. Those who did were more productive Ctrl QA with AI nber.org/digest/sep97/h…









Are you guys aware I am coding mostly on my phone now all day via Termius to Claude Code on my server while I go with gf to the dentist, clothing store, cafe, etc. 😛✌️










I am more Dominican than Austin Wells.




What if a codebase was actually stored in Postgres and agents directly modified files by reading/writing to the DB? Code velocity has increased 3-5x. This will undoubtedly continue. PR review has already become a bottleneck for high output teams. Codebase checked-out on filesystem seems like a terrible primitive when you have 10-100-1000 agents writing code. Code is now high velocity data and should be modeled at such. Bare minimum, we need write-level atomicity and better coordination across agents, better synchronization primitives for subscribing to codebase state changes and real-time time file-level code lint/fmt/review. The current ~20 year old paradigm of git checkout/branch/push/pr/review/rebase ended Jan 2026. We need an entirely new foundational system for writing code if we’re really going to keep pace with scale laws.





