Andrei Chernykh

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.

1,573

141 Comments

If you're looking for a new docs framework for your dev tool, I can't recommend Docusaurus enough. 1. You can change the appearance of any component—no matter how big or small—by ejecting its raw React code into your source tree. I've ejected almost all of its major components and restyled them with Tailwind. 2. It supports content written with MDX, which is like Markdown but better. MDX lets you write JSX tags so you can render React components (like badges and banners) directly inline your content. No more messy templating. 3. It bundles Prism for code snippet highlighting. So you if you want to change how each and every token of your language gets styled—which I do—you can override it with a simple centralized map—which I have. 4. You can swap out its on-site search engine with Algolia, now widely considered the best option for developer sites. It is, in other words, the perfect tool for people like me who are obsessed with every pixel.

118

16 Comments

Shout-out to 💻 Octavian Contis, who recently posted about the Shopify theme inspector being a bit tedious. I felt that, so I added a little something to Alfred to help out. You can now set Alfred to: - Automatically disable the inspector. - Restore your previous inspector state. - Or just let Shopify do its thing. The setting persists across all Shopify stores and browser sessions as long as Alfred remains active. It's a small change, but hopefully, it saves you a few clicks and a bit of frustration. Hope you find it useful! *Extension link available in description* #Shopify #ShopifyDev #ThemeDev #WebDev #Productivity #BrowserExtension

59

10 Comments

We kept hearing the same frustration from teams using visual testing: "I spent an hour approving timestamp changes." "Our CI is blocked because of a rotating banner." "The real bug was buried under 200 irrelevant diffs." That's the reality of visual testing today. The tools work, they catch every pixel that moves. But they don't understand context. They can't tell you what actually matters for your product, your brand, your release. So we asked: what if the tool could help you focus on what you care about? Today, we're launching the Visual Review Agent for Percy. Here's what's different: it doesn't just flag changes, it helps teams understand them. Natural-language summaries explain what shifted. You can create custom review rules so the agent highlights only the visual changes relevant to your use case. And it tracks ROI at the build level, so you can show exactly how much time and effort you've saved. Early teams have cut their review cycles by up to 3x. The real impact? Teams are back to doing what they do best — improving quality, not chasing false positives.That's the unlock we've been chasing. Try BrowserStack's Visual Review Agent in your builds today: https://lnkd.in/d3NcbEDD

173

1 Comment

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 Comments

You may see folks claiming that they can get "A.I." coding assistants to do exactly what they want by completely and precisely describing the software they require up-front, and hailing the return of Big Design Up-Front. Anyone who's spent more than a handful of hours using these tools will know that this simply isn't true.

103

116 Comments

New episode with Matt Palmer from Replit We get into Replit's crazy growth since the launch of Agent. And Matt shares useful tips on making videos for devs and writing great docs. Find the full episode on Spotify, YouTube, Apple Podcasts etc.

61

5 ARIA attributes every dev should know (and 2 to avoid) Most developers know ARIA exists, but which attributes actually matter for everyday accessibility work? Before we get started, remember the first rule of ARIA: Don't use ARIA unless you have to. If semantic HTML can do the job, use that instead. But when you do need ARIA, here are 5 ARIA attributes that are actually useful: 1. aria-labelledby - Describe the current element with the text from another element on the page. Better than aria-label because it allows you to reference existing visible text on the page and keep it translatable. 2. aria-describedby - Connects help text, error messages, or extra context to form fields and other elements. Screen readers announce this after the main label. 3. aria-expanded - Essential for dropdowns, accordions, mobile menus - anything that opens and closes. Bonus: pair it with aria-controls to define which element it's controlling. 4. aria-current - Perfect for programatically defining the current page in navigation, active step in a process, or current item in pagination. Much clearer than visual styling alone. 5. aria-live - Announces dynamic updates to screen readers. Use "polite" for status messages, "assertive" for urgent alerts. Two to avoid (or use carefully and thoughtfully): 1. aria-label - It's typically a better choice to choose another way to label elements, with text inside a button tag, a label tag associated with a form field, or visible text associated with the aria-labelledby attribute. Treat aria-label as a last resort when no other method of labeling an element can be used. 2. role - Most of the time, there's no need for that role attribute when you use semantic HTML. Skip adding role="button" on a div - just use a button tag. A proper heading tag doesn't need a heading role or an aria-level attribute. The best accessibility starts with good semantic HTML. ARIA is intended to fill in the gaps, not replace the foundation. What ARIA attributes do you find most useful? Any that trip up your team?

52

14 Comments

Building AI for testing isn't about replacing human judgment—it's about amplifying it. When we started working on the Visual Review Agent for Percy (BrowserStack's visual testing product), the technical challenge was clear: can AI see visual changes the way a developer or QA engineer would. Not just "what changed" but "does this change matter?" Traditional pixel-diff tools flag everything. A timestamp shift gets the same treatment as a broken layout. The result? Alert fatigue and bottlenecked releases. We approached this differently: - Natural-language summaries for each visual change, understand what shifted at a glance, no mental parsing of red pixel overlays. - Customizable prompts let you define what matters. Brand colors? Layout shifts? CTA changes? You set the focus. - Toggle between AI-powered diffs and traditional pixel comparisons, at build or snapshot level. Full control over your review workflow. - Build-level ROI metrics quantify how many diffs were filtered as noise and how much review time you saved. Early results: review cycles cut by up to 3x, excited to see where teams take this. Try it in your builds today: https://lnkd.in/dsVx3HzT

93

3 Comments

You can just ship your org chart! Not even a joke: when organizations grow beyond a certain size, you want to ship to the same app without coordinating with "that other team". In the frontend space, the technology to enable that is called microfrontends, and we just shipped public beta support on Vercel. This is after an extensive private beta period with several large enterprise companies, so while we call it beta, the tech is already battle tested in production. https://lnkd.in/gn9n_EHp

117

13 Comments