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 · #22532

Y

Yannick Gladow

Personal blog · dev-log.meprogrammingai

Yannick Gladow writes Dev Log, a personal blog at dev-log.me about programming and ai. Since 2026, 3 different Hacker News readers have linked it 14 times, most often “Formal Verification in Any Language for Everybody”. It is still writing: the last post was on 2026-10-24, and you can follow it by feed.

Visit the blog
14mentions?
3HN people?
2026–2026first – last linked?

Notes on software engineering by Yannick Gladow

Most-linked posts?

  1. Formal Verification in Any Language for Everybody
    2 people · 3 mentions · first linked 2026-03-31

What Hacker News says?

  1. As everyone is an expert now[1] on paper I think it is unfortunately time for a shift again. For years I was big proponent of asynchronous remote work. But it seems like the only reasonable way forward is to discuss things face to face. I still prefer to prepare things async, but then discuss them in person to understand if people actually understand what they are talking about. So far I also have a good time with r…

    Comment linking /everyone_is_an_expert_now/

    on “Appearing Productive in the Workplace”
  2. Submitted Formal Verification in Any Language for Everybody as a story · 4 points

    HN discussion
  3. I want to add something else to this. In the process of writing this, I also played with formal verification and formally verified the suggestion engine, which was a really nice side discovery. The basic idea is to write a prove in Lean4 and then test both the production implementation (Haskell) and the Lean implementation against random inputs. Compare if the results are the same. If that is the case -> you can be…

    Comment linking /formal_verification_in_any_language_for_everybody/

    on “Show HN: CLI to order groceries via reverse-engineered REWE API (Haskell)”
  4. Submitted Don't Embarrass Me, Claude as a story · 3 points

    HN discussion
  5. Same here it just feels like something so simple, I’d rather have it under my own control. That way I can keep it independent of claude as well. I use it for all kind of routine tasks like updating the summary of projects I am working on or tracking some personal activities. My setup looks like this: https://www.dev-log.me/click_recurring_tasks_for_claude/

    Comment linking /click_recurring_tasks_for_claude/

    on “Claude Code Routines”
  6. Submitted It's hard to build the right thing as a story · 2 points

    HN discussion
  7. I also discussed this a bit more here: https://www.dev-log.me/everyone_is_an_expert_now/

    Comment linking /everyone_is_an_expert_now/

    on “Thinking Fast, Slow, and Artificial: How AI Is Reshaping Human Reasoning”
  8. Submitted I Have Trust Issues with My AI. Canary Comments Help as a story · 2 points

    HN discussion
  9. I think right now a good approach can be using AI everywhere where it helps us in doing the hard work. Not taking the hard work over, but making the task easier in a supporting role. Few things that work really well for me: - AI creating un-opinionated summaries of PRs to help me get started reviewing - AI being an interactive tutor while I’ll still do the hard work of learning something new [1] - AI challenging my…

    Comment linking /jokes_on_you_ai_llms_for_learning/

    on “Breaking the Spell of Vibe Coding”
  10. Submitted Formal Verification in Any Language for Everybody (lean 4) as a story · 1 points

    HN discussion
  11. > Why not have an agent create a perfect “review plan” for human consumption? Split the review up in parts that can be individually (or independently) reviewed and then fixed by the coding agent. Have a proper ordering in files (GitHub shows files in a commit alphabetically, which is suboptimal), and hide boring details like function implementations that can be easily unit tested. Yes exactly! I have been using this…

    Comment linking /pr_review_navigator_for_claude/

    on “Haskell for all: Beyond agentic coding”
  12. Submitted AI to stay in Flow – a personal decision on how I chose to (not) use AI as a story · 1 points

    HN discussion
  13. I have the same feeling recently that we should focus more on using AI to enable us, to empower us to do the important things. Not take away but enhance, boring , clear boilerplate yes, design decisions no. And making reviewing easier is a perfect example of enhancing our workflow. Not reviewing for us, but supporting us. I am recently using this tiny[1] skill to generate an order on how to review a PR and it has be…

    Comment linking /pr_review_navigator_for_claude/

    on “Haskell for all: Beyond agentic coding”
  14. Submitted Jokes on You AI: Turning the Tables – LLMs for Learning as a story · 1 points

    HN discussion

Search all of HN for dev-log.me