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

Top all-time · #9276

T

The Pug Automatic

Personal blog · thepugautomatic.comprogrammingweb

The Pug Automatic is a personal blog at thepugautomatic.com about programming and web. Since 2013, 8 different Hacker News readers have linked it 8 times, most often “Understanding Elixir macros”. It is still writing: the last post was on 2025-07-17, and you can follow it by feed.

Visit the blog
8mentions?
8HN people?
2013–2021first – last linked?
Links on Hacker News per year · peak 4 in 2015

Too few sampled comments (2) to say how often HN recommends it.?

Why HN links it

HN readers link these posts on React, Rails view helpers, and reviewing pull requests after the fact, cited as examples and as a source for the after-the-fact review approach.

Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

A blog by @henrik about Ruby, Elixir, Vim etc.

Most-linked posts?

  1. Understanding Elixir macros
    2 people · 2 mentions · first linked 2015-11-01

What Hacker News says?

  1. There are plenty of examples in other frameworks, e.g. sometimes view helpers in Rails output HTML. In certain situations it helps you write much cleaner code and it's easier to make more complex view components. Rails form helpers output HTML. http://apidock.com/rails/ActionView/Helpers/TextHelper/conca... http://thepugautomatic.com/2013/06/helpers/ http://guides.rubyonrails.org/form_helpers.html https://github.com…

    Comment linking /2013/06/helpers/

    on “React.js Introduction for People Who Know Just Enough JQuery”
  2. Submitted Systematically removing code as a story · 32 points

    HN discussion
  3. Another option is to do away with blocking on pull requests altogether and review after the fact. It has some benefits (and some downsides). I blogged about that here: http://thepugautomatic.com/2014/02/code-review/ We use a home-grown tool on top of GitHub to review commit-by-commit after the fact: https://github.com/henrik/remit

    Comment linking /2014/02/code-review/

    on “LGTM is a simple pull request approval system for GitHub”
  4. Submitted Understanding Elixir macros as a story · 5 points

    HN discussion
  5. Submitted Understanding Elixir macros as a story · 4 points

    HN discussion
  6. Submitted Interactive rebase against the remote master as a story · 1 points

    HN discussion
  7. Submitted Render Rails views with locals, not instance variables (2013) as a story · 1 points

    HN discussion
  8. Submitted String inheritance is overused as a story · 1 points

    HN discussion

Search all of HN for thepugautomatic.com

Linked by the same people?