#DevTools

[b0rroso]

[adafruit]

🎉New Pico 2 W just dropped - and CircuitPython is ready to go!🎉

We just got the OK to put the Pico 2 W in the shop. You can pick it up at

, and you might be wondering: hey, do you have CircuitPython built for it? The answer is YES! We have secretly added support, and v9.1.2 has a build ready. We'll be adding it to the

downloads page shortly, but if you've got one in hand before launch somehow, you can check out the builds in the Absolute Latest S3 Bucket

the pico 2w is a great upgrade with twice the speed, twice the SRAM and twice the flash memory, solving many frustrations folks had with the original Pico W.

[danielweasly]

Copilot Use Cases For Developers

Microsoft Copilot is revolutionizing the way developers interact with development tools, providing AI-powered assistance across a range of Microsoft products like Visual Studio, Azure, and GitHub. With Copilot integrated into these environments, developers can streamline workflows, automate routine tasks, and leverage advanced features for improved productivity. For example, in Visual Studio, Copilot helps write code faster by suggesting context-aware completions, refactoring code, and even generating entire functions based on brief descriptions. This drastically reduces the time spent on boilerplate code and increases efficiency, allowing developers to focus on more creative and complex aspects of their projects.

Furthermore, Microsoft Copilot empowers developers to work smarter by integrating with cloud-based services like Azure. By leveraging machine learning and AI, it can suggest optimized solutions, recommend cloud resources, and assist in troubleshooting infrastructure issues. This level of automation and intelligent support enables developers to make better decisions quickly, while reducing the cognitive load and manual effort needed to manage cloud-based applications. As Microsoft Copilot continues to evolve, it will increasingly become an indispensable tool in the developer toolkit, transforming how software is built and deployed in today’s fast-paced technological landscape.

Click Here to know more: https://www.intelegain.com/top-10-copilot-use-cases-in-2025/

[jcmarchi]

Clever Polypane Debugging Features I’m Loving

New Post has been published on https://thedigitalinsider.com/clever-polypane-debugging-features-im-loving/

Clever Polypane Debugging Features I’m Loving

I’m working on a refresh of my personal website, what I’m calling the HD remaster. Well, I wouldn’t call it a “full” redesign. I’m just cleaning things up, and Polypane is coming in clutch. I wrote about how much I enjoy developing with Polypane on my personal blog back in March 2023. In there, I say that I discover new things every time I open the browser up and I’m here to say that is still happening as of August 2024.

Polypane, in case you’re unfamiliar with it, is a web browser specifically created to help developers in all sorts of different ways. The most obvious feature is the multiple panes displaying your project in various viewport sizes:

I’m not about to try to list every feature available in Polypane; I’ll leave that to friend and creator, Kilian Valkhof. Instead, I want to talk about a neat feature that I discovered recently.

Outline tab

Inside Polypane’s sidebar, you will find various tabs that provide different bits of information about your site. For example, if you are wondering how your social media previews will look for your latest blog post, Polypane has you covered in the Meta tab.

The tab I want to focus on though, is the Outline tab. On the surface, it seems rather straightforward, Polypane scans the page and provides you outlines for headings, landmarks, links, images, focus order, and even the full page accessibility tree.

Seeing your page this way helps you spot some pretty obvious mistakes, but Polypane doesn’t stop there. Checking the Show issues option will point out some of the not-so-obvious problems.

In the Landmarks view, there is an option to Show potentials as well, which displays elements that could potentially be page landmarks.

In these outline views, you also can show an overlay on the page and highlight where things are located.

Now, the reason I even stumbled upon these features within the Outline tab is due to a bug I was tracking down, one specifically related to focus order. So, I swapped over to the “Focus order” outline to inspect things further.

That’s when I noticed the option to see an overlay for the focus order.

This provides a literal map of the focus order of your page. I found this to be incredibly useful while troubleshooting the bug, as well as a great way to visualize how someone might navigate your website using a keyboard.

These types of seemingly small, but useful features are abundant throughout Polypane.

Amazing tool

When I reached out to Kilian, mentioning my discovery, his response was “Everything’s there when you need it!”

I can vouch for that.

[loonbase]

I originally shared this on Twitter but might as well post it here too! 

With suit models going public, I thought I'd share a neat tool I made for making a bunch of suit renders extremely quickly. I have a hotkey that would take a snapshot w/ a transparent background & a tool that would trim out the extra transparent space. The tool allowed us to save a LOT of time since we could pick from thousands of different poses to work off for any suit we had in-game!

[vidadelafuerza]

JavaScript Node.js PowerShell JSON Repeat

Lately, I've taken a lot of time to reacquaint myself with JavaScript usage in Node.js. Specifically, I'm learning all the basic things I enjoy doing in PowerShell: File manipulation (list, read, write) and data manipulation (parse, extract, interpret, summarize).

Specifically, my favorite thing is to see something of interest on a website and/or analyze a website's requests in the Network tab of DevTools (CTRL+SHIFT+I). It has to be something useful. Such things can be scraped for data I might want. The way I do that is in the Network tab of DevTools (Chrome, MS Edge). Looking at a request, I can right click and get the PowerShell (or other code) that would give me that exact same information in Windows Terminal. Then, I typically do an ad-hoc script to get what I want.

Current Web Scrape++ Project

The project that has my interest at the moment is one where I'm taking all the text of a copyrighted version of the Bible, then using DOM queries and JavaScript to get just the verse numbers and verse text per chapter from the HTML. It sounds as complicated as it is, but it's the kind of thing I do for fun.

Node.js comes into play when I want to loop through all the HTML I've pulled and sanitized. The sanitization wasn't easy. I kept only the HTML with actual Bible text - which reduced the HTML payload to less than 2% its original size. That part was in PowerShell and Visual Studio Code. But I digress.

Using the Console of DevTools, I already have the JavaScript I'll need to pull what I want from the HTML file data into an array of "verse" objects, which I can then easily translate to JSON and write out.

Next, my goal is to take the data, store it as JSON files, and then manipulate it with PowerShell. For instance, I wonder what it looks like if I replace the word "Lord" with "Earl" or "Duke". As silly as that sounds, that's the entire modus operandi for my project, which has been maybe as much as 6 to 8 hours. The rest probably won't take that long, but each step has to be pursued with the smallest steps I can think to make. (There's no use looping 1189 chapters / files of HTML text to get erroneous stuff, so I go small and then large.)

[devreview]

Secret Lead Generation : Effective Strategies & Tools 2023

In this article, I will introduce you to practical AI tools that can help you earn $5000 or more a day. Many individuals have successfully made thousands of dollars by using these AI tools.

Click Here to Disclose the truth

[wedevcommunity]

Why Git Is Still the Backbone of Modern Development

Collaboration. Versioning. Control.

In 2025, Git remains the cornerstone of any development workflow. Whether you're working solo or in a team, Git provides the structure to track changes, roll back updates, and collaborate seamlessly. From GitHub to GitLab, it’s more than just version control, it’s the bridge between chaos and organization in every project.

This post is for the devs who live by their commit messages. Who know that branching, merging, and rebasing aren’t just buzzwords, they’re lifelines.

Master Git. Master development.

[forcecrow]

🚀 𝐒𝐚𝐥𝐞𝐬𝐟𝐨𝐫𝐜𝐞 𝐒𝐜𝐫𝐚𝐭𝐜𝐡 𝐎𝐫𝐠𝐬 are temporary, disposable environments designed for quick development and testing. 🛠️ These clean-slate orgs allow developers to build and deploy custom applications swiftly, making them perfect for agile teams. 💻✨

💡 𝐖𝐚𝐧𝐭 𝐭𝐨 𝐝𝐢𝐯𝐞 𝐝𝐞𝐞𝐩𝐞𝐫? 👇 𝐂𝐥𝐢𝐜𝐤 𝐭𝐡𝐞 𝐜𝐨𝐦𝐦𝐞𝐧𝐭𝐬 𝐛𝐞𝐥𝐨𝐰 𝐟𝐨𝐫 𝐚𝐥𝐥 𝐭𝐡𝐞 𝐝𝐞𝐭𝐚𝐢𝐥𝐬!

[fraoula1]

𝐓𝐡𝐞 𝐇𝐨𝐥𝐲 𝐓𝐫𝐢𝐧𝐢𝐭𝐲 𝐨𝐟 𝐖𝐞𝐛3 🔥

Want to build your own dApp in 2025? These 3 Web3 tools — Hardhat, Truffle Suite, and Web3.js — are must-haves for every blockchain developer. Whether you're deploying smart contracts or creating responsive dApp interfaces, these tools make Web3 development smooth, fast, and efficient.

From automated testing to real-time blockchain interaction, learn which tool fits your needs and why they’re dominating the Web3 space!

Watch more https://youtube.com/shorts/J-RIfZ53GWk

👇 Drop a 🔥 if you’re building in Web3!

[womaneng]

View this post on Instagram

A post shared by Zeynep Küçük Woman Engineer (@woman.engineer)

💁🏻‍♀️If you’re still juggling tools, context windows, and messy pull requests… 

Let me put you on something better 👇

✅ Plug-and-play with your stack Qodo lives inside your IDE + Git. No switching tabs, no workflow chaos. Just clean, fast integration.

🧠 Quality-first AI This isn’t just autocomplete. Qodo understands architecture, catches edge cases, and writes code you’d actually review and approve.

🛠️ Built-in smart code reviews  Find issues before they hit your PR. It’s like having a senior dev on standby.

👥 Team-friendly from day one  Stay consistent across large teams and complex repos — Qodo Merge makes collaboration frictionless.

✨ Been using it for a year. Not looking back. 

🤩If you’re a dev, you owe it to yourself to try Qodo Merge.

✨Qodo’s RAG system brings real-time, scalable context to your engineering workflow. From monorepos to microservices, get the right code insights, right when you need them. Less guesswork. More clarity. Better code. 🚀

[b0rroso]

[adafruit]

CP2105 dual UART breakout 🔌💻

Sometimes, you need more than one UART for interfacing with hardware. So instead of getting two CP2102 breakouts

you could use this CP2105

chip. We exposed the two CDC UARTs on either side plus the modem control signals so you could use this for bootloading various microcontrollers. Coming soon!

[development-stratagem]

Using the right software development tools ensures efficient management and successful deployment. These tools enhance speed, reduce infrastructure overhead, and streamline workflows. Agile design, CI/CD, containerization, and security testing help automate tasks for faster, high-quality development. Practices like TDD and agile development optimize collaboration and software functionality. Ultimately, these strategies ensure a seamless user experience and robust software performance. Read more.

[jcmarchi]

CSS Carousels

New Post has been published on https://thedigitalinsider.com/css-carousels/

CSS Carousels

The CSS Overflow Module Level 5 specification defines a couple of new features that are designed for creating carousel UI patterns:

Scroll Buttons: Buttons that the browser provides, as in literal <button> elements, that scroll the carousel content 85% of the area when clicked.

Scroll Markers: The little dots that act as anchored links, as in literal <a> elements that scroll to a specific carousel item when clicked.

Chrome has prototyped these features and released them in Chrome 135. Adam Argyle has a wonderful explainer over at the Chrome Developer blog. Kevin Powell has an equally wonderful video where he follows the explainer. This post is me taking notes from them.

First, some markup:

<ul class="carousel"> <li>...</li> <li>...</li> <li>...</li> <li>...</li> <li>...</li> </ul>

First, let’s set these up in a CSS auto grid that displays the list items in a single line:

.carousel display: grid; grid-auto-flow: column;

We can tailor this so that each list item takes up a specific amount of space, say 40%, and insert a gap between them:

.carousel display: grid; grid-auto-flow: column; grid-auto-columns: 40%; gap: 2rem;

This gives us a nice scrolling area to advance through the list items by moving left and right. We can use CSS Scroll Snapping to ensure that scrolling stops on each item in the center rather than scrolling right past them.

.carousel display: grid; grid-auto-flow: column; grid-auto-columns: 40%; gap: 2rem; scroll-snap-type: x mandatory; > li scroll-snap-align: center;

Kevin adds a little more flourish to the .carousel so that it is easier to see what’s going on. Specifically, he adds a border to the entire thing as well as padding for internal spacing.

So far, what we have is a super simple slider of sorts where we can either scroll through items horizontally or click the left and right arrows in the scroller.

We can add scroll buttons to the mix. We get two buttons, one to navigate one direction and one to navigate the other direction, which in this case is left and right, respectively. As you might expect, we get two new pseudo-elements for enabling and styling those buttons:

::scroll-button(left)

::scroll-button(right)

Interestingly enough, if you crack open DevTools and inspect the scroll buttons, they are actually exposed with logical terms instead, ::scroll-button(inline-start) and ::scroll-button(inline-end).

And both of those support the CSS content property, which we use to insert a label into the buttons. Let’s keep things simple and stick with “Left” and “Right” as our labels for now:

.carousel::scroll-button(left) content: "Left"; .carousel::scroll-button(right) content: "Right";

Now we have two buttons above the carousel. Clicking them either advances the carousel left or right by 85%. Why 85%? I don’t know. And neither does Kevin. That’s just what it says in the specification. I’m sure there’s a good reason for it and we’ll get more light shed on it at some point.

But clicking the buttons in this specific example will advance the scroll only one list item at a time because we’ve set scroll snapping on it to stop at each item. So, even though the buttons want to advance by 85% of the scrolling area, we’re telling it to stop at each item.

Remember, this is only supported in Chrome at the time of writing:

We can select both buttons together in CSS, like this:

.carousel::scroll-button(left), .carousel::scroll-button(right) /* Styles */

Or we can use the Universal Selector:

.carousel::scroll-button(*) /* Styles */

And we can even use newer CSS Anchor Positioning to set the left button on the carousel’s left side and the right button on the carousel’s right side:

.carousel /* ... */ anchor-name: --carousel; /* define the anchor */ .carousel::scroll-button(*) position: fixed; /* set containment on the target */ position-anchor: --carousel; /* set the anchor */ .carousel::scroll-button(left) content: "Left"; position-area: center left; .carousel::scroll-button(right) content: "Right"; position-area: center right;

Notice what happens when navigating all the way to the left or right of the carousel. The buttons are disabled, indicating that you have reached the end of the scrolling area. Super neat! That’s something that is normally in JavaScript territory, but we’re getting it for free.

Let’s work on the scroll markers, or those little dots that sit below the carousel’s content. Each one is an <a> element anchored to a specific list item in the carousel so that, when clicked, you get scrolled directly to that item.

We get a new pseudo-element for the entire group of markers called ::scroll-marker-group that we can use to style and position the container. In this case, let’s set Flexbox on the group so that we can display them on a single line and place gaps between them in the center of the carousel’s inline size:

.carousel::scroll-marker-group display: flex; justify-content: center; gap: 1rem;

We also get a new scroll-marker-group property that lets us position the group either above (before) the carousel or below (after) it:

.carousel /* ... */ scroll-marker-group: after; /* displayed below the content */

We can style the markers themselves with the new ::scroll-marker pseudo-element:

.carousel /* ... */ > li::scroll-marker content: ""; aspect-ratio: 1; border: 2px solid CanvasText; border-radius: 100%; width: 20px;

When clicking on a marker, it becomes the “active” item of the bunch, and we get to select and style it with the :target-current pseudo-class:

li::scroll-marker:target-current background: CanvasText;

Take a moment to click around the markers. Then take a moment using your keyboard and appreciate that we can all of the benefits of focus states as well as the ability to cycle through the carousel items when reaching the end of the markers. It’s amazing what we’re getting for free in terms of user experience and accessibility.

We can further style the markers when they are hovered or in focus:

li::scroll-marker:hover, li::scroll-marker:focus-visible background: LinkText;

And we can “animate” the scrolling effect by setting scroll-behavior: smooth on the scroll snapping. Adam smartly applies it when the user’s motion preferences allow it:

.carousel /* ... */ @media (prefers-reduced-motion: no-preference) scroll-behavior: smooth;

Buuuuut that seems to break scroll snapping a bit because the scroll buttons are attempting to slide things over by 85% of the scrolling space. Kevin had to fiddle with his grid-auto-columns sizing to get things just right, but showed how Adam’s example took a different sizing approach. It’s a matter of fussing with things to get them just right.

This is just a super early look at CSS Carousels. Remember that this is only supported in Chrome 135+ at the time I’m writing this, and it’s purely experimental. So, play around with it, get familiar with the concepts, and then be open-minded to changes in the future as the CSS Overflow Level 5 specification is updated and other browsers begin building support.

[asadmukhtarr]

The MERN stack (MongoDB, Express.js, React.js, Node.js) is a popular full-stack JavaScript framework for building modern web applications. This stack allows developers to use a single language (JavaScript) across both client-side and server-side code. If you're a MERN stack developer, mastering key tasks within each of these technologies is crucial for creating robust and scalable web applications.

In this guide, we'll walk through the 10 most important tasks every MERN stack developer should master, helping you build a strong foundation for web development.