I have a script that runs every 5 mins that does a robocopy for each local repo to OneDrive, excluding all the git system files. I don’t really like the idea of pushing half-finished / broken code.
Rarely need to actually copy stuff back out of onedrive, but it’s good enough on the few occasions I forget to push before changing machines.
Maybe also look ip a good component library, for C# I use MudBlazor, which has great documentation that helps a lot to pick the right component for the job, and a lot of the hard work is already done in terms of styles/themes.
For my apps I use the MVVM pattern and write all the backend logic first, then that helps me narrow down the right way to display it.
I can see the appeal of having a generic way to log particular methods, it’s a bit jank to intercept your own code, and it’s easier to debug in general with explicit log messages with more detail.
Also recommend serilog as another commentor mentioned, and you can combine this with global static using Serilog.Log once in your project and then you only need to call Debug(“something”) etc. anywhere else in the code.
FYI the try finally statement has different behavior in dot net, if you use the same pattern use
try { } catch { throw; }Use throw and not throw ex to preserve the stack trace.
Misleading description, it’s only a brief summary about Agile/Scrum.
Can’t say I’m a fan of the methodology either…
For my sins I spend a significant part of my time maintaining smalltalk, and it most definitely is not productive.
The syntax is ugly and cumbersome when you start chaining messages. Any advantages the evangelists tout are available in modern languages without the baggage of this dead one.
Today if you want something ‘simple, flexible, interactive’ (interpreted, GC and likely faster) python would almost certainly be a better choice.