Never use the word “User” in your code

You’re six months into a project when you realize a tiny, simple assumption you made at the start was completely wrong. And now you need to fix the problem while keeping the existing system running—with far more effort than it would’ve taken if you’d just gotten it right in the first place.

https://codewithoutrules.com/2018/09/21/users-considered-harmful/

Why you can have millions of Goroutines but only thousands of Java Threads

Many seasoned engineers working in JVM based languages have seen errors like this: OutOfMemory…err…out of threads. On my laptop running Linux, this happens after a paltry 11500 threads. 

If you try the same thing in Go by starting Goroutines that sleep indefinitely, you get a very different result. On my laptop, I got up to 70 million goroutines before I got bored. So why can you have so many more Goroutines than threads? The answer is a fun journey down the operating system and back up again. And this isn’t just an academic issue – it has real world implications for how you design software. I’ve run into JVM thread limits in production literally dozens of times, either because some bad code was leaking threads, or because an engineer simply wasn’t aware of the JVM’s thread limitations.

https://rcoh.me/posts/why-you-can-have-a-million-go-routines-but-only-1000-java-threads/
Design a site like this with WordPress.com
Get started