> Build your own programming language

https://craftinginterpreters.com/ is excellent for this

>Build your own filesystem

Found a few links:

* https://blog.carlosgaldino.com/writing-a-file-system-from-sc...

* https://www3.nd.edu/~pbui/teaching/cse.30341.fa17/project06....

* https://stackoverflow.com/questions/4714056/how-to-implement...

> Build your own webcam and webcam client

This might help, depending on how deep you want to go:

https://m.youtube.com/watch?v=PaXweP73NT4

> Build your own keyboard

This is something I've been interested in lately as well & came across this video: https://www.youtube.com/watch?v=M_VuXVErD6E

It's targeting a split keyboard, but I think it details the general steps involved pretty well.

I was thinking of posting something along these lines, nice to see someone else also aware of this niche!

Software point of view, you'd like to use QMK or ZMK, and KiCad to design the hardware (PCBs). Reddit's r/olkb and r/ergomechkeyboards are great places to start!

Bonus: QMK supports trackpads and nipple-pointers too! (Not sure about mice though)

>> Build your own girlfriend

Or build your own religion. Them you can build as many humans as you want.

^ Snarky yet accurate comment about Elon Musk and "The Mission".

I would love to see "Build your own protocol"

I would love to understand the architecture of an MMO

wwwweird science!

> Build your own MMO

The first M makes this infeasible.

> Build your own girlfriend ;)

Eww. And illegal.

I knew someone would say this.

"Never roll your own cryptography", despite the ambiguity of its phrasing, means never use uncertified crypto in production unless you're willing to take the risk. It doesn't mean to never build cryptography without an expert's permission. Everyone who has ever published world-class cryptography has rolled their own crypto.

That is what I meant by my comment, I was not referring to learning exercises, I should've been more clear, though.

My apologies then. I've seen this phrase repeated ad nauseam even when its not warranted and I want to point out that it shouldn't be followed blindly.

“20 years of abstinence-only cryptography education hasn’t gotten us anything but an endless supply of bad crypto in production systems”

People absolutely should. The best way to understand how something works is to build it.

What that phrase means is you shouldn't use hobby crypto libraries for any important production services. But that's also not the point behind "Build Your Own" type projects. So your advice isn't correct in this scenario.

Everyone should build one, as early as possible and fail and then come to this realization.

the only issue is what it means to "fail". it's not really an issue until you're hacked and then it's too late

to fail doesn't mean to fail in production

right, but how else are you going to know your crypto is broken? what unit test is going to fail?

if you need expert opinion on your library order a security audit. otherwise even expert-designed systems have failed and most people know that it is very unwise to give security guarantees to devices that have so many moving parts