<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: David Webb</title>
    <description>The latest articles on DEV Community by David Webb (@davidwebb915).</description>
    <link>https://dev.to/davidwebb915</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4126319%2F0b58fdc5-2a36-41a6-92ae-ef1eaa23f487.png</url>
      <title>DEV Community: David Webb</title>
      <link>https://dev.to/davidwebb915</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/davidwebb915"/>
    <language>en</language>
    <item>
      <title>When the Ground Shifts: What the Yijing Gets Right About Position (位)</title>
      <dc:creator>David Webb</dc:creator>
      <pubDate>Mon, 02 Nov 2026 03:05:57 +0000</pubDate>
      <link>https://dev.to/davidwebb915/when-the-ground-shifts-what-the-yijing-gets-right-about-position-wei--2465</link>
      <guid>https://dev.to/davidwebb915/when-the-ground-shifts-what-the-yijing-gets-right-about-position-wei--2465</guid>
      <description>&lt;p&gt;Look at Europe this month. Cost-of-living protests rolling through France and Germany, general strikes called across Spain, Portugal, and Italy, coalition governments recalculating under street pressure — Prague's ongoing protests being one live case. Whatever your politics, the structural fact is the same: &lt;strong&gt;the ground is moving&lt;/strong&gt;, and millions of people are quietly asking the same question — &lt;em&gt;am I standing in the right place for what's already happening?&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The &lt;em&gt;Yijing&lt;/em&gt; (易经) has a precise term for this: &lt;strong&gt;位&lt;/strong&gt; (wèi) — position. Not rank. Not job title. Position in the structural sense: where you stand relative to the forces around you, and whether that standing is supported or exposed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Being right, in the wrong place
&lt;/h2&gt;

&lt;p&gt;A hexagram line has two attributes: what it &lt;em&gt;is&lt;/em&gt; (yang or yin, strong or yielding) and &lt;em&gt;where it sits&lt;/em&gt;. The tradition is blunt — a capable line in a bad position fares worse than a modest line in a good one. 当位 ("in position") versus 不当位 ("out of position").&lt;/p&gt;

&lt;p&gt;You have seen this in every collapsing organization: the talented person whose department is being unwound, the solvent business on the wrong side of an energy-price shock, the skilled professional in a city whose economy just re-priced. Nothing about &lt;em&gt;what they are&lt;/em&gt; changed. The structure under them moved — and their position revalued overnight.&lt;/p&gt;

&lt;p&gt;The old texts describe the fourth line — the position just below the ruler — as 近君多惧, "near power, much fear." High visibility, low control: the classic exposed position. Most burnout is not too much work. It is fourth-line work: proximity to decisions you don't make.&lt;/p&gt;

&lt;h2&gt;
  
  
  The sequence the tradition actually teaches
&lt;/h2&gt;

&lt;p&gt;When the ground shifts, the received sequence is not panic and it is not optimism. It is: &lt;strong&gt;穷则变，变则通，通则久&lt;/strong&gt; — "when things exhaust, they change; change opens passage; passage endures." Exhaustion is treated as &lt;em&gt;structural information&lt;/em&gt;, not personal failure. A stuck system tells you the old position is spent.&lt;/p&gt;

&lt;p&gt;But — and this is the part self-help skips — the &lt;em&gt;Yijing&lt;/em&gt; pairs every call to change with a call to read your position first. Change from an exposed position looks like flight. Change from a supported position looks like strategy. Same move, different 位, opposite outcomes.&lt;/p&gt;

&lt;h2&gt;
  
  
  A practical position audit
&lt;/h2&gt;

&lt;p&gt;Strip the mysticism and three questions remain, answerable by anyone:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Support&lt;/strong&gt;: what in your current structure holds you up — and is it strengthening or weakening?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Exposure&lt;/strong&gt;: where are you visible to forces you don't control (your employer's sector, your city's cost base, one client, one platform)?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Season&lt;/strong&gt;: is this a hold-year or a move-year for you specifically — not for "the economy," for you?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Most people run this audit only after being forced to. The tradition's whole argument is that the audit is cheaper before.&lt;/p&gt;

&lt;p&gt;At &lt;a href="https://tangoera.com" rel="noopener noreferrer"&gt;TangoEra&lt;/a&gt; we do this with actual instruments: a BaZi chart converts your birth moment into a structural map — day master, configuration, a three-year structural view — so "which line am I standing on" stops being a metaphor. Every element is reproducible and checkable; we publish what the structure says and what it does not, and it never claims to predict events.&lt;/p&gt;

&lt;p&gt;If your ground is shifting this season, start with the piece on &lt;a href="https://tangoera.com/blog/changing-your-mind-without-shame/" rel="noopener noreferrer"&gt;changing your mind without shame&lt;/a&gt; — because repositioning begins with being allowed to re-decide.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Structure, not prophecy. The Yijing predicts nothing; it only asks better questions.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>philosophy</category>
      <category>culture</category>
      <category>selfimprovement</category>
      <category>lifecoaching</category>
    </item>
    <item>
      <title>Election Night Is a Masterclass in Two Old Variables: Timing and Position</title>
      <dc:creator>David Webb</dc:creator>
      <pubDate>Mon, 02 Nov 2026 03:05:55 +0000</pubDate>
      <link>https://dev.to/davidwebb915/election-night-is-a-masterclass-in-two-old-variables-timing-and-position-3lag</link>
      <guid>https://dev.to/davidwebb915/election-night-is-a-masterclass-in-two-old-variables-timing-and-position-3lag</guid>
      <description>&lt;p&gt;On Tuesday, November 3, America votes in its midterms — 435 House seats, a third of the Senate, 39 governorships, all contested on a single Tuesday. Commentators will spend the evening arguing about &lt;em&gt;who&lt;/em&gt; wins. The older question — the one at the root of the &lt;em&gt;Yijing&lt;/em&gt; (易经) — is different: &lt;strong&gt;when&lt;/strong&gt; and &lt;strong&gt;from where&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Classical Chinese decision theory compresses this into two characters: &lt;strong&gt;时&lt;/strong&gt; (shí, timing) and &lt;strong&gt;位&lt;/strong&gt; (wèi, position). Almost every line of the &lt;em&gt;Book of Changes&lt;/em&gt; is really a comment on one of these two variables. Not "what is fated," but "is this the right season for this move, and are you standing in the right place to make it?"&lt;/p&gt;

&lt;h2&gt;
  
  
  Watch the timing variable on election night
&lt;/h2&gt;

&lt;p&gt;Midterm elections have a rhythm of their own. The party holding the White House has historically bled seats at the midpoint — not because millions of voters individually change their nature, but because the &lt;em&gt;season&lt;/em&gt; changed around them. The same message, the same candidate, the same policy — delivered in year two instead of year four — lands differently.&lt;/p&gt;

&lt;p&gt;That is textbook 时. The &lt;em&gt;Yijing&lt;/em&gt;'s first hexagram makes the point with its opening line: &lt;strong&gt;潜龙勿用&lt;/strong&gt; — "the submerged dragon does not act." The strongest force in the system, in the wrong season, holds. Not weakness. Timing discipline.&lt;/p&gt;

&lt;p&gt;Polls have missed before, and they will miss somewhere again. But notice &lt;em&gt;what kind&lt;/em&gt; of miss repeats: polling consistently struggles with timing questions (who has momentum at the close, who peaked a month too early) far more than with position questions (which district leans which way). Confusing a timing problem for a position problem is the classic error — in elections and in careers.&lt;/p&gt;

&lt;h2&gt;
  
  
  The line that decides your year isn't your talent
&lt;/h2&gt;

&lt;p&gt;Here is the part that survives the news cycle. In a hexagram, a line's fortune depends on its &lt;strong&gt;position&lt;/strong&gt; — fifth line versus third line, central versus extreme, supported versus isolated. The same line, moved one place up or down, changes its meaning entirely.&lt;/p&gt;

&lt;p&gt;Translate that out of the courtly metaphor: your leverage this season depends less on your raw ability and more on &lt;em&gt;where that ability stands relative to the structures around it&lt;/em&gt; — your market, your team, your city, your decade.&lt;/p&gt;

&lt;p&gt;Which raises a practical question most people never answer precisely, because it feels mystical and isn't: &lt;strong&gt;in the current structure of your life, which line are you actually standing on?&lt;/strong&gt; Holding position when the structure favors you is strategy. Holding position when the season has turned is just delay with better branding.&lt;/p&gt;

&lt;h2&gt;
  
  
  A reproducible version of the question
&lt;/h2&gt;

&lt;p&gt;This is what we work on at &lt;a href="https://tangoera.com" rel="noopener noreferrer"&gt;TangoEra&lt;/a&gt;. A BaZi chart — the four-pillar system behind this tradition — is essentially a &lt;em&gt;timing and position instrument&lt;/em&gt;: a birth moment converted into a structural map of when pressure and openings arrive for you specifically, year by year. No fate verdicts, no predictions about events. Every claim ties back to a visible structure you can check, question, and re-verify — closer to an audit than an oracle.&lt;/p&gt;

&lt;p&gt;We wrote a plain-English piece on the hardest timing question most people carry — &lt;a href="https://tangoera.com/blog/how-long-to-wait/" rel="noopener noreferrer"&gt;how long to wait before forcing a decision&lt;/a&gt; — because "should I move now or hold" is rarely a courage problem. It is almost always a 时 and 位 problem wearing a courage costume.&lt;/p&gt;

&lt;p&gt;On election night, enjoy the returns. And when a race flips against every forecast, ask the older question: did the candidate lose — or did the season move?&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This piece is cultural and analytical, not political. It predicts nothing and endorses no one.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>philosophy</category>
      <category>decisionmaking</category>
      <category>culture</category>
      <category>selfimprovement</category>
    </item>
    <item>
      <title>Character Is Not a Verdict</title>
      <dc:creator>David Webb</dc:creator>
      <pubDate>Sat, 31 Oct 2026 03:46:29 +0000</pubDate>
      <link>https://dev.to/davidwebb915/character-is-not-a-verdict-1872</link>
      <guid>https://dev.to/davidwebb915/character-is-not-a-verdict-1872</guid>
      <description>&lt;p&gt;Pattern Comparison · August 16, 2026&lt;/p&gt;

&lt;h1&gt;
  
  
  Character Is Not a Verdict
&lt;/h1&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;    August 16, 2026
    ·
    By TangoEra
    ·
    Last updated: August 26, 2026
    ·
    [Back to Blog](/blog/)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;Free: get the pattern-over-label reflection checklist — one email, instant delivery.&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;    Send my checklist
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;You have been told that your traits write your future. That the patterns you carry are sentences. Introversion becomes isolation. Intensity becomes burnout. Caution becomes regret. The language of personality has been hijacked by simplistic labels, as if a single assessment could freeze your trajectory into a straight line.&lt;/p&gt;

&lt;p&gt;It cannot. Your patterns are data points. Not a fixed trajectory.&lt;/p&gt;

&lt;p&gt;The same decision-maker whose directness closes a deal in one negotiation can alienate a key partner in another. The same gap-spotter who identifies the opening in one market misses the foundation in the next. The same vision-oriented decision-maker who produces a masterpiece in isolation ships nothing in chaotic conditions. Your operating pattern is real. It is measurable. It is consistent. But it is not a verdict. It is a starting coordinate. The map updates as new data points are generated by your actions.&lt;/p&gt;

&lt;p&gt;What determines trajectory is not the pattern you carry. It is what you do with the awareness of it. A decision-maker with transformation tendencies who adopts structural discipline becomes a force that builds. A decision-maker with consolidation tendencies who learns to install adaptive gates becomes a structure that breathes. A decision-maker who innovates and finds a team that trusts their process becomes a leader capable of navigating uncharted territory. Nothing in your wiring prevents the shift. Only the story you tell about the wiring does.&lt;/p&gt;

&lt;p&gt;TangoEra does not predict outcomes. We map decision signals. The signal provides a real-time data snapshot of your operating conditions. The move is still yours. Your operating pattern is a high-performance instrument, providing clear data. You are the decision-maker. An instrument only produces results when directed with skill and awareness.&lt;/p&gt;

&lt;p&gt;Your edge is awareness. Your trap is letting a label close the case before the evidence is in.&lt;/p&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;  personal growthdecision signalsoperating patternsself awarenesscareer strategyTangoEra&lt;br&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;h2&gt;
&lt;br&gt;
  &lt;br&gt;
  &lt;br&gt;
  A profile is not a verdict.&lt;br&gt;
&lt;/h2&gt;

&lt;p&gt;Get your free 90-second decision map and see the full picture.&lt;br&gt;
  &lt;a href="https://dev.to/quiz?utm_source=blog-cta&amp;amp;utm_medium=article-end&amp;amp;utm_campaign=character-not-verdict"&gt;Get my free 90-second decision map&lt;/a&gt;&lt;/p&gt;

</description>
      <category>decisionmaking</category>
      <category>psychology</category>
      <category>selfimprovement</category>
      <category>mentalmodels</category>
    </item>
    <item>
      <title>Ask Who Benefits: One Question That Cuts Through Most Confusion</title>
      <dc:creator>David Webb</dc:creator>
      <pubDate>Sat, 31 Oct 2026 03:46:27 +0000</pubDate>
      <link>https://dev.to/davidwebb915/ask-who-benefits-one-question-that-cuts-through-most-confusion-33p0</link>
      <guid>https://dev.to/davidwebb915/ask-who-benefits-one-question-that-cuts-through-most-confusion-33p0</guid>
      <description>&lt;h1&gt;
  
  
  Ask Who Benefits: One Question That Cuts Through Most Confusion
&lt;/h1&gt;

&lt;p&gt;2026·By TangoEra·Last updated: August 29, 2026·&lt;a href="https://dev.to/blog/"&gt;Back to Blog&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;When an explanation stops making sense, stop auditing the words and start auditing the arrangement: ask who benefits, and what keeps paying them. The subscription that renews itself, the meeting that never dies, the advice that always ends in a purchase — none of these need a more convincing explanation. They need an owner. Persistent behavior is usually someone's position, and once you see whose, the confusion starts to collapse into design.&lt;/p&gt;

&lt;p&gt;What follows is a description of that pattern, grounded in published research rather than opinion: Smith (1776) saw it in commerce, Gneezy and Rustichini (2000) at a daycare, and both found that behavior follows incentives more reliably than stated intentions. Reading the arrangement therefore tells you more than re-reading the explanation attached to it. One scope note before anything else: this is a description, not a verdict about who you are. This is a pattern, not an identity. Patterns can be read, which is exactly what makes them useful.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Does "Ask Who Benefits" Actually Mean?
&lt;/h2&gt;

&lt;p&gt;Ask it literally. When you cannot tell why something keeps happening — why the advice keeps pointing one way, why the rule never gets fixed, why the "free" service keeps escalating — the instinct is to go back over the explanation, hunting for the sentence you must have misread. Skip that move. The explanation is doing its job; that is why you have one. Ask the boring question instead: who benefits from this persisting, and what arrangement keeps paying them? It sounds almost too simple, which is why it gets skipped — the question is boring on purpose, and boring questions are the ones that keep working.&lt;/p&gt;

&lt;p&gt;Notice what the question does not ask. Not who is secretly evil, and not who is running a scam. It is a structural question: every persistent arrangement has someone whose position it maintains — a margin, a metric, a title, a habit. That is what persistence means. Behaviors that benefit nobody do not keep happening; they get fixed, defunded, or quietly forgotten. So when something will not die, the working assumption is not corruption. It is maintenance. Somewhere, the thing is doing a job for somebody, and the job is being paid for — which is why the free tool gets more aggressive every year, and why the helpful advice always seems to end at a checkout page. Someone's position is being maintained, and once you know whose, the behavior stops reading like a mystery and starts reading like a design.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Do Incentives Beat Stated Intentions?
&lt;/h2&gt;

&lt;p&gt;Because intentions live in sentences and incentives live in payoffs, and payoffs are steadier. Smith (1776) made the point about dinner: the butcher does not feed you out of kindness. "It is not from the benevolence of the butcher..." — you eat because serving you serves his own interest. Your meal arrives on time precisely because nobody has to feel anything about you for it to arrive. Goodwill is optional in that transaction; interest is structural. That is not a complaint about the butcher — it is the reason you can rely on him.&lt;/p&gt;

&lt;p&gt;Gneezy and Rustichini (2000) added the twist that makes the question powerful: incentives do not just change the math of a situation, they change what the situation means. In their field study of daycares — published under the title "A Fine is a Price" — a fine was introduced for parents who picked up children late, and lateness went up rather than down. The fine had quietly converted a moral obligation into a purchasable price, and some parents decided the price was fair. The incentive did not add pressure to the old meaning; it replaced the meaning.&lt;/p&gt;

&lt;p&gt;So when stated reasons and actual behavior diverge, you know why to trust the behavior: words report intentions, but arrangements report payoffs. An explanation can say anything and survive on charm. A persistent arrangement has to keep paying for itself, cycle after cycle, in real money, time, or relief — which is what makes it the more honest witness.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Do You Run the Question on Real Situations?
&lt;/h2&gt;

&lt;p&gt;Two steps, in order. First, name the thing that persists — not the thing that annoyed you once, but the thing that has survived every attempt to change it. Second, ask what keeps paying for it: whose margin, whose metric, whose title, whose comfort? A good answer names three things: who collects, what they collect (money, attention, relief, status), and how often the payment cycles. When in doubt, follow the incentives — they are the part of the story that has to keep paying for itself. If you cannot name the collector, you have not finished asking; if you can, the behavior usually explains itself.&lt;/p&gt;

&lt;p&gt;Then test it on three ordinary scenes. The gym membership renews itself not because the cancellation button is technically hard to build, but because your inaction is the product — the whole business model is priced on the people who meant to quit. The weekly meeting that never dies usually survives because attending it is someone's position; cancel it, and somebody loses a calendar entry, a headcount, a reason to be in the loop. The influencer whose honest reviews always end in a promo code is not confused about quality — the review is the ad, and the ad is what pays. None of this requires bad actors, which is the uncomfortable part: everyone in these scenes can be doing their job correctly, and the arrangement still produces the behavior you keep trying to explain.&lt;/p&gt;

&lt;p&gt;Run it a few times and two ways of reading the world separate cleanly:&lt;/p&gt;

&lt;p&gt;Reading wordsReading arrangementsAsks: "what does this statement mean?"Asks: "who is this statement maintaining?"Trusts stated reasons by defaultTreats stated reasons as one input among incentivesGets confused when words and behavior divergeExpects the divergence; reads behavior as the signalReacts case by caseSpots the pattern once and predicts the next case&lt;/p&gt;

&lt;p&gt;The left column is not stupid — it is just slower, because it starts from zero in every new case. The right column expects the gap between words and behavior, reads the behavior as the signal, and gets faster with every case it sees. One caution before you adopt it: point the question at arrangements, not at agonizing. If what keeps confusing you is your own undecided choice, that is a different problem — the kind you solve when you &lt;a href="https://dev.to/blog/stop-second-guessing/"&gt;stop second-guessing yourself&lt;/a&gt;, not the kind you solve by hunting for a beneficiary.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Happens Next When You Start Asking It?
&lt;/h2&gt;

&lt;p&gt;Expect two things, in this order. First, the world gets quieter. You stop re-litigating each case and start spotting the pattern once and predicting the next one: you can hear the auto-renewal, the dead meeting, and the promo code arriving before they do. Confusion stops feeling like a puzzle you failed and starts feeling like information you can use. You also start hearing advice differently: before asking whether a recommendation is good, you ask why is this advice being given, and where the answer flows. Most advice is not wrong; it is oriented, and the orientation is the part nobody reads aloud.&lt;/p&gt;

&lt;p&gt;Second — and this is the step most people skip — you eventually have to point the question at yourself. Your own habits persist for the same reason everything else does. The scroll you swear you will cut tonight, the alarm you keep snoozing, the cart you abandon at checkout every single time: each one survives because something is being paid, and the beneficiary is usually a comfort you are protecting. The arrangement is internal — relief now, in exchange for the thing you said you wanted. That is not corruption. It is maintenance, the same logic as the gym membership, except that you are sitting on both sides of the transaction.&lt;/p&gt;

&lt;p&gt;None of this is an accusation, and none of it is a verdict about who you are. It is the same structural read you give everyone else, aimed at the one arrangement you actually control. Be warned, though: naming the comfort costs something, because naming it means admitting the price you have been quietly paying — which makes it &lt;a href="https://dev.to/blog/the-trade-off-you-keep-refusing/"&gt;the trade-off you keep refusing&lt;/a&gt;. Name it anyway. This is a pattern, not an identity. Patterns, unlike identities, can be renegotiated — and the person holding the pen is you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Read the arrangement, not the explanation.&lt;/strong&gt; Take the free TangoEra assessment to map your decision style — and see how this pattern shows up in yours.&lt;a href="https://dev.to/quiz?utm_source=blog-cta&amp;amp;utm_medium=article-end&amp;amp;utm_campaign=ask-who-benefits"&gt;Get my free 90-second decision map&lt;/a&gt; &amp;nbsp; &lt;a href="https://dev.to/free-snapshot?utm_source=free-snap&amp;amp;utm_medium=nav&amp;amp;utm_campaign=v2-20260903"&gt;Free snapshot&lt;/a&gt;&lt;/p&gt;

</description>
      <category>decisionmaking</category>
      <category>psychology</category>
      <category>selfimprovement</category>
      <category>mentalmodels</category>
    </item>
    <item>
      <title>Why the same effort pays 10x at a different position</title>
      <dc:creator>David Webb</dc:creator>
      <pubDate>Thu, 29 Oct 2026 09:31:14 +0000</pubDate>
      <link>https://dev.to/davidwebb915/why-the-same-effort-pays-10x-at-a-different-position-58n7</link>
      <guid>https://dev.to/davidwebb915/why-the-same-effort-pays-10x-at-a-different-position-58n7</guid>
      <description>&lt;p&gt;正文（发前扩写 800-1000 词）：改编 K2 已过稿《It is Not You. It is Your Timing x Position.》——易经时位框架：Timing=窗口、Position=坐标，结果≈两者乘积；面向 builders/founders 讲 ship 时机与市场窗口；结尾 CTA=canonical 链接。&lt;br&gt;
源料：~/agent/state/soc-queue/drafts/medium-tp1-timing-position.md&lt;/p&gt;

</description>
      <category>career</category>
      <category>decisionmaking</category>
      <category>iching</category>
    </item>
    <item>
      <title>How a 60-Cycle Calendar System Works as a 60-Year Periodic Algorithm</title>
      <dc:creator>David Webb</dc:creator>
      <pubDate>Thu, 01 Oct 2026 06:45:53 +0000</pubDate>
      <link>https://dev.to/davidwebb915/how-a-60-cycle-calendar-system-works-as-a-60-year-periodic-algorithm-1c7b</link>
      <guid>https://dev.to/davidwebb915/how-a-60-cycle-calendar-system-works-as-a-60-year-periodic-algorithm-1c7b</guid>
      <description>&lt;p&gt;I started looking at BaZi, or Four Pillars of Destiny, because its output seemed oddly structured. It did not look like a paragraph of free-form symbolism. It looked like a compact record: four paired labels, each drawn from repeating sequences, with rules for translating a birth time into those labels.&lt;/p&gt;

&lt;p&gt;As a data engineer, I’m inclined to ask what the schema is, where the boundaries sit, and what happens when the input is ambiguous. Those questions don’t prove anything about the system’s claims. They do make its calendar mechanics interesting to reverse-engineer.&lt;/p&gt;

&lt;h2&gt;
  
  
  A cycle built from two counters
&lt;/h2&gt;

&lt;p&gt;The basic unit is a pair: one Heavenly Stem and one Earthly Branch. There are 10 stems and 12 branches. Both advance one position at a time, so the first pair returns when both counters have completed whole cycles. That takes the least common multiple of 10 and 12: 60 steps.&lt;/p&gt;

&lt;p&gt;There’s a small combinatorics wrinkle. Ten times twelve gives 120 possible pairings if every stem could match every branch. But the traditional sequence advances both lists together, so only 60 pairings occur. Starting from Jia-Zi, the sequence proceeds Jia-Zi, Yi-Chou, Bing-Yin, and so on, until it returns to Jia-Zi.&lt;/p&gt;

&lt;p&gt;In code, I might represent a position with an integer &lt;code&gt;n&lt;/code&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Stem index: &lt;code&gt;n mod 10&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Branch index: &lt;code&gt;n mod 12&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Full pair: the two indexed symbols&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Advance &lt;code&gt;n&lt;/code&gt; by one to move to the next pair. Advance it by 60 and the pair is back where it started. That’s the core periodic algorithm: two clocks with different periods, sharing one step counter. (&lt;a href=""&gt;aa.usno.navy.mil&lt;/a&gt;)&lt;/p&gt;

&lt;p&gt;The 60-step sequence can label years, months, days, and hours, but those are not one giant clock ticking at the same speed. Each unit has its own rule for finding the current position in the cycle. The shared encoding makes the labels comparable; the calendar conventions decide where one unit ends and the next begins.&lt;/p&gt;

&lt;h2&gt;
  
  
  Turning a timestamp into four pillars
&lt;/h2&gt;

&lt;p&gt;A chart has four pillars: year, month, day, and hour. Each pillar is one stem-branch pair. A simplified software pipeline looks something like this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Parse the birth timestamp, location, and time-zone context.&lt;/li&gt;
&lt;li&gt;Convert the timestamp to the calendar’s working local time.&lt;/li&gt;
&lt;li&gt;Determine which year and solar-term month contain it.&lt;/li&gt;
&lt;li&gt;Find the sexagenary day index.&lt;/li&gt;
&lt;li&gt;Divide the day into two-hour branch intervals, then derive the hour stem from the day stem.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The year pillar is not always switched at the same boundary across every convention. Many BaZi methods use the solar term Li Chun as the year boundary rather than Lunar New Year. Month pillars also follow solar terms: the year is divided into 12 solar months, with month changes anchored to particular terms. So a person born in early February may land on different year labels under different year-boundary conventions.&lt;/p&gt;

&lt;p&gt;The day pillar is a position in its own 60-day sequence. The hour branch divides the day into 12 two-hour periods; for example, Zi is commonly associated with roughly 11 p.m. to 1 a.m. The hour stem is not an independent counter that can be looked up from clock time alone: its assignment is linked to the day stem.&lt;/p&gt;

&lt;p&gt;This is why two implementations can accept the same date and still disagree. They may be using different boundaries, different day-rollover conventions, or different assumptions about what “local time” means. The symbolic lookup can be perfectly consistent while the input normalization differs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Civil time is not solar time
&lt;/h2&gt;

&lt;p&gt;A timestamp such as &lt;code&gt;01:30&lt;/code&gt; is a statement about a clock, not directly about the Sun’s position. Civil clocks follow time-zone rules. Apparent solar time follows the Sun’s local position, which varies with longitude and with the equation of time.&lt;/p&gt;

&lt;p&gt;The IANA Time Zone Database is useful here because it records time-zone offsets and daylight-saving transitions for named regions. But historical coverage and confidence vary, especially for dates before 1970. A location name alone is not enough; a robust input needs a date and a specific zone, and an ambiguous local time may also need its UTC offset or an explicit “first or second occurrence” marker. (&lt;a href=""&gt;iana.org&lt;/a&gt;)&lt;/p&gt;

&lt;p&gt;Consider New York on November 7, 2021. At the end of daylight saving time, clocks moved from 2:00 a.m. daylight time back to 1:00 a.m. standard time. That means &lt;code&gt;01:30&lt;/code&gt; occurred twice: once at UTC−4 and again at UTC−5. A timestamp containing only the city and wall-clock reading cannot distinguish those two instants. The IANA zone rules can resolve the transition once the input identifies which occurrence it means. (&lt;a href=""&gt;timeanddate.com&lt;/a&gt;)&lt;/p&gt;

&lt;p&gt;If a method uses true solar time, there is another adjustment. First resolve the civil time-zone offset, including daylight saving time. Then account for longitude relative to the time zone’s standard meridian, and for the equation of time. As a rough rule, each degree of longitude corresponds to about four minutes of solar-time difference. New York is near 74° west, while Eastern Standard Time is based on a 75° west meridian, so the longitude correction is about four minutes ahead of standard clock time. The equation-of-time adjustment varies by date and can reach around 16 minutes. (&lt;a href=""&gt;aa.usno.navy.mil&lt;/a&gt;)&lt;/p&gt;

&lt;p&gt;Those minutes matter most near a boundary. If the corrected time falls close to a two-hour branch change, different normalization choices could produce a different hour branch. Near a day boundary, a convention for when the sexagenary day turns over could affect the day pillar too. This is less a mystical mystery than a familiar data-quality issue: the model has edge cases, and the pipeline needs to state its assumptions.&lt;/p&gt;

&lt;h2&gt;
  
  
  The ten-year phase as a state machine
&lt;/h2&gt;

&lt;p&gt;BaZi also describes longer luck cycles, often called decade pillars. In many methods, a sequence of these ten-year phases is derived from the month pillar. The direction of travel and the starting age depend on conventions that can involve the birth year and the distance to a nearby solar term. Each phase advances through the stem-branch sequence, with a new phase roughly every ten years.&lt;/p&gt;

&lt;p&gt;That invites a state-machine analogy. The birth chart is the initial state; the decade pillar is a phase that changes at a calculated boundary; the current year and other calendar cycles provide additional inputs. A reader can describe the state at a given date by identifying which phase is active and which cycle labels apply.&lt;/p&gt;

&lt;p&gt;The analogy has limits. A state machine tells us how labels change under stated rules. It does not establish that those labels cause or reliably describe events. Also, a ten-year phase is not simply “one sixth of a 60-year loop” in every practical calculation: its start and direction depend on conventions, and other calendar boundaries run alongside it.&lt;/p&gt;

&lt;p&gt;Still, the algorithmic structure is elegant. A small number of cyclic counters, plus carefully defined transition rules, produce a compact time-based representation. The trickiest part is not the modulo arithmetic. It is agreeing on the exact instant and the calendar rules before the arithmetic begins.&lt;/p&gt;

&lt;h2&gt;
  
  
  Boundaries
&lt;/h2&gt;

&lt;p&gt;I treat BaZi as a cultural-computational system for insight and reflection, not a tool for forecasting outcomes. The cycle math can be described and tested; that does not validate claims that chart labels determine a person’s character or life events. I make no outcome claims here. At most, the system can serve as entertainment or a prompt for decision-support conversations, with real-world decisions grounded in evidence relevant to the decision itself.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'm still unsure about
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Which time-normalization convention is most faithful to historical BaZi practice: civil clock time, local mean solar time, or apparent solar time?&lt;/li&gt;
&lt;li&gt;How much do different schools’ boundary rules change charts in practice, especially for births near midnight or a solar-term transition?&lt;/li&gt;
&lt;li&gt;Can a software implementation clearly expose uncertainty in old time-zone records without making the chart interface unreadable?&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>programming</category>
      <category>history</category>
      <category>algorithms</category>
      <category>calendar</category>
    </item>
    <item>
      <title>Birth times are messy inputs: timezones, DST, and solar time</title>
      <dc:creator>David Webb</dc:creator>
      <pubDate>Wed, 30 Sep 2026 13:45:50 +0000</pubDate>
      <link>https://dev.to/davidwebb915/birth-times-are-messy-inputs-timezones-dst-and-solar-time-35mp</link>
      <guid>https://dev.to/davidwebb915/birth-times-are-messy-inputs-timezones-dst-and-solar-time-35mp</guid>
      <description>&lt;p&gt;Title: Birth times are messy inputs: timezones, DST, and solar time&lt;/p&gt;

&lt;p&gt;I thought the evaluation engine would be the hard part. I was wrong; timestamp normalization took longer.&lt;/p&gt;

&lt;p&gt;A local civil-time reading has to account for historical daylight-saving changes, sub-hour offset adjustments, and longitude corrections before it can yield true solar time. Then come the edge cases: solar-term transitions, and the competing rules that flip a calendar day at 23:00 or midnight. Either choice can change the state initializer.&lt;/p&gt;

&lt;p&gt;Now I treat each raw birth timestamp as unvalidated input and send it through a strict timezone transformation pipeline.&lt;/p&gt;

&lt;p&gt;When building a software pipeline for this calendar system, the input stage is deceptively complex. A timestamp such as &lt;code&gt;01:30&lt;/code&gt; is a statement about a civil clock, not the Sun's position. Civil clocks follow regional time-zone rules, whereas apparent solar time depends on the Sun's actual position, shifting with longitude and the equation of time.&lt;/p&gt;

&lt;p&gt;I rely on the IANA Time Zone Database (zoneinfo) to handle historical offsets and daylight-saving transitions (DST). But historical coverage varies in accuracy, especially for dates prior to 1970. A location name alone is insufficient. To resolve an ambiguous timestamp, you need a date, a specific zone, and an explicit UTC offset or occurrence marker.&lt;/p&gt;

&lt;p&gt;Take New York on November 7, 2021. At the end of daylight saving time, clocks fell back from 2:00 a.m. daylight time to 1:00 a.m. standard time. That means &lt;code&gt;01:30&lt;/code&gt; occurred twice: once at UTC−4 and again at UTC−5. Without an explicit occurrence marker, a wall-clock reading cannot distinguish those two instants.&lt;/p&gt;

&lt;p&gt;If a calendar method requires true solar time, additional adjustments must be chained together. First, you resolve the civil time-zone offset and DST. Next, you apply a longitude correction relative to the zone's standard meridian. Each degree of longitude shifts solar time by roughly four minutes. New York sits near 74° west, while Eastern Standard Time is based on a 75° west meridian, placing New York about four minutes ahead of standard clock time. Finally, the equation of time must be applied, which fluctuates by date and can shift the result by up to 16 minutes.&lt;/p&gt;

&lt;p&gt;These minutes matter most near boundaries. The hour branch divides the day into 12 two-hour intervals, such as Zi from roughly 11 p.m. to 1 a.m. Because Zi begins at 11 p.m. (23:00), some conventions flip the calendar day at 23:00, while others wait until midnight. Because the hour stem is derived from the day stem, choosing 23:00 versus midnight flips both the day pillar and the hour stem. This is why two implementations receiving the same input date can yield different charts.&lt;/p&gt;

&lt;p&gt;I am still unsure about which time-normalization convention is most faithful to historical practice: civil clock time, local mean solar time, or apparent solar time. I also wonder how to clearly expose uncertainty in old zoneinfo records without making the chart interface unreadable—a common challenge when surfacing historical data.&lt;/p&gt;

&lt;p&gt;Not medical, legal, or financial advice. A cultural and cognitive framework for self-reflection; outputs vary by individual.&lt;/p&gt;

</description>
      <category>programming</category>
      <category>algorithms</category>
      <category>history</category>
      <category>culture</category>
    </item>
    <item>
      <title>I tried to put a 2,000-year-old calendar into one boundary rule</title>
      <dc:creator>David Webb</dc:creator>
      <pubDate>Wed, 30 Sep 2026 13:45:13 +0000</pubDate>
      <link>https://dev.to/davidwebb915/i-tried-to-put-a-2000-year-old-calendar-into-one-boundary-rule-16im</link>
      <guid>https://dev.to/davidwebb915/i-tried-to-put-a-2000-year-old-calendar-into-one-boundary-rule-16im</guid>
      <description>&lt;p&gt;Title: I tried to put a 2,000-year-old calendar into one boundary rule&lt;/p&gt;

&lt;p&gt;I once tried to fit different traditional calendar schools into one boolean truth table. The disagreements looked like logic bugs until I saw the structural assumptions underneath.&lt;/p&gt;

&lt;p&gt;An ancient astronomical cycle's boundary depends on which solar coordinate or epoch anchor you choose as the primary axis. Each school has a self-consistent coordinate system and its own edge definitions; one truth table can't reconcile them without flattening those differences.&lt;/p&gt;

&lt;p&gt;Now my schema keeps core graph processing separate from boundary parsing. I made the parsing strategy configurable by calendar convention instead of baking one convention in as the absolute truth.&lt;/p&gt;

&lt;p&gt;Early on, I expected that translating a birth time into four pillars (year, month, day, and hour) would follow a single standard. When comparing outputs across different BaZi tools, I noticed they frequently disagreed on edge cases. For instance, the year pillar boundary is not uniformly set at Lunar New Year across all schools. Many conventions anchor the year transition to the solar term Lichun instead. A person born in early February can land on completely different year labels depending on which year-boundary convention the software enforces.&lt;/p&gt;

&lt;p&gt;Month pillars present similar branch points. The calendar divides the year into 12 solar months, anchoring month transitions to specific solar terms rather than lunar months. Meanwhile, the day pillar relies on its own 60-day position, with competing rules turning the day over at 23:00 or at midnight. Because the hour stem assignment is linked to the day stem, changing the day rollover boundary cascade-updates the hour pillar too.&lt;/p&gt;

&lt;p&gt;Longer ten-year phases, or decade pillars, add another layer of configuration. Derived from the month pillar, their direction and starting age depend on conventions involving the birth year and the distance to a nearby solar term. Each phase advances through the stem-branch sequence every ten years. This works like a state machine where the birth chart provides the initial state and the decade pillar updates at calculated transition points, though the machine merely models label shifts under stated rules.&lt;/p&gt;

&lt;p&gt;Attempting to hardcode all these rules into one rigid conditional block caused constant refactoring. The underlying modulo lookup is perfectly consistent; the divergence happens entirely during boundary parsing and input normalization.&lt;/p&gt;

&lt;p&gt;To clean up the system, I refactored the pipeline. Step one parses the timestamp, location, and timezone context. Step two converts the timestamp to working local time. Step three identifies the year and solar-term month. Step four calculates the sexagenary day index. Step five divides the day into two-hour intervals and derives the hour stem.&lt;/p&gt;

&lt;p&gt;I separated core cycle calculations from the boundary parsing rules. By keeping the schema modular and making boundary strategies configurable by calendar convention, the engine avoids declaring one school's edge definitions as universal truth.&lt;/p&gt;

&lt;p&gt;I am still unsure how much different schools' boundary choices alter charts across large population datasets, especially for births occurring near midnight or solar-term transitions. Accepting that distinct coordinate systems exist made the code far more maintainable.&lt;/p&gt;

&lt;p&gt;Not medical, legal, or financial advice. A cultural and cognitive framework for self-reflection; outputs vary by individual.&lt;/p&gt;

</description>
      <category>programming</category>
      <category>algorithms</category>
      <category>history</category>
      <category>culture</category>
    </item>
    <item>
      <title>I found a 60-step cycle in a 2,000-year-old calendar</title>
      <dc:creator>David Webb</dc:creator>
      <pubDate>Wed, 30 Sep 2026 13:45:03 +0000</pubDate>
      <link>https://dev.to/davidwebb915/i-found-a-60-step-cycle-in-a-2000-year-old-calendar-aoc</link>
      <guid>https://dev.to/davidwebb915/i-found-a-60-step-cycle-in-a-2000-year-old-calendar-aoc</guid>
      <description>&lt;p&gt;Title: I found a 60-step cycle in a 2,000-year-old calendar&lt;/p&gt;

&lt;p&gt;While parsing a sexagenary calendar record, I kept getting hung up on two counters: one wraps at 10, the other at 12, and both advance together. Their least common multiple is 60, so the pair repeats as a 60-step state machine. No fractional adjustments needed.&lt;/p&gt;

&lt;p&gt;That fixed sequence indexes cyclical time markers across days, months, and years. I wrote it as a discrete modulo generator using integer arithmetic alone. It shows how ancient astronomers maintained a continuous, drift-free epoch reference for more than two millennia.&lt;/p&gt;

&lt;p&gt;When I first started looking at BaZi, or Four Pillars records, I expected paragraphs of free-form symbolic prose. Instead, I found a compact record of four paired labels: year, month, day, and hour. Each pillar consists of one stem-branch pair drawn from two repeating counters. There are 10 Heavenly Stems and 12 Earthly Branches. If every stem could pair with every branch independently, you would get 120 combinations. But the traditional algorithm steps both lists simultaneously. Starting from Jia-Zi, the sequence proceeds to Yi-Chou, then Bing-Yin, and so on. Because both counters step in tandem, only 60 distinct pairings occur before the system returns to Jia-Zi.&lt;/p&gt;

&lt;p&gt;In code, this periodic state can be represented with a single integer scalar n. The stem index is evaluated as n mod 10, and the branch index as n mod 12. Incrementing n by 1 advances to the next paired symbol, while incrementing n by 60 returns the system to its starting pair. It operates like two clocks with different period lengths sharing a single step counter.&lt;/p&gt;

&lt;p&gt;This shared encoding makes cycle positions directly comparable across time scales, but those four pillars are not one giant clock ticking at a uniform speed. Each unit uses its own rules to find its current index. A day is divided by the hour branch into 12 two-hour intervals, such as Zi around 11 p.m. to 1 a.m. The hour stem is not an isolated counter looked up from clock time alone; its assignment is linked directly to the day stem.&lt;/p&gt;

&lt;p&gt;Beyond the initial birth chart, the system extends into longer ten-year phases derived from the month pillar. These decade pillars advance through the stem-branch sequence every ten years. This invites a state-machine analogy where the birth chart acts as the initial state, the decade pillar changes at a calculated boundary, and current calendar cycles provide additional inputs. However, this state machine only tells us how labels transition under defined rules; it does not establish physical causation.&lt;/p&gt;

&lt;p&gt;I am still unsure about which time-normalization convention is most faithful to historical practice: civil clock time, local mean solar time, or apparent solar time. What stands out to me as a data engineer is the structural elegance. Integer arithmetic alone maintains a periodic index without requiring floating-point adjustments.&lt;/p&gt;

&lt;p&gt;Not medical, legal, or financial advice. A cultural and cognitive framework for self-reflection; outputs vary by individual.&lt;/p&gt;

</description>
      <category>programming</category>
      <category>algorithms</category>
      <category>history</category>
      <category>culture</category>
    </item>
    <item>
      <title>I Modeled BaZi as a State Machine</title>
      <dc:creator>David Webb</dc:creator>
      <pubDate>Wed, 30 Sep 2026 13:38:27 +0000</pubDate>
      <link>https://dev.to/davidwebb915/i-modeled-bazi-as-a-state-machine-571f</link>
      <guid>https://dev.to/davidwebb915/i-modeled-bazi-as-a-state-machine-571f</guid>
      <description>&lt;p&gt;What happens when a birth time lands in the hour a solar term changes? A 30-minute error can swap an entire pillar.&lt;/p&gt;

&lt;p&gt;I spent the past year building a computation engine for this system and reverse-engineering its rules. I don't treat it as a mystical practice. I think of it as a modeling system written in ancient language. Once I translated the terms into engineering concepts, the underlying structures started to look familiar.&lt;/p&gt;

&lt;h2&gt;
  
  
  The graph under the classical terms
&lt;/h2&gt;

&lt;p&gt;The implementation starts with a directed graph of five nodes: Wood, Fire, Earth, Metal, and Water. Its edges have three action types:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;fuels&lt;/code&gt;: A's energy pattern nourishes B&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;shapes&lt;/code&gt;: A's pattern constrains and molds B&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;drains&lt;/code&gt;: A's pattern draws energy out of B&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Every classical rule maps onto the graph. The traditional vitality states a node can occupy are canonical network states under an external drive signal. Once the graph is in place, the rest is graph traversal.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the ten roles do
&lt;/h2&gt;

&lt;p&gt;The system defines ten archetypal roles, ten orthogonal dimensions for observing personality. I use a role matrix: for each input, every dimension gets an activation weight. In the product, we render them as interactive archetype animals because people parse the animals faster than abstract factors.&lt;/p&gt;

&lt;p&gt;The roles describe dynamics. One may fuel or drain you, and pressure changes which one activates.&lt;/p&gt;

&lt;h2&gt;
  
  
  Time has two layers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Long phases: The lifespan is segmented into extended phases, each with a different dominant graph configuration.&lt;/li&gt;
&lt;li&gt;Annual drive: Each year contributes an external input that perturbs the network.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Put together, these form what I call an energy-weather layer, a rolling state simulation over time. The weather comparison only goes so far. A forecast can say rain may be coming; packing an umbrella is your decision. The system leaves that decision alone.&lt;/p&gt;

&lt;h2&gt;
  
  
  The day node is the reference
&lt;/h2&gt;

&lt;p&gt;The baseline activation state is the day node among the four time pillars. I measure every other node relative to it using the graph's edges. That reference frame keeps the calculation from turning into interpretive mush.&lt;/p&gt;

&lt;h2&gt;
  
  
  The boundary cases take the work
&lt;/h2&gt;

&lt;p&gt;Most of the engineering effort went into handling boundaries.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;True solar time: Clock time follows your time zone's central meridian. Solar position at the actual birthplace can differ by tens of minutes. Usually that's harmless. Near an hour when a solar term changes, a 30-minute error can swap an entire pillar.&lt;/li&gt;
&lt;li&gt;Daylight saving: North America changed its DST rules in 2007, and the southern hemisphere shifts in the opposite direction. I delegate conversions to the platform's IANA time-zone data rather than maintaining a table by hand.&lt;/li&gt;
&lt;li&gt;Half-hour offsets: Adelaide is UTC+9:30; Kolkata is UTC+5:30. Any conversion that assumes whole-hour offsets breaks.&lt;/li&gt;
&lt;li&gt;Year and month boundaries: Lichun in early February sets the year boundary. Lunar New Year doesn't. Month boundaries follow solar terms, not calendar days. Two schools disagree about the day boundary at 23:00, so I exposed that choice as a config flag. It's a schema decision.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The part I'm still unsure about
&lt;/h2&gt;

&lt;p&gt;My working theory is that these systems began as observation-based models, recording patterns in human behavior in its time and place, using the formal language available then. I suspect the mystical framing accumulated in later centuries. I can't establish that history from the implementation, so I keep it as a theory.&lt;/p&gt;

&lt;p&gt;We show the computed pattern from someone's birth data. It doesn't tell them who they are.&lt;/p&gt;

&lt;p&gt;The full derivation is documented on the AcrosStar blog.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclaimer: this post is not medical, legal, or financial advice. The system described is a cultural and cognitive framework for self-observation; outputs vary by individual.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>programming</category>
      <category>algorithms</category>
      <category>history</category>
      <category>culture</category>
    </item>
    <item>
      <title>Launching on Product Hunt this Tuesday — the build-in-public log of a decision tool</title>
      <dc:creator>David Webb</dc:creator>
      <pubDate>Sun, 27 Sep 2026 12:10:07 +0000</pubDate>
      <link>https://dev.to/davidwebb915/launching-on-product-hunt-this-tuesday-the-build-in-public-log-of-a-decision-tool-1g71</link>
      <guid>https://dev.to/davidwebb915/launching-on-product-hunt-this-tuesday-the-build-in-public-log-of-a-decision-tool-1g71</guid>
      <description>&lt;p&gt;Six months ago I started logging my own decisions after noticing I kept repeating the same mistakes — not from lack of information, but from never looking at &lt;em&gt;how&lt;/em&gt; I decide. That habit became &lt;strong&gt;TangoEra&lt;/strong&gt;: a quiz that maps your decision profile (how you weigh risk, how you handle trade-offs, where you stall) plus a decision log that turns your real choices into data, so the profile sharpens with every decision you record.&lt;/p&gt;

&lt;p&gt;We're in free beta: 3 Starter report seats open every day.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Tomorrow (Wednesday) we're launching TangoEra on Product Hunt.&lt;/strong&gt; If decision fatigue is your thing, we'd genuinely love your support — and your honest feedback.&lt;/p&gt;

&lt;p&gt;Beta seats: &lt;a href="https://tangoera.com/beta-tester" rel="noopener noreferrer"&gt;https://tangoera.com/beta-tester&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;What decision are you procrastinating on right now?&lt;/p&gt;

</description>
      <category>producthunt</category>
      <category>buildinpublic</category>
      <category>saas</category>
      <category>productivity</category>
    </item>
    <item>
      <title>We Built a Decision-Making Tool: 30 Days of Funnel Data</title>
      <dc:creator>David Webb</dc:creator>
      <pubDate>Fri, 25 Sep 2026 16:32:22 +0000</pubDate>
      <link>https://dev.to/davidwebb915/we-built-a-decision-making-tool-30-days-of-funnel-data-4883</link>
      <guid>https://dev.to/davidwebb915/we-built-a-decision-making-tool-30-days-of-funnel-data-4883</guid>
      <description>&lt;p&gt;For the last 30 days we've been building &lt;strong&gt;TangoEra&lt;/strong&gt; — a decision-support tool that turns a short structured assessment into a visual "decision profile": how you weigh risk, time horizons, compensation vs. growth, and the other dimensions that actually drive your big calls.&lt;/p&gt;

&lt;p&gt;This is the honest build-in-public report: what we shipped, what the funnel data says, and the uncomfortable lesson week one taught us.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we built first
&lt;/h2&gt;

&lt;p&gt;We went against the usual indie playbook. Instead of shipping fast and instrumenting later, we spent the early weeks on the unglamorous layer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A 7-dimension assessment (quiz) with per-step telemetry, so we can see exactly where people drop off&lt;/li&gt;
&lt;li&gt;A results/paywall flow with UTM-tagged sources (blog CTA, embedded quiz, result page) so every channel is separately measurable&lt;/li&gt;
&lt;li&gt;Three lead-capture pages wired into the same event pipeline&lt;/li&gt;
&lt;li&gt;An analytics-events worker streaming into a queryable dataset (we learned the hard way that eventually-consistent key-value lists lie to you at small volume — direct SQL on the event table is the only read we trust now)&lt;/li&gt;
&lt;li&gt;An SEO/content layer: a decision-framework blog, Open Graph cards, hreflang for six languages&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;By launch-plus-one-week the engineering checklist was 79/79 green, 20 Pinterest pins were scheduled, and a 232-URL audit of the site came back clean.&lt;/p&gt;

&lt;h2&gt;
  
  
  Then we opened the window and measured
&lt;/h2&gt;

&lt;p&gt;We gave the funnel a clean measurement window (T0 + ~28 hours of stable, fully instrumented production) and pulled the authoritative dataset directly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;External funnel events: 0.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Not near-zero. Zero. The daily event ledger confirmed it: every single event in the window traced back to our own smoke tests and probes. No quiz completions, no CTA clicks, no leads — from real visitors — in the entire window. Site UVs sat in the "hundreds per day" range on a good day, and the distribution channels we'd stood up (Pinterest, directories) hadn't produced their first outbound click yet.&lt;/p&gt;

&lt;h2&gt;
  
  
  The lesson: we built a product and forgot a distribution engine
&lt;/h2&gt;

&lt;p&gt;Here's the part that stung. The conversion copy was fine. The instrumentation was fine. The drop-off analysis we wanted to run? &lt;strong&gt;Statistically impossible&lt;/strong&gt; — you can't analyze a funnel with &lt;code&gt;n = 0&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;When the sample size is zero, every A/B test, every headline tweak, every paywall experiment is theater. We had optimized a machine that nothing was flowing through.&lt;/p&gt;

&lt;p&gt;So week two got re-planned around a single sentence from our review doc: &lt;strong&gt;the funnel experiment is short on traffic, not copy.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;What changed:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Distribution became a first-class workstream, not an afterthought — one owner, daily cadence, its own backlog&lt;/li&gt;
&lt;li&gt;Content moved from "support docs for SEO" to an actual channel: decision-framework articles targeting long-tail queries, each with a hard CTA into the quiz&lt;/li&gt;
&lt;li&gt;We started measuring channels individually (separate UTM sources per surface) so that when traffic &lt;em&gt;does&lt;/em&gt; arrive, we already know which door it came through&lt;/li&gt;
&lt;li&gt;We set explicit kill criteria: a channel that can't produce outbound clicks in 30 days gets cut, no sentiment involved&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where the data actually helped
&lt;/h2&gt;

&lt;p&gt;Zero is a useful number. Because the instrumentation was solid &lt;em&gt;before&lt;/em&gt; traffic existed, we can state the null result with confidence instead of wondering if the analytics are lying. We also caught a real bug class early — our first read of the "zero" was itself wrong (a stale list API masked 11 probe events that &lt;em&gt;should&lt;/em&gt; have been there), which taught us to verify reads with strong-consistency queries before making decisions on them.&lt;/p&gt;

&lt;p&gt;That meta-lesson — instrument the instrument — turned out to be worth the week by itself.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's next
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Ship the distribution backlog (channels already live: Pinterest, startup directories, guest posts on decision-making content)&lt;/li&gt;
&lt;li&gt;Re-open the funnel window with the same rigor once inbound traffic crosses a threshold where numbers mean something&lt;/li&gt;
&lt;li&gt;Publish the week-2 review the same way: real data, no varnish&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you're building something too and you've also stared at a dashboard full of zeros — you're not behind, you're just at the step most people skip over. The fix isn't more features. It's more doors.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Follow along — we're posting these reviews weekly. And if decision-making content is your thing, the &lt;a href="https://tangoera.com/quiz?utm_source=devto&amp;amp;utm_medium=post&amp;amp;utm_campaign=w1-report" rel="noopener noreferrer"&gt;TangoEra quiz&lt;/a&gt; is free: three questions, one visual decision profile.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>buildinpublic</category>
      <category>indiehackers</category>
      <category>startup</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
