-Off by default
-Asks you first directly
-It doesn't appear in the middle of the screen forcing you to choose if you want to continue
-"No" option and not "remind me later"
Another yacht for Gaben
Dmitry Suzdalev retweeted
A small UX detail I'm surprised hasn't caught on: new or moved clickable items should only become valid once the mouse moves again. If something suddenly moves underneath your mouse pointer and you click it by accident, the click shouldn't go through.
Dmitry Suzdalev retweeted
Zeiger Image Viewer version 0.3 is out! Full precision HDR and EXR with exposure controls, animated WebP, in-app updates, closed Linux alpha, and more!
links in the comments below
Dmitry Suzdalev retweeted
I had a similar reaction. Everyone should applaud performance improvements, but gauge against the “speed of light”, not just a sloppy competitor. If you are measuring in seconds, you may have already anchored yourself incorrectly.
Structure the UI so you can put locally cached media up just a few vblanks after the process launches.
Structure the server so it can return everything necessary for the dynamic UI in one single query that was kicked off in parallel with the Gfx API initialization, branching to a modern transport protocol for large media files.
You should be able to double click on the launcher and have it responsive before your muscle memory can slam the pointer to a location to click on.
This is hilarious and awesome.
Awesome because this has annoyed millions of peoples for years.
Hilarious because WHY DOES IT TAKE 5 SECONDS TO SHOW A MENU OF GAMES?!
Steam takes 10 SECONDS?!
Do you realize how much time that is for a CPU with a modern internet connection? Am I crazy!? What am I missing?
Dmitry Suzdalev retweeted
I hadn't seen this one before - someone on reddit posted this fantastic trick for creating shell "runnable" C files
Dmitry Suzdalev retweeted
9 am: i can’t wait till bedtime
10 pm: i’ve always wanted to write my own operating system
Dmitry Suzdalev retweeted
wise words from the best systems engineer I've worked with:
"two things that make code actually maintainable:
1. reduce the layers a reader has to trace
2. reduce the state a reader has to hold in their head"
applies to every codebase. always.
Dmitry Suzdalev retweeted
Jimmy Lefevre's talk is out! A walkthrough of all the regularities and oddities that go into shaping the text you see on your screen.
youtu.be/7Tr0ty9-yeQ
Dmitry Suzdalev retweeted
Hey, happy to announce that the RAD Debugger is now available for Linux (in alpha). It is early and preliminary! Expect random weirdnesses *for sure*, but it is ready to be played with!
github.com/EpicGames/raddebu…
Dmitry Suzdalev retweeted
A general piece of advice for not just programming but most other problem solving: always favour subtraction over addition. You should always try to get the job done by taking something away first, and only if that isn’t working resort to adding something new.
Dmitry Suzdalev retweeted
BREAKING: A non-mathematician lab employee used an UNRELEASED model to narrow the P vs. NP problem down to just TWO possible answers
Dmitry Suzdalev retweeted
Replying to @agriffini
My biggest gripe is that exceptions are fired deep inside low level code. You should not have error handling there. You should handle errors up front, before you put broken data in your data structure. You have lost track of who put the wrong data in the system if you find it later, and you can't give proper error messages and can't usually recover cleanly. And you spend a lot of CPU cycles in low level processing code checking for errors. Complexity covers the whole code base. That's a bad design. And it has hidden gotos all over the place. Super hard to reason about code bases like that.


























