codevirtualize 🇨🇴 @codevirtualize

SpaceX was less than 10 people back then. We didn’t even have office furniture.

DogeDesigner @cb_doge

6 days ago

SpaceX started with a mariachi band party in 2002.

1K 2K 20K 40.6M 1K

@iam_elias1 Rings similar to this paper...

@trademindhq Agreed, without sound distribution we can't prosper as a state or civilization.

Two economists just published a mathematical proof that AI will destroy the economy. Not might. Not could. Will — if nothing changes. The paper is called "The AI Layoff Trap." Published March 2, 2026. Wharton School, University of Pennsylvania. Boston University. Peer reviewed. Mathematically modeled. The conclusion is one sentence. "At the limit, firms automate their way to boundless productivity and zero demand." An economy that produces everything. And sells it to nobody. Here is how you get there. A company fires 500 workers and replaces them with AI. A competitor fires 700 to keep up. Another fires 1,000. Every company is behaving rationally. Every company is following the incentives correctly. And every company is building a trap for itself. Because the workers who were fired were also customers. When they lose their jobs faster than the economy can absorb them, they stop spending. Consumer demand falls. Companies respond by cutting costs — which means automating more workers — which means less spending — which means more falling demand — which means more automation. The loop has no natural exit. The researchers tested every proposed solution. Universal basic income. Capital income taxes. Worker equity participation. Upskilling programs. Corporate coordination agreements. Every single one failed in the model. The only intervention that worked: a Pigouvian automation tax — a per-task levy charged every time a company replaces a human with AI, forcing them to price in the demand they are destroying before they pull the trigger. No government has implemented this. No major economy is seriously discussing it. Meanwhile the numbers are already tracking the curve. 100,000 tech workers laid off in 2025. 92,000 more in the first months of 2026. Jack Dorsey fired half of Block's workforce and said publicly: "Within the next year, the majority of companies will reach the same conclusion." Nobody is doing anything wrong. Companies are following their incentives perfectly. That is exactly the problem. Rational behavior. At scale. Simultaneously. With no mechanism to stop it. Two economists built the math. The math leads to one place. Source: Falk & Tsoukalas · Wharton School + Boston University · arxiv.org/pdf/2603.20617

Pell is to silver as Fibonacci is to gold johndcook.com/blog/2024/09/0…

En la marcha de los alérgicos al trabajo que buscan la revocatoria de Noboa organizada por Washington Andrade se coló la loca de Pabel Muñoz. Mmvg nada haces para Quito, aún así te atreves a asistir y abandonar a tu pueblo. Reelección que te manden a la v vas a tener.

keyboard_arrow_left Previous keyboard_arrow_right Next

El Correismo como cada día son menos y no les da para llenar media plaza, se van de metidos a una marcha de los trabajadores Y con eso grabar y hacer creer al país que son millones aún, más ridículos imposible.

Unbelievable scenes in El Salvador today. Hundreds have gathered demanding a total ban on Bad Bunny music. The protesters are literally claiming the music 'lowers IQ' and turns people gay. 🇸🇻

Un trabajador enganchó justo a un chorro de mierda queriéndole robar la bici y lo impidió literalmente PEGÁNDOLE UNA PATADA EN EL ORTO JAJAJAJAJ El chad se preparó toda la vida para cagar a patadas a un negro. Toca bancar.

Having been part of the industry for 50 years, I can confidently report that none of this is true. Sure, writing code has a non-zero cost; this is true of any artifact. But you know what costs even more, Jonathan? Writing bad code; writing unnecessary code; writing more code than you really need simply because you think you might need it someday or you are too lazy or sloppy to clean up after yourself. Anything that costs nothing is often worth nothing as well, and results in significant unintended consequences.

Jonathan Ross @JonathanRoss321

a month ago

For 50 years, software engineering ran on code rationing. Writing code was expensive, so we rationed it carefully through roadmaps, RFCs, prioritization meetings, and scope reviews. This created a role: the No Engineer. No, that won't scale. No, we don't have bandwidth. No,

388 213 2K 738K 695

@SokeyeA @clairevo The best product managers did what you say since the dawn of computing. Tools come and go, the only permanent thing is to embrace change.

“I’ll kill it before you do” This is so real I think the Product role is shifting to talking to users more, getting the right feedback, deciding which product bets to take, validating solutions through prototypes, experiments and MLPs iteratively and capturing long term value for the business & customers And less of writing long documentation, roadmaps, ticket handoffs and more The iteration loops have become much shorter for PMs

@bibryam But opening a PR has always been faster than writing a PRD

PR >> PRD. The handoff era is over. → When opening a PR is faster than writing a PRD, AI changes how product gets built. The old roles start to collapse.

"PR >> PRD" Yep. the handoff era is over. but it's not just the roles collapsing. it's the tools. Every PM tool was built for a world where humans did the coordination. tickets docs roadmaps presentations all of that was scaffolding for work AI now does faster and cheaper. slapping AI on top doesn't fix it. The foundation is already out of date. I build @chatprd every day knowing i have to replace its core before something else does: claude code, another startup, something i haven't imagined yet. Radical humility and endless paranoia are the only product strategies that make sense right now. So sure. the PRD is dead. But I'll kill it before you do.

Bilgin Ibryam @bibryam

2 months ago

PR >> PRD. The handoff era is over. → When opening a PR is faster than writing a PRD, AI changes how product gets built. The old roles start to collapse.

1 2 15 20K 12

We are in the age of "redo". The days of software prophets jealously guarding their architecture and obsessing over every detail are over. By the time you get it right, the goals have shifted, probably even transformed. I say this as someone who’s as guilty of software perfectionism as anybody. Everything moves too fast. You can’t be emotionally attached to your software. A new approach blows past what you've been building by hand? You just have to say who cares, I’m moving on. That’s just the way the world is now. Constant reevaluation is really all that you can do to keep up in this environment. Software egos used to make sense. The products that stood the test of time and didn't collapse under their own weight were carefully grown over time by a visionary architect. Is clean code dead? not exactly. But building something exactly how you want it AND keeping up? You can only pick one. Don't get anchored to the moment you tried something revolutionary. We might not get it right, but we can redo it fast. With more experience and better methods. > "Radical humility and endless paranoia are the only product strategies that make sense right now" - @clairevo

claire vo 🖤 @clairevo

2 months ago

"PR >> PRD" Yep. the handoff era is over. but it's not just the roles collapsing. it's the tools. Every PM tool was built for a world where humans did the coordination. tickets docs roadmaps presentations all of that was scaffolding for work AI now does faster and cheaper.

21 7 168 39K 114

@nicolekcha Production code is not cheap to replace, just imagine critical applications in finance and health where failures not only cost money but lives. Vibe coding has a place but doesn’t make it trivial to get into production, as changing code is not a game but a serious task.

Hard disagree. The same "Yes Engineers" didn't suddenly gain taste and system design intuition just because things got easier to build. Without these traits, they are going to be the slop cannons that produce unsustainable messes that work for 1-3 weeks and then break and are forgotten. Debt will still accumulate, it will just take a different shape, less in hard code and more in product decisions and system-wide connectivity. Experienced No Engineers are sensing this accumulation right now and the good ones will shift their restraint from code rationing to something new. If they don't, they'll remain No Engineers 1.0 and you're right. Yes, redo is cheap now (x.com/nicolekcha/sta…), but restraint is still about when and what to redo. With an abundance of code, product sanity will require careful coordination more than ever.

Jonathan Ross @JonathanRoss321

a month ago

For 50 years, software engineering ran on code rationing. Writing code was expensive, so we rationed it carefully through roadmaps, RFCs, prioritization meetings, and scope reviews. This created a role: the No Engineer. No, that won't scale. No, we don't have bandwidth. No,

388 213 2K 738K 695

@JonathanRoss321 x.com/nicolekcha/sta…

nicole @nicolekcha

a month ago

Hard disagree. The same "Yes Engineers" didn't suddenly gain taste and system design intuition just because things got easier to build. Without these traits, they are going to be the slop cannons that produce unsustainable messes that work for 1-3 weeks and then break and are

2 1 27 8K 7

@JonathanRoss321 When hardware was expensive, we rationed hardware. When people became more expensive than hardware, we rationed people. But the core issue remains the problems we are trying to solve and the requisite understanding. Cheap code isn't increased understanding.