Work in progress: 82,651 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #8310

H

hueypetersen.com

Personal blog · hueypetersen.com/postsprogramming

hueypetersen.com is a personal blog at hueypetersen.com about programming. Since 2013, 9 different Hacker News readers have linked it 10 times, most often “The State Machines of Core.Async”. The last post was in 2016, but the archive is still widely read.

Visit the blog
10mentions?
9HN people?
2013–2017first – last linked?
Links on Hacker News per year · peak 4 in 2013

Most-linked posts?

  1. The State Machines of Core.Async
    4 people · 4 mentions · first linked 2013-08-02
  2. Om.next from a Relay / GraphQL Perspective
    2 people · 2 mentions · first linked 2016-06-10

What Hacker News says?

  1. This was also asked a year ago, and I pointed to Zach Tellman, and that comment was upvoted by others. I'll post the same again. Because he always has excellent reasons for the decisions that he makes, I find it interesting to read his code and try to figure out why he made the decisions that he did. This is in Clojure: https://github.com/ztellman/manifold/blob/master/src/manifol... Also, it is fascinating to consid…

    Comment linking /posts/2013/08/02/the-state-machines-of-core-async/

    on “Ask HN: What are some examples of good code?”
  2. Submitted Om.next from a Relay / GraphQL Perspective as a story · 93 points

    HN discussion
  3. I think some of your frustrations might stem from your workflow. You really have to use the REPL to get the most out of Clojure development. For example, you should never change a bunch of code in different files and then try to run it and hope it works. Clojure workflow would be to change a particular function, send it to the REPL, see that it does what you want, then change the next function, and so on. ClojureScr…

    Comment linking /posts/2016/02/13/om-next-from-a-relay-graphql-perspective/

    on “State of Clojure 2016 – Results and Analysis”
  4. Submitted The State Machines of Core.Async as a story · 84 points

    HN discussion
  5. You can read more about the State Machines of core.async here: http://hueypetersen.com/posts/2013/08/02/the-state-machines-...

    Comment linking /posts/2013/08/02/the-state-machines-of-core-async/

    on “Co-routines as an alternative to state machines (2009)”
  6. Submitted First Thoughts on GraphQL with Clojure as a story · 2 points

    HN discussion
  7. Most macros fall under one of three categories. Improving performance by removing function calls or doing work at compile time eg https://github.com/ztellman/vertigo emulates c-style structs and uses macros to calculate the correct array offsets at compile-time, so you can treat a byte-array like a rich clojure datastructure but it compiles down to inline array access. Controlling binding or control flow eg https://…

    Comment linking /posts/2013/08/02/the-state-machines-of-core-async/

    on “Lisp for C++ programmers”
  8. Submitted Code Read of core.async Timeouts as a story · 2 points

    HN discussion
  9. Submitted Graph Traversal with Clojure as a story · 2 points

    HN discussion
  10. Submitted Modeling Queries in a GraphQL Like Way as a story · 1 points

    HN discussion

Search all of HN for hueypetersen.com

Linked by the same people?