Luke Seale
lbseale.bsky.social
Luke Seale
@lbseale.bsky.social
Rust 🦀 | Haskell ➡️ | Financial Modeling 📊 | Renewable Energy Finance 🌞

Lol I hope you got this from NCD
December 25, 2025 at 2:19 PM
Wharton doesn't get enough hate for this
October 25, 2025 at 2:05 PM
My first job was as an engineer at a chemical plant and we watched those videos for training. I think about them all the time. So yes, we're friends.
October 22, 2025 at 1:02 PM
I use a lot of HashMaps in Rust and this still happens to me all the time
October 16, 2025 at 3:07 PM
I think about this all the time. The best I can do is to think that everyone forgot why we had all these norms. They have to re-learn why they're important the hard way.
October 8, 2025 at 1:09 AM
I once used it to derive functions for marshalling and validating data from a foreign language.

I'd define a Haskell type, then the TH macro would generate the function for building and validating it from the foreign data.
October 5, 2025 at 4:22 AM
I will be forever perplexed by the inability of those who are out of touch to recognize that they are out of touch
September 24, 2025 at 6:55 PM
Are you saying that Hegseth will be able to successfully defend himself by claiming he didn't know these actions are illegal? Isn't that not considered a valid defense?
September 19, 2025 at 11:38 PM
Rust's documentation is very strong and has type searching. One reason I like it better than Haskell: Rust has a culture of thorough documentation and examples. Haskell libraries are less consistently well-documented.
August 23, 2025 at 3:06 PM
Just started The Fractal Organization by Hoverstadt, I am already loving it
July 24, 2025 at 4:11 PM
Rofl, jinx! Yeah of course use your engineering judgement to keep it as simple as you can.
June 17, 2025 at 1:41 PM
Another thing I like about this approach is that transformations between these types are pretty easy to write if you have a type checker. So it's not too difficult to support having the right type for the right job.
June 17, 2025 at 1:40 PM
Well explained! I have been working on getting my colleagues to see our software this way.

Once you learn to think in terms of types, it's hard to remember that other developers don't.
June 17, 2025 at 1:29 PM
If and when I want to handle this cleanly, I'll add a check at the boundary for whether the dates are reasonable. So the input will be rejected before I even do any arithmetic that might fail.

It's too much overhead to bubble errors up from that deep into the logic
June 15, 2025 at 3:34 PM
Here's why I'm ok with it: My application does a lot of date arithmetic. It's possible it overflows and goes beyond 9999-12-31.

I'm completely ok with crashing if that happens. It means you've entered silly input. So there are unwraps everywhere. Idk what a better solution would be.
June 15, 2025 at 12:38 PM
My favorite memory about this was a CS major friend asking me "Why do planes do whatever they do instead of this:" and he held his hand flat at a slight up angle.

My answer: "That is what they do"
May 28, 2025 at 12:58 PM
After taking aerodynamics classes in college, I am appalled by how badly airplanes are explained to people. All you need to know: flow of air goes down, plane stays up. Stick your hand out of a car window and try it.
May 28, 2025 at 12:56 PM
Like the other commenter, I thought of Abraham Lincoln. That was only around 200 years ago and the amount of death and poverty is staggering. Even the wealthiest people experienced it!
May 1, 2025 at 1:15 PM
Careful they might unplug you
April 25, 2025 at 3:48 PM