Sam Skjonsberg

@codeviking

Software engineer located in the PNW ☕️. When I'm not at my laptop you'll find me enjoying a cup of coffee or adventuring with my wife and two dogs.

Seattle, WA
Joined March 2010

Tweets

You blocked @codeviking

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @codeviking

  1. Retweeted
    18 hours ago

    How to tell if a humanity-destroying AI could be around the corner? I reframe the perennial debate regarding superintelligence in empirical terms:

    Undo
  2. Feb 19

    There’s something to be said for seeing the sun both rise and set.

    Undo
  3. Feb 18

    Wow indeed. I have to say, while reading this I felt nothing but gratitude and appreciation for how lucky I am to work at AI2. We're truly an open research institute, everything we do is shared in great detail in papers, demos, complementary content, and more...

    Undo
  4. Retweeted
    Feb 13

    Announcing the AI2 Computer Vision Explorer! This new tool from is a collection of demos of popular and state-of-the-art models for a variety of tasks - try, compare, and evaluate, using our images or your own!

    Undo
  5. Retweeted
    Feb 11

    Congratulations to , , , & of the AI2 MOSAIC team for this fantastic recognition of their WinoGrande paper at !

    Undo
  6. Retweeted
    Feb 9

    Come work with me to prototype cutting-edge AI systems. It's a sprint, not a marathon: (please RT)

    Undo
  7. Retweeted
    Feb 4

    Univ. of Washington President Ana Mari Cauce joins AI2’s board to build on Paul Allen’s legacy via

    Undo
  8. Jan 30

    I share the concerns expressed by the community about how different Yarn 2 is from NPM. I realize there's some problems that it solves, but the easy interop between the two was a key value proposition for me.

    Undo
  9. Jan 24

    Yikes. I couldn’t help feeling like something was wrong the first time I encountered the new design. My brain was hard coded to the former UI.

    Undo
  10. Retweeted
    Jan 16

    An unprecedented partnership to seed Seattle startups: , , and fund the incubator. Join us!

    Undo
  11. Retweeted
    Jan 15

    Exclusive: Apple acquires , edge AI spin-out from Paul Allen’s AI2, for price in $200M range

    Undo
  12. Jan 15

    Regardless, is a very powerful tool. Well done!

    Show this thread
    Undo
  13. Jan 15

    Would love to know how other users handle this, and what and co are thinking here. Maybe there's some improvements or changes coming, or there's a pattern I'm not finding?

    Show this thread
    Undo
  14. Jan 15

    But the resulting code feels clunky, and has to repeated wherever we use getInitialProps. This seems like a regression from the "good old days" of editing the `500.html` template in one's web server of choice (nginx and/or apache being two of my favorites).

    Show this thread
    Undo
  15. Jan 15

    The examples I see all point to doing this by conditionally setting status codes in `getInitialProps` provided `ctx.res` exists AND by returning properties that tell the component UI to render the error page.

    Show this thread
    Undo
  16. Jan 15

    On the client we likely want to display the same error page w/o modifying the URL, and for bonus points, phone home somehow so we know about the error (this, of course, is likely best handled by something like Sentry).

    Show this thread
    Undo
  17. Jan 15

    On a server we want to issue a canonical HTTP response. For instance, a 500 page that's branded and helps maintain user trust.

    Show this thread
    Undo
  18. Jan 15

    It's a tricky problem, given the method might be executed on the client or server, where one would handle errors differently.

    Show this thread
    Undo
  19. Jan 15

    We've had good luck using NextJS , and are expanding our use of it. That said we can't seem to land on an effective pattern for handling errors in `getInitialProps`.

    Show this thread
    Undo
  20. Jan 14

    Maybe this feature already exists, and it's just not easy to find?

    Show this thread
    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·