jankins

When I broke my collarbone on my dominant arm I learned Dvorak left-handed layout a QMK keyboard. I configured some layers to make all the symbols needed for programming easy to access, and hold-space-for-shift. I learned the layout using Epistory, a typing game. There’s several similar games now that look helpful. It was slower but workable.

A braille embosser is pretty much the soundtrack to my childhood (along with the dectalk pronouncing “c colon backslash greater-than”). My dad is blind and I’m so appreciative of the technologies that helped him succeed alongside his sighted colleagues. I also credit his love of technology for my own career.

> not a really winnable game

It’s totally winnable! The player almost always has a chance to avoid death. Deaths are usually due to missing knowledge or laziness/impatience. The knowledge is really really hard to gain without wikis, and I absolutely wouldn’t have ascended without wikis, but reading them added another layer of fun for me.

Your phrase “discussing sexual content” strikes me as really odd. If you discuss a “traditional” relationship with a 5 year old, you’re already discussing sexual content on the same level & terms that you would use if you were talking about sexual orientation and gender identity.

This seems like a leap. Admin has increased 45% in the same time faculty has increased 56%. And the timeframe is 20 years. Is there too much bureaucracy? I don’t know. But I don’t think this article is enough to say so. The faculty quotes don’t offer any concrete information, unless you’ve already decided what you’re going to believe, I guess.

There’s a dead comment with a negative take about the YouTube comments being turned off, and I just wanted to point out - the conf is hosted in a really cool custom real-time conference mud, built by em lazer-walker. It’s a fun thing that is worth checking out

Any mathematical instruction I have found helpful has had a big emphasis on building “intuition“. This post was the first explanation I encountered that explained floating point encoding in a way that was immediately relatable and understandable to me. There are multiple ways to describe a thing, different people have different relationships to a thing which may make some descriptions more well-suited than others, and different people have different goals.

Such a good writer. His Wolfenstein book had the best explanation I’ve ever seen for how floating point numbers are encoded, and that explanation is in the first several pages. If you don’t have an understanding of floating point encoding, that alone is worth the purchase price.

My first thought was terminating SSL at a proxy or using sslstrip with a VPN or something - I feel like there’s definitely a way to do what he wants. Each option might come with some UX cost though.

At the same time, I’d have to Google to figure it out, and I’d want to see if I could optimize for viewing new pages. I think optimizing new pages could also be really important for learning to code. Maybe mosh into a server with a fast, reliable connection and then use that server to access the web with lynx. The idea being that less data would need to be transferred between the mosh client and server than between the mosh server and website. I would suppose that every interaction like scrolling down would have some latency, but new page requests would have less latency. I’m not sure if bandwidth usage and latency would be good enough for their circumstances though.

This is my favorite Swift gotcha :D

This bug bit me one time back before remote debugging came out when I was developing an app for a device that plugged into the lightning port. The only way to debug was to send log messages over the network to a log server running on my laptop, and the connected device sent messages to satellites where there was often a 10-minute gap in connectivity. And I couldn’t reproduce it in tests. That took some time to diagnose!

I like to bring this issue up if an interview candidate seems extremely bought in to protocol-driven development. I wouldn’t be surprised if any level of dev wasn’t aware of it, but would be impressed if anybody identified it.

> You can make `rustc` happy by following suggestions, but may end up puzzled as to the reasons for the changes it suggests.

This is how I felt, but it wasn't bad: I think you start to pick up on the patterns. In other words, learning isn't short-circuited after you've made rustc happy, even though you're still a bit puzzled - you'll carry the experience along with you and continue to learn from it later.