59 points speckx 1 hour ago 21 comments

bryanlarsen 42 minutes ago | parent

A standard piece of advice is that every developer should do a major project in every big language family. A Lisp, an OO language, a functional language, Prolog, VHDL or Verilog, a Forth, et cetera. They'll all make you think differently and teach you lessons you will use outside of the family.

jghn 37 minutes ago | parent

This. It's not Rust in the author's case. It's being exposed to a language that's enough different from what they're used to that it affects their big picture.

pjmlp 27 minutes ago | parent

Yes, especially since many of the type system features younger devs assign to Rust, are present in most Standard ML derived languages.

It is a scale, and there are other languages that go beyond Rust, with dependent types, effects, capabilities, linear types, formal profs,...

jahnu 25 minutes ago | parent

What counts as a major project?

kccqzy 24 minutes ago | parent

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.

RussianCow 19 minutes ago | parent

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.

treyd 18 minutes ago | parent

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.

win311fwg 8 minutes ago | parent

One that has expanded enough to be able to read email.

lnenad 23 minutes ago | parent

Agreed 100%. This is the single most useful thing I experienced in my career.

brightball 11 minutes ago | parent

100% agree with this.

Elixir was somewhere between my 12th-14th language and nothing changed my perspective so much as understanding why the BEAM works the way it does.

nomel 7 minutes ago | parent

> Verilog

My favorite side quest that I definitely recommend. Physical parallelism is so fun to reason about.

I had the advantage of sitting next to a proper professional to bounces questions off of, so I was able to get an SPDIF decoder to work in about a week! It was a very interesting lesson in the costs of abstraction, and why you will never really find abstraction layers in hardware.

begueradj 5 minutes ago | parent

It's like saying a novelist should write a major novel in every important spoken language.

wizzwizz4 3 minutes ago | parent

At the very least, a short story.

MomsAVoxell 2 minutes ago | parent

I have applied this for decades, with multiple languages under my belt, and multiple million-dollar projects on my CV, and meanwhile I have found another similar rule that I think also sharpens a developers mind:

Put Lua in things.

Now, before you anti-Lua types start jumping on that down-vote, let me explain. Putting Lua in things is easy - and it is hard. It teaches you how to treat other things with respect, and it teaches you how to disregard other things and "Just Use Lua™".

You can learn the language - multiple variants of it. You can learn the 'things' you're putting it in. You can learn how a VM works, what byte code is, how it can be used effectively - and how it can be used counter-productively, too.

It will teach you the limits of a language - Lua, and C - and it will teach you the strengths of both (as well as Rust, and all the other things you an get an FFI scaffolding built around).

You can use Lua to produce your own domain specific language. You can use it to replace whatever other language the "thing" is using. You can use it to minimize the impact of a VM and scripting and byte code - you can learn how to maximize these things as well.

You can learn how slow/fast pieces of the system interact productively and effectively - you can learn how things get mightily messed up, also, if you use the wrong lubricant.

In the end, you may not even end up using it for productive things - but you might. Either way, by applying this maxim, you can learn pretty much everything interesting there is to learn about software (besides LLM's) in today's modern stack madness, and then some.

Seriously, give it a try.

The other one of these (there are a few), is to do a Linux From Scratch session at least twice a year. Do it this year, but plan on doing it again next year as well.

Iterate. Extend. Ignite.

harveymadeunico 2 minutes ago | parent

If you could maybe reduce that down a bit that would be great. No one in their right mind has the time for major projects in all of those.

Another way to do it would be the standard low->high level and then one based on lambda calculus. Von Neumann and Church.

Assembly, C, Java, Clojure.

Assembly, C, C#, F#.

Assembly, Fortran, Rust, Rust, Brainf*ck.

xeubie 16 minutes ago | parent

Rust enums conflate the tag type with the union type that uses it. These should be separate things. In the example here, you can see that Rust gives no way to represent the tag type `{Human, Cat}`. In Zig there is an enum which is a set of tags, and a union which is backed by that enum and can have fields. It is obviously better to have these as separate concepts rather than conflating them. You often want the kind without the data, and Rust gives you no way to represent it. I'm not sure why I am bothering to rant about this but it's one of my biggest annoyances with the language.

clownstrikelol 8 minutes ago | parent

Sure you can, bringing data along for the ride is optional in Rust. Nothing is forcing you to use it like a tagged union, it’s an optional (but useful) feature.

If you want specific values (integer or otherwise) associated with specific variants (i.e. Human = 1, Cat = 4) you can do that too. Use the #[repr(T)] or impl the From / Into traits yourself.

slopinthebag 7 minutes ago | parent

i dont understand what rust doesn't give you that zig does?

Jtsummers 1 minute ago | parent

[delayed]

coldtea 12 minutes ago | parent

Such enlightenment was a common read back in the glorious days of before 2023.

But reading this in 2026, when the entirety of the profession has changed (for better or worse) due to LLMs, seems strange.

Like someone writing how some new preservation method for making food last longer revolutionized how they manage their pantry, shortly after the invention of the fridge.

I like the post - it's just sad how many will not have these epifanies anymore, or they wont mean anything, and how many starting today would already just say "how quaint" and move on.

bingobongo84 1 minute ago | parent

Agreed. My first thought reading this was “does this really matter anymore?”