C# is a great language, I don’t know much about game dev but I know unity and godot game engines have good support for c#. You can target Windows/Linux/Mac on all the common architectures. All the build tools are available on the command line if that’s your thing.
I agree that report and record are different. To me record means it’s preserved in some managed way.
The implementation has the ability to vary quite widely from simply printing to stdout, logging to a file, writing to a queue / database, and yet the same name will continue to reflect all those possibilities
This makes it sound like the intent goes beyond logging, but not so far as recording. That’s how I come to ‘report’ as the correct verb.
I would use reportMissingData
So then he’s innocent, case closed.
I was thinking the same thing, until I read Minecraft. Java mods…
Lapce looks pretty cool, for an alpha.
Check for an asterisk after the file name (in the tab/title bar), it means “unsaved changes”.
Scroll down…
Being able to document the exact algorithms used to solve a problem is sort of a ‘Holy Grail’ in programming. Most programmers aren’t afforded the time to document to that level. This would require refining the code down to a single cohesive story that describes the functionality of the implementation. It’s great when you can spend the time on it, but the problem is that the code is actually “working” long before that point. Most employers want to stop paying for code after it starts working.
This is what I’ve been looking for, thank you.
I’ve never looked into it very deeply, but it uses a styling spec called EditorConfig. Check it out, https://editorconfig.org/
Thank you!
If you’re using visual studio (2022 is current) the idiomatic styling will be mostly correct by default (Ctrl k,e will reformat).
So, the question is, how do you deliver better code faster?
I think there question needs to be: how do we convince people that it’s “worth it” to pay for better code?
I get it, we all want to do our jobs well and excel in the craft. The problem i see here is that the stated need for cleanup, refactoring and documentation is immediately followed with a ‘but’. But there is no but, imo.
Code that “works” isn’t good enough, and we need a full stop right there and heads around the table nodding up and down in unison. But they’ll take the inferior POC build every time over investing in a “good” solution that incorporates lessons learned. Next they complain that it can’t be modified easily (“but, it’s just a simple change!”), and bemoan the state of software development.
I think once you’ve absorbed a bunch of data, it takes time to put all the connections together.
AKA Personal Liberty
That’s great to hear! I’m in the manufacturing sector in the US. Things seem tight.
https://learn.microsoft.com/en-us/dotnet/standard/simd
Is this what you’re looking for?
You can’t explain that!
Ok, I’m in for $2 /month too, thanks for setting the standard!