Log inSign up
Log inSign up
LaurieWired
4,510 posts
LaurieWired profile banner
@lauriewired

LaurieWired

@lauriewired
researcher @google; serial complexity unpacker; youtube.com/@lauriewired ex @ msft & aerospace
somewhere in Protocol 7
linktr.ee/lauriewired
Joined January 2023
306 Following
165.1K Followers
RepliesRepliesRepostsRepostsMediaMediaArticlesArticles

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
  • Pinned
    @lauriewired
    LaurieWired
    @lauriewired
    Sep 29
    My CppCon Keynote, “The Address is Not The Place” is now up on YouTube! It’s not often that we get new tiers added to the memory hierarchy of computing, but it sure is fun! You can certainly get ahead of the curve by thinking about the programmatic challenges this will cause
    17
  • @lauriewired
    LaurieWired
    @lauriewired
    13h
    Stealing work isn’t a bad thing. In Computer Science, it can even be quite good. In 1995, MIT wanted to win the 8th World Computer Chess Championship…really badly. Somehow, they convinced Sandia National Laboratories to let them borrow Paragon, the world’s 2nd fastest
    17
  • @lauriewired
    LaurieWired
    @lauriewired
    Oct 5
    If you want to know who survives AI, look at what happened to Hollywood in the 1970s. Movie Studios used to enforce tight “shooting ratios”; usually 5:1, maybe 10:1 TOPS. As in, for every 5 feet of film shot, at least 1 foot had to end up in the final cut (35mm was expensive!)
    148
  • @lauriewired
    LaurieWired
    @lauriewired
    Oct 3
    The strongest “I’m living in the future” moment was the First Contact demo on the Oculus CV1 in ~2016 and I’ve been chasing it ever since. Yeah yeah we’ve got AI and self driving cars and stuff now, but it doesn’t hit the same. Shame that the space kind of fizzled out…but
    117
  • @lauriewired
    LaurieWired
    @lauriewired
    Oct 2
    The boom in Linux CVEs lately should get you thinking. Surely, given a finite codebase, there are also a finite number of bugs / unintended behavior, thus, a finite amount of vulnerabilities. Theoretically, a “solvable” problem. Right? Well…not at all actually. It gets a bit
    123