/ blog / archive — 4 entries
BLOG_
> cat /var/log/thoughts.log
Field notes from 35+ years in the trenches. Mostly C# / .NET / Avalonia,
some Rust, rants about OOP, retro emulation, and whatever weird thing has me up at 2am.
Showing4of 4 entries · filter:
csharp
> order by date DESC
2026 // current cycle
0x12
2026.05.14
Why learn modern system design if the old ways still work?
The old ways do still work. WinForms in VB.NET 10 on Visual Studio 2026 is a perfectly modern stack. Modern system design is not asking you to give up forms, events, or any of the tools that already serve you well. It is a small set of techniques you can add behind them, when a project starts to want them.
6′
0x10
2026.05.12
Frugal again - rules for writing code that respects the machine
The hardware curve has flattened. The papering-over is ending. Here are the rules for writing code that respects the machine it actually runs on, with .NET specifics.
14′
0x0D
2026.04.30
What did you love about VB6, and what frustrates you about modern .NET?
Two open questions for anyone who shipped real work on Visual Basic 6 and is now writing C# against modern .NET. What specifically did VB6 get right that you miss? And what do you find frustrating about the modern toolchain that VB6 didn't make you fight? I shipped about a hundred VB3-through-VB6 line-of-business systems between 1995 and 2010, and I'm trying to get to the root of what was actually good before too much of the institutional memory leaves the room.
4′
0x06
2026.04.27
Visual Studio 2026 still ships the form designer Alan Cooper drew in 1987
Every UI framework Microsoft has shipped since WinForms (2002) was sold as its successor. WPF, Silverlight, UWP, MAUI, Blazor desktop. Twenty-four years on, WinForms is still there, on modern .NET, with a designer that any VB6 developer would recognise on sight. The Cooper and Geary form-designer architecture from 1987 is still the path of least resistance for a working line-of-business app in 2026, and that is not an accident.
12′