driggy

Senior Software Engineer at Nordeus ( @[email protected]

[driggy @igorst]

Finally decided to start my own blog where I can dump my thoughts. Mostly #csharp and #zig topics for now: https://t.co/Ph2OrDfFFg

[Łukasz | Wookash Podcast @wookash_podcast]

RADDBG has so much inbuilt cool visualisations and features that lots of debuggers lack, it's mindblowing.

@rfleury walks me through how to get the most out of it

https://t.co/1FZbxe3LBH

[Casey Muratori @cmuratori]

One of the things I would love to see from PC monitor reviewers is benchmarks for how long it takes to start using the monitor. How long does it take to come back from sleep? How long does it take to switch inputs? I feel like some of the lag here has gotten unacceptably long.

[Top Eleven @topeleven]

16 years ago, our journey started...
Since then, there have been millions of matches played, trophies lifted, rivalries born, alarms set for transfers, hearts broken in stoppage time… and memories made - together. 💙

That wouldn’t be possible without you, Managers.
To celebrate everything we built together, birthday gifts are waiting for you in-game.🎁

And the Golden 16 celebration is still going strong, with more challenges, more goals, and more rewards ahead.
This squad is 16 years old now, but it still feels like we're just getting started!
Thank you for playing Top Eleven!

[John Crickett @johncrickett]

"Nobody reviews compiler output, why review AI code?"

Wrong. We do review compiler output. Godbolt exists. Disassemblers exist. Anyone doing serious performance work reads what the compiler produced. The premise is false.

But the analogy itself is flawed. It compares two things that aren't comparable.

A compiler takes a formal language as input. Languages with grammars and semantics defined precisely enough that "what does this code mean" has only one answer.

An LLM takes natural language as input. Natural languages are ambiguous. "Write me a function that handles user input safely" has a thousand valid interpretations and a thousand more invalid ones. The LLM picks one. You don't know which. Unless you look at the code.

Compilers are built from specifications and designed to meet them. The output is the result of a defined translation. When the output violates the spec, it's a bug.

LLMs are built from whatever was in their training data. There is no spec. There can't be one, natural languages have no defined semantics that map to code.

Compilers are semantically deterministic. The same input produces output with the same behaviour, every time. LLMs are not. Partly by design and partly due to hardware variance, batch size, inference order, and floating point operations (and no setting temperature to zero does not address those). All of which can push the same prompt to produce different code.

Compilers complain loudly when the input is nonsensical. LLMs fail silently, producing plausible-looking, but wrong code.

We trust compiler output because the trust was earned across decades of use, with millions of engineers using the same tools. Early compilers were reviewed heavily. Hand-written assembly was the default because trust hadn't been earned yet.

We're at the hand-written assembly stage with AI. We may never get to the trust-the-output stage for the reasons explained above.

If you’re a software developer, you should own what goes to production. The compiler analogy is a way of skipping that responsibility.

[Ryan Fleury @rfleury]

I’m hoping this to be true. Once the format is more stable, and once we have better tool coverage (remote/dump debugging, crash reporters, etc.), I think it’ll be doable to start with an LLVM patch, such that Clang/lld can begin natively producing RDI. Unlikely to ever happen with MSVC, but we can at least replace the linker there, and produce it natively that way.

[driggy @igorst]

@EricLengyel OMG! This is huge! Thank you very very much 😊

[Ritesh Oedayrajsingh Varma @rovarma]

New article! A user is reporting full system freezes while using Superluminal on Linux. What do you do? Cry? Well, we did a little bit.

But we also dove into the kernel...again, fixing several issues in eBPF's spinlock implementation. Read all about it:

https://t.co/HHAyGdnZYZ

[Ryan Fleury @rfleury]

“native has nothing to offer”

No, you’ve just either never bothered to seriously try it, or you just suck.

[Nordeus @Nordeus]

We’re hiring at Nordeus! 🙌

🚀Open positions:

👉Client Engineer (Game Team)
👉Senior Backend Engineer
👉Social Media Intern (Games)
👉Data Scientist

Check out our careers page!
https://t.co/7x8qBMIfAw

[Nordeus @Nordeus]

Last week, we had the pleasure of welcoming Strauss Zelnick, CEO of Take-Two Interactive, to Nordeus.

With a full auditorium at Nordeus, Branko and Strauss sat down for a traditional fireside chat. We discussed the state of the industry, the future of AI, and our shared approach to building hit games played by millions. 📲

Strauss also took questions from the audience, but one exchange stood out: “What’s one question leaders should ask themselves more often?”.
His answer was simple “What value did I add to my team this week?” - a key takeaway that stayed with us.

Everyone left the conversation encouraged and proud, with a renewed focus on building teams and moving the needle of our games! 🙌

[driggy @igorst]

@TheGingerBill while when I see a cast I see type specified for an expression on its left. I am not saying your choice is bad because of it, just that I don't see it as consistent in this regard. 2/2

[driggy @igorst]

@TheGingerBill Thank you very much for this great post! Just to add my 2 cents. You said "the type must be on the left of the expression since that is how declarations work too" but when i see declaration I see type being specified for a variable on its right 1/2

[driggy @igorst]

Just started thinking about some problem and my brain went: I can just ask #AI about it. But then it hit me. How long until the problem solving parts of my brain just atrophy because I just give up every time? 😱

[Nordeus @Nordeus]

Last week in London, Nordeus won the award for Best Employer Website at @TheRADawards !

#TheRADAwards are known as the #Oscars of the industry, celebrating excellence in employer branding and communications for over three decades (36 to be exact 🙌).
This year's edition was 🎤 hosted by the phenomenal Claudia Winkleman.

This recognition belongs to everyone at Nordeus. ✨Thank you to all of our teams for bringing it to life.

P.S. This year, we were honored to be recognized alongside an incredible lineup of finalists, including websites from the @LEGO_Group , @sanofi , @DiageoEU , @Primark , @WilliamsF1 , @Arm , @nationalgrid , @CoxEnterprises , and Leeds Building Society making this win even more special!

[Nordeus @Nordeus]

Real impact happens when knowledge is shared, and when schools are treated as living spaces for growth - for students and teachers alike. 🎓

Nordeus team members saw firsthand that supporting education goes far beyond opening doors or donating equipment.

Through Makers Labs and the @NFondacija , we continue to invest in high-school education 🎒as we believe the future isn’t built in isolation.
It’s built through trust, long-term commitment, and people who actively show up for the next generation! 🙌

[Mike Turitzin @miketuritzin]

I just released my video about the engine (and game) I've been working on.

The engine is based on dynamic SDFs, and the video describes how it works and what it makes possible.

Link in the reply!

This is my first YouTube video and it took forever - please repost!

[Ryan C. Gordon @icculus]

Start the new year with a really big SDL3 release! 3.4.0 finally shipped, before the stroke of midnight! https://t.co/LPThLN98y2

[Sebastian Aaltonen @SebAaltonen]

My "No Graphics API" blog post is live! Please repost :)

https://t.co/uL8HsfIlNV

[Nordeus @Nordeus]

When something runs 250,000+ times, even 1% matters, and a 29× speed-up changes everything.

Our newest engineering blog post 👉 “From 30s to 1.2s: Speeding Up Resource List Rebuilds by 29×,” is live!

This deep dive by our Junior Software Engineer, Petar Mihajlović, breaks down how we optimized one of our core #Unity workflows - the Resource List rebuild.

If you’ve ever worked with large Unity projects, you know the pain.
Read the full blogpost here: https://t.co/ePN1Trzy8P

[Justin Elze @HackingLZ]

For those going home to visit family this weekend:

• Samsung calls it Auto Motion Plus
• LG calls it TruMotion
• Sony calls it Motionflow
• Roku calls it Action Smoothing
• Google TV calls it Motion Enhancement
• Vizio calls it Smooth Motion Effect.