@ThePrimeagen I remember time when he was pushing for real OOP: everything is object, that's the only right way to program. Like going to conferences and pitching it from the scene. Now he's just on a new thing.
I've been coding for 40 years. Here are the top 5 things I wish I knew when I started.
1. 90% of the job is debugging and fixing, not creating new code. Which is still fun if you're good at it.
I used to think programming was mostly writing fresh, clever stuff. In reality, most of your time is spent in other people's (or your own past self's) messy code, chasing down why something that "should" work doesn't. Get really good at debugging early. Learn assembly reading, call stacks, and kernel debuggers. It pays off hugely. The best engineers I saw were absolute magicians at this.
2. Manage complexity from day one (ie: don't write slop and "fix it later" if it goes somewhere).
Very early on, I'd hammer out code and refactor afterward. Big mistake. Now I start with clean, skeletal structure (minimalism first) and flesh it out carefully, with AI or not.
Messy code compounds and becomes unfixable. Upfront discipline on architecture, naming, and simplicity saves enormous pain later, especially in large systems like Windows.
3. Tools and processes matter more than you think
We suffered with basic diff/manual deltas instead of modern source control like Git. Branching, testing, and good tooling would have made porting and collaboration way smoother. Invest in your environment, automation, and reproducible builds early. Good tools amplify your output; bad ones (or none) drag everything down.
4. Understand the problem and existing code deeply before writing
Don't jump straight to coding. Map out the problem, study what's already there (you'll inherit a lot), and plan. Low-level knowledge (hardware quirks, alignment issues on different architectures like MIPS/Alpha) was crucial. Also: assert early and often. It forces clarity.
5. People, politics, and "the right tool for the job" beat pure tech arguments.
Brilliant engineers still argue endlessly. Sometimes it's about ego, not merit. Learn to spot the difference and "steer" the conversation rather than "winning" it.
Bonus from experience: Side projects like Task Manager (started at home because I wanted the tool) can become your biggest hits. Ship small, useful things often. If you're just starting, focus on fundamentals, patterns over syntax, and building resilience for the long haul. It's going to be a wild ride, but the fundamentals still matter.
It's been 3 months since the 100x vibers started 100x vibin'! So, post your 25-years-of-work-equivalent project here, so we can signal boost and everyone can celebrate the Life's Work that you did in 3 months. Looking forward to it, Let's Go!!!
LLM hallucination is just math fitting a smooth curve and producing the most likely continuation. It’s matrix multiplication, so it will always output something that maps to a language object. None of this has anything to do with consciousness.
Whenever humans invent a new tech - from fire to writing to steam engines - we project god onto it and use it to explain things we don’t yet understand - for eg consciousness.
> be me, applied scientist at amazon
> spend 6 months building ML model that actually works
> ready to ship
> manager asks "but does it Dive Deep?"
> show him 37 pages of technical documentation
> "that's great anon, but what about Customer Obsession?"
> model literally convinces customers to buy more stuff they don't need
> "okay but are you thinking Big Enough?"
> mfw I am literally increasing sales
> okay lets ship it
> PM says there's not enough Disagree and Commit
> we need to disagree about something
> team spends 2 hours debating whether the config file should be YAML or JSON
> engineering insists on XML "for backwards compatibility"
> what backwards compatibility, this is a new service
> doesn't matter, we disagree and commit to XML
> finally get approval to deploy
> "make sure you're frugal with the compute costs"
> model runs on a potato, costs $2/month
> finance still wants a cost breakdown
> write 6-pager about why we need $2/month
> include bar raiser in the review
> bar raiser asks "but can we do it for $1.50? we need to be Frugal"
> spend another month optimizing to hit $1.50
> ready to deploy again
> VP decides we need to "Invent and Simplify"
> requests we rebuild the entire thing using a new framework
> framework doesn't exist yet
> "show some Ownership and build it yourself"
> 3 months later, framework is half done
> org restructure happens
> new manager says this doesn't align with team goals anymore
> project cancelled
> model never ships
> manager gets promoted to L8 for "successfully reallocating resources"
> team celebrates with 6-pager retrospective about what we learned
> mfw we delivered on all 16 leadership principles
> mfw we delivered nothing else
> amazon.jpg
Am trying to get coredns working on Ubuntu, need to vent off: I hate k8s and systemd evil spawns such as resolvectl with a passion. Whatever these developers grew up with, it wasn't Unix. Logs without timestamps, some special commands to view logs, things stop working randomly...
@GeorgeGwiazda@Ch0ux@escidiqui I think the abundance of measure words in Chinese is there to counter misunderstanding caused by many nouns having the same syllables, the measure words provide more context. It'd be hard to understand what a 'shi' means if there were only 个
@cajun_exile @LindasGamingCo1 @JeffFisch Oh yes, maps, wonderful invention. Have a look at one and measure distance between Chukotka (Russia) and Alaska (USA). What is it? 50 miles?