What I learned from a 250 GB C:\Autodesk\WI folder
A field note on what the C:\Autodesk\WI folder is, why Autodesk installer files can pile up, and what I checked before cleaning disk space.
By Ahmed Revit Workflow
Owner / field desk
Ahmed
Ahmed owns the site and turns field-tested work into reusable notes for builders, BIM leads, and tool-minded teams.
- Beat
- BIM, Revit, automation, and practical technology notes
- Published
- 15 posts
By Ahmed 
BIM automation must survive handoff
Ahmed explains why BIM and Revit automation is only finished when another teammate can run it safely, understand the inputs, recover from mistakes, and trust the handoff.
By Ahmed BIM Revit Workflow
AI workflow demos should show the handoff file
Ahmed and Zack explain why AI workflow demos should show the exported file, review notes, cleanup path, and handoff evidence before claiming production value.
By Ahmed AI BIM Workflow
Dynamo cleanup scripts need a rollback plan
Ahmed explains why every Dynamo cleanup script needs a rollback plan before it touches live Revit models, parameters, views, or sheets.
By Ahmed Dynamo Revit Workflow
Family libraries need ownership before automation
Ahmed explains why Revit family libraries need named ownership, standards, review gates, and retirement rules before automation starts reorganizing content.
By Ahmed Revit BIM Workflow
How to decide whether a tool belongs in the pipeline
Ahmed gives BIM, AI, and creator teams a practical decision matrix for deciding whether a tool belongs in production, stays in experiments, or gets rejected.
By Ahmed AI BIM Workflow
Revit batch tools need a test model first
Ahmed explains why Revit batch tools should prove themselves on a small test model before touching production files, shared standards, or live deliverables.
By Ahmed BIM Revit Workflow
Revit cleanup scripts should write reports first
Ahmed explains why Revit cleanup scripts should produce reviewable reports before they rename, delete, rebind, or rewrite anything in a live model.
By Ahmed Revit BIM Workflow
Revit family automation needs boring naming rules
Ahmed explains why Revit family automation needs stable, boring naming rules before scripts, agents, or batch tools start touching production content.
By Ahmed Revit BIM Workflow
Revit shared parameter file traps I keep hitting
Ahmed turns repeated Revit shared-parameter mistakes into a practical checklist for names, GUIDs, bindings, schedules, and team handoff.
By Ahmed Revit BIM Workflow
Shared parameters are an interface
Ahmed explains why Revit shared parameters should be treated like an interface contract between models, families, schedules, tags, exports, and automation.
By Ahmed BIM Revit Workflow
When AI belongs in a BIM or creator workflow
Ahmed and Zack explain how to decide whether AI belongs in a BIM, Revit, 3D, or creator workflow by testing the handoff, risk, and cleanup path.
By Ahmed AI BIM Workflow
Static sites still need real provenance
Ahmed explains how a static Astro and Cloudflare blog can still run like a review-first publishing system with provenance, CI, and guarded deploys.
By Ahmed Workflow AI
Hello, subarashi.dev — what this is and isn't
Why I'm starting a working notebook on tech, automation, AI, Revit, and BIM - and the rules I'm setting before I forget them.
By Ahmed Workflow
Letting AI draft BIM posts without losing the plot
How AI assistants draft posts for this site: a small protocol, a review-first default, and a hard line about what I sign my name to.
By Ahmed AI Workflow BIM