{"id":3498,"date":"2026-02-24T23:58:58","date_gmt":"2026-02-24T23:58:58","guid":{"rendered":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2026\/02\/24\/the-dongle-died-at-midnight-winforms-agent-saved-my-german-moms-business-trip\/"},"modified":"2026-02-24T23:58:58","modified_gmt":"2026-02-24T23:58:58","slug":"the-dongle-died-at-midnight-winforms-agent-saved-my-german-moms-business-trip","status":"publish","type":"post","link":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2026\/02\/24\/the-dongle-died-at-midnight-winforms-agent-saved-my-german-moms-business-trip\/","title":{"rendered":"The Dongle Died at Midnight \u2013 WinForms Agent Saved my German Mom\u2019s Business Trip"},"content":{"rendered":"

An 82-year-old German industrial engineer, a 22-year-old UI framework, and an AI that finally understands WinForms Designer serialization walk into a hotel room at midnight. There\u2019s no punchline. Just a dead dongle and a dead \u2026 line. Well, I admit, it\u2019s sort of hard to believe, but how these three are connected is really no joke. But let\u2019s connect the dots, and start with my mom, who I\u2019d say is the main character in this absolutely true story.<\/p>\n

This post walks through the full journey \u2014 from capturing requirements in German via Teams, to transforming a messy transcript into an English specification using LLMs, to generating Designer-compatible WinForms code through cascaded prompting \u2014 and what it reveals about prompt-driven development.<\/p>\n

My mom is\u2014let\u2019s use the grammatically fitting tense here\u2014retiring<\/em>. Present Continuous. Emphasis on the -ing<\/em>. In 2007, she turned 65 and officially retired, but kept working in her profession as a REFA-engineer with her own, little but effective consultancy business. Since then, every autumn, she declares: \u201cNext February, I\u2019m definitely retiring for good.\u201d<\/p>\n

If you\u2019ve never heard of REFA, well, don\u2019t worry. It\u2019s a pretty European thing. Actually mainly used in Germany and the adjacent countries alright, and the methodology never really made it over the pond. We get to that later in more detail. In any case, the following story is not made up\u2014it\u2019s 100% true. It happened exactly as described here. Well, to be fair, it happened the way I remember it for those parts of the story where I didn\u2019t have notes or better memory aids. And I have quite a few of those aids, which, by the way, makes them an important part of the story\u2014but more on that also later.<\/p>\n

As if I do not have enough to do already<\/h2>\n

The day IT happened was a day when I had been particularly undisciplined. I looked at my Todo list, and once again it became painfully clear: you cannot make open items disappear by staring at them. I was supposed to write quite a few of those typical year-end reflection pieces for a series of colleagues and\u2014of course\u2014my manager. And that\u2019s something that never really flows easily from my fingertips. What was easier, though, was listening to Dara O\u2019Briain, my favorite comedian, who had somehow made his way into my current YouTube playlist.<\/p>\n

\u201c\u2026I\u2019m a numbers guy, I\u2019m a dweeb all right and I apologize, I am a bit of a nerd\u2026\u201d Oh, are you, Dara? Guess who else is and cannot concentrate. \u201c\u2026and I am sorry, if you\u2019re into homeopathy\u2014it\u2019s water! How often does this need to be said\u2026\u201d And before he could continue his rant about this particular field of medicine, my phone rang. Saturday, 1:30 PM Redmond time is pretty unusual for someone to call from here, which in my case makes Germany as the origin of the call more likely. But that\u2019s then again also concernedly late for Germany and could only mean one thing: my mom. My problem: I heard<\/em> the phone but couldn\u2019t see it. My definitely not Dara O\u2019Briain-compatible assumption: mobile phones are only physically present when you don\u2019t need them. The moment they ring, they teleport somewhere else. I tried to track-down the ringing, while Dara continued \u201c\u2026well, they get on my nerves with their \u2018well, science doesn\u2019t know everything.\u2019\u2014see, science knows it doesn\u2019t know everything\u2026 otherwise, it\u2019d stop!\u2026\u201d I had to join the laughter of the crowd. Noticing the ringing getting louder, and being literally on a good trajectory, I nodded while Dara continued: \u201c\u2026but just because science doesn\u2019t know everything doesn\u2019t mean you can fill in the gaps with whatever fairy tale most appeals to you\u2026\u201d Damn, Dara, I couldn\u2019t agree more. And, oh, there it was. The phone. My mom.<\/p>\n

German-style naming \u2013 \u201cVerband f\u00fcr Arbeitsstudien und Betriebsorganisation eV\u201d<\/h2>\n

Growing up in Germany, I always thought every German compound word starting with the prefix \u201cReich-\u201d would be so negatively connoted that I probably shouldn\u2019t even go near it. And I know, especially in the 80s and 90s, A LOT of my fellow Germans thought that way. So whenever friends and classmates from school asked, \u201cHey, what do your parents do?\u201d, I stated truthfully my dad is a traveling salesman, and \u2013 without going into explaining that REFA term any further \u2013 my mom was a REFA engineer. Which is not only true, it\u2019s also something nobody could really do anything with\u2014even<\/em> in Germany, where the whole REFA thing had been invented back in 1924. And although the original abbreviation\u2014not a secret, mind you\u2014\u201dReichs-Committee for Working-Time Determination\u201d was renamed around the 1970s to \u201cVerband f\u00fcr Arbeitsstudien und Betriebsorganisation e.V.\u201d (Work Studies and Business Organization Association), in German-speaking countries the REFA methodology for optimizing workplace ergonomics and time studies was and still is known pretty much exclusively by these four letters: REFA<\/a>. And the reason it is such an important part of the economy in the German-speaking area of Europe is that it is one of the very few methodologies which is accepted and agreed on by most of the unions and bigger companies\u2019 own work councils.<\/p>\n

\u201cHey, how are you doing?\u201d I asked my mom. \u201cDon\u2019t even get me started,\u201d she replied. \u201cHere, when I try to start it\u2026\u201d<\/p>\n

It took me a moment to find out what \u2018it\u2019 was. But from context and level of indignance, it was quickly pretty clear that she was talking about her very special, Windows Win32-based consulting\u2014or better: time-study\u2014software.<\/p>\n

She continued, \u201cit says something about a General Protection Fault in Model something-or-other, and then, well anyway, I can\u2019t take any time-span samples. And the support-folks already tried using Windows Quick Assist, hung around in my Surface (Go 3, let me add) for more than an hour, but they couldn\u2019t figure out anything meaningful either. I\u2019m here at my client\u2019s (\u2026industrial laundry plant\u2026) in Waibstadt, and I can\u2019t do \u2026!\u201d Well, let\u2019s not translate what she said next\u2014but know that she can \u201cswear like a Pipe Sparrow,\u201d as they say in German, although the correct translation of that bird is presumably Reed Bunting. We just call them Pipe Sparrows in German. Anyway. Conclusion: The reporting part of the software would run without the dongle, alright. But the time study module\u2014which was literally why she was there\u2014not a chance to get that repaired and running.<\/p>\n

So, What Happened to Her?<\/h2>\n

My mom uses a time study software from a reputable German ISV that specializes in REFA methodology. The principally very solid, well-designed software for the domain, maintained by professionals who actually understand industrial time studies, has one catch: the actual time tracking<\/em> functionality requires a hardware dongle. Classic software protection from an era when copy protection meant physical dongles, not cloud licensing.<\/p>\n

And here\u2019s where hardware reality meets the modern Surface ecosystem: The dongle uses USB-A. The Surface Go 3 \u2013 a remarkably light and portable Windows tablet that\u2019s perfect for walking industrial floors all day \u2013 has only USB-C. So naturally, my mom was using some kind of USB hub. Convenient, yes. Robust when you\u2019re carrying it between industrial ironer stations daily? Not so much.<\/p>\n

\"Surface<\/p>\n

Now, this is all assumptions, and bottom line: It also doesn\u2019t really matter (or rather didn\u2019t, when the effect of the symptoms became clear): Over time, either the hub itself developed a cable break, or the USB-C port on the Surface had simply fatigued from all that dangling weight. A dongle, mostly hanging off a hub hanging off a tablet that gets moved around industrial laundries? That\u2019s a mechanical failure waiting to happen. So, they tried, then I tried, but ultimately: no dice. The GPF was there to stay.<\/p>\n

Why Ask an 82-Year-Old on a 500-Mile Journey<\/h2>\n

So, here\u2019s the question: Why would an industrial laundry fly in (well, trust Deutsche Bahn to transport) an 82-year-old REFA time-study engineer from 500 miles away? The answer is: experience<\/em>. Specifically, experience in one critical aspect of REFA methodology that can\u2019t be automated. And here is where I\u2019d ask you to bear with me with some German terms: Starting with the so-called Leistungsgrad<\/em> (degree of performance) \u2013 a special form of visually and from observation assessed performance rating of employees, usually working in production plants.<\/p>\n

\"Photo<\/p>\n

When my mom conducts Zeitaufnahmen<\/em> (time studies), she\u2019s not just clicking a stopwatch. She\u2019s measuring Ablaufabschnitte<\/em> (process steps) \u2013 in the case of the ironer: grabbing laundry, clipping it in<\/a>, handling pieces that fall out \u2013 and for each step, she\u2019s estimating whether the worker is operating at 100% normal pace, faster, or slower. That judgment call, honed over decades, is what makes the resulting work values fair. Too generous, and the company overpays. Too strict, and workers can\u2019t achieve bonuses no matter how hard they try.<\/p>\n

This was important because this particular client had just installed new industrial ironers. These massive units process hundreds of kilograms of linens per hour, operated by teams of up to five workers per station. The company pays incentive wages: base salary plus bonuses when teams exceed the performance baseline. But to calculate that baseline fairly, you need accurate time studies. And for accurate time studies on new equipment, you need someone with the experience to judge \u201cnormal\u201d performance on day one.<\/p>\n

That\u2019s the win-win: The laundry gets a fair, union-approved wage system that improves productivity. The workers get transparent performance targets and real earning potential. And my mom gets to keep doing what she\u2019s loved doing for \u2013 let\u2019s not count the years too precisely.<\/p>\n

Why This Business Case Is a Perfect WinForms Scenario<\/h2>\n

Let\u2019s pause and recognize what we have here, because it matters for understanding why this is your absolute typical WinForms Line of Business application type, and also, why WinForms development has been so successful and popular (and honestly, still is):<\/p>\n

    \n
  1. It\u2019s culturally and geographically specific.<\/strong> REFA methodology is a Central European thing \u2013 primarily German-speaking countries. The terminology (Zeitaufnahme<\/em>, Ablaufabschnitt<\/em>, Leistungsgrad<\/em>) doesn\u2019t translate cleanly. This is industrial engineering born from post-war German manufacturing culture, still practiced today in ways that would seem antiquated to Silicon Valley but are perfectly rational in context.<\/li>\n
  2. It\u2019s incredibly niche.<\/strong> How many time study applications for incentive wage systems in industrial laundries exist? How many developers have ever heard of Zeitarten<\/em> (time types like \u201cmachine time\u201d, \u201chandling time\u201d, \u201cinterruption time\u201d)? This is domain knowledge that lives in REFA training books and practitioners\u2019 heads \u2013 not Stack Overflow threads.<\/li>\n
  3. It\u2019s exactly what WinForms was designed for.<\/strong> A specialized tool, very user-interaction demanding, for a specialized profession, running on a Surface tablet in an industrial environment. No web framework needed. No cloud dependency. Just a robust, offline-capable Windows application that does one thing really well: capture time measurements accurately.<\/li>\n<\/ol>\n

    This is the WinForms sweet spot: domain-specific, business-critical, and economically viable only because development effort can be contained. In the past, building such an application would require either (a) a developer spending weeks learning REFA methodology, or (b) a REFA expert learning to code \u2013 neither economically feasible for such a narrow use case. (But, just as a side-remark, often enough the main target audience for classic Visual Basic V4 to V6 at the time, and \u2013 for what it\u2019s worth \u2013 Python today.)<\/p>\n

    A Year Earlier: No Chance. But Now?<\/h2>\n

    Under the normal IT-industry circumstances we learned to love over the last 40 years, that phone call would at that point have reached nearly the finish line. It may have turned me into an amateur therapist \u2013 listening sympathetically, maybe offering to cover unexpected hotel costs. But that would have been it. But \u2013 something fundamentally shakes the industry up. And that\u2019s why and where I got bold for the first time in the IT space beyond the Microsoft walls \u2013 and also yet oddly confident at the same time. Because an idea popped into my head, which was: building a replacement application from scratch. From scratch? In a weekend? While she\u2019s on-site? Was I kidding myself?<\/p>\n

    See, this was no longer constrained by the status quo of Rapid Application Development from just a year ago \u2013 the discipline that made WinForms famous and accepted for over 25 years. This was, well, this is<\/em> now Rapid-RAD, if you will. And not without a bit of pride, I might add: WinForms was the exact right candidate for it, since the new Visual Studio Copilot-based WinForms Expert Agent I had been working on the previous months had just found its way into the latest released VS version, and was now waiting for me to test it under absolute real-life conditions.<\/p>\n

    But this wasn\u2019t a year ago. This was November 2025. And I had Visual Studio 2026, GitHub Copilot, and \u2013 crucially \u2013 the understanding that I didn\u2019t need to be a REFA engineer myself. I just needed enough domain-specific knowledge to follow her explanations, and then by asking targeted questions to capture what my mom knows. And guess what: That\u2019s exactly how a typical User Story collecting, Customer\/Product Owner\/Developer meeting is supposed to be done!<\/p>\n

    \u201cMom,\u201d I said, \u201cI think I might actually be able to help you. Not with the dongle \u2013 that\u2019s dead. But maybe I can build you something that lets you do your time recordings. At least well enough to get through this assignment.\u201d<\/p>\n

    There was a pause. My mom has seen enough technology promises to be skeptical. But she also knows I wouldn\u2019t make offers lightly \u2013 ones I can only attempt to deliver.<\/p>\n

    \u201cOkay,\u201d she said. \u201cWhat do you need from me?\u201d<\/p>\n

    \u201cTell Me Everything\u201d \u2013 Via Microsoft Teams<\/h2>\n

    \u201cLet\u2019s do a Teams call,\u201d I said. \u201cI need you to explain exactly what you do during a time study. What buttons you see on your Surface\u2019s screen, when and why you press them, what data you capture, what the workflow looks like. Everything.\u201d<\/p>\n

    \"Mom<\/p>\n

    For about an hour and a half, my mom walked me through the entire process: how she defines process steps before starting, how each step gets a numbered button, how the master clock runs continuously while individual timings are captured per button press, how interruptions are categorized, how the data exports to CSV for further analysis in Microsoft Excel.<\/p>\n

    She told me about the industrial ironer stations, the clips that carry laundry through heated rollers, the percentage of pieces that fall out, and why machine counts never match actual operator workload. She explained performance rating \u2013 how she walks the floor first to get a sense of \u201cnormal,\u201d then adjusts measurements when workers speed up because they\u2019re being observed (which, by the way, would actually hurt their incentives later \u2013 just saying).<\/p>\n

    And somewhere in there, she told me about the time she stood in an operating room during actual<\/em> surgeries with a sterilized clipboard<\/em>, measuring process differences using washed, sterilized reusable surgery cloth versus throw-away surgery cloths for a hospital cost analysis. But that\u2019s a story for another time. (Guess what though \u2013 washing won.)<\/p>\n

    The call ended past midnight German time. My mom went to bed, probably still skeptical but at least feeling heard. I had a Teams recording and an automatically generated German transcript, and the rest of the Saturday.<\/p>\n

    \"Mom<\/p>\n

    From Transcript to Specification: Enter Copilot<\/h2>\n

    While she went to bed, I got to work. In this case, the time difference between Germany and Washington State was actually quite helpful.<\/p>\n

    I started with the Teams transcript. It was a \u2026 well, let\u2019s say, it started out actually pretty usable, until it was not. And I\u2019m not sure whether having the conversation in German helped the quality. We had:<\/p>\n