William Yao

@williamyaoh

Software Engineer. Formerly at , . I push around lambdas.

Minneapolis, MN
Vrijeme pridruživanja: veljača 2018.

Tweetovi

Blokirali ste korisnika/cu @williamyaoh

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

  1. Prikvačeni tweet
    2. srp 2018.

    When you fuck up in life, you'll probably be confronted by an uncomfortable fact that you're not as good a person as you think you are. That's okay. That's normal. It's a part of being human, and accepting it and working to improve how you behave is how you grow up.

    Prikaži ovu nit
    Poništi
  2. proslijedio/la je Tweet
    20. sij

    New release is out, bringing bug fixes and support for (unsafe) raw sql fragments. Get it while it's hot!

    Poništi
  3. proslijedio/la je Tweet
    19. sij

    I’m pleased to present the flame-bait sequel to my previous blog post: “No, dynamic type systems are not inherently more open.” (Please send me your hatemail at your earliest convenience.)

    Poništi
  4. 11. sij

    i just realized that the three musketeers of typeclasses - Functor, Applicative, Monad - spells out FAM that's almost too perfect my FAM got me you gotta learn about your FAM the jokes just write themselves

    Poništi
  5. 11. sij

    A checklist for becoming proficient at Haskell, along with advice, learning resources, and exercises

    Poništi
  6. 11. sij

    For those coming from other languages: what specific problems are you getting stuck on? Don't worry if it's too trivial: it can be something as small as not knowing how to have a list with both Ints and Bools in it, or fighting with indentation /4

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

    A blanket injunction to "throw away everything you've learned about programming" seems less useful to me than figuring out exactly what ends up being most confusing to, say, a Java or PHP programmer, and *teaching that*. /3

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

    I don't see people asking questions about what the :: in function signatures means, for instance. I don't see people getting stuck on what basic constraints like Eq and Ord mean. I see a lot about managing state. So clearly some spots are more troublesome than others. /2

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

    I don't think it's controversial to say that people coming from imperative/OO tend to need to 'unlearn' when they come to FP. What I'd like to know is specifically *what* they need to unlearn. Not a lot of people seem to be trying to figure that out. /1

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

    Would y'all like to see something like this, but for going from proficient to "advanced", whatever that means?

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

    Some things I'd add are getting comfortable with defining your own datatypes, especially sum types; and getting comfortable with pattern matching

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

    This is a *really* good checklist for going from zero to proficient at Haskell

    Prikaži ovu nit
    Poništi
  13. proslijedio/la je Tweet
    6. sij

    my hell in 2020 will be me in san francisco, being forced to wear allbirds and lululemon pants, sitting on a beanbag chair, and listening to podcasts by 28 year old founders about distribution, completely sober

    Prikaži ovu nit
    Poništi
  14. proslijedio/la je Tweet
    6. sij

    People should write all kinds of stuff in Haskell to see what sticks. I write compute heavy servers, other people write PL analysis tools. It may never explode in popularity, but that’s impossible to predict. Think of the odd Ruby/Textmate screencast synergy back in the day!

    Poništi
  15. 5. sij

    It seems rather condescending to make a blanket statement about what someone else should and shouldn't use. Use what you find interesting and don't let anyone talk down to you.

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

    A rebuttal to the recent trend of "don't ever use the advanced parts of Haskell" posts

    Prikaži ovu nit
    Poništi
  17. 28. pro 2019.

    For those of you trying out Opaleye, here's some help for a common pattern: abstracting out common columns from your table definitions

    Poništi
  18. 16. pro 2019.

    the same way we have italics and bold, I need a font styling for deadpan

    Poništi
  19. 15. pro 2019.

    There are a lot of type-safe SQL libraries in Haskell. I wrote example projects in each to help you choose

    Poništi
  20. proslijedio/la je Tweet
    8. pro 2019.

    did an excellent links collection for and . I did now compile all articles into a single PDF document (which got now 230 pages) for reference. Blog: Direct Link to PDF:

    Prikaži ovu nit
    Poništi
  21. 30. stu 2019.

    If you're on the fence about whether to use Haskell, or if you're trying to convince your coworkers to use strongly-typed FP, here's a 'Why Haskell' for you

    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:

    ·