upvote
I think the advice works well for projects that are on the order of 10k lines of code. "Major" is subjective, but that's big enough to be non-trivial yet small enough not to be a huge time investment.
reply
Could be lots of things.

A common example I give is a basic chat client/server, to learn how networking code feels, especially nonblocking IO. Especially if you're implementing the same protocol in the different languages since it means you won't necessarily be as biased by what protocol patterns are easy to implement in one language.

reply
I don't know if it counts as "major" to the OP, but early in my career, I wrote a Sudoku solver in several languages as part of learning them. It was just complex enough of a problem that I got a glimpse into the patterns that succeed or fail for different languages, especially when it comes to things like optimization, which is sometimes hard to observe in business applications.
reply
Just yesterday I finished my small sudoku "game" including generator in Odin and it was such a fun project. Not major by line count but optimizing it to generate a new puzzle in <100 ms was a fun exercise.

For anyone curious, I generate the sudokus by first randomly filling an empty grid in a way that follows the sudoku rules, then emptying random cells where doing so doesn't make the solution ambiguous (a sudoku has exactly one valid solution). The first step to fill the grid works almost exactly like a normal backtracking solver but going through the cells in random order, and for a major speed boost the backtracking is far more aggressive (always resetting half the progress so far instead of just going back one step). Checking if a sudoku has multiple solutions is again normal backtracking but only exiting at the second time it finishes or after going through all combinations. The rest is modern computers being fast and limiting the number of iterations to avoid the super slow worst cases.

reply
At the beginning of my university studies (second or third semester), one of the homework assignments was to write a Sudoku solver. I spent a lot of time on it, prototyping it with JS and HTML so that I could visualize step by step how to solve Sudoku in general, implementing the techniques in code that I had previously been doing by hand when doing Sudoku puzzles in the past.

I am not sure if everyone else looked up techniques online or what for how to do it, or if they skipped that assignment, or made a very simplified solver that only handled some basic techniques. We hadn’t really learned much of anything yet in any of the classes of the course that would be useful for making a general solver. I thought I was supposed to figure it all out on my own, and that it should be able to handle any Sudoku puzzle that a person could solve. And in the end, despite many, many hours of working on it over many days it was still far from a complete solver. And I also didn’t have time to write it in the programming language we were using in the course. I was prototyping in JS and HTML because I wanted to see visually the sudoku puzzle and be able to switch between having the computer find next number and clicking on the number myself, to discover in detail how I was thinking when I was solving Sudoku puzzles, so that in turn I could implement those techniques in code.

I lost a little bit of motivation for the class with that, and dropped out of the class soon after because I found the class to be generally uninspiring and hard to stay motivated for, in spite of being interested in programming in general and having learned programming languages and made little programs of my own already since High School. Later I dropped out of the whole study, as I was struggling to study across most subjects and wasn’t passing enough classes to be able to continue.

My interest in programming continued, however, and I’ve been developing software both professionally and as a hobby with sometimes pretty good results during the years since, and having done so for companies both small and big, and in multiple different programming languages.

But I think the way I handled trying to implement the Sudoku solver is a way of working on things that I already had since before then and that I continued also later, and that that is also part of the reason that things go wrong for me when they do. Both professionally and also elsewhere in life.

The last job I had, I was laid off for not performing well enough. And I think in part I was still working on tasks at that job in some sort of wrong way all these years later, that may be similar in some ways to what I may have done wrong with for example that Sudoku solver assignment. And probably in many other cases too both before and after.

And now that AI is here I’m not really sure how to land a new job as developer at all. Even though I would like to. Combined with the sense that there is too much ups and downs in success rate of what I’ve been working on over the years to be able to present myself in an impressive manner to employers. I value honesty and integrity, and I find it difficult to really imagine that I could sell myself well at this point when I look back at my life so far, in spite of sometimes doing things well, because of the times that projects have not gone well.

reply
Depending on what kind of concepts you want exposure to.

If you just want generic pure computation: write an interpreter for a toy language. If it’s too large, write a macro expander that can handle C style or TeX style macros.

If you want events and concurrency: write a tmux clone that can work with multiple terminals.

If you want IO but specifically networking: write a toy HTTP server that only supports 1.0.

reply
That is up to you to decide
reply
One that has expanded enough to be able to read email.
reply
"Show HN: I wrote my own kernel in [insert niche language here], here is what I learned"
reply