<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://danielphayward.com/feed.xml" rel="self" type="application/atom+xml" /><link href="https://danielphayward.com/" rel="alternate" type="text/html" /><updated>2026-03-09T17:01:59+00:00</updated><id>https://danielphayward.com/feed.xml</id><title type="html">Daniel Hayward’s Blog</title><subtitle>Essays and fiction from Daniel Hayward</subtitle><author><name>Daniel Hayward</name></author><entry><title type="html">Why bother with LinkedIn?</title><link href="https://danielphayward.com/li/" rel="alternate" type="text/html" title="Why bother with LinkedIn?" /><published>2026-03-02T00:00:00+00:00</published><updated>2026-03-02T00:00:00+00:00</updated><id>https://danielphayward.com/li</id><content type="html" xml:base="https://danielphayward.com/li/"><![CDATA[<p>I see a handful of types of posts on LinkedIn listed below in roughly most often to least.</p>

<ol>
  <li>Information about a product/service/”thought leader-y” (whether it’s being sold or not)</li>
  <li>AI doom / AI hype</li>
  <li>Policing how others use LI or telling others how to do their jobs</li>
  <li>Trending posts (Coldplay concert, create an action figure of yourself, year wrapped, current one is asking AI if I should walk to the carwash, that kind of thing)</li>
  <li>Rage/clickbait (some of this is funny to me, when people intentionally wrongly name famous people or characters)</li>
  <li>Other</li>
</ol>

<p>A note, I’ve posted a lot of product/service/”thought leader-y” type posts (this post might fall into that category, you be the judge). If you write in any or all of the other categories, great for you, do whatever makes you happy. I’m not saying how you should use LI.</p>

<p>But why do I go back to LI again and again?</p>

<p>Instead of thinking of LI as a platform, who are the people that post what I consistently find interesting?</p>

<p><a href="https://www.linkedin.com/in/cedchin/">Cedric Chin</a> highlights stuff he’s posted on his blog, he has permanently changed the way I think for the better.</p>

<p><a href="https://www.linkedin.com/in/thatjillian/">Jillian Richardson</a>, <a href="https://www.linkedin.com/in/louis-the-butterfield/">Louis Butterfield</a> and <a href="https://www.linkedin.com/in/tom-zehentner-cpa-a0591b5b/">Tom Zehentner</a> are the closest I get to weird LinkedIn, but I’ve also had conversations with them. It feels like they’re not being weird to be weird. Often I laugh or smile when reading them.</p>

<p><a href="https://www.linkedin.com/in/alexcboyd/">Alex Boyd</a> posts thoughtful comments and takes on current events related to his work and what’s going well with his holding company.</p>

<p><a href="https://www.linkedin.com/in/patrick-black-211023b3/">Patrick Black</a> posts literal explosions and I’ll hit like on every single post of his I see, but it’s the conversation underneath that’s interesting.</p>

<p><a href="https://www.linkedin.com/in/jordancrawford/">Jordan Crawford</a> and <a href="https://www.linkedin.com/in/michael-haimowitz/">Mike Haimowitz</a> are comment machines and the important bit is that they care a lot about what they’re saying. I have the strong suspicion that neither automate their use of LI.</p>

<p>One thing I notice is that these people are in sales or are content creators full time. They’re good at it. What you can’t see from the list is that I spend more time reading their comment conversations than their content.</p>

<p>I spent some time reflecting and wish there were more construction folks on this list; that’s my industry. I want to be involved with it, but I don’t see a ton of thoughtful reflection here, on this platform. It may be a function of how online people are or a fact of the industry itself.</p>]]></content><author><name>Daniel Hayward</name></author><category term="non-fiction" /><category term="business" /><category term="construction" /><summary type="html"><![CDATA[I see a handful of types of posts on LinkedIn listed below in roughly most often to least.]]></summary></entry><entry><title type="html">Mental Load</title><link href="https://danielphayward.com/mental-load/" rel="alternate" type="text/html" title="Mental Load" /><published>2026-02-26T00:00:00+00:00</published><updated>2026-02-26T00:00:00+00:00</updated><id>https://danielphayward.com/mental-load</id><content type="html" xml:base="https://danielphayward.com/mental-load/"><![CDATA[<p>Once upon a time, there was a little boy who’s parents did everything for him. When he was in high school, his mom packed his lunch and in college got care packages. Eventually he married a woman who planned every event, every holiday, every vacation with lists and did the grocery shopping. He packed his clothes to get ready and then would wait in the car jingling the change in his pocket. What was taking so long? Why are you so stressed dear, it’s vacation.</p>]]></content><author><name>Daniel Hayward</name></author><category term="fiction" /><summary type="html"><![CDATA[Once upon a time, there was a little boy who’s parents did everything for him. When he was in high school, his mom packed his lunch and in college got care packages. Eventually he married a woman who planned every event, every holiday, every vacation with lists and did the grocery shopping. He packed his clothes to get ready and then would wait in the car jingling the change in his pocket. What was taking so long? Why are you so stressed dear, it’s vacation.]]></summary></entry><entry><title type="html">Cancer Rate Charts</title><link href="https://danielphayward.com/cancer-rates/" rel="alternate" type="text/html" title="Cancer Rate Charts" /><published>2026-02-03T00:00:00+00:00</published><updated>2026-02-03T00:00:00+00:00</updated><id>https://danielphayward.com/Cancer-Rate-Charts</id><content type="html" xml:base="https://danielphayward.com/cancer-rates/"><![CDATA[<p>Last month, I saw some graphs about cancer rates post COVID with people in saying (but giving themselves plausible deniability) that the vaccine caused a huge spike in cancer rates.  They didn’t cite their sources and the graphs themselves weren’t identifiable as coming from a specific place, so I went to <a href="https://seer.cancer.gov/statfacts/html/all.html">the National Cancer Institute’s</a> website to look at the data.</p>

<p><strong>1978-2022 Cancer Rate per 100k Population</strong></p>

<p><img src="/assets/images/Cancer-Rates-1978-2022.png" alt="image-20260203134445415" /></p>

<p>There is only data through 2022 because cancer incidence takes 22 months for the NIH to compile, which seems very long to me but ostensibly it is because they are being thorough. The significant drop is in 2020, my guess is that screening dropped off significantly in that year, but that’s just a hunch. Maybe 45 years is too many look at all at once except to see the broadest of trends.</p>

<p>Here’s just the last 13 years.</p>

<p><strong>2009 to 2022 Cancer Rate per 100k Population</strong></p>

<p><img src="/assets/images/Cancer-Rates-2009-2022.png" alt="image-20260203134734430" /></p>

<p>To me, this at least seems like a big nothing burger. Death rate from cancer is slowly decreasing over time mostly like it has been for close to 45 years. So if this is the information, what about the graphs that I saw?</p>

<p>They changed the axes of some of the charts so they didn’t start at zero and mucked around with the years so that they were comparing disparate years and axes with the whole purpose of making the variation in numbers seem more drastic than it is.</p>

<p>Doing this unintentionally is bad form, doing it on purpose is lying.</p>]]></content><author><name>Daniel Hayward</name></author><category term="non-fiction" /><category term="essay" /><category term="health" /><summary type="html"><![CDATA[Last month, I saw some graphs about cancer rates post COVID with people in saying (but giving themselves plausible deniability) that the vaccine caused a huge spike in cancer rates. They didn’t cite their sources and the graphs themselves weren’t identifiable as coming from a specific place, so I went to the National Cancer Institute’s website to look at the data.]]></summary></entry><entry><title type="html">Case Study: Denver International Airport</title><link href="https://danielphayward.com/dia/" rel="alternate" type="text/html" title="Case Study: Denver International Airport" /><published>2026-01-30T00:00:00+00:00</published><updated>2026-01-30T00:00:00+00:00</updated><id>https://danielphayward.com/dia</id><content type="html" xml:base="https://danielphayward.com/dia/"><![CDATA[<p>Below is a case-study of the Denver International Airport. This is a mega-construction project with a final cost to the city of Denver of $6.8 billion. The text below is taken from <a href="https://www.gao.gov/products/t-rcedaimd-95-184?utm_source=danielphayward.com">GAO-95-184</a>, which is a government accountability report. Even though I’ve modified the text, it has largely been by removing it for clarity.</p>

<p>At the end there’s a link to my marked up version of this case study. If you choose to review this as a case study, here are some <a href="https://commoncog.com/how-note-taking-can-help-you-become-an-expert/#how-do-you-construct-a-cft-hypertext-system-for-yourself?utm_source=danielphayward.com">rough directions</a>, though the whole article is well worth your time.</p>

<h1 id="denver-international-airport">Denver International Airport</h1>

<h2 id="overview">Overview</h2>

<p><a href="https://en.wikipedia.org/wiki/Stapleton_International_Airport">Stapleton</a> was a major airline hub , was close to downtown, and had recently undergone $100 million in improvements. However, its capacity was reduced in bad weather, and nearby residents opposed expansion because of airport noise. In 1988, the City and County of Denver (both hereafter referred to as the City) made a preliminary agreement to acquire land for a new airport. In May 1988, voters in Adams County approved annexation of the land for the airport.</p>

<p>With a design-build PDM, the City joined with a joint-venture engineering, architecture, and airport-design firm. Together, they coordinated and ensured the quality of some 61 design contracts, 134 construction contractors, and over 2,000 subcontractors . These contractors and subcontractors would be responsible for building terminals, concourses, roadways, parking lots, and more than 33 miles of runways and taxiways.</p>

<p>In 1989, the City began to solicit bids for construction without obtaining formal input on the airport’s design from the airlines. In negotiations with these major tenants to sign gate leases, the City agreed to some very large and significant redesign. These decisions triggered far-reaching changes to the design and construction of DIA’s buildings and systems, many of them in mechanical, electrical, and telecommunications systems that are complex and difficult to coordinate. For example, at Continental Airlines’ suggestion, the City moved the international gates away from the north side of the main terminal to its Concourse A and built a passenger bridge from Concourse A to the main terminal, duplicating the function of a below-ground “people-mover” system.</p>

<p>United Airlines also requested substantial modifications when it negotiated an agreement with the City. Most significantly, United requested an automated baggage handling system for Concourse B to ensure that nearly all of its transferring passengers’ bags reached flights very quickly. At that time, the City planned to allow each airline to develop its own baggage system as long as this system did not interfere with any airportwide automated baggage system that the City might wish to install in the future.</p>

<p>The City had already explored the feasibility of installing an airportwide automated baggage system. In August 1990, a study commissioned by the City indicated that the highly complex and technically difficult state-of-the-art automated baggage system necessary for an airport of that size could probably not be built and tested in time to meet the scheduled opening date of October 1993. Specifically, the consultant’s report discussed the risks involved with five baggage system options. Following the consultant’s report, the City decided to open the airport using a conventional tug-and-cart baggage system. However, after United agreed to sign a 30-year lease in June 1991, the City decided to develop an automated system for the entire airport. According to the consultant’s report, the automated system selected was the one option that posed the greatest risk for not meeting the airport’s scheduled October 1993 opening date.</p>

<p>The opening of the airport was postponed at first because of construction delays and later because of problems with the automated baggage system, solely as a result of problems in getting the baggage system to work properly. Recognizing that the contractor for the baggage system could not predict when the automated baggage system would be operating, the City decided in July 1994 to build an alternative baggage system. February 28, 1995, was established as the airport’s new opening date.</p>

<p>DIA opened with the conventional baggage system providing service to all concourses, while a partially functioning automated baggage system served Concourse B. Specifically, the automated system was only operating for the luggage of United passengers on Concourse B–and only for normal size bags on outbound flights and large size bags, such as skis on inbound flights. The City expects the automated system to be fully operational for Concourse B in July 1995 and for Concourse A in August 1995. A decision on whether to extend the automated system to Concourse C–the most distant concourse from the terminal–will be made later. According to City officials, the carriers operating from Concourse C are satisfied with the alternative baggage system. The total construction cost of the baggage handling system–both the automated and conventional systems–is about $300 million to date.</p>

<h2 id="costs">Costs</h2>

<p>In November 1988, before selecting a site for the airport, the City developed a “conceptual estimate” of $1.3 billion for constructing a new airport. The earliest firm estimate for the cost of design and construction of the airport was contained in the May 1990. A bond series prospectus prepared by the City.</p>

<p>The City estimated that construction costs would abet at about $2.08 billion, excluding planning, land, interest, and finance charges. This estimate was revised in February 1992 to $2.7 billion. The principal reason for the growth in the cost was the additional requirements(<strong>operator input</strong>), facilities, such as tenant finishes in increasing apron sizes in the aircraft parking areas, widening and lengthening a concourse, expanding the parking structure, and adding the automated baggage system.</p>

<p>In February 1994, the City revised the estimated cost of construction to $2.92 billion. Two factors made up this increase: (1) $30 million, mainly for the terminal, electronic systems, and tenant improvements in concourses A and B, and (2) $194 million for additional facilities requested by the airlines. In September 1994, the project’s estimated cost was increased to include $51 million for a back-up baggage handling system and about $24 million for additional capital projects. As shown in table 1, the updated 
costs for the baggage systems brought the final construction cost at the airport’s opening to about $3 billion.</p>

<p>Financing costs were another major expense. These costs included about $958 million for capitalized interest and bond financing incurred before the airport’s opening. These expenses brought DIA’s estimated total cost to about $4.2 billion. When other costs, including those for air traffic control facilities, special airline facilities, into account, and rental car facilities, are taken into account total cost is estimated to be over $4.8 billion.</p>

<p>About half of the total federal funds for the project–$327 million–have been or will be spent on the construction of airfield pavement. Federal funds are also used for the construction of some airport buildings, land purchases, and support and engineering.</p>

<h2 id="quality-assurance-system">Quality Assurance System</h2>

<p>DIA’S total airfield pavement, 135,000 concrete panels, required placing approximately 5.3 million square yards of concrete. Construction work was performed simultaneously on 3+ runways and airport structures quality assurance inspectors were responsible for many different and aspects of the airfield’s construction.</p>

<p>We reviewed the City’s construction reports and project records for 3 of the 5 runway systems. These three systems comprised about 32,000, or 24%, of DIA’s 135,000 panels. These records showed that about 14,400, or 45%, of the 32,000 panels inspected did not conform to the contracts’ specifications when the concrete was initially placed by the contractors. About 3,000 contained clay and cracking, the remaining 11,300 were improperly installed by a contractor.</p>

<p>In most cases, the City required contractors to repair or replace panels that had problems at their cost per the contracts.</p>

<p>On one runway, concrete was contaminated with clay. This occurred because inspectors did not inspect the batch plant where the contractor was mixing concrete and the contractor failed to notice that a critical screen was missing. As a result, clay went into the mix for 10 days while paving continued. The contamination was discovered when clay was found on the pavement’s surface approximately 3 weeks later.</p>

<p>According to the City, the problems with the tie bars occurred because it was not always evident to contractors or inspectors that the machines installing the tie bars had not spaced them properly or that workers were not operating the machine properly. In July 1993, the City tested two runways and sections of other pavements on the airfields where it suspected that the contractors had improperly installed the tie bars. The tests, using special ground-penetrating radar (GPR) instruments, showed that the contractor had not installed tie bars in thousands of panels according to specifications, had installed too few or too many tie bars or had installed tie bars at the incorrect depth. The City allowed the contractor to make repairs by inserting additional tie bars. The City told us that all repairs related to the tie bars had been completed.</p>

<h2 id="quality-assurance-process-misses">Quality Assurance Process Misses</h2>

<p>We found some instances in which the City–through its quality assurance program–did not ensure that the contractor corrected the 10,374 identified problems with the pavement as required. To verify that the contractor had completed repairs related to the tie bars, we examined portions of two runways and taxiways on February 24, 1995. Many of the nonconforming panels we inspected had not been repaired. According to the design engineer for the taxiway, if tie bars are not properly installed, the joint between the panels could widen enough to cause settlement, faulting, and failure of the concrete on each side of a joint.</p>

<p>As a result of our examination, the City performed a 100% visual inspection of both runway systems on February 26, 1995, less than 48 hours before the airport opened. After determining that the 762 panels with too few tie bars had not been repaired, the City will require the contractor to begin repairs in June 1995. However, the City is not going to repair about 400 panels we identified as having too many tie bars. The City is not requiring the contractor to repair these panels because the City’s design engineers concluded that the performance or life of the runways will not be affected by the presence of too many tie bars. However, an FAA pavement expert with whom we discussed the issue told us that the presence of too many tie bars could cause panels to break and crack.</p>

<p>In addition to these unresolved problems, questions remain about whether problems exist on another runway and taxiway system. For example, GPR tests conducted at seven locations on the runway system identified a shortage of tie bars in each location. Specifically, 63% (210 of 334) of the panels tested did not conform with the contract’s specifications. The City told us that the panels had been repaired by the responsible contractor. While the City plans no additional tests, it does plan to visually inspect all the pavement.</p>

<p>In May 1995, FAA requested that the City provide its inspection records so the agency could ascertain how extensive DIA’s pavement problems are and whether the City’s GPR tests included an adequate sample of panels. FAA plans to use this information to determine if additional testing should be conducted.</p>

<h2 id="faa-is-correcting-construction-problems">FAA Is Correcting Construction Problems</h2>

<p>DIA’s principal air traffic control facilities–the TRACON building and the 300-foot air traffic control tower–have been subject to allegations of poor design and workmanship or substandard construction. Except for some problems with cracks and water damage at the TRACON facility that FAA is addressing, we have not found support for these allegations.</p>

<p>The $19 million TRACON building was completed in September 1992. By December 1992, FAA’s project engineers found several cracks along non-weight-bearing walls. According to FAA officials who have since reviewed the construction plans for the facility, a slip joint –a critical design element necessary to compensate for expected expansion and contraction of the soil underneath the building–was overlooked during design and construction. The soil has expanded beyond the 2-inch limit that the building’s foundation was designed to accommodate. FAA’s engineers assume that this movement is causing the building’s walls to crack. According to FAA, the floor’s movement has not affected the operations or safety of the facility. Repairs, to be paid for by FAA, are under way and are estimated to cost between $150,000 and $175,000; $150,000 had already been obligated as of March 1995.</p>

<p>FAA’s project engineers also found water damage on some of the TRACON facility’s walls where cracks had appeared because the contractor installed rain gutters that were too small. As a result, water backed up and seeped into several non-weight-bearing The contractor’s l-year warranty on the work had expired. Action is being taken to install exterior gutters at an estimated cost of between $90,000 to $100,000.</p>

<p>FAA examined the air traffic control tower after allegations were made that it was leaning. In March 1993, FAA surveyed the tower shaft and verified that it was standing straight as designed. In January 1995, FAA again surveyed the tower shaft and found that it was straight.</p>

<p><a href="/assets/pdfs/20260130-case-study-dia.pdf">Here’s a link to my marked up version</a></p>]]></content><author><name>Daniel Hayward</name></author><category term="non-fiction" /><category term="construction" /><category term="case-study" /><summary type="html"><![CDATA[Below is a case-study of the Denver International Airport. This is a mega-construction project with a final cost to the city of Denver of $6.8 billion. The text below is taken from GAO-95-184, which is a government accountability report. Even though I’ve modified the text, it has largely been by removing it for clarity.]]></summary></entry><entry><title type="html">Case Studay: Hanford Construction Cost</title><link href="https://danielphayward.com/hanford/" rel="alternate" type="text/html" title="Case Studay: Hanford Construction Cost" /><published>2026-01-30T00:00:00+00:00</published><updated>2026-01-30T00:00:00+00:00</updated><id>https://danielphayward.com/hanford</id><content type="html" xml:base="https://danielphayward.com/hanford/"><![CDATA[<p>Below is a case-study of the construction Hanford Vitrification Plant. This is a mega-construction project with the latest estimated cost to of $33-42 billion. The text below is taken from <a href="https://www.gao.gov/products/gao-06-602t?utm_source=danielphayward.com">GAO-06-602t</a>, which is a government accountability report. Even though I’ve modified the text, it has largely been by removing it for clarity.</p>

<p>At the end there’s a link to my marked up version of this case study. If you choose to review this as a case study, here are some <a href="https://commoncog.com/how-note-taking-can-help-you-become-an-expert/#how-do-you-construct-a-cft-hypertext-system-for-yourself?utm_source=danielphayward.com">rough directions</a>, though the whole article is well worth your time.</p>

<h1 id="hanford-construction-cost">Hanford Construction Cost</h1>

<h2 id="overview">Overview</h2>
<p>The Department of Energy (DOE) manages Hanford’s tank waste through two main contracts: a tank farm operations contract to maintain safe storage of the waste and to prepare it for retrieval, and a construction contract with Bechtel to design, construct, and commission the operation of a waste treatment plant.</p>

<p>The Hanford waste treatment construction project includes the construction of three primary processing facilities, a large analytical laboratory, and 23 supporting buildings on a 65 acre site. The three primary processing facilities are:</p>

<ul>
  <li>
    <p>the pretreatment facility, which receives the waste from the tank farms and separates it into its low-activity and high-level waste components;</p>
  </li>
  <li>
    <p>the high-level waste facility that immobilizes high-level waste for offsite disposal through a process known as vitrification, which mixes nuclear waste with molten glass; and:</p>
  </li>
  <li>
    <p>the low-activity waste facility, which vitrifies the low-activity waste for onsite disposal.</p>
  </li>
</ul>

<p>The waste treatment plant facilities are large and complex. For example, Bechtel estimates that the completed project will contain almost 270,000 cubic yards of concrete and nearly a million linear feet of piping. The largest building, the pretreatment facility, has a foundation the size of four football fields and is expected to be 12- stories tall.<sup id="fnref:1" role="doc-noteref"><a href="#fn:1" class="footnote" rel="footnote">1</a></sup></p>

<h2 id="cost-and-schedule">Cost and Schedule</h2>

<p>In 2000 at initial award, the contract price was $4.3 billion, including contractor fee and project contingencies. In 2003, Bechtel revised the estimate to $5.7 billion, based on changes DOE wanted to make in plant capacity and to correct for estimating errors and other problems that were already occurring on the project. In December 2005 estimate of the cost to complete the project, an estimate that DOE has not yet approved, totals about $10.5 billion plus contractor fee. Bechtel is still revising its estimate of the project costs, and the final estimate will very likely be higher. For example, in a February 2006 hearing before the Senate Armed Services Committee, the Secretary of Energy said that the final cost for the project could be nearly $11 billion.</p>

<p><strong>Figure 1: Progression of Cost Estimates for WTP Construction Project.</strong></p>

<table>
  <thead>
    <tr>
      <th>Year</th>
      <th>Cost Estimates</th>
      <th>Notes</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>December 2000</td>
      <td>$4.3 billion</td>
      <td>Initial contract price at award</td>
    </tr>
    <tr>
      <td>March 2003</td>
      <td>$5.7 billion</td>
      <td>Revised contract at negotiation</td>
    </tr>
    <tr>
      <td>March 2005</td>
      <td>$8.3 billion</td>
      <td>Bechtel’s revised cost estimate (not DOE approved)</td>
    </tr>
    <tr>
      <td>December 2005</td>
      <td>$10.5 billion</td>
      <td>Bechtel’s revised cost estimate (not DOE approved)</td>
    </tr>
    <tr>
      <td>February 2006</td>
      <td>$10.9 billion</td>
      <td>Energy Secretary’s cost estimate in Feb 2006 Senate hearing</td>
    </tr>
    <tr>
      <td>July 2018</td>
      <td>$33-42 billion</td>
      <td>U.S. Army Corps of Engineers, Parametric Evaluations of the Waste <br />Treatment and Immobilization Plant (Washington, D.C.: July 10, 2018)</td>
    </tr>
  </tbody>
</table>

<p><em>Note: These cost estimates do not include contractor performance fees and are not adjusted for inflation, about 15% over the time period.</em></p>

<p>In 2000, the estimated date to complete the construction of the waste treatment project was 2011. This date corresponded to the work schedule agreed to by DOE in the Tri-Party Agreement under which DOE was to begin operating the waste treatment facilities by 2011. However, Bechtel’s latest estimate, not yet approved by DOE, is that the construction project will be completed by 2017 or later, at least a 6-year extension and a 50 percent increase in the project’s schedule, (it was finally completed in 2023).</p>

<p>Furthermore, the revised cost and schedule estimates Bechtel developed in December 2005 are not final and will likely increase further. At least through the rest of 2006, DOE and Bechtel will continue to address identified technical and safety issues and incorporate additional design changes into its estimates. For example, Bechtel is currently reviewing several technical issues recently raised by a panel of experts DOE invited to study the project. Bechtel plans to incorporate changes resulting from the review into a new cost estimate. This revised estimate is expected to be complete in late May 2006. Once that estimate is available and DOE has completed its review of the estimate, DOE and Bechtel will need to agree on a revised contract price that incorporates any changes made to the project, including any changes to the fee that Bechtel can potentially earn. DOE officials do not expect to have these activities completed until late 2006</p>

<h2 id="shared-responsibility">Shared Responsibility</h2>

<p>Bechtel made a number of miscalculations on a broad range of activities when developing and revising its cost estimates for the project. Specifically, we found that Bechtel:</p>

<ul>
  <li>underestimated by more than 50 percent the engineering hours needed to design the facilities (a small portion of this increase was due to changes in seismic design criteria). The current estimate for design hours is now over 14 million hours<sup id="fnref:4" role="doc-noteref"><a href="#fn:4" class="footnote" rel="footnote">2</a></sup>.</li>
  <li>underestimated the cost of key commodities like steel. Steel prices climbed sharply once project construction started<sup id="fnref:5" role="doc-noteref"><a href="#fn:5" class="footnote" rel="footnote">3</a></sup>.</li>
  <li>incorrectly assumed that it could obtain an exception to the fire code and avoid applying a protective coating on some of the structural steel used in the facilities and instead use a less expensive sprinkler system<sup id="fnref:6" role="doc-noteref"><a href="#fn:6" class="footnote" rel="footnote">4</a></sup>.</li>
</ul>

<p>Bechtel also incorrectly estimated the amount of contingency funds that would be needed to account for project uncertainties. In 2000, Bechtel estimated that $500 million in contingency was needed. However, in its December 2005 estimate, Bechtel proposed that a total of $2.8 billion in contingency be allocated to the project<sup id="fnref:7" role="doc-noteref"><a href="#fn:7" class="footnote" rel="footnote">5</a></sup>. The $2.8 billion in contingency funds included $1.76 billion to address technical and programmatic risks outside the current scope of the project and an additional reserve of about $1 billion for potential future problems not yet identified.</p>

<p>Finally, Bechtel was ineffective at ensuring that the completed facilities would meet nuclear safety requirements. In March 2006, DOE’s Office of Enforcement issued a report documenting a number of different safety problems with the construction project, including a failure to (1) include safety requirements in design documents<sup id="fnref:8" role="doc-noteref"><a href="#fn:8" class="footnote" rel="footnote">6</a></sup>, (2) identify and use the correct design codes and safety standards, and (3) track design changes to ensure purchased materials and supplies were consistent with those changes<sup id="fnref:9" role="doc-noteref"><a href="#fn:9" class="footnote" rel="footnote">7</a></sup>. These failures led to significant problems. For example, Bechtel ordered approximately 70 tanks with incorrect structural specifications to ensure the quality of their welds. These tanks, that will be located in inaccessible areas of the waste treatment plant, were in various stages of fabrication. Had this problem not been identified, the quality of welds for all of these tanks could have been flawed. One tank had already been installed using these incorrect specifications before the problem was discovered. The tank was installed because neither the supplier nor Bechtel had performed the required weld inspection. Furthermore, when the welds were first repaired the subcontractor used incorrect welding rods, requiring more rework to repair the repairs.</p>

<p>In addition, in September 2005, Bechtel discovered errors that had been made in structural steel calculations for the laboratory facility[^2]. These potentially serious errors included design specifications that were incorrect and discrepancies between engineering calculations and design drawing specifications, which led to replacing steel already purchased and correcting hundreds of engineering drawings. Of significant concern, a 2005 DOE-sponsored survey found that some construction and engineering employees were reluctant to raise safety concerns to Bechtel management, fearing reprisal[^25].
[^2]: An example of <strong>skill deficit</strong> in engineering, possibly compounded by <strong>motivated reasoning</strong>.
[^25]: An example of commitment to ignorance, Bechtel management created this environment and it succeeded.</p>

<p>In our view, DOE’s management of the project has been flawed, as evidenced by (1) adopting a fast-track approach to design and construction activities that both created and exacerbated problems and (2) failing to exercise adequate and effective oversight of contractor activities, both of which contributed to cost and schedule increases.</p>

<p>DOE’s decision to pursue a fast-track, design-build approach under which technology development, facility design, and construction activities were carried out concurrently has proven to be regrettable<sup id="fnref:10" role="doc-noteref"><a href="#fn:10" class="footnote" rel="footnote">8</a></sup>. DOE adopted the fast-track approach because of commitments made under the Tri-Party Agreement to have facilities operating by 2011, and to treat all of the tank waste by 2028<sup id="fnref:11" role="doc-noteref"><a href="#fn:11" class="footnote" rel="footnote">9</a></sup>. However, using a fast-track approach for nuclear facilities is considered “high risk,” and is not recommended for designing and constructing one-of-a-kind, or first-of-a-kind complex nuclear facilities. DOE’s own project management guidance cautions against using this approach for complex facilities. For example, DOE Order 413.3 cautions that a design-build approach should only be used in limited situations, such as when work scope requirements are well defined, projects are not complex, and technical risks are limited.</p>

<p>Furthermore, the project approach included optimistic assumptions<sup id="fnref:13" role="doc-noteref"><a href="#fn:13" class="footnote" rel="footnote">10</a></sup> that virtually every major safety, technology, regulatory, and nuclear material acquisition uncertainty could be resolved while facilities were being constructed at an unusually fast pace for the largest, most complex, first-of-a-kind, nuclear waste treatment plant in the United States<sup id="fnref:12" role="doc-noteref"><a href="#fn:12" class="footnote" rel="footnote">11</a></sup>. Less than one year after construction began, DOE was already experiencing problems with construction activities outpacing design<sup id="fnref:14" role="doc-noteref"><a href="#fn:14" class="footnote" rel="footnote">12</a></sup>, technology problems that were affecting the critical path of the construction project, contractor safety control inadequacies, and outdated facility seismic criteria. Despite these problems, DOE insisted on continuing its fast-track design-build approach under its accelerated cleanup plan until early 2005<sup id="fnref:16" role="doc-noteref"><a href="#fn:16" class="footnote" rel="footnote">13</a></sup>. At that point, the effect of these and other unresolved issues, contractor performance problems, and signs of significant cost growth and schedule delays caused DOE to direct Bechtel to significantly slow construction, rework the design, and reevaluate safety, seismic, and regulatory requirements.</p>

<p>Under nuclear industry guidance, which recommends that facility design be essentially complete before construction begins, major environmental, technological, and regulatory issues can be resolved in advance of construction. The benefit of this process is that most uncertainties are resolved before major capital is at risk, and the potential for project delay is significantly reduced<sup id="fnref:17" role="doc-noteref"><a href="#fn:17" class="footnote" rel="footnote">14</a></sup>. On this project, under the fast track approach, actual schedule delays of more than two years have occurred, contributing to more than 1,000 workers being laid off, and work on the two largest waste treatment facilities coming to a halt.</p>

<p>GAO, the Safety Board, and others have criticized DOE in the past for using the fast-track approach for large, complex first-of-a-kind nuclear cleanup facilities. We issued reports in 1993, and again in 1998, that were critical of DOE for using an approach that differs so significantly from nuclear industry guidelines for constructing complex nuclear facilities. The Safety Board cautioned in June 2002, and again in March 2004, that a fast-track, design-build approach could lead to expensive plant modifications or to the acceptance of increased public health and safety risks. In June 2004, we recommended that DOE avoid using a fast-track approach to designing and constructing its complex nuclear facilities. The department accepted this recommendation, but apparently believes that it does not apply to this project. At the time of our 2004 report, the department could not identify a single instance where it had successfully used the approach to construct a large, complex nuclear cleanup facility. Despite the fact that DOE has never been successful with this approach on any complex nuclear cleanup project, Bechtel reported in its most recent cost and schedule estimate that a “fast-track engineering, procurement, and construction” approach is a standard commercial approach for large projects and the best approach for a schedule-driven project.</p>

<p>DOE’s lack of oversight of Bechtel’s activities has also been unfortunate. DOE did not ensure adherence to normal project reporting requirements and, as a result, status reports provided an overly optimistic assessment of progress on the project. For example, in January 2005, DOE’s project status report indicated that costs and scheduled work to date were proceeding as planned. However, Bechtel was not providing accurate information<sup id="fnref:19" role="doc-noteref"><a href="#fn:19" class="footnote" rel="footnote">15</a></sup>. The project almost always appeared to be on schedule because Bechtel adjusted the project baseline schedule to match actual project results. In addition, DOE headquarters oversight officials were generally unaware<sup id="fnref:18" role="doc-noteref"><a href="#fn:18" class="footnote" rel="footnote">16</a></sup> of the full extent of the problems with the project.</p>

<p>DOE is responsible for ensuring that its activities follow nuclear safety requirements and generally receives no outside regulatory oversight of nuclear safety. Contributing to the problem, DOE’s internal safety oversight had been significantly reduced since 2000. Key responsibilities to ensure quality control of contractors were placed under the responsibility of the DOE project manager who also had primary responsibility for meeting project cost and schedule targets<sup id="fnref:20" role="doc-noteref"><a href="#fn:20" class="footnote" rel="footnote">17</a></sup>. In late 2003, DOE began recognizing some of the nuclear safety problems on the project but many of these problems dated back to 2002, or earlier. Finally, in 2005 and 2006, according to the WTP project manager, DOE withheld a total of $800,000 in performance fee from Bechtel for industrial and nuclear safety problems, but problems continued. In 2006, DOE assessed a civil penalty of $198,000 for a number of nuclear safety violations<sup id="fnref:21" role="doc-noteref"><a href="#fn:21" class="footnote" rel="footnote">18</a></sup>. DOE also recently increased the number of staff assigned to oversee safety activities.</p>

<h2 id="technical-challenges">Technical challenges</h2>
<p>In 2002, the Safety Board began expressing concerns that the seismic standards used to design the facilities were not based on the most current ground motion studies and computer models, and were not based on geologic conditions present directly under the construction site. After more than 2 years of analysis and discussion, DOE contracted for a new seismic analysis that confirmed the Safety Board’s concerns that the seismic criteria were not “sufficiently conservative” for the two largest treatment facilities–the high-level waste facility and the pretreatment facility. Revising the seismic criteria caused Bechtel to recalculate thousands of engineering estimates and to rework[^30] thousands of design drawings to ensure that tanks, piping, cables, and other equipment in these facilities were adequately anchored. Bechtel determined that the portions of the building structures already constructed were sufficiently robust to meet the new seismic requirements. By December 2005, however, Bechtel estimated that engineering rework and other changes to tanks and other equipment resulting from the more conservative seismic requirement would increase project costs by about $750 million to $900 million and result in a 26 month schedule delay.</p>

<p>In 2003, potential problems with the pulse jet mixers caused project construction delays. Bechtel initially planned to rely on computer modeling to confirm that the mixer would successfully keep the tank waste uniformly mixed. However, because these mixers were designed to be placed in “black cells” in the pretreatment facility where they could not be repaired or modified after operations began because of the high levels of radiation in the cells, mixer failure was considered high risk. Given this risk, in April 2003, just 9 months before the design configuration for the mixers was to be completed, Bechtel decided to conduct laboratory tests of the mixers to ensure that they would successfully mix the tank waste. Based on laboratory performance testing, Bechtel found that the mixers did not adequately work. Consequently, the mixers had to be re-designed. The tanks that were to house the mixers also had to be redesigned with greater structural support to accommodate more forceful mixing pumps and other modifications. DOE spent about two years addressing problems with the pulse jet mixers. According to DOE’s project manager, Bechtel has completed the testing and design modifications for the mixers. As of May 2005, this problem had contributed more than $300 million to the project’s cost growth.</p>

<p>In June 2004, we reported on the possibility of hydrogen gas building up in the plant’s tanks, vessels, and piping systems, and noted that the buildup of flammable gas in excess of safety limits could cause significant safety and operational problems. Although DOE and Bechtel have been aware of this problem since 2002, the problem has not been fully resolved. As of March 2006, Bechtel continued to assess how to resolve this technical problem but has not identified final solutions. In April 2005, Bechtel estimated that this problem contributed about $90 million to the project’s cost growth.</p>

<p>In March 2006, an external technology review identified another technological problem called “line plugging,” involving the potential that solid and liquid radioactive and hazardous wastes could plug waste treatment facility piping systems during treatment operations. Described as the most serious problem the external group identified, the report emphasized that unless corrected, this flaw could prevent the plant from operating successfully. The review concluded that the treatment plant’s piping systems could begin plugging within days to a few weeks of operational start up. The external review did not estimate the potential cost and schedule impact of correcting this problem, but concluded that DOE identify and consider the corrective actions needed to resolve the problem. Bechtel plans to address these actions in its final cost and schedule estimate due in late May 2006<sup id="fnref:22" role="doc-noteref"><a href="#fn:22" class="footnote" rel="footnote">19</a></sup>.</p>

<p><a href="/assets/pdfs/20260130-case-study-hanford.pdf">Here’s a link to my marked up version.</a></p>
<div class="footnotes" role="doc-endnotes">
  <ol>
    <li id="fn:1" role="doc-endnote">
      <p><strong>coordination complexity</strong> - the facility is large, many sub-contractors will be involved and the quantities are enormous. The site is something like 57 acres. <a href="#fnref:1" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:4" role="doc-endnote">
      <p>pretty significant <strong>skill deficit</strong> <a href="#fnref:4" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:5" role="doc-endnote">
      <p>An example of <strong>skill deficit</strong> in estimating, possibly compounded by <strong>motivated reasoning</strong>, maybe even competing incentives. <a href="#fnref:5" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:6" role="doc-endnote">
      <p>This seems like <strong>exceptionalism</strong>. Why do construction estimators / owners confidently assert that certain parts of the code or requirements won’t apply to them? Often, it is because they get away with this. <a href="#fnref:6" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:7" role="doc-endnote">
      <p>What is typical contingency on construction projects? Does that change for mega projects? This is a doubling of contingency change and I know in the end, this still wasn’t enough, the total project is estimated (in 2025) to cost $33-42 billion <a href="#fnref:7" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:8" role="doc-endnote">
      <p>This isn’t just a <strong>skill deficit</strong> with Bechtel, the design documents should have included them, this was a significant issue with DOE management of the project. This will require <strong>in-flight design</strong>. <a href="#fnref:8" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:9" role="doc-endnote">
      <p><strong>change management</strong> seems to be a significant problem - especially when design changes are significant. I see “tracking changes” problems present in many large projects, and in my current work for a large utility contractor. <a href="#fnref:9" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:10" role="doc-endnote">
      <p>Regrettable indeed! The project has blown up from 6 years and ended up being 23 years and went from $4.3 billion to $33-42 billion. <a href="#fnref:10" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:11" role="doc-endnote">
      <p>It seems like there is some tacit understanding that has DOE pushing the timeline and continually shooting themselves in the foot. Is it politics? Ego? Hanford has been cleaning up since 1989 at this point, why rush everything? I won’t be able to learn. <a href="#fnref:11" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:13" role="doc-endnote">
      <p>An example of <strong>exceptionalism</strong>, and I do see this with contractors and projects that I’ve been on. People do not always know what rules they can and cannot work around. An example of ignoring experts usually working out well would lead to ignoring them even when they shouldn’t be, possibly an example of <strong>hard constraints</strong>. <a href="#fnref:13" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:12" role="doc-endnote">
      <p>This is exactly the opposite of the guidance from DOE Order 413.3, it goes against better judgement. An example of <strong>first-build</strong> concept. <a href="#fnref:12" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:14" role="doc-endnote">
      <p>An example of results from <strong>in-flight design</strong>. I see this on many of the projects from experience. <a href="#fnref:14" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:16" role="doc-endnote">
      <p>This is when Bush Jr. started his second term in office, I’m not sure if there were politics involved in this decision timing syncing up with this or it’s just happenstance. <a href="#fnref:16" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:17" role="doc-endnote">
      <p>If design resolves the problems that almost always plague mega-projects (think iron rule) why would DOE fast track anything, ever? <a href="#fnref:17" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:19" role="doc-endnote">
      <p>An example of when people will distort systems or data in order to avoid consequences, whether willful or ignorant. <a href="#fnref:19" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:18" role="doc-endnote">
      <p>This might be an example of a commitment to ignorance, Bechtel didn’t want to know about the problems. See also above related to the safety culture. <a href="#fnref:18" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:20" role="doc-endnote">
      <p>This is an example of competing incentives and lack of internal controls. <a href="#fnref:20" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:21" role="doc-endnote">
      <p>At this point, the almost $1 million is 1/10,000 of what they’ve charged the project.  If Bechtel was getting a 1% margin (they were getting more) on their cost, that’s 100x than .01%. <a href="#fnref:21" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
    <li id="fn:22" role="doc-endnote">
      <p>A.  What kind of delusion made Bechtel think they would solve this problem in 3 months when they hadn’t solved the hydrogen build-up problem for 4 years? It might be an example of <strong>motivated reasoning</strong> and <strong>exceptionalism</strong>. <br /> B. This problem (and the hydrogen build up) aren’t problems caused by people, they are physics or technical problems. An example of <strong>hard constraints</strong>,No amount of bullying or cajoling can make physics comply. I think it is possible that leaders equate these two kinds of problems. The Denver International Airport Baggage System is another case like this. <a href="#fnref:22" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
  </ol>
</div>]]></content><author><name>Daniel Hayward</name></author><category term="nuclear" /><category term="construction" /><category term="case-study" /><category term="non-fiction" /><summary type="html"><![CDATA[Below is a case-study of the construction Hanford Vitrification Plant. This is a mega-construction project with the latest estimated cost to of $33-42 billion. The text below is taken from GAO-06-602t, which is a government accountability report. Even though I’ve modified the text, it has largely been by removing it for clarity.]]></summary></entry><entry><title type="html">Umwelt</title><link href="https://danielphayward.com/umwelt/" rel="alternate" type="text/html" title="Umwelt" /><published>2026-01-21T00:00:00+00:00</published><updated>2026-01-21T00:00:00+00:00</updated><id>https://danielphayward.com/Umwelt</id><content type="html" xml:base="https://danielphayward.com/umwelt/"><![CDATA[<p>Umwelt is a German word (no people has better words or engineering) that means roughly “sensed environment.” I’d like to take this idea a little forward, umwelt was first conceived in the world of biology. It includes the idea of threats and resources but largely refers to what a creature can sense in a physical domain. In the wikipedia article about it it also refers to what resources and threats a creature can “see” based on their experience.</p>

<p>You and I can grow up in the same house, go to the same schools, have the same parents, but if you and I see the world differently then we have a different umwelt.  You never knew what it was to have an older sister, or friends that lived on the same street. I never knew what it was like to live a thousand lives through authors, or what it would have been like to have a childhood having read Narnia. I never knew what it was like to be in a STEM program in high school because, though I was smart I “<a href="https://youtu.be/xkXpcs_an80?si=bIYeCGobStCNLsCU?utm_source=danielphayward.com">never applied myself.</a>”</p>

<p>But if you can’t see it, then it isn’t a part of <em>your</em> umwelt. A mantis shrimp has a wildly different experience than a tuna fish. The <a href="https://www.boem.gov/newsroom/ocean-science-news/peacock-mantis-shrimp?utm_source=danielphayward.com">mantis shrimp has 16 photoreceptors</a> (humans have 3), they can see UV and polarized light. If you can’t sense something; it isn’t a part of your sensed environment. A non-biological example is after my wife and I bought a Toyota Rav4, I noticed them everywhere. Before having a little girl, I didn’t notice how people have few boundaries with children (and often don’t think of them as people).</p>

<p>But you can change part of what you experience by paying attention to different things. There’s the common saying “<a href="https://xkcd.com/703/?utm_source=danielphayward.com">you don’t know what you don’t know</a>,” so how do you pay attention to things you don’t know about? By having different experiences, learning new techniques, and best by spending time with different kinds of experts. We learn to see more like the people we spend time with. You could lurk in online forums, reading <em>good</em> books, start a new hobby, or put into practice things you “know.”</p>

<p>The best way to be able to see better is by iterating over a process and getting feedback. Ideally, the feedback is from an expert, someone whose judgment you can pull on. If you’re practicing writing, coding, or creating any kind of document that you can upload to an LLM, then that works but caveat emptor<sup id="fnref:1" role="doc-noteref"><a href="#fn:1" class="footnote" rel="footnote">1</a></sup>.</p>

<p>So go.</p>

<p>Go write a story, work with wood, crochet (or knit, I refuse to know the difference), draw a seascape, and find someone who lives in that domain to critique your work.</p>

<h2 id="essays-for-more-reading">Essays for more reading:</h2>

<p><a href="https://www.henrikkarlsson.xyz/p/learningsystem?utm_source=danielphayward.com">The Learning System</a>, <a href="https://www.henrikkarlsson.xyz/p/christopher-alexanders-architecture?utm_source=danielphayward.com">Christopher Alexander’s Architecture</a>, <a href="https://www.henrikkarlsson.xyz/p/popular-education-in-sweden-much?utm_source=danielphayward.com">Popular Education in Sweden</a>, <a href="https://commoncog.com/putting-mental-models-to-practice/?utm_source=danielphayward.com">Expert Decision Making</a></p>

<div class="footnotes" role="doc-endnotes">
  <ol>
    <li id="fn:1" role="doc-endnote">
      <p>I’d recommend reading Cedric Chin’s “<a href="https://commoncog.com/how-to-use-ai-without-becoming-stupid/?utm_source=danielphayward.com">How to Use AI without Becoming Stupid</a>” for a few examples and exploration of using LLMs well. The gist is that you should not offload your judgement to an LLM, my opinion is that LLMs will never become meaning making entities, but they are pushing the boundaries of what that means and calling into question lots of types of “work.” <a href="#fnref:1" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
    </li>
  </ol>
</div>]]></content><author><name>Daniel Hayward</name></author><category term="non-fiction" /><category term="essay" /><summary type="html"><![CDATA[Umwelt is a German word (no people has better words or engineering) that means roughly “sensed environment.” I’d like to take this idea a little forward, umwelt was first conceived in the world of biology. It includes the idea of threats and resources but largely refers to what a creature can sense in a physical domain. In the wikipedia article about it it also refers to what resources and threats a creature can “see” based on their experience.]]></summary></entry><entry><title type="html">Reading Plans</title><link href="https://danielphayward.com/reading-plans/" rel="alternate" type="text/html" title="Reading Plans" /><published>2026-01-19T00:00:00+00:00</published><updated>2026-01-19T00:00:00+00:00</updated><id>https://danielphayward.com/Reading-Plans</id><content type="html" xml:base="https://danielphayward.com/reading-plans/"><![CDATA[<p>As is pretty common for Christians, they think about reading through the Bible this coming year around January.</p>

<p><a href="https://gracecityportland.org/our-team?utm_source=danielphayward.com">My pastor</a> mentioned the best reading plan that he had come across was Robert Murray’s reading plan. I found a <a href="https://mcheyne.info/mcheyne-reading-plan/?utm_source=danielphayward.com">copy online</a> included with the reading plan is a warning and encouragement (from 1862), which I had never seen before with a Bible reading plan.</p>

<p>The warning is that by following a reading plan your faith may become stale, you may become self-righteous or self condemning (different outcomes of the same belief), and the Word may lose it’s awe-inspiring nature. I had heard these warnings before or had experience with them generally.</p>

<p>There are five encouragements two of which I have heard many times, it is good that we would read through the entire Bible in a year and it will be easier to open the Bible when you don’t have to decide what to read.</p>

<p>The other encouragements are about reading in community: people will have things besides gossip to discuss, parents will know what their children are reading and can reflect on that with them, the pastor will be able to preach on what the congregation has been reading, and we will think of others who we know are reading the same passages as us and will better be able to pray for them.</p>

<p>At first I thought to myself, “how quaint, thinking that many people in my close community would be reading the same passages continually.” It shows how alone I am, and how alone I suspect others are. This is a reshaped idea of the church calendar. My in-laws go to a liturgical church and have a pretty good idea of what the sermon will be about every single week and have for years.</p>

<p>There are positives and negatives to this. From conversations with them they don’t think that every passage gets attention. But, their pastors also might have a harder time hiding from preaching on uncomfortable sections of the Bible.</p>

<p>The pastors also don’t feel any pressure or waste time making sermon series. Making graphics, three to five alliterative points, or gathering passages from across the Bible to make a point. The topic is set, so to speak.</p>

<p>What would it be like to be reading the same passages on a daily basis as your friends, your family, your pastor.</p>

<p>How much better is:</p>

<ul>
  <li><em>“I’ve been thinking about the smoking pot and Abraham, isn’t that so weird.”</em></li>
  <li><em>“Why do you think Leviticus is written the way it is?”</em></li>
  <li><em>“Why did God ask Abraham why Sarah laughed?”</em></li>
</ul>

<p>Than:</p>

<ul>
  <li><em>“Did you see the game last night?”</em></li>
  <li><em>“How’s work been?”</em></li>
  <li><em>“Crazy that the powerball is so high.”</em></li>
  <li><em>“It’s awfully warm for January, huh?”</em></li>
</ul>]]></content><author><name>Daniel Hayward</name></author><category term="non-fiction" /><category term="essay" /><category term="Christian" /><summary type="html"><![CDATA[As is pretty common for Christians, they think about reading through the Bible this coming year around January.]]></summary></entry><entry><title type="html">Prefab Homes for Us?</title><link href="https://danielphayward.com/prefab-homes-for-us/" rel="alternate" type="text/html" title="Prefab Homes for Us?" /><published>2026-01-16T00:00:00+00:00</published><updated>2026-01-16T00:00:00+00:00</updated><id>https://danielphayward.com/Prefab-Homes-for-Us</id><content type="html" xml:base="https://danielphayward.com/prefab-homes-for-us/"><![CDATA[<p>In Sweden 85% of new single family homes and 40% of multifamily homes are partially or completely built in a factory, compared to the US at roughly half that.</p>

<p>Brian Potter wrote a <a href="https://www.construction-physics.com/p/should-us-homebuilders-emulate-sweden?utm_source=danielphayward.com">thoughtful essay</a> about prefab homes, it is well worth a read. Why doesn’t the US have more prefab homes? The gist of it is the cost of Swedish homes are 70% more than US homes and they aren’t any faster at building them. When building anything in the US, speed is one of the most important factors. There are a variety of reasons that prefab homes are still a good idea for the Swedes (i.e. reducing time on site, quality control) but he buries the lead.</p>

<p>The cost of building multi family homes was roughly flat from 2017-2023 in Sweden (or decreasing, if you convert it to USD). Even if this isn’t entirely because of prefabrication, it’s a strong hint that construction companies in the US should look to for ideas.</p>]]></content><author><name>Daniel Hayward</name></author><category term="non-fiction" /><category term="construction" /><summary type="html"><![CDATA[In Sweden 85% of new single family homes and 40% of multifamily homes are partially or completely built in a factory, compared to the US at roughly half that.]]></summary></entry><entry><title type="html">PAYSTUB PORTAL</title><link href="https://danielphayward.com/payroll-portal/" rel="alternate" type="text/html" title="PAYSTUB PORTAL" /><published>2026-01-09T00:00:00+00:00</published><updated>2026-01-09T00:00:00+00:00</updated><id>https://danielphayward.com/Payroll-Portal</id><content type="html" xml:base="https://danielphayward.com/payroll-portal/"><![CDATA[<blockquote>
  <p>[!NOTE]</p>

  <p>If you work at a large organization, you’ll get the joke, if you aren’t here’s a taste of what it’s like to sit under some flourescent lights for a few minutes. The names of the innocent (there are none) and guilty (there are many) have been changed.</p>

</blockquote>

<p><strong>From:</strong> Bill Buffnone [zrqfmsptu@babycompany.com]
 <strong>Sent:</strong> Friday, January 9, 2026 1:36:53 PM
 <strong>To:</strong> Romy Hellmann [ftnfeflbuj@babycompany.com]; Zack Jones [ltuzhjbynd@babycompany.com]; Neal Lake [tigstgyibz@giantcompany.com]; Hinkley Pinkley [wppjreeryk@petite.co]; Cuppa Joe [aksvxhqhaq@babycompany.com]; Hakuna Matata [noworries@babycompany.com]; Gob GoHARD [soHARD@littlegroup.io]; Nicole Maclennan [LxrdNdrqOu@petite.co]; CORAL Notifications ; All Users[_HM-AllUsers@giantcompany.com]; Non-All Users [_HW-AllUsers@giantcompany.com]; WoodStockOffice ws-all@smallco.com; Bob Loblaw [KXWtwpqkIJ@petite.co]; Brad Paisley [cqdbzroxju@petite.co]; Jeff Epistein [itlgojvbsp@petite.co]
 <strong>Cc:</strong> Ryan Gorman [rgorman@petite.co]; Freezer Fridge [refridge@petite.co]; Mi Opinion [opinion@petite.co]; Craig Cravats [mtn@babycompany.com]; BC HR [BC_HR@babycompany.com]; IW_catime [catime@petite.co]; Bobby Shorts [shorts@giantcompany.com]
 <strong>Subject:</strong> Re: PAYSTUB PORTAL</p>

<p>My paystub portal is working.</p>

<p>Sam Buffnone</p>

<p>Field Mechanic</p>

<p>Baby Company</p>

<p>909-800-7000</p>

<hr />
<p>On Jan 9, 2026, at 1:38 PM, Greg Harbaugh [gharbaugh@babycompany.com] wrote:</p>

<p>Yes, please</p>

<p>Please don’t Get <a href="https://aka.ms/o0ukef">Outlook for iOS</a></p>

<hr />
<p><strong>From:</strong> Robert Struble [vwkgcbuyfh@giancompany.com]
 <strong>Sent:</strong> Friday, January 9, 2026 1:36:53 PM
 <strong>To:</strong> Romy Hellmann [ftnfeflbuj@babycompany.com]; Zack Jones [ltuzhjbynd@babycompany.com]; Neal Lake [tigstgyibz@giantcompany.com]; Hinkley Pinkley[wppjreeryk@petite.co]; John Bushel [aksvxhqhaq@babycompany.com]; Hakuna Matata[noworries@babycompany.com]; Gob GoHARD [soHARD@littlegroup.io]; Nicole Maclennan [LxrdNdrqOu@petite.co]; CORAL Notifications ; All Users[_HM-AllUsers@giantcompany.com]; Non-All Users [_HW-AllUsers@giantcompany.com]; WoodStockOffice ws-all@smallco.com; Bob Loblaw [KXWtwpqkIJ@petite.co]; Brad Paisley [cqdbzroxju@petite.co]; Jeff Epistein [itlgojvbsp@petite.co]
 <strong>Cc:</strong> Ryan Gorman [rgorman@petite.co]; Freezer Fridge [refridge@petite.co]; Mi Opinion [opinion@petite.co]; Craig Crags[mtn@babycompany.com]; IWHR [IW_HR@babycompany.com]; IW_catime [catime@petite.co]; Bobby Shorts [shorts@giantcompany.com]
 <strong>Subject:</strong> Re: PAYSTUB PORTAL</p>

<p>Hey guys, let’s take this topic and subject off of a group email please</p>

<p>Get <a href="https://aka.ms/o0ukef?utm_source=danielphayward.com">Outlook for iOS</a></p>

<hr />
<p><strong>From:</strong> Romy Hellmann [ftnfeflbuj@babycompany.com]
 <strong>Sent:</strong> Friday, January 9, 2026 10:35:02 AM
 <strong>To:</strong> Zack Jones [ltuzhjbynd@babycompany.com]; Neal Lake [tigstgyibz@giantcompany.com]; Hinkley Pinkley[wppjreeryk@petite.co]; John Bushel [aksvxhqhaq@babycompany.com]; Hakuna Matata[noworries@babycompany.com]; Gob GoHARD [soHARD@littlegroup.io]; Nicole Maclennan [LxrdNdrqOu@petite.co]; CORAL Notifications ; All Users[_HM-AllUsers@giantcompany.com]; Non-All Users [_HW-AllUsers@giantcompany.com]; WoodStockOffice ws-all@smallco.com; Bob Loblaw [KXWtwpqkIJ@petite.co]; Brad Paisley [cqdbzroxju@petite.co]; Jeff Epistein [itlgojvbsp@petite.co]
 <strong>Cc:</strong> Ryan Gorman [rgorman@petite.co]; Freezer Fridge [refridge@petite.co]; Mi Opinion [opinion@petite.co]; Craig Cravass [mtn@babycompany.com]; IWHR [IW_HR@babycompany.com]; IW_catime [catime@petite.co]; Bobby Shorts [shorts@giantcompany.com]
 <strong>Subject:</strong> RE: PAYSTUB PORTAL</p>

<p>Sorry, just getting caught up with emails, is there something wrong with paystub portal?</p>

<p>Sent from my Spaceship</p>

<hr />
<p><strong>From:</strong> Zack Jones [ltuzhjbynd@babycompany.com] 
 <strong>Sent:</strong> Friday, January 9, 2026 11:56 AM
 <strong>To:</strong> Neal Lake [tigstgyibz@giantcompany.com]; Hinkley Pinkley[wppjreeryk@petite.co]; John Bushel [aksvxhqhaq@babycompany.com]; Hakuna Matata[noworries@babycompany.com]; Gob GoHARD [soHARD@littlegroup.io]; Nicole Maclennan [LxrdNdrqOu@petite.co]; CORAL Notifications ; All Users[_HM-AllUsers@giantcompany.com]; Non-All Users [_HW-AllUsers@giantcompany.com]; WoodStockOffice ws-all@smallco.com; Bob Loblaw [KXWtwpqkIJ@petite.co]; Brad Paisley [cqdbzroxju@petite.co]; Jeff Epistein [itlgojvbsp@petite.co]
 <strong>Cc:</strong> Ryan Gorman [rgorman@petite.co]; Freezer Fridge [refridge@petite.co]; Mi Opinion [opinion@petite.co]; Craig Crass[mtn@babycompany.com]; IWHR [IW_HR@babycompany.com]; IW_catime [catime@petite.co]; Bobby Shorts [shortshorts@giantcompany.com]
 <strong>Subject:</strong> Re: PAYSTUB PORTAL</p>

<p>Can everyone stop replying to all</p>

<p>Sent from my Samsung</p>

<hr />
<p><strong>From:</strong> Freddy Ocean [tigstgyibz@giantcompany.com]
 <strong>Sent:</strong> Friday, January 9, 2026 8:54:56 AM
 <strong>To:</strong> Hinkley Pinkley[wppjreeryk@petite.co]; John Bushel [aksvxhqhaq@babycompany.com]; Hakuna Matata[noworries@babycompany.com]; Gob GoHARD [soHARD@littlegroup.io]; Nicole Maclennan [LxrdNdrqOu@petite.co]; CORAL Notifications ; All Users[_HM-AllUsers@giantcompany.com]; Non-All Users [_HW-AllUsers@giantcompany.com]; WoodStockOffice ws-all@smallco.com; Bob Loblaw [KXWtwpqkIJ@petite.co]; Brad Paisley [cqdbzroxju@petite.co]; Jeff Epistein [itlgojvbsp@petite.co]
 <strong>Cc:</strong> Ryan Gorman [rgorman@petite.co]; Freezer Fridge [refridge@petite.co]; Mi Opinion [opinion@petite.co]; Craig Ass[mtn@babycompany.com]; IWHR [IW_HR@babycompany.com]; IW_catime [catime@petite.co]; Bobby Shorts [shortershorts@giantcompany.com]
 <strong>Subject:</strong> RE: PAYSTUB PORTAL</p>

<p><em>+</em></p>

<hr />
<p><strong>From:</strong> Hinkley Pinkley [wppjreeryk@petite.co] 
 <strong>Sent:</strong> Friday, January 9, 2026 11:36 AM
 <strong>To:</strong> John Bushel [aksvxhqhaq@babycompany.com]; Hakuna Matata[noworries@babycompany.com]; Gob GoHARD [soHARD@littlegroup.io]; Nicky Sticks [LxrdNdrqOu@petite.co]; CORAL Notifications ; All Users[_HM-AllUsers@giantcompany.com]; Non-All Users [_HW-AllUsers@giantcompany.com]; WoodStockOffice ws-all@smallco.com; Bob Loblaw [KXWtwpqkIJ@petite.co]; Brad Paisley [cqdbzroxju@petite.co]; Jeff Epistein [itlgojvbsp@petite.co]
 <strong>Cc:</strong> John Jinglehimer [shmidt@petite.co]; Freezer Fridge [refridge@petite.co]; My Opinion [opinion@petite.co]; Craig S[mtn@babycompany.com]; IHR [MYHR@babycompany.com]; 
 <strong>Subject:</strong> Re: PAYSTUB PORTAL</p>

<p>What is the ETA for pay stub portal to be repaired? I can log in, I had to reset my password but my last pay check of the year for 2025 or the first one of 2026, WE 12/28/25. Is not available to view. I have several employees questioning their pay checks from the storm we were on and I have no way to verify the correct hours were paid out, please update. Thank you.</p>

<p>Go Get <a href="https://aka.ms/o0ukef?utm_source=danielphayward.com">Outlook for iOS</a></p>

<hr />
<p><strong>From:</strong> John Bushel[aksvxhqhaq@babycompany.com]
 <strong>Sent:</strong> Thursday, January 8, 2026 3:22:02 PM
 <strong>To:</strong> Hakuna Matata[noworries@babycompany.com]; Gob GoHARD [soHARD@littlegroup.io]; Nicole Maclennan [LxrdNdrqOu@petite.co]; CORAL Notifications ; All Users[_HM-AllUsers@giantcompany.com]; Non-All Users [_HW-AllUsers@giantcompany.com]; WoodStockOffice ws-all@smallco.com; Bob Loblaw [KXWtwpqkIJ@petite.co]; Brad Paisley [cqdbzroxju@petite.co]; Jeff Epistein [itlgojvbsp@petite.co]
 <strong>Subject:</strong> Re: PAYSTUB PORTAL</p>

<p>I had same issue today and updated password. Issue resolved</p>

<p>Get <a href="https://aka.ms/o0ukef?utm_source=danielphayward.com">Outlook for iOS</a></p>

<hr />
<p><strong>From:</strong> Hakuna Matata[noworries@babycompany.com]
 <strong>Sent:</strong> Thursday, January 8, 2026 6:19:42 PM
 <strong>To:</strong> Gob GoHARD [soHARD@littlegroup.io]; Nicole Maclennan [LxrdNdrqOu@petite.co]; CORAL Notifications ; All Users[_HM-AllUsers@giantcompany.com]; Non-All Users [_HW-AllUsers@giantcompany.com]; WoodStockOffice ws-all@smallco.com; Bob Loblaw [KXWtwpqkIJ@petite.co]; Brad Paisley [cqdbzroxju@petite.co]; Jeff Epistein [itlgojvbsp@petite.co]
 <strong>Subject:</strong> RE: PAYSTUB PORTAL</p>

<p>I am not able to log in as well – it tells me it does not recognize my username or password??</p>

<p><strong>Mahalo,</strong></p>

<p>Hakuna
PA III, PA
<strong>Baby Company</strong> |[noworries@babycompany.com]**</p>

<hr />
<p><strong>From:</strong> Gob GoHARD [soHARD@littlegroup.io] 
 <strong>Sent:</strong> Thursday, January 8, 2026 1:17 PM
 <strong>To:</strong> Nicole Maclennan [LxrdNdrqOu@petite.co]; CORAL Notifications ; All Users[_HM-AllUsers@giantcompany.com]; Non-All Users [_HW-AllUsers@giantcompany.com]; WoodStockOffice ws-all@smallco.com; Bob Loblaw [KXWtwpqkIJ@petite.co]; Brad Paisley [cqdbzroxju@petite.co]; Jeff Epistein [itlgojvbsp@petite.co]
 <strong>Subject:</strong> Re: PAYSTUB PORTAL</p>

<p>Nicole, you should probably contact Giant Company HR. That email address is hr@giantcompany.com</p>

<p>Gob GoHARD</p>

<p><em>(213) 267-9932</em></p>

<hr />

<p><strong>From:</strong> Nicole Refürp [LxrdNdrqOu@petite.co]
 <strong>Sent:</strong> Thursday, January 8, 2026 4:15:15 PM
 <strong>To:</strong> CORAL Notifications; All Users[_cjmkwvyson@giantcompany.com]; Non-All Users - [vapxkp@giantcompany.com]; WoodStockOffice ws-all@smallco.com; Bob Loblaw[KXWtwpqkIJ@petite.co]; Brad Paisley [cqdbzroxju@petite.co]; Jeff Epipen [itlgojvbsp@petite.co]
 <strong>Subject:</strong> RE: PAYSTUB PORTAL</p>

<p>I so I have a question, I’m no longer able to log in to my paystub portal with my credentials I have been using. Is this an issue you guys are aware of and correcting or what am I supposed to do?</p>

<p>Nicole Refürp</p>

<hr />

<p><strong>From:</strong> CORAL Notifications
 <strong>Sent:</strong> Monday, January 5, 2026 11:41 AM
 <strong>To:</strong> _X1 - All Users [_X1-AllUsers@giantcompany.com]; _X2 - All Users [_X2-AllUsers@giantcompany.com]; WoodStockOffice ws-all@smallco.com; Bob Loblaw [KXWtwpqkIJ@petite.co]; Aurora Borealis [cqdbzroxju@petite.co]; Jeff Epistein [itlgojvbsp@petite.co]
 <strong>Subject:</strong> PAYSTUB PORTAL</p>

<p>PAYSTUB PORTAL</p>

<p>We are currently experiencing technical issues with the paystub portal affecting paychecks with a pay date of January 2, 2026.</p>

<p>Our IT team is actively working to resolve the issue. A follow-up notification will be sent as soon as access is fully restored.</p>

<p><a href="https://www.goodreads.com/quotes/123557-god-s-final-message-to-his-creation-we-apologize-for-the?utm_source=danielphayward.com">We apologize for the inconvenience.</a></p>]]></content><author><name>Daniel Hayward</name></author><category term="fiction" /><category term="humor" /><summary type="html"><![CDATA[[!NOTE] If you work at a large organization, you’ll get the joke, if you aren’t here’s a taste of what it’s like to sit under some flourescent lights for a few minutes. The names of the innocent (there are none) and guilty (there are many) have been changed.]]></summary></entry><entry><title type="html">Lily Wins the Argument</title><link href="https://danielphayward.com/argument" rel="alternate" type="text/html" title="Lily Wins the Argument" /><published>2025-12-29T00:00:00+00:00</published><updated>2025-12-29T00:00:00+00:00</updated><id>https://danielphayward.com/argument</id><content type="html" xml:base="https://danielphayward.com/argument"><![CDATA[<p>Ethan walked into the large, dimly lit living room with the manner of a man uncertain if he was entering a birdhouse or a room packed with dynamite; he was prepared for either. The minor argument during lunch hadn’t come to a clear end, leaving the question of whether Lily was inclined to continue or let it go. She sat in an armchair by the tea table, her posture stiff; in the subdued light of a December afternoon, Ethan’s glasses didn’t help much to read her expression.</p>

<p>As a way to ease the tension, he remarked about the soft religious glow. He or Lily would often make such comments between 4:30 and 6 on winter evenings; it was part of their married routine. There wasn’t a customary response to it, but Lily provided none.</p>

<p>Maximus lounged on the Persian rug, enjoying the firelight without much regard for Lily’s mood. His lineage was as purely Persian as the rug, and his fur was reaching its peak beauty in its second winter. The page-boy, who had a penchant for artistic names, had christened him Maximus. If left to themselves, Ethan and Lily might have chosen something simpler like Cat, but they weren’t insistent.</p>

<p>Ethan poured himself some tea. Seeing that Lily remained quiet, he readied himself for another attempt.</p>

<p>“My remark at lunch was more of a hypothetical,” he said. “You seem to be taking it personally.”</p>

<p>Lily maintained her defensive silence. The bullfinch filled the silence with a tune from the last drama they had been watching. Ethan began to feel a bit down. Lily wasn’t sipping her tea. Maybe she wasn’t feeling well. But Lily was never reserved when feeling unwell; she’d often declare, “Nobody knows the suffering I endure from indigestion.” It was one of her favorite lines, though lack of knowledge could only have been due to not listening. There was enough information about her indigestion to fill a book.</p>

<p>Yet, Lily didn’t seem unwell.</p>

<p>Ethan began to think he was being treated unfairly; naturally, he began to make concessions.</p>

<p>“I suppose,” he ventured, taking a central spot on the hearth rug next to Maximus, “I might be at fault. If it’ll make things better between us, I’m willing to strive for a better life.”</p>

<p>He wondered vaguely how that would be possible. Temptations came to him, tentatively and without insistence, like a neglected paperboy asking for a Christmas tip in February for no better reason than that he hadn’t received one in December. He had no intention of yielding to them any more than he intended to buy fish knives or fur scarves that are advertised year-round. Still, there was something impressive in this voluntary renunciation of potentially lurking misdeeds.</p>

<p>Lily showed no signs of being impressed.</p>

<p>Ethan looked at her nervously over his glasses. Being on the losing side of an argument with her was nothing new. Losing while on a monologue was a new humiliation.</p>

<p>“I’ll go get ready for dinner,” he declared, trying to inject some sternness into his voice as he reached the door.</p>

<p>At the door, a final pang of weakness made him make one more plea.</p>

<p>“Aren’t we being a bit silly?”</p>

<p>But Lily still said nothing.</p>

<p>Maximus stretched his velvet paws and hopped onto a bookshelf right under the bullfinch’s cage. It was the first time he’d seemed to notice the bird, but he was carrying out a long-held theory with mature precision. The bullfinch, who had fancied himself a king, suddenly shrank into a third of his usual size. He began to flutter and chirp frantically. He had cost twenty-seven shillings, not counting the cage, but Lily made no move to intervene. She’d been deceased for two hours.</p>]]></content><author><name>Daniel Hayward</name></author><category term="fiction" /><summary type="html"><![CDATA[Ethan walked into the large, dimly lit living room with the manner of a man uncertain if he was entering a birdhouse or a room packed with dynamite; he was prepared for either. The minor argument during lunch hadn’t come to a clear end, leaving the question of whether Lily was inclined to continue or let it go. She sat in an armchair by the tea table, her posture stiff; in the subdued light of a December afternoon, Ethan’s glasses didn’t help much to read her expression.]]></summary></entry></feed>