Hillel Wayne
Everything, newest first — across every channel. Their profile → · Subscribe
Hiding
22 October
30 September
16 September
1 September
18 August
29 July
From one piece Formal methods with Hillel Wayne 24 beliefs, in the piece's order there
-
korrents.com
Nobody in software treats debugging as a discipline; it is left as a handful of basic heuristics.Their words
But this is the book that I give to every junior engineer because I think like nobody ever really talks about debugging as like a discipline outside of like basic heuristics.
-
Their words
And up until now that like could only really happen if one of those people in that family that community or that school was like really really into computers. But now it's possible for everybody to have situated software.
-
Their words
I predict that in the next 10 years software development will survive, but it will become like any other white-collar professional work. No more $200,000 salaries, unlimited vacation, or incredible employee bargaining power.
+ 21 more
-
Their words
So, it's hard to tell how much of like the loss of the past few years was AI versus the end of like zero interest rate policy and like the post-COVID crash. And I think it's more the latter, but like again, LLMs are still getting better.
-
Their words
I think it is making it more popular. I don't know if it'll make it go mainstream, but it's definitely making it a lot more popular. It's bringing it from maybe like 0.1% to 0.3% which is huge.
-
Their words
And often I found with my clients I have to tell them like it's doing a good job at generating the actual design, but in actually expressing what the design is supposed to do, it cannot do that yet. You have to do that part yourself.
-
Their words
As a general thing we've seen like to get good results you have to already know how to get good results without it. It just helps you get good results faster.
-
Their words
I love formal methods, but I think it's a fairly niche tool for most people and I think like property-based testing is in general going to be useful for more people.
-
Their words
I think a lot of the reason people are skeptical of these is because they've been burned by things like case and UML and all these other miracle solutions that were forced on them by people who wanted them to use it no matter what.
-
Their words
I think the case of TLA+ and most, not all, but most formal methods, they shine the most in highly computational domains, where most of the problems are highly technical and not like business embedded.
-
Their words
And I wonder sometimes if that is the reason people don't recognize the use of math in software engineering is because the math they do need is not the math they've been exposed to.
-
Their words
But I think it is more useful for most developers to have an exposure to like what math has in the various fields versus just going all in every single field when they see them, right? You've got to know what's available to know what's most useful for you. And most math will not be useful for you.
-
korrents.com
Concurrency is hard not because human brains cannot handle it but because nobody gets enough practice at it.Their words
I think a large part of the problem of why it's hard for us is because you don't get a lot of practice. Usually when you have a race condition in a system, you find out months later and then you try a fix and you find out weeks later after that if the fix actually worked.
-
Their words
Then the actual system might still have bugs, but we can iron out the issues in the abstraction such that we don't actually build them in the real system.
-
energyformal proofnuclear power
Their words
but I can tell you with first hand experience nuclear power plants do not care about this stuff. They're actually just fine with with with thorough testing.
-
Their words
when you start talking about like most interesting domain problems, you have to pull in so much context that basically even writing what the function is supposed to do becomes a nightmare. The imperative program you write that will get correct 99% of the time is probably good enough to use in almost all cases.
-
Their words
I think this project and writing about it and thinking about it has firmly moved me from the camp of we are definitely not to we probably are.
-
Their words
And that kind of compiling of information about the materials is something other fields do that we don't do. An analogy that I would think of in software would be something like a 500-page book on how to version an API.
-
korrents.com
Software iterates better than every other engineering field and plans worse than all of them.Their words
while we are a lot better at iterating than other fields, we're worse at the planning part. Like we still need to do some kind of planning before we iterate and we just aren't as good as those other fields.
-
korrents.com
Version control is the one thing every traditional engineer wishes their old field had.Their words
Yeah, I interviewed like 20 people on this. I think all 20 mentioned version control as the thing they wish they had in their old field.
-
Their words
Software is kind of unique in having the third kind of the practitioner conference where we are just meeting to get better at what we do. We also are really the only kind to really focus heavily on like open source in making our knowledge freely available.
-
korrents.com
Software did not invent iterative development: mining engineers had their Agile revolution in 1960.Their words
And the first thing he pointed out to me was that they had their Agile revolution in 1960.
-
Their words
The core tension of engineering is between how expensive it is to make a mistake and how quickly you can iterate. The faster you can iterate, the less planning you need to do before you iterate, and the more expensive it is, the more planning you need to do.
-
Their words
If I had to summarize what I found in general, I'd put it like this. Everybody hates waterfall.
21 July
14 July
7 July
17 June
10 June
2 June
28 May
20 May
13 May
6 May
28 April
21 April
15 April
1 April
24 March
18 March
10 March
23 February
25 September 2025
9 September 2025
6 August 2025
-
Lovedrcmnd.app
Making Software: What Really Works, and Why We Believe ItTheir words
But no blog post has influenced me as profoundly as Data and Reality or Making Software. There is no blog or talk about debugging as good as the Debugging book.
7 May 2025
1 April 2025
12 March 2025
4 March 2025
3 February 2025
11 September 2024
15 July 2024
17 June 2024
29 May 2024
14 May 2024
1 May 2024
10 April 2024
1 April 2024
18 March 2024
5 January 2024
21 August 2023
18 May 2023
7 April 2023
2 August 2022
1 July 2022
22 June 2022
Nothing matches.
What is a korrent?
A korrent is a belief a person has stated in their own words: one sentence stating the claim, backed by a quote and a source, kept at korrents.com.
Under a name here, the quoted block is what they actually said. The korrent beneath it is the claim those words support, in korrents' wording — tap it to see the record, its source, and who else holds it.
Nobody here wrote their own korrents. They are compiled from public statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they do, this site shows a machine translation beneath the post, in this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the serif above is exactly what the person published, and it is what to quote them on. A translation can be wrong in ways that matter, especially about tone.
Only the post's own words are translated. A quoted post, a linked article and a belief on korrents.com are left in their original language.