Historic American Buildings Survey/Historic American Engineering Record/Historic American Landscapes Survey - About this Collection
Measured drawings, photographs, and written historical and architectural information for structures and sites dating from the 17th-20th centuries in the U.S. and its territories. Documentation for more than 43,000 sites and structures; records being added.
The Power of 10: Rules for Developing Safety-Critical Code
The Power of 10 Rules were created in 2006 by Gerard J. Holzmann of the NASA/JPL Laboratory for Reliable Software.[1] The rules are intended to eliminate certain C coding practices that make code difficult to review or statically analyze. These rules are a complement to the MISRA C guidelines and have been incorporated into the greater set of JPL coding standards.[2]
Schedule adherence: When 50% construction activities are off track
New benchmarks from 200+ construction projects reveal average schedule adherence rates across sectors and regions.
Digital Construction Week | Innovation in the built environment
The UK’s leading event for innovation and technology in the built environment. Explore the latest developments in digital construction.
Engineering management after the cost of code collapsed
I have been a director of engineering for a bit over three years now, and I still hear and read what I call the "old rules" repeated over and over: a director should not spend time coding, good work takes time, protect the team from the business, get consensus before
Single Stair Reform Bills are nearing a vote! Vote Yes on HB 5570 and 5571!
Single-Stair legislation would be a powerful reform to our outdated building code!
W Social and the ancient art of neighbourliness - We Can Just Do Things
Good behaviour matters more than good code
W Social and the ancient art of neighbourliness - We Can Just Do Things
Good behaviour matters more than good code
Local Env as Code: Is it possible yet
Guest post by Jan Van Bruggen, Developer Relations Lead at itopia In the past decade, we’ve seen the rise, standardization and meme-ification of “as code”: Infrastructure as Code, Monitoring as Code…
Better tools made Copilot code review worse. Here's how we actually improved it.
How migrating Copilot code review to shared Unix-style code exploration tools reduced review cost by reshaping agent workflows around pull request evidence.
Reflections on Declarative Configuration
Advantages and pitfalls of Infrastructure as Code, and the distinction between IaC and Declarative Configuration.
Does Code Cleanliness Affect Coding Agents? A Controlled Minimal-Pair Study
As autonomous coding agents see rapid adoption, their evaluation has primarily focused on task completion rates holding the target codebase fixed. This leaves a critical question unanswered: does the structural and stylistic quality, or ``cleanliness'' of the underlying code affect an agent's ability to navigate and modify it? To isolate the effect of code cleanliness from agent capability, we introduce an evaluation protocol built around minimal pairs: repositories that match on architecture, dependencies, and external behaviour, but differ on static-analysis rule violations and cognitive complexity. The pairs are constructed in both directions, by agent pipelines that either degrade a clean repository or clean a messy one. We author 33 tasks across six such pairs, evaluated through hidden tests at the application's public surface. Across 660 trials with Claude Code, code cleanliness does not change the agent's pass rate. However, it substantially alters the agent's operational footprint: agents working on cleaner code use 7 to 8% fewer tokens and reduce file revisitations by 34%. Our findings suggest that traditional maintainability principles remain highly relevant in the era of AI-driven development, shaping the computational cost and navigational efficiency of coding agents. Code cleanliness joins model choice, harness, and prompting as a factor that materially affects agent behaviours.
How Do Scientists Use Claude Code?
Measuring Claude Code adoption among 16,000 scientists on GitHub
In the 19th and early 20th centuries, building oversight in North America and Europe was minimal and inconsistent. Many cities relied on one final inspection, often conducted after completion or after occupancy had already begun. Many inspectors would issue a single “pass/fail” stamp of approval, and enforcement focused on obvious hazards rather than systematic verification of structure, materials, or systems.