Log inSign up
Log inSign up
Pierre-Henry @ PierreHenry.Dev
4,004 posts
Pierre-Henry @ PierreHenry.Dev profile banner
@phenrysay

Pierre-Henry @ PierreHenry.Dev

@phenrysay
Author of famous Software & Webapps. Love doing things in a better way..! 𝙇𝙞𝙛𝙚 𝙞𝙨 𝙁𝙐𝙉...only 𝗶𝗳 𝘆𝗼𝘂 𝘄𝗮𝗻𝘁 to!😊 · meal.ph7.me · github.ph7.me
Palo Alto, CA 🌴
retainr.io
Joined February 2013
1,095 Following
292 Followers
RepliesRepliesRepostsRepostsMediaMediaArticlesArticles

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·US TIDA·Ads Info·© 2026 X Corp.
  • Pinned
    @phenrysay
    Pierre-Henry @ PierreHenry.Dev
    @phenrysay
    Aug 10
    Most systems do not fail because code is hard. They fail because the next change has no clear owner. I build product software around the work that keeps it honest: clear boundaries, one source of truth, failure paths and rollback. I share the decisions, code and mistakes here.
  • @phenrysay
    Pierre-Henry @ PierreHenry.Dev
    @phenrysay
    19h
    Code gets read far more than it gets written. Clear names, small functions and honest trade-offs are a gift to the next person.
  • @phenrysay
    Pierre-Henry @ PierreHenry.Dev
    @phenrysay
    Oct 8
    Regret is to be punished twice. First, you suffer for the harm you have caused. Then, you suffer again because you regret having caused it. ┌──────────────────────┐ │ REGRET │ │ │ │ CAUSE HARM │ │
    One act. Two kinds of suffering
  • @phenrysay
    Pierre-Henry @ PierreHenry.Dev
    @phenrysay
    Oct 8
    A feature request can hide a duplicate. I ask: what working path will this recreate? If the answer is “the current one, just slightly differently,” I stop. New code creates a second behaviour to test, monitor, and explain. The safest feature may be the one you refuse.
    1
  • @phenrysay
    Pierre-Henry @ PierreHenry.Dev
    @phenrysay
    Oct 8
    I learn a lot by revisiting my old code. Before changing it, I write down: The assumption I’d revise. The behaviour I must preserve. Then I improve one decision, not the whole module. Newer code is not proof of better judgement.
    A hand holds a white cup of coffee beside an open laptop on a café table. The laptop screen and warm background lights are out of focus.