💾 Archived View for dazlab.uk › tinylog › _tl0008.gmi captured on 2024-08-25 at 00:14:27. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-05-26)
-=-=-=-=-=-=-
▀██ ▀██ ▀██
▄▄ ██ ▄▄▄▄ ▄▄▄▄▄▄ ██ ▄▄▄▄ ██ ▄▄▄
▄▀ ▀██ ▀▀ ▄██ ▀ ▄█▀ ██ ▀▀ ▄██ ██▀ ██
█▄ ██ ▄█▀ ██ ▄█▀ ██ ▄█▀ ██ ██ █
▀█▄▄▀██▄ ▀█▄▄▀█▀ ██▄▄▄▄█ ▄██▄ ▀█▄▄▀█▀ ▀█▄▄▄▀
Another sub-entry in the Tinylog of dazlab.
Some people (most people) will read the title `C#: The Proper Way` and take it to mean what I'm putting out there is what C# programming should be; this is not the case. What I'm putting out is going to be my, entirely amateurish, version of C#.
`The Proper Way` is not in reference to how one *should* use C#, it's in how *I* need to use it in order to get any traction with learning to program, from going from writing some scripts and very basic `real` programs, to doing what is actually considered programming. I've a creative mind, though one entirely grounded in reality; that is, thinking in terms of the machine.
Programmers are an opinionated bunch; there's not a piece of code on this planet that some developer won't look over at think `pfft, that's not how that should be done`. Which is strange, as nobody does this to the same degree when reading something one has written in a non-computer language. A writer's style is allowed to breathe, is permitted be his own; a programmer's style is seemingly mandated through peer-pressure and `whataboutism`.
In short, I'm happy to diverge from conventional wisdom in this regard. If the resultant program works, then who gives a flying fig what the code looks like. A lot of the design patterns dictated by the developer community concern code reusability and maintainability. I'm writing for my own use. It's not a library, I don't want or need to collaborate. I also don't care much for maintaining the final program, and it will be largely useless. The code, terrible as it may be, is my own.
By me, for me.