Musashi

ts from a BCD value is a simple shift by 4 bits (6 cycles) rather than a VERY expensive divide (140 cycles).

up in a couple of weeks and release, such as https://github.com/kstenerud/virtual-builders The key is to build empathy with your potential users. What will their motivations be that lead them to try out your project? What will they be looking for when they use it? What would someone who has never seen the project before struggle with? (that last one is the hardest because you're so close to the project that it's hard to see what it's like to know nothing about it). These tell you what kind of UX you'll need, what kind of documents you'll need, what kind of tutorials you'll need, how to structure your project for your target audience, etc ("it's for everybody" is never a good idea). Building a project is a lot like building a startup. You need to figure out your target market. That means lots of tests, lots of talking, lots of listening, market research, competitor analysis, even some pivots. A lot of times it comes down to recruiting people to just try it and do a brain dump of everything that goes wrong or frustrates or confuses them. I've done show-HN posts for things that are unreleased (e.g. https://news.ycombinator.com/item?id=34720488 ), just to get the valuable criticism. It's nearly impossible to develop good projects in a vacuum. If you're not posting out of worry for doing it wrong, THAT IS doing it wrong. The point is to find out where you're doing it wrong so that you can correct it! And that's where the crowd is a HUGE help. You can't build something great without looking foolish first.

as I said, it's pretty low maintenance. Today, my latest itch is efficient and human-accessible data communications, and so I'm spearheading a new bidirectional, general-purpose, platform agnostic, encryption-capable, transport-agnostic RPC protocol [3], including all of the supporting technology it requires [4] [5] [6] [7] [8] [9]. If it takes off, it will save the entire planet a TON of time, energy, and cost, and I'll probably not see any donations or thanks from those who benefit the most. Please don't take this as complaining. I'm still going to develop and support my babies, because I'm not doing this for the money; I'm doing it to better the state of computing systems (mostly for my own sanity). However, because I'm forced to find separate employment to support my family, it leaves me with FAR less time to focus on these technologies. My estimate would be that I'm running at 1/4 my usual velocity when I require separate employment. For bigger projects that turns a 1 year project into 4 years. However, from a company perspective I also understand. Giving donations is actually a big pain in the ass, especially if it's to a foreign entity. Normal invoices are FAR easier, but then how do you structure it for free access + payment options without pissing people off? It's a tricky situation... [1] https://github.com/kstenerud/KSCrash [2] https://github.com/kstenerud/Musashi [3] https://github.com/kstenerud/streamux [4] https://github.com/kstenerud/concise-encoding [5] https://github.com/kstenerud/compact-float [6] https://github.com/kstenerud/compact-time [7] https://github.com/kstenerud/varpad [8] https://github.com/kstenerud/variable-bit-padding [9] https://github.com/kstenerud/vlq

ve never tried before. You absolutely should try diving into things before you know what you're getting into. Even if it doesn't turn out the way you wanted, you're in for one hell of a ride, and what you'll learn is priceless. [1] https://github.com/kstenerud/KSCrash [2] https://github.com/kstenerud/Crash-Manager [3] https://github.com/kstenerud/musashi/ [4] https://github.com/kstenerud/compact-float [5] https://github.com/kstenerud/concise-binary-encoding