Lance Fisher

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

So many senior engineers are out of work right now. That’s not a talent problem. That’s a leadership failure. The industry’s been chasing hype, handing complex systems to undertrained devs and calling it innovation. Eventually, the bill comes due. Maybe then we’ll remember that experience isn’t optional when things actually need to work.

900

80 Comments

If you’re planning to modernize a legacy system that's been running for years and still manages a high volume of client traffic, the strangler fig pattern might be something that can help. Read Martin Fowler's blog post about the Strangler Fig pattern application. https://lnkd.in/gxKMuQ5G https://lnkd.in/gMxK3KUS If you’ve walked this path, what tipped your decision one way or another? #modernization #StranglerFig #SRE #softwarearchitecture #engineeringmanagement

40

PSA: If you remove or deprecate a feature, give your engineering team the time to fully remove that feature from your codebase. Your future self (and your future team) will probably not remember to thank you, but their higher velocity might be a thank you enough. Every line of code in production comes with a cost, however hidden it may be in the present moment. End of message.

16

5 Comments

Missing form labels, empty buttons, links that go nowhere... Let's stop calling this "accessibility debt." This is just incomplete development. The real issue isn't that accessible code costs more to retrofit. It's that we're calling basic HTML requirements "extra work." A button without text? That's not accessibility debt - that's unfinished code. A form input without a label? That's not technical debt - that's skipping steps. A link that doesn't go anywhere? That's not an edge case - that's broken. These things should be in your Definition of Done already. Not because of WCAG, but because they're fundamental to how HTML works. When we frame basic semantic markup as "accessibility work," we make it sound optional. It's not. It's just good development. Start there. Get the fundamentals right. The rest gets easier once your team stops thinking of working buttons and labeled forms as "nice to have." #WebDevelopment #Accessibility #TechDebt

109

15 Comments

The invisible productivity tax. Every engineering leader I speak to knows it well. A simple UI change should be a quick merge, but instead, it breaks dozens of automated tests. Your build goes red. Deployments stall. Someone has to stop what they're doing and spend the next few hours hunting down selectors. Our data shows teams lose an average of 15 minutes per broken locator. Do the math across dozens of tests and hundreds of UI changes, and you're looking at hundreds of hours spent maintaining tests instead of shipping features. So we at BrowserStack built the Self-Healing Agent. It automatically identifies and fixes broken locators the moment they happen, whether you're using Selenium, Playwright, or Appium across web and mobile apps. It offers both instant remediation and transparent logs, showing exactly how locators were fixed, and even auto-proposes permanent code updates to strengthen your test suites. Teams are seeing up to 40% reduction in automation build failures. Available now on Automate, App Automate and Low Code Automation: https://lnkd.in/dchB595C

252

3 Comments

Engineers should constantly ask why, push back on bad ideas, and suggest alternatives. Some of our clients find it jarring at first. "Why is my developer questioning requirements?" Because that's what great engineers do. They think. They challenge. They improve. Unless, you want silent compliance and mediocre products 🤔

112

24 Comments

Tired of hearing excuses from your dev team? (Here’s what high-performing teams do differently.) Every time you ask why a project isn’t done, there’s a new story: ⤷ “We ran into unexpected challenges.” ⤷ “The requirements changed.” ⤷ “It turned out bigger than we thought.” It’s like playing whack-a-mole with your own roadmap. But here’s the truth: Good dev teams don’t hide behind blockers. They build with boundaries. What the Best Teams Do: 1/ Set unmovable deadlines → Not vague estimates → Real dates that drive accountability 2/ Define scope clearly → What’s in? What’s not? Put it in writing → Scope creep dies in documentation 3/ Protect momentum → No shifting goalposts → No sprinting in circles ⤷ Why It Matters: A dev team that avoids hard lines doesn’t just delay launches. They build a wall between you and your goals. If that’s what you’re up against, it’s not a people problem, is a standards one. Ready to work with a team that delivers? Start here: https://lnkd.in/gBr3wFRC 👉 Follow for more no-BS advice on building faster, accountable dev teams.

33

29 Comments

You call it "over-engineering" when devs make software more complicated than it needs to be. But simpler solutions often require *more* thought. Complexity's easy. You just keep typing. (Or prompting.) That's why I call over-complicating "under-engineering".

258

35 Comments

I am digging more into the #Storyline #JavaScript API and this week exploring what you can do with the depth (z-index) property. In this week's video, I cover how to adjust the depth of objects on the stage. This allows you to take an object that is below something else and bring it forward. I use it for a card example and bringing cards forward. Check out the full video here: https://lnkd.in/g3j5cP5j

37

6 Comments

So which models produce HTML that has the least accessibility errors, and at what cost? Mapped it out here (bottom left is the best). This is helpful for understanding which models are most compliant for those with disabilities and do it efficiently. Qwen and Gemini 2.5 Flash lead the pack. Hat tip to Ben Ogilvie for pointing me to this: aimac.ai

55

2 Comments

{quarto-webr} v0.4.3 "Bumpity Bump" is a new maintenance release of the Quarto extension that enables interactive R code execution in web browsers. This update bumps to R 4.5.1 by default (via webR 0.5.2). 🔗 Repo: https://lnkd.in/gjSFKBUf #RStats #Quarto #WebR #DataScience

30