everdimension

@stolinski Easily solvable. Become worse at stuff that you're good at by not practicing it

It's crazy how AI is really good at the stuff I don't know anything about and total dog shit at the stuff I do.

“Dude did you vibe code this slop? This feature sucks!” Been getting this more recently. And no, I didn't “vibe” it. Did you ever consider, for one single second… That I might just be retarded? And I wrote this organic slop myself?

You start working with a junior dev who has zero context, and you guide them to become a senior who knows everything about a project With AI, you start with a senior who has zero context, and guide them to become a junior who knows everything about a project

@ryanflorence Yoo

The kids would lose their minds when I hopped on their board and kick flipped as an LDS missionary. I never had the guts for anything in a skate park.

@ryanflorence ref.current.resetComponentState() could do they same but explicitly With key the intention isn't always clear though you can have conventions to make it so

<Comp key={remountKey} /> My hunch has always been that this is a hack, and you should make the component behavior correctly instead of just wiping it out. What say you?

spend all your life savings on tokens go in debt if you have to

"Do you use Jira?"

@DavidKPiano We did write code in notepad for a while though...

Okay let's be real, writing code was never the hard part. Understanding the problem, making the tradeoffs, knowing what (not) to build, etc... LLMs made the typing 10x faster but it didn't make the thinking 10x easier. Also let's not pretend we were writing code in notepad before LLMs. We had frameworks, generators, libraries, intellisense, snippets, autocomplete, StackOverflow (RIP), and an entire ecosystem of abstractions designed to make writing code not *that* tedious.

@UndertheSkyBlog @MrPitbull07 Science teaches us that a lot of things that are true are against our instincts. You can't blame the mother here

@MrPitbull07 This behavior from the doctor enrages me. The behavior from the mother is honestly not much better. That people trust medical doctors more than their own brains or even their own mothers on the regular is disgustingly common and tragically dangerous.

My mother had me in 1962. Her pediatrician told her to feed me every four hours, no exceptions. “Babies need to learn discipline from day one,” he said. “If you feed on demand, you’ll spoil them.” I was a small baby, struggling to gain weight. I cried constantly between feedings. My mother told me years later that it was torture. She’d sit outside my nursery door, crying herself, listening to me scream, watching the clock. Fifteen more minutes. Ten more minutes. Her own mother—my grandmother—begged her to just feed me. “The baby is hungry. Listen to your instincts.” But my mother trusted the doctor more than herself. “He went to medical school. He must know better than I do.” By my two-month checkup, I’d barely gained any weight. The doctor said I was “failing to thrive” and put me on a supplement formula. My mother said, “Should I feed her more often?” He said, “Absolutely not. Stick to the schedule. She’ll adjust.” It wasn’t until my grandmother secretly started feeding me when my mother was out of the house that I started gaining weight properly. My mother carries guilt about this sixty years later. “I ignored every instinct I had because a man in a white coat told me to.” ~Amelia Carter Via FB

@Hesamation Good take, but this just explains why software quality was low before ai Was lowering the bar always a necessary measure to deliver?

"the people who struggle with coding agents are those who try to push their way too hard. partially why I find coding with agents easy is that I've led engineering teams before". this is a unique view on AI coding, that to maximize your output you have to "let go" a bit and accept that the way AI will build the project might not be 100% aligned with your way, it might not even be 100% correct, but it will push the project forward. and if you realize later that you don't like an approach, you can always go back to it later and iterate over it. so there's not always an absolute total gain, but the overall performance is what matters in the end.

Single prompt to create a perfect MVP 58 prompts to fix a minor flickering transition bug without breaking nearby layout

@housecor But why do you need to maintain the skill is the question

Key takeaway: If you use AI to do things you don’t understand, then your skills will atrophy. The solution? Don’t merely delegate. Ask questions. Seek to understand. AI is a wonderful just-in-time teacher.

@PlumbNick @Youclidean The draft reads much better and actually more engaging

@Youclidean Because I asked it to clean my draft. Here- you can see the original version too if you prefer it.

Well this isn’t exactly how I hoped my day would start. After 8 years, I just got laid off - as did 16k of my peers. But before anyone rushes in with explanations that make them feel better, let me be clear about what this wasn’t. It wasn’t performance and it wasn’t AI. It wasn’t location, versatility or impact. I was an L7, I led global AI enablement. I built systems executives depended on, moved wherever the company needed me and fixed problems that had been sitting untouched because no one else could untangle them. And I was still cut. Here’s the part we’re all supposed to politely ignore: in the U.S. right now, experience isn’t an asset, it’s a liability. And if you’re expensive because you’re good at what you do, the system eventually “optimizes” you out. This doesn’t happen in isolation. It’s enabled by a global labor market with almost no guardrails. Companies aren’t just competing on products anymore, they’re arbitraging labor across borders, wages, benefits and worker protections. When replacement is cheaper than retention, the decision gets framed as strategy instead of consequence. AI becomes the excuse, not the cause. It’s the clean narrative that hides what’s actually happening: experienced workers being swapped out through global labor substitution while leadership talks about “efficiency” and “the future of work.” That cycle keeps repeating because nothing in our policy stack meaningfully pushes back. Trade, labor and technology policy all pretend they’re separate, and workers pay the price for that fiction. I saw this coming and that’s why I’m running for Congress. I understand how this system works because I’ve lived inside it and I know it won’t fix itself. This is a rules problem and the rules are written by people who don’t bear the cost. If this resonates, don’t just nod along and move on. Support my candidacy, back someone who actually understands how global labor, AI and corporate incentives intersect and believe me when I say I am motivated to address this directly. By pretending this is inevitable, we’re accepting the outcome. #amazonlayoffs

@kentcdodds @ryanflorence Huh I don't remember missing that at all It kinda seemed that finally we're doing things right by simplifying what props are

@ryanflorence I remember missing this a lot when I came from angular to react

Something angular.js (v1) really got right was transcluded attribute directives <div draggable> in html does all sorts of stuff with that div. So does `tabindex` or `contenteditable`

@rohanpaul_ai I'm just surprised companies could function with engineers coding without a purpose

Jensen Huang says nothing would give him more joy than if none of his engineers were coding at all. Instead, they’re just solving undiscovered problems. His framework is 'Purpose vs Task' - coding is just a task, that should be minimized (ideally to 0).

Interestingly, code used to be easy to write and hard to read. With AI, you can end up with code that's easy enough to read and easy to refactor using AI, but has a "I'm not getting into this mess" property about it once you contemplate refactoring it by hand.

@housecor Why is this a "key decision"?

If I don't specify a tech stack, many Vibe coding tools automatically choose React. It's a logical choice because React is so popular. But it's also concerning because this abstracts a key decision, fails to consider the app's goals, and entrenches React leadership position.

I don't know what that means, though

Historically, technological progress meant doing more by removing human process and adding predictability, even if at the expense of quality (hence negative connotation of "mass produced"). With AI, manual process is being removed along with predicability. That's the difference

@isnovo309 🔥

Адекватные бабушки 😁