self

Forever junior engineer. now in stealth startup, ex-@bytedance. Thought and opinions all mine!

[Ben Vinegar @bentlegen]

🇨🇦 Painful to remember many PCs from this era were using Canadian GPUs:

- ATI Radeon (ATI was acquired by AMD in 2006, who still employs 1,600 people in Markham, ON)

- Matrox G-series (Matrox is still around, but focuses on niche graphics cards)

What might have have been …

[Matei Zaharia @matei_zaharia]

Really excited to open source a new project: Omnigent, a meta-harness for AI agents.

It lets you build multi-agent coding and custom agents, sitting above Claude Code, Codex, Pi, and agent SDKs to let you compose them. It also adds live collaboration and rich control policies.

[Ideogram @ideogram_ai]

Introducing Ideogram 4.0: the best open image model in the world.

Think it. Make it. Own it.

Download the weights, fine-tune on your own data, and run it on your hardware. Live on every Ideogram plan and the API today.

[Ryan Dahl @rough__sea]

This has been said a thousand times before, but allow me to add my own voice: the era of humans writing code is over. Disturbing for those of us who identify as SWEs, but no less true. That's not to say SWEs don't have work to do, but writing syntax directly is not it.

[Keycard @KeycardLabs]

The full episode of the MCP Debate at @aidotengineer has dropped!

Listen to hot takes from @ianlivingstone and @dexhorthy as they dig into MCP, agentic workflows, tool bloat, and the future of the agentic web.

https://t.co/fe6wjNMPCx

[Gergely Orosz @GergelyOrosz]

The only two Big Tech companies that neither did mass layoffs when business was booming, nor when things looked bleak:

Apple** and NVIDIA

All others (Amazon, Google, Meta) did (and do) mass cuts as business is booming. Corporate reality

**Apple not since 1997 that is

[Matt Hobbs (@[email protected]) @TheRealNooshu]

🧵As I mentioned last week https://t.co/CcU3PLPTpj removed jQuery as a dependency for all frontend apps, meaning 32 KB of minified & compressed JS was removed. So let's see what difference this has made for users by examining our RUM data. Thread will mainly focus on JS CPU time.

[Devon Govett @devongovett]

How to write fast code: reduce memory access. All of these tips stem from that:

1. Reduce the size of your data structures so more can fit in CPU cache.
2. Replace strings with numbers.
3. Make use of bit flags. Don’t waste space on booleans.
4. Access memory linearly.

[Ben See @ClimateBen]

Global warming’s threat to the food supply is seen as far more pressing by many scientists than the melting glaciers and rising sea levels that occasionally grab the headlines. 🧵

[Well Paid Geek 🚀💻 JavaScript @WellPaidGeek]

Non coding skills the professional coders need:

* Requirements analysis
* Communication with management
* Ability to review others code well

[Lillian Li @lillianmli]

1) With Russia being partly blocked from the SWIFT international payments system.

All eyes (in the Chinese financial system) are on the Chinese clearing and settlement system CIPS.

A primer on what it is and potential implications for the future of dollar hegemony:

[Lucas Ou-Yang @LucasOuYang]

Ever since I've started working at #Tiktok 1 year ago many friends r curious about what it's like at a Chinese company and the differences vs American tech

This question is more important as Chinese tech companies have become increasingly
competitive and relevant globally

[Tetrate @Tetrateio]

It’s here!! The best place on the web to learn the fundamentals of Envoy. Take the free @Envoyproxy certification course at Tetrate Academy. Complete with:

✅ Labs
✅ Modules
✅ Quizzes

Sign up here: https://t.co/gr7ykX9zo7

#servicemesh #cloudnative

[Patrick McKenzie @patio11]

A thing I would also probably do, if I were making engineering decisions again: all shipping products of company have two options for APIs:

a) /private/ namespace
b) it’s a real endpoint customers could call themselves with real docs, real support, real deprecation, etc

[Swizec Teller @Swizec]

Today is my birthday which means I've been coding for 25 years. A quarter century 😱

Here's 25 lessons I've learned about code. In no particular order. 👇

[Corey Quinn @QuinnyPig]

So an anonymous Twitter person DM'd me this morning with a scenario. "I work at a large cloud company that makes inscrutable naming decisions, and I have an offer elsewhere for 35% more. Should I take it?"

Oh good heavens yes. A thread...

[Simon Wardley @swardley]

At this point, I'll dig up some old favourites ... starting with ...

[Amelia Wattenberger 🪷 @Wattenberger]

We just released an exploration I've been wanting to do for a while:

✨✨
Can we visualize a codebase?
✨✨

We always look at our code in a file/folder list - what would a bird's-eye-view look like, and how could that enhance our understanding of code?

https://t.co/dFpdoWtxyJ

[self @chesireCode]

@sarah_edo Love this viz! Does the book have a section on how to explain things better? The graph certainly does!

[self @chesireCode]

@shreyas Thanks for sharing! I love this point about people in particular, and (6) too. Herein lies the challenge, we don't really know about our potential co-workers until we join.

Aside from knowing someone inside whose judgement we can trust, I'm not sure how we can find out publicly.