Click any tag below to further narrow down your results
Links
@zilevandamme on X
A short X post jokingly declares its author part of the "indigenous people" of Jack Dorsey's former platform, calling Elon Musk their coloniser. It responds to a quote post asking why critics of Musk still use the site he owns.
- The post frames continued X use as a joke about refusing to leave "colonised" land, not a serious political argument.
- It quotes @stockbella's challenge: if people dislike Musk so much, why do they still use his platform?
- The reply plays on the platform's history, contrasting Jack Dorsey's founding of Twitter with Musk's later ownership.
A former Stripe new grad shares how to ramp up fast at the company: pick a narrow area and become its go-to person, then take ownership of small problems and build from there. It leans heavily on how AI tools should and shouldn't fit into learning.
- Become the team's mini-expert in one narrow area first; the author became the point person on Dashboard charts within about four months and kept that value for over a year and a half.
- Learn to ask better questions: use LLMs for "what" questions and people for "why," and come with what you've tried and a hunch before asking for help.
- Use AI to speed up execution, not to replace understanding; don't ship code you can't explain, and slow down in your first months to absorb how systems break.
- Take ownership early by fixing small frustrations yourself and prototyping fixes in an afternoon, then demoing them to stakeholders rather than waiting for approval.
The author argues that developers using AI fall into two distinct camps—those who read and understand generated code ("accelerators") and those who delegate implementation entirely to AI ("vibecoders")—and that these aren't points on a spectrum but fundamentally different commitments with different long-term costs.
- Reading code matters because programming is ultimately about building a mental model of the domain, not just producing working software; without understanding the implementation, you lose the ability to explain decisions, anticipate consequences, and adapt to change.
- Vibecoders risk accumulating "intent debt" as context drifts between sessions and requirements get lost, while accelerators risk drifting into vibecoding if they stop reading diffs—there's no safe middle ground.
- The choice between these approaches isn't about how much the AI writes, but about your relationship to the output and whether you're committed to maintaining ownership of the reasoning behind the code.
As AI and LLMs make competent drafts trivial, the real edge shifts to human judgment—spotting what’s generic, diagnosing flaws, and owning outcomes. True value comes from combining taste with context, constraints, and stakes, not just selecting polished AI outputs.
- AI makes generic "7/10" drafts nearly free, so the scarce skill becomes diagnosing precisely why something is generic or risky, not just picking the best AI output
- The practical drill: generate 10-20 AI versions of an artifact, write a "fails because..." line for each, then rewrite the best under hard constraints (no buzzwords, one idea per sentence, real trade-offs noted)
- Refusal—recognizing when "good enough" hides risk or mismatches real needs—matters more than selection
- Real authorship requires holding actual stakes (regulatory liability, brand damage, budget/material constraints) that AI can't bear, so curation alone leaves humans without genuine ownership
To secure a promotion, proactively take on responsibilities associated with the role you aspire to, even before receiving the title. Consistent, sustained performance and ownership of broader team issues are key, demonstrating capability and readiness for advancement.
- Act like you already have the next-level role by taking on its responsibilities before getting the title or promotion
- Consistency over time matters more than a single impressive moment—sustained ownership proves readiness
- Look for gaps or broader team problems no one owns, and step in to solve them rather than waiting to be asked
- Making yourself hard to replace in a higher role (i.e., someone would struggle to "take your position") signals you're already operating at that level