submitted by CodiUnicorn to events
1 points | 0 comments
The next part in a series of live talks on building a custom programming language using C++ is dedicated to creating an AST. This session will lay the groundwork for everything that comes next in this language implementation journey: semantic analysis, evaluation, and beyond.
Join the live session to dive deeper into compiler design.
submitted by CodiUnicorn to programmer_humor
395 points | 23 comments
submitted by CodiUnicorn to javascript
4 points | 1 comments
https://nesbitt.io/2026/04/16/features-everyone-should-steal-from-npmx.html
submitted by CodiUnicorn to programmer_humor
400 points | 19 comments
submitted by CodiUnicorn to programmer_humor
517 points | 23 comments
submitted by CodiUnicorn to gamedev
10 points | 5 comments
https://pvs-studio.com/en/blog/posts/1375/
submitted by CodiUnicorn to programmer_humor
255 points | 20 comments
submitted by CodiUnicorn to programmer_humor
236 points | 5 comments
submitted by CodiUnicorn to gamedev
4 points | 0 comments
https://pvs-studio.com/en/blog/posts/1361/
submitted by CodiUnicorn to programmerhumor
229 points | 10 comments
submitted by CodiUnicorn to programmerhumor
534 points | 33 comments
submitted by CodiUnicorn to golang
3 points | 0 comments
https://pvs-studio.com/en/blog/posts/go/1350/
Gophers, hey. Confusing ^ with exponentiation instead of XOR in Go seems like a pretty easy mistake to make. The bug itself is simple, but it still shows up even in some well-known projects with large codebases.
How often does this happen in your code?