Update with some extra stuff (finally, but still missing a ton of stuff

I didn't add to this yet)

README.md

@@ -110,7 +110,9 @@ TODO: this took me very long to make, will add this later (remind me if I forgot
 
 But tldr; handmade hero, all of it, then u should be able to learn on your own.
 
-Also for math, the [BSC 2025 talk by Ginger Bill](https://www.youtube.com/watch?v=YNtoDGS4uak), and Freya Holmer's [Math for Gamedev](https://www.youtube.com/watch?v=MOYiVLEnhrw&list=PLImQaTpSAdsD88wprTConznD1OY1EfK_V) series.
+For math, the [BSC 2025 talk by Ginger Bill](https://www.youtube.com/watch?v=YNtoDGS4uak), and Freya Holmer's [Math for Gamedev](https://www.youtube.com/watch?v=MOYiVLEnhrw&list=PLImQaTpSAdsD88wprTConznD1OY1EfK_V) series are great resources.
+
+[This Problem Changes Your Perspective On Game Dev](https://www.youtube.com/watch?v=o5K0uqhxgsE)
 
 ### Compiler and Language design
 
@@ -125,8 +127,15 @@ there is also a "Core Dumped" video covering it on youtube, but I find the blog
 
 Jonathan Blow talks, specifically Jai ones where he shows features like compile time and AST injection.
 
-Programming language documentation, specifically the zig docs, odin docs, cakelisp, Nim, cppfront
-and probably some more that I forgot.
+Christopher Lerno blogs (on handmade network), specifically [language design lessons](https://c3.handmade.network/blog/p/8682-some_language_design_lessons_learned).
+
+Programming language documentation, specifically the C3 docs, zig docs, odin docs, cakelisp, Nim,
+cppfront and probably some more that I forgot.
+
+Also talking with other language designers is great (although beware of advice, see C Lerno's blog),
+feel free to message me, I am always open to language design/implementations discussions.
+
+["Boundaries of Language Design" with Andrew Kelley & Ginger Bill](https://www.youtube.com/watch?v=3K8znjWN_Ig)
 
 ## Resources (unordered)
 
@@ -135,8 +144,23 @@ and probably some more that I forgot.
 - [Semantic compression by Casey Muratori](https://caseymuratori.com/blog_0015)
 - [On bad advice](https://www.scattered-thoughts.net/writing/on-bad-advice/)
 - [John Carmack on Inlining code](http://number-none.com/blow/john_carmack_on_inlined_code.html)
-- [Ryan Fleury blogs](https://www.rfleury.com/archive?sort=new)
+- ["Papers I have loved" by Casey Muratori](https://www.youtube.com/watch?v=SDS5gLSiLg0)
+- [Package Managers are Evil by GingerBill](https://www.gingerbill.org/article/2025/09/08/package-managers-are-evil/#fnref:1)
+- [How to address binary compatibility on Linux](https://jangafx.com/insights/linux-binary-compatibility#containers)
+- [Mock Interview with Shawn McGrath](https://www.youtube.com/watch?v=cfyWvJdsDRI&t=5s) - Best way to do interviews
+- [Handmade Network "fishbowls"](https://handmade.network/fishbowl)
+
+Blogs:
+
 - [Casey Muratori's Blogs](https://caseymuratori.com/)
+- [Matklad's Blogs](https://matklad.github.io)
+- [Ryan Fleury blogs](https://www.rfleury.com/archive?sort=new)
+- [Bill Hall's (gingerBill) Blogs](https://www.gingerbill.org/article/)
+
+Data oriented design:
+
+- [CppCon 2014: Mike Acton "Data-Oriented Design and C++"](https://www.youtube.com/watch?v=rX0ItVEVjHc)
+- [Andrew Kelley: A Practical Guide to Applying Data Oriented Design (DoD)](https://www.youtube.com/watch?v=IroPQ150F6c)
 
 [^1] Unless u write your own OS, but even then, you'd be interfacing with hardware. and I assume you are not going to manufacture your own CPU.  
 [^2] Certain CPUs use 52-bit or 56-bit, because of some super computers hitting the 256TB limit (bruh)