🕵️‍♂️ How Google's PageRank algorithm works

A thread on HN about bad code in legacy projects both makes me think how little we've learned as a discipline over the years and, honestly, how little credit we give ourselves for some pretty major

Fun going down this list and thinking: "Hmm, plausible at a well-run modern software shop", "Hmm, possible, but requires implausible tradeoffs", "Literally disallowed by languages", and "If you were to attempt doing that our test suite wouldn't let you merge."

I think we as an industry celebrate (not quite the right word) failure too much and don't celebrate success nearly enough. There is no DailyWTF for competent execution, word of which generally stays pretty local to the source while incompetence passes into legend.

Alrighty let me try to thread the needle on being the change I want to see in the world while not giving away anything that will get me in trouble:

Ruby has wonderful developer ergonomics. Typed languages are easier for machines to guarantee the correctness of. We built a type checker for Ruby (and I believe it is slated for OSS release sometime).

c.f.

Two years ago on a weekend, I built a tool to make it easier to evaluate Twitter accounts. Since then 36590 people used it to analyze 55390 different Twitter accounts.

Over the last months @mmkaradeniz and I made a new version. We launched it last night:

@accountanalysis doesn't use machine learning or AI „magic“. Instead of telling users if an account is authentic or not, it helps them to evaluate the accounts themselves.

It visualizes the different features (date, time, type, app, etc.) of Tweets to make them interpretable. /1

@accountanalysis The core concept is still the same, but it looks much better and is easier to operate. Not only for the users, but us developers as well. Enabling us to continuously roll out new features in the future.

Side-by-side screenshots of the old and new version. /2

@accountanalysis Some people had questions what different charts displayed and how they could be interpreted. There are now explanations for all charts, that can be toggled on and off at any time. /3

@accountanalysis The selected/retrieved Tweet count moved to the top to make it clear that not all Tweets of an account are analyzed. 3200 is the API limit by Twitter. It's possible to get more through the Premium API, but I don't think people would pay $100+ for the analysis of one account. /4

A thread about Eastshade's bike mechanic!

When I originally thought of putting a bicycling in Eastshade, I was pretty sure it wasn't going to work, for the simple fact that if it was easy, we'd see a lot more rideable bikes in games. Well, I was wrong. It took a mere week.

Its essentially a first person controller with extra momentum, resulting in the the movement direction lagging behind your look direction. Then I used the angle between the look and the movement to dictate camera "bank" and handle bar rotation, and voila! Game changing feature!

The look of the bike was harder than the movement. Bicycles are fairly modern, so it was tricky to fit it to the setting. I took some artistic liberties and settled on a penny farthing (but wooden), ignoring how impossible that would be to ride on the rugged terrain in Eastshade.

Surprisingly, the hardest part was sound. It didn't feel like riding a bike until I found the right sounds and how to trigger them. For a while I was stuck thinking too realistically. A penny farthing is fixed gear, pedaling sounds nothing like a regular modern bike.

Finally I abandoned realism and went with sounds normal people would associate with biking. We're all so used to modern bikes that we strongly associate the distinct ticking of a freewheel mechanism (think of the sound when you stop pedaling and coast on a modern bike).