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
Vrijeme pridruživanja: ožujak 2010.

Tweetovi

Blokirali ste korisnika/cu @codeviking

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @codeviking

  1. proslijedio/la je Tweet
    prije 15 sati

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

    Poništi
  2. 30. sij

    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.

    Poništi
  3. 24. sij

    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.

    Poništi
  4. proslijedio/la je Tweet
    16. sij

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

    Poništi
  5. proslijedio/la je Tweet
    15. sij

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

    Poništi
  6. 15. sij

    Regardless, is a very powerful tool. Well done!

    Prikaži ovu nit
    Poništi
  7. 15. sij

    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?

    Prikaži ovu nit
    Poništi
  8. 15. sij

    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).

    Prikaži ovu nit
    Poništi
  9. 15. sij

    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.

    Prikaži ovu nit
    Poništi
  10. 15. sij

    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).

    Prikaži ovu nit
    Poništi
  11. 15. sij

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

    Prikaži ovu nit
    Poništi
  12. 15. sij

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

    Prikaži ovu nit
    Poništi
  13. 15. sij

    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`.

    Prikaži ovu nit
    Poništi
  14. 14. sij

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

    Prikaži ovu nit
    Poništi
  15. 14. sij

    Forcing me to use a homegrown DSL for doing so isn't terribly user-friendly. I'd suggest adding a simple UI that at the very least allows one to export one content type into another environment.

    Prikaži ovu nit
    Poništi
  16. 14. sij

    If you follow me on Spotify, you should just follow (and listen to ), as they're the source of any music I discover.

    Poništi
  17. 14. sij

    I often "brute force" a solution, then rewrite it....and then rewrite it again. This iterative process is one I've landed on as an effective way to write (what I consider to be) high quality code.

    Prikaži ovu nit
    Poništi
  18. 14. sij

    On the other hand, when I code quickly I generally arrive at small, simple and clean abstractions. Moving fast allows for faster feedback loops, which either clarify the problem I'm solving or the path to the solution.

    Prikaži ovu nit
    Poništi
  19. 14. sij

    In my career I've found that when I spend a lot of time up front trying to think through an abstraction, I usually get it wrong. The code that results is unintuitive and clunky.

    Prikaži ovu nit
    Poništi
  20. 14. sij

    I take issue with the term "tactical tornado". I write code quickly, but don't feel I leave a "wake of destruction" behind me. In fact, I think the term itself is harmful in that it discourages something I find to be immensely important when writing code.

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·