Piotr Stachowicz

Pull Requests shouldn’t feel like this. We’ve all opened a large PR review and thought: “Well... this is going to hurt.” Sure, small PRs are great, but sometimes you need the full picture. That’s where stacked PRs help (been using Graphite for that, a tool for managing PRs and code reviews). Stacked PRs treat your feature development as a chain of commits / PRs layered on top of each other. Think of it like a Jenga tower: each block (PR) builds on top of the previous one. pr1 → main pr2 → pr1 pr3 → pr2 Now it’s getting even better. I just got early access to Graphite Chat 👇 - I can literally ask it “what’s going on in this PR?” and it gives me the full story, codebase history, past PRs, even outside context. - I can just highlight it and ask “explain this”, instant breakdown. - Flags risks before reviewers even show up. - When someone leaves feedback, it helps me make sense of it and suggests fixes. - And the best part? When CI blows up, I can just ask “why did this break?” and actually get an answer. I’ll even be able to pop open the Graphite Editor right inside Chat to view and edit the codebase. Reviews feel lighter, more collaborative. Exactly how they should.

1573

141 komentarzy

It's happening: the "Vibe coding cleanup specialist" role is here. A natural consequence of mass-adoption of tools like Lovable and v0 by Vercel, and probably a new market in the making. It may be a great way for software engineers to find new work-streams. I'm not sure if it is a pleasant work to do, but that's another story. For studios like Pixelmatters, for now, this is not attractive as the clients that need this kind of work are often individuals (B2C) and not companies (B2B) and are unlikely to have a significant budget to invest on their MVP. Still, surely an evolution of the industry to keep an eye on.

172

30 komentarzy

styled-components has entered maintenance mode. Its maintainer was refreshingly honest: "Don't use this for new projects." Respect. But what about the millions of components already in production? My colleague Cody recognized the problem immediately. He submitted a PR with React 18 optimizations back in July 2024. With maintenance mode, that PR wasn't going anywhere. So Cody did what great engineers do. He turned our lingering PR into a fork, optimized it further, then opened it up for everyone. Linear tested it: 40% faster initial renders. No big code changes needed. The kicker? styled-components never implemented React 18's useInsertionEffect - a hook specifically designed for CSS-in-JS performance. It shipped in March 2022. Cody PR'd it fixed it in a day. We're calling it styled-components-last-resort because that's what it is. Not a new maintenance path. Not a forever solution. Just a performance bridge while teams migrate properly. Sometimes open source isn't about building the future. Sometimes it's about helping each other manage the present. Massive credit to Cody Olsen for the implementation, Kenneth Skovhus at Linear for testing, and Evan Jacobs for maintaining styled-components for years. Technical deep dive: https://lnkd.in/dk4CfsP8 GitHub: https://lnkd.in/duzY-Vy6 What's your styled-components migration plan?

111

3 komentarze

AI is everywhere. But it's not the first wave we've seen. The Evolution We've Witnessed: 1. We started with manual testing, that’s how most of us learned the craft 2. Then automation arrived: Selenium, Cypress, Playwright, CI/CD 3. Now AI dominates every discussion, every team, every meeting Here's what's different this time: Unlike automation, which took years to settle into the industry, AI is already transforming how we work today. But here's the constant truth: Those with strong fundamentals (problem-solving, critical thinking, domain knowledge) always adapt faster.So what do we do? 📌 We keep learning. 📌 We stay curious. 📌 We explore the new. But we also hold on to what really matters. Because the people who grow the fastest and last the longest, are the ones with strong fundamentals. Ready to start your AI journey? If you’re interested in AI but aren’t sure where to begin, I’ve put together a beginner-friendly playlist on YouTube that can help you get started: https://lnkd.in/gtTBT9rr #AI #Testing #Automation #CareerGrowth #QualityEngineering #Learning #ABAutomationHub

52

3 komentarze

Cultural Debt > Technical Debt We expect tech debt to slow us down. Cultural debt is also sneaky, and it compounds faster. Every time we skip a hard conversation, rush a promotion, or glorify heroics over healthy systems, execution drags. PRs stall. Decisions loop. Great people leave. A simple Cultural Debt Ledger I recommend: Shortcut → Interest → Signal → Repay Ignored feedback → Silent disengagement → Fewer ideas, more surprises → Create visible feedback channels with SLAs; close the loop in public. Rushed promotions → Perceived unfairness → Calibration drama, retention risk → Document criteria, run cross-functional promo panels, publish outcomes. Hero culture → Burnout + brittle systems → Same names in every postmortem → Rotate on-call, reward prevention work, track toil as a metric. Meetings without decisions → Rework + thrash → “Who owns this?” on repeat → Add DRIs, decision logs, and a default-by date. Values-as-posters → Misaligned choices → Slack DMs > docs, side deals → Tie values to trade-offs; review big bets against them. Start small: pick one line item this week. Name an owner. Set a due date. Pay it down. Because when culture compounds, velocity returns.

55

5 komentarzy