Not sure if it was due to higher load from HN or my IP location, but your website is inaccessible to me right now: "This deployment is temporarily paused."
For me also it is unreachable
"This deployment is temporarily paused"
How a devboard works (and how to make your own)
11–20 of 35 posts
Re: How a devboard works (and how to make your own)
#12Dang, I wanna read this but the site seems down
Re: How a devboard works (and how to make your own)
#13Honestly my problem is that all my designs turn into devboards since I always have a kind of "FOMO" of not breaking something out and then needing it later to bodge things... and then I'm left with a crowded board where I don't even use two thirds of things...
Test pads are great for these anxious breakouts. I usually drop tons and tons of test pads on the back of my boards as it's a very dense and unobtrusive way to expose traces that you probably don't need.
Re: How a devboard works (and how to make your own)
#14Dang, I wanna read this but the site seems down
Re: How a devboard works (and how to make your own)
#15While the deployment is down you can read it on web.archive.org https://web.archive.org/web/20251107235749/https://kaipereir...
Re: How a devboard works (and how to make your own)
#16I don't like this tutorial. It purports to teach you "what everything on the PCB fundamentally does, and what every single component on your PCB is actually for!" but it gets the reasoning for a lot of stuff wrong, sometimes badly wrong. I think every single instance of a component with a numerical value picks the value with a misleading or even completely wrong justification. Even if the tutorial gets to an OK schem…
Do you have a tutorial that you like?
I agree with the sibling comment that "How to decide what you need on your devboard" is the tutorial that would be nice to see. This article is trying to do too many things at once (design a dev board, baby's first schematic, baby's first PCB, baby's first JLCPCB order,...) and that's really the only one that's novel. The rest of it is standard EE stuff that's covered in a lot of places (with varying degrees of success).
As for decoupling, I've written about how to do it in various places scattered across the internet. I should really collect it all in one place one of these days.
Re: How a devboard works (and how to make your own)
#17Re: How a devboard works (and how to make your own)
#18I don't like this tutorial. It purports to teach you "what everything on the PCB fundamentally does, and what every single component on your PCB is actually for!" but it gets the reasoning for a lot of stuff wrong, sometimes badly wrong. I think every single instance of a component with a numerical value picks the value with a misleading or even completely wrong justification. Even if the tutorial gets to an OK schem…
Can you clarify the issues with KiCad's BOM flow?
Re: How a devboard works (and how to make your own)
#19I don't like this tutorial. It purports to teach you "what everything on the PCB fundamentally does, and what every single component on your PCB is actually for!" but it gets the reasoning for a lot of stuff wrong, sometimes badly wrong. I think every single instance of a component with a numerical value picks the value with a misleading or even completely wrong justification. Even if the tutorial gets to an OK schem…
This reads like the author just wanted to format his ChatGPT-aided build record in a lecture manual format, rather than being an attempt at such material.
Re: How a devboard works (and how to make your own)
#20I thought this article would first start with the most essential question: "How to decide what you need on your devboard". Without that critical piece of design work, you may as well call this "How to build a Raspberry Pi Nano from scratch". Which, to be fair, is also a good article to write. But step 1 for really building a dev board is answering the question, "What do I need from this that I can't get from a $5 Ama…
I just go the other way - dev boards are so cheap you can just take a scalpel to them and take off the bits you don’t want.