/DevTools

Introducing AI Assistance In Chrome DevTools

- Addy Osmani tl;dr: “A feature I'm particularly excited about is the AI's ability to prototype fixes. It can suggest changes to your styles and DOM structure, which are then reflected in the Changes panel. This allows you to experiment with solutions in real-time, without the fear of breaking your codebase.”

featured in #560


AI Tools For Software Engineers, But Without The Hype

- Gergely Orosz Simon Willison tl;dr: “Ways to use LLMs efficiently, as a software engineer, common misconceptions about them, and tips / hacks to better interact with GenAI tools.”

featured in #553


The Five Principles Of Modern Developer Tools

- Sam Seely Chris Bell tl;dr: Engineering teams are increasingly outsourcing non-core, yet critical parts of their stack to third-party vendors. This post delves into the challenges and emerging solutions of using third-party services in your stack. It discusses five key principles of modern developer tools: code-based resource management, source control management, rich type definitions, CI/CD integration and managing tools as part of your deployment lifecycle.

featured in #501


How To Successfully Adopt A Developer Tool

- Lou Bichard tl;dr: Adopting developer tools is not the same as successfully adopting developers tools. It’s a socio-technical challenge involving strategy, timing and people that can be broken down into three steps: champions, use cases, scale. Avoid the premature ‘all-hands’ demo and embrace the power of building a champion.

featured in #480


How To Successfully Adopt A Developer Tool

- Lou Bichard tl;dr: Adopting developer tools is not the same as successfully adopting developers tools. It’s a socio-technical challenge involving strategy, timing and people that can be broken down into three steps: champions, use cases, scale. Avoid the premature ‘all-hands’ demo and embrace the power of building a champion.

featured in #472


The Five Principles Of Modern Developer Tools

- Chris Bell Sam Seely tl;dr: Engineering teams are increasingly outsourcing non-core, yet critical parts of their stack to third-party vendors. This post delves into the challenges and emerging solutions of using third-party services in your stack. It discusses five key principles of modern developer tools: code-based resource management, source control management, rich type definitions, CI/CD integration and managing tools as part of your deployment lifecycle.

featured in #466


The Five Principles Of Modern Developer Tools

- Chris Bell Sam Seely tl;dr: "Here are the principles of the modern developer tool that emerged from our own work solving customer challenges, and that we're seeing in other developer tools we use." The authors discuss the following: (1) Work with resources in code. (2) Source control management. (3) Rich type definitions. (4) Run tests locally and in your CI workflow. (5) Manage as part of your deployment lifecycle.

featured in #462


Meta Developer Tools: Working At Scale

- Neil Mitchell tl;dr: “Every day, thousands of developers at Meta are working in repositories with millions of files. Those developers need tools that help them at every stage of the workflow while working at extreme scale. In this article we’ll go through a few of the tools in the development process. And, as an added bonus, those we talk about below are open source so you can try them yourself.”

featured in #430


Watch Transitions in Slow Motion in Chrome’s DevTools

- Jim Nielsen tl;dr: “The animations panel lets you slow down the animations happening in the browser so you watch them play out at much slower speeds and troubleshoot the mechanics of the animation.”

featured in #420


Modern Web Debugging In Chrome DevTools

- Bramus Van Damme Victor Porof tl;dr: "As an author, you want to see and debug the code that you wrote, not the deployed code. To make up for it, you can now have the tree show the authored code instead. This makes the tree more closely resemble source files you get to see in your IDE, and these files are now separated from the deployed code." The authors discuss how this works and other additions to Chrome's DevTools. 

featured in #348