


ai babysitter prev @linkedin , @joinodf OD50-1, @opensea, 💻 disapora ✈ #atl, #aus, #sf, #mia, #nyc, 🛬




Rock & Roll Hall Of Fame is tonight ◻️SADE ◻️LUTHER VANDROSS ◻️WU-TANG CLAN ◻️QUEEN LATIFAH ◻️MC LYTE ◻️FELA KUTI ◻️PHIL COLLINS All getting inducted 🔥

if you're feeling a little uneasy about the grounding of all US planes remember to spend as much time on your phone as possible. the more information you ingest as you scroll the calmer you will become

this is spot on. earlier this year i had to let go of our front-end engineers. not a decision i took lightly, but opus + technical designer + backend was simply more efficient. here's what changed from where i sit: 1. front-end was mostly a translation job. designer makes it in figma, FE engineer turns it into components. models now do that translation really well, especially on standard stacks like react + tailwind where there's a mountain of training data. 2. handoffs were too costly. design to FE to backend meant two handoffs and fidelity lost at each one. a designer who can prompt and ship directly cuts one out. fewer syncs, fewer "that's not what i designed" msgs. 3. the evalset for UI is clear as day. you look at it and know if it's right, so the AI iteration loop is fast and cheap. backend mistakes stay invisible until they're expensive (data, security, scale), which is why humans still sit there. notice security, platform and backend are the roles growing in this chart. 4. the bottleneck moved to the edges. the scarce skills now are taste (knowing what good looks like) and systems (making sure the thing underneath doesn't break). pure implementation sat in the middle and got squeezed from both sides. if you're front-end today, the people i see thriving have moved toward design engineering or full-stack product work.
Engineering is changing: FDE is ascendant while mobile and front-end roles are disappearing. Open mobile and front-end engineers jobs have been nearly halved in the past year!

- Restaurants have no moat. - Anyone can vibecook their own meal. - You can build your own burger at home at a fraction of the cost it takes you to get it from a restaurant. - If a restaurant builds a really good recipe, copycats will instantly reverse taste it and steal it. Restaurants are dead.

Phase 1: "Wow, skills are great for internal tools" Phase 2: "Huh, converting that skill to a script made it 100x faster, use no tokens, and work the same way everytime" Phase 3: "Interesting, hosting that script on a server made it accessible to the whole team and when we make updates, everyone gets them" Phase 4: "Maybe we could sell access to that server, surely other companies have this problem" and thus, saas was reborn

You're not a real engineer if you don't have a mystery $0.53 AWS bill coming from a rogue service in perpetuity.



The 10-year database architecture cycle: 2015: SQL is obsolete. Schemas are too rigid. Put everything in NoSQL JSON documents. 2018: Wait, we need to join users and orders. Let's write a 400-line nested loop in JavaScript to join them in RAM. 2021: Wait, if the server crashes halfway through the loop, we lose money. We need ACID transactions. 2026: Quietly puts everything back in PostgreSQL and never speaks of it again.


Every methodology eventually collapses into this one. The rest are just what we call it in the retro.

Today’s PHP security risks got me thinking about how I could have been more vulnerable with you. Perhaps we can patch things up and be there 4 one another.

The fun fact about the eMudhra certificate leak is that the numbers were so low that only an AI or a flawed/test script would have found them. No sane human would have thought that a fellow human could have done something that stupid.