Tag Archives: SciTech

Science, technology (probably mostly around software development), various geekery.

The Thiel question

“What important truth do very few people agree with you on?”

Hashmaps are O(1). The number of people who don’t know this is astonishing.

Function documentation should include pre- and postconditions and invariants (since actual Design by Contract can be problematic due to side effects in call trees). I guess if you’re going to do real DBC, you should only access primitive data members without making function calls.

Logic does not belong in the database.

Caching is good. (Maybe these last two are indications that I’m not working at the right company.)

Developer documentation is worth the effort.

Slack (and MS Teams) is terrible. See above. Curation is worth the effort.

Long ‘switch’ statements are bad. Dispatch lookup tables are (probably) better.

Thread by @oulasvirta: “Rant: Nine reasons why I don’t believe in current VR/AR technology. HoloLens, Magic Leap, and Oculus: Mind-blowing videos, and the market is […]”

https://threadreaderapp.com/thread/1103298711382380545.html

Bomp, bomp, bomp. Another one bites the dust.

[I already retweeted this, but I forgot to add it to my blog.]

[Update: Sigh. Apparently, I did add it to my blog, but, for some reason, I didn’t think I had.]

On the Next Big Thing

https://twitter.com/Noahpinion/status/1104910913126055937?s=17

Noah Smith 🐇 (@Noahpinion) Tweeted:

That answer surprised me. What about AI? Self-driving cars? Robots?

He basically said that none of these things seemed to be working out that well. Self-driving cars had disappointed, AI gains seemed to peter out in most areas after an initial burst of progress…

https://threadreaderapp.com/thread/1104910381217046528.html

“Programming Sucks”

https://www.stilldrinking.org/programming-sucks

Can’t believe I never posted this to this blog.

« Every programmer occasionally, when nobody’s home, turns off the lights, pours a glass of scotch, puts on some light German electronica, and opens up a file on their computer. It’s a different file for every programmer. Sometimes they wrote it, sometimes they found it and knew they had to save it. They read over the lines, and weep at their beauty, then the tears turn bitter as they remember the rest of the files and the inevitable collapse of all that is good and true in the world.

This file is Good Code. It has sensible and consistent names for functions and variables. It’s concise. It doesn’t do anything obviously stupid. It has never had to live in the wild, or answer to a sales team. It does exactly one, mundane, specific thing, and it does it well. It was written by a single person, and never touched by another. It reads like poetry written by someone over thirty.»