When do you go public? [HACKADAY]() Do Bounties Hurt FOSS? [Read Article Now»]( Horrendous Mess of Wires By [Elliot Williams]( When do you post your projects? When theyâre done? When theyâre to the basic prototype stage? Or all along the way, from their very conception? All of these have their merits, and their champions. In the post-all-along-the-way corner, we have Hackadayâs own [Arya Voronova], who [outlines the many ways that you can start documenting your project before itâs even a fully fledged project](. She calls these tidbits âbreadcrumbsâ, and it strikes me as being a lot like keeping a logbook, but doing it in public. The advantages? Instead of just you, everyone on the Internet can see what youâre up to. This means they can offer help, give you parts recommendations, and find that incorrect pinout that one pair of eyes would have missed. It takes a lot of courage to post your unfinished business for all to see, but ironically, thatâs the stage of the project where you stand to gain the most from the exposure. On the opposite end of the spectrum are the folks who document their projects at the very end. We see a ton of these on Hackaday.io and in peopleâs personal blogs. Itâs a great service to the community, frankly, because at that point, youâre already done with the project. This is the point where the reward, for you, is at its minimum, but itâs also the point where you feel least inhibited about sharing if youâre one of those people who are afraid of showing your work off half-done. The risk here, if youâre like me, is that youâre already on to the next project when one is âdoneâ, and going back over it to make notes seems superfluous. Those of you who do it regardless, we salute you! And then thereâs the middle ground. When youâre about one third of the way done, you realize that you might have something half workable, and you start taking a photo or two, or maybe even typing words into a computer. Your git logs start to contain more than just âfixed more stuffâ for each check-in, because what if someone else actually reads this? Maybe youâre to the point where youâve just made the nice box to put it in, and youâre not sure if youâll ever go back and untangle that ratâs nest, so you take a couple of pictures of the innards before you hot glue it down. Iâm a little ashamed Iâm probably on the âpost only when itâs doneâ end of things than is healthy, mostly because I donât have the aforementioned strength of will to go back. What about you? Where do you lie on the project-reporting spectrum? Head on over to Hackaday tomorrow morning and let us know! From the Blog ---------------------------------------------------------------
[A Raspberry Pi 5 is Better Than Two Pi 4s]( By [Elliot Williams]( Elliot gets hands on the new Raspberry Pi 5 and starts to kick the tires. [Read more »](
[The Oldest Living Torrent is 20 Years Old]( By [Lewin Day]( A twenty-year old torrent? Lewin looks back at the distribution method that's not dead yet. [Read more »](
[A Pulse Of Annoyance About Oscillators, Followed By A Flyback Of A Rant]( By [Jenny List]( Honestly, we didn't know how to make a real flyback circuit. Jenny sets us straight. [Read more »]( [Hackaday Podcast](
[Hackaday Podcast 238: Vibrating Bowl Feeders, Open Sourcery, Learning to Love Layer Lines]( By [Hackaday Editors]() What happened last week on Hackaday? The Podcast will get you up to speed. [Read more »]( If You Missed It --------------------------------------------------------------- [That’s not a Junker… That’s My Generator]( [Hackaday Prize 2023: Stretch Your Day With This 29-Hour Clock]( [Tetris Clone Uses 1000 Lines of Code, and Nothing Else]( [Feed Your Fasteners in Line, With a Bowl Feeder]( [Beating Apple’s Secret Lid Angle Sensor Calibration With Custom Tool]( [Looking Inside a 3D Printer Nozzle with Computed Tomography]( [Hackaday]() NEVER MISS A HACK
[Share]( [Share]( [Share]( [Terms of Use]( [Privacy Policy]( [Hackaday.io]( [Hackaday.com]( This email was sent to {EMAIL} [why did I get this?]( [unsubscribe from this list]( [update preferences]( Hackaday.com · 61 S Fair Oaks Ave Ste 200 · Pasadena, CA 91105-2270 · USA