Michal Klos

R&D, Pixels, Applied ML, Demoscene. ex-ByteDance/TikTok AI Lab. ex-games. Opinions are my own.

[Michal Klos @_spolsh]

2nd place in 4K PC Executable Gfx, thank you! Cheers to @deadlineBER for the awesome party!
https://t.co/ItnWyyzUje

Congrats to Timbrhoggvandi with Forg for the 1st place

#demoscene

[Michal Klos @_spolsh]

@boulabiar I recently optimized wasm target for a Rust project. 2/3 are bindings filler and std. To go lower I'd need to write gpu backend myself
https://t.co/VV9IepJ66u

[Michal Klos @_spolsh]

@debamitro @ChShersh Ever heard about WAT talk? classic :)
https://t.co/lG7gQWMo4V

[Son Luong @sluongng]

Codex just found a “workaround” of not having sudo on my pc…

[Michal Klos @_spolsh]

I optimized Pill Engine wasm binary to bellow 500kb, less than ThreeJS. Interested in details?
https://t.co/VV9IepJ66u

[Michal Klos @_spolsh]

@vaxryy @lcamtuf has a solution for you

[Dave W Plummer @davepl1968]

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.

[Michal Klos @_spolsh]

wasm was merged https://t.co/2vI7LAh5aV

[Michal Klos @_spolsh]

Pill Engine can into wasm and WebGPU. The binary out of the box is 5mb, way too large
https://t.co/5sCcxdh8Ds

[Michal Klos @_spolsh]

@pshufb F

[Michal Klos @_spolsh]

@SebAaltonen Main point in my rules file is: Evidence then claim.
So a test code, diagnostic numbers or at least docs.

[Michal Klos @_spolsh]

@stefan_3d @LundukeJournal 25 years since the article and counting and still relevant today. Meanwhile a new generation of developers arrived

[Michal Klos @_spolsh]

@designworkplan @cory https://t.co/Ok8KF8bwvm

[Michal Klos @_spolsh]

@designworkplan @cory See Project PIWO PWr, Wroclaw, PL - clever control over lightbulbs in each building room and an annual show during University concert celebration

[Michal Klos @_spolsh]

@valigo I know polish, easy.
Now German vs enterprise java please.

[Michal Klos @_spolsh]

@SebAaltonen @jmbynx BMW is better for shitposting economy ;)

[Michal Klos @_spolsh]

@svadrb AI Agent automation that iterates on a problem with a simplified bruteforce methodology.
> You need a goal, a metric, and a loop that never quits.

https://t.co/B1WJHKq8dy

[Michal Klos @_spolsh]

@tanujDE3180 @SebAaltonen TBH this question baits Bloom filter answer to the point it kills creative problem solving skills Google would seek.

[Michal Klos @_spolsh]

@memecrashes Cool command, I didn't know it's on macs too

[Michal Klos @_spolsh]

The subpixel rendering was so delicious on the big party screen. Well done, my personal party favorite!

[Natt Akuma(ナット)🛠️ @akumanatt]

That's right! We went beyond the LCD pixels of the GBA for the wild compo! My recently bought DS Lite finally had a good use.
Full video at my channel https://t.co/kmfX4Us4LM

[Michal Klos @_spolsh]

@SebAaltonen True and not true - more time and better product usually corelate, BUT 1 day ugly app marketed to correct community may win validation with 1 year app kept in the basement