Sabitlenmiş Tweet
Victor :)
15.7K posts

Victor :)
@VictorieeMan
Engineering & Maths apprentice, who likes winning and helping others to do the same. Victoriee for us all! #bitcoin⚡[email protected]
victoriee.eth Katılım Ekim 2019
95 Takip Edilen286 Takipçiler
Victor :) retweetledi
Victor :) retweetledi

@kristinatastic Can’t decide if I’m more impressed with “1960” or “€6.10” 🤯
English

@kristinatastic Euro didn't exist back then. But if you inflation adjust the original Swedish price from 65 sek to today you get 900 sek which is about 85 euro today
English
Victor :) retweetledi

@RetroMoviesDB Indiana Jones are just three movies; not really a Triology parted story
English

@Elizabeth_eno2 "Tell them about Digital ID, my king" - Grima Wormtounge Starmer
English

Britains political system in a picture:

GB Politics@GBPolitcs
🚨NEW: King Charles: "My ministers will also proceed with the introduction of Digital ID."
English
Victor :) retweetledi
Victor :) retweetledi

Reasons to continue working past reaching financial goals for retirement:
1. Your career is on coast mode - that is you did all the hard work and now are reaping the rewards, because of seniority, indispensability, practice and familiarity
2. You are working on super important World changing stuff and so need to continue until it is done
3. Maintain status in the eyes of pe4ers, friends, family, and yourself
4. Accumulate more wealth (than you need ) to pass on to your children
5. Just cant quit because of habit and lack of other purpose in life
If none of the above apply, please retire and let the younger generation fill your position.
English
Victor :) retweetledi
Victor :) retweetledi
Victor :) retweetledi

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.

English
Victor :) retweetledi




















