Command devlog #2
—Hello again proggers—
5 hours. For a patch-and-test pass. Not because the bugs were hard, because Windows decided the build machine needed an ATL error to ruin a chunk of the day.
ATL. of all things. ATL
Not a feature devlog this time. This one’s the boring-but-necessary kind — patching up bugs, wrestling with the models, and actually testing the stuff from devlog #1 before any of it gets near a push. Command’s Flutter/Dart, so at least the actual app-side debugging felt normal. The build machine did not.
Cat or dog? flutter test
Okay let’s get into it~
—Yap—
No new features this round. Just cleanup. Turns out shipping four features to local branches at once means devlog #2 is entirely “make sure the four features from devlog #1 actually hold up” — and then an 11 hour detour into Windows build tooling that had nothing to do with Dart at all.
—The Great Suffering—
1 — The Windows ATL Bug
The actual reason this took 5 hours. Build machine choked on an ATL-related error that had nothing to do with the Flutter/Dart side of things and everything to do with Windows being Windows. Ate a big chunk of the day before the rest of the work could even start.
a Flutter project should not know what ATL is, and yet
2 — General Patch-Up
Once the build machine cooperated, a round of small bug fixes across the existing work — nothing dramatic enough for its own section, just the usual pile of “that’s not supposed to do that” from actually testing instead of building.
3 — Model Issues
Ran into friction on the model side, the kind that only shows up once real data flows through instead of a clean test fixture.
4 — Testing, Actually
Spent real time testing rather than building, a different muscle entirely, and found what needed finding because of it.
—FAQ (no one asked these but they are here)—
Q: What is a “progger”?
A: A human programmer. You. The one who lost a chunk of the day to a Windows Active Template Library error in a Dart project.
Q: What is Command built in?
A: Flutter and Dart.
Q: What’s ATL doing in a Flutter build pipeline?
A: A very good question. Windows build tooling drags in native dependencies that have nothing to do with your actual language, and one of them decided to break.
Q: Why no new features this devlog?
A: Because four features from last time needed to survive testing, and then 5 hours went to a build machine instead.
Q: Is any of this pushed yet?
A: Still local. Getting closer, slower than planned.
—This is the end*—
*end for now, Windows build tools permitting
PIPER!!!