Hacker News: teivah

New comment by teivah in "Linux 7.0 Broke PostgreSQL: The Preemption Regression Explained"

teivah — Wed, 29 Apr 2026 18:56:17 +0000

I used that post as a source yes, and it’s stated explicitly but it’s not the only one. One section in particular is similar since we both present the different preemption modes. However, both audiences are different. thebuild.com has an audience composed of PostgreSQL enthusiasts (if not experts) and I don’t. So a significant part of my post was about explaining things from first principles (what’s a page, a TLB, a spinlock, etc.). I explain way more “basic” things and he goes beyond me in terms of how to cope with the problem. I don’t think the posts are closed.

New comment by teivah in "Working on complex systems: What I learned working at Google"

teivah — Thu, 15 May 2025 11:54:51 +0000

Sorry about that, I'm my newsletter provider (Substack) which is very buggy sometimes.

New comment by teivah in "Working on complex systems: What I learned working at Google"

teivah — Thu, 15 May 2025 08:18:19 +0000

I wasn't aware of bonuses-as-a-service. Thanks for sharing.

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

teivah — Sat, 12 Apr 2025 13:31:19 +0000

Generics are already there.

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

teivah — Fri, 11 Apr 2025 22:54:34 +0000

His review contains comments annotated on a book of 300+ pages. I don't think it would have made this section any better by deep diving into his review.

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

teivah — Fri, 11 Apr 2025 12:36:55 +0000

Outdated I'd rather say :) I documented here https://100go.co/#not-being-careful-with-goroutines-and-loop... but you're right, it was fixed (alongside 2 other mistakes in the 100).

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

teivah — Fri, 11 Apr 2025 11:02:54 +0000

No worries I didn't take it as a criticism. I understand your point. I mean when we sign a contract there's a minimum number of pages to write. But personally, I never felt the pressure of having to add more stuff.

Instead, my DE multiple times told me that it's better to favor just-in-time teaching over just-in-case teaching. Meaning multiple times, he made me drop certain section because they weren't really serving the chapter. They were "perhaps helpful" and he made me drop all of those.

I guess it also depends on who you're working with and which publisher. On this aspect, Manning was fair, imo.

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

teivah — Fri, 11 Apr 2025 10:55:51 +0000

I said I was a source of inspiration for the mistakes in my book. Said differently, I've done a lot of mistakes myself which ended up being a section in the book.

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

teivah — Fri, 11 Apr 2025 08:17:26 +0000

It's your opinion, nothing wrong with it. Let me try to see if I can make you change it at least a bit.

> The first paragraph is totally pointless - we are reading a book about 100 most common mistakes, obviously this mistake is very common, how did this increased the value?

There are different levels in terms of common mistakes, and this one was probably one that all the devs did at some point. So I think highlighting the fact it's a frequent one does make sense.

> Then we have another line that explaining what happens in the code, which is totally useless because the code is super trivial.

I have a rule: always explain the intention of the code. Even if it's 5 lines of code, it helps the reader to better understand what we will want to highlight.

> Then the code, with more explanations on the side as if the previous line was not clear.

The explanations on the side do not impact the size of the book so the argument doesn't hold. I did it in many code snippets to highlight where the reader needs to focus.

> I understand that book publishers feel they need to justify the price of a book by reaching the 300p mark in some or other way

This is more about guiding the readers, making sure the expectations are crystal clear and that they can follow me throughout an explanation. You judge it as a criteria to justify the price of the book, but it's not the real reason. At least not for my book and I'm sure it's the case for many others :)

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

teivah — Thu, 10 Apr 2025 22:26:10 +0000

#63 isn't about the lack of execution guarantees when you execute multiple goroutines without proper synchronization; it was related to loop variables and goroutines.

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

teivah — Thu, 10 Apr 2025 22:13:40 +0000

That's why Manning will consider a 100 Rust Mistakes edition.

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

teivah — Thu, 10 Apr 2025 22:09:10 +0000

More details here: https://100go.co/#not-being-careful-with-goroutines-and-loop.... My example was probably terrible as it's one of the three mistakes in the book that aren't relevant anymore, thanks to Go's recent updates.

Thank you very much for your comment, though. It means a lot.

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

teivah — Thu, 10 Apr 2025 21:49:38 +0000

Agreed. That was also my point when I mentioned the book started the "100 ${LANGUAGE} Mistakes and How to Avoid Them" series at Manning.

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

teivah — Thu, 10 Apr 2025 21:46:41 +0000

Thank you!

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

teivah — Thu, 10 Apr 2025 21:46:28 +0000

I just noticed my post was on HN. Thank you very much :)

Probabilistic Increment: A Randomized Algorithm to Mitigate Hot Rows

teivah — Wed, 19 Feb 2025 18:26:49 +0000

Article URL: https://www.thecoder.cafe/p/probabilistic-increment

Comments URL: https://news.ycombinator.com/item?id=43105505

Points: 1

# Comments: 0

New comment by teivah in "AI tool that helps SREs and DevOps teams"

teivah — Thu, 09 Jan 2025 21:58:08 +0000

If you're focused on k8s I'd suggest K8sGPT

Scalable Causal Consistency with No Slowdown Cascades

teivah — Wed, 08 Jan 2025 23:02:13 +0000

Article URL: http://muratbuffalo.blogspot.com/2025/01/i-cant-believe-its-not-causal-scalable.html

Hacker News: teivah

New comment by teivah in "Linux 7.0 Broke PostgreSQL: The Preemption Regression Explained"

New comment by teivah in "Working on complex systems: What I learned working at Google"

New comment by teivah in "Working on complex systems: What I learned working at Google"

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

New comment by teivah in "The Story Behind “100 Go Mistakes and How to Avoid Them”"

Probabilistic Increment: A Randomized Algorithm to Mitigate Hot Rows

New comment by teivah in "AI tool that helps SREs and DevOps teams"

Scalable Causal Consistency with No Slowdown Cascades

Snapshot Isolation vs. Serializability

Refactoring with Codemods to Automate API Changes