Following all the helpful advice re my journey (as they say these days) from the safe (albeit peculiarly non-standard) realm of Delphi to the brave new world of Dot Net, WPF and now (scary …) MVVM, I have just spent the last hours looking at MVVM examples. Whilst recognising the advantages of the formalisation, separation of UI and logic, etc. that this gives - particularly in major development environments with teams of developers, probably spread out geographically as well as functionally, I still wonder whether it is a bit of overkill for the single person Windows desktop developers like me.
A lot is talked about the enhanced robustness of the above approaches in terms of code maintenance, ability to change UI without damaging logic, etc, etc. and I accept all this. But for the single person developer, where looking back at code that you did 6 weeks ago requires a major exercise in analysis, it is perhaps less relevant (or is it more relevant?)
My mind goes back to the halcyon days of Z80 programming in hex (assembler - couldn’t afford that!)
So Hex Code 77, (Load HL Immediate) became embedded in my memory!
Perhaps what we need today is a RemObjects DotNet for dummies (i.e. for the over 70s like me)
Although the above is light hearted (in the main!), I would love to see what “programming” looked like in 20 years time, and more amusingly, what “programmers” of that time felt about today.
Finally to you MVVM enthusiasts - do I really need it for my Login Screen?