As much as this hurts, yeet; as an alias throw; is hilarious
Lightfire228
joined 1 year ago
The technology behind the registry is fine (which is what I think @VinesNFluff meant)
But it's execution in Windows was ass
In theory, a configuration manager with DB-like abilities (to maintain relationships, schematic integrity, and to abstract the file storage details), isn't a bad idea
But the registry as it is today is pure pain
Sanity checks
Always, always check if your assumptions are true
- am i even running the function?
- is this value what i think it is?
- what is responsible for loading this data, and does it work as expected?
- am i pointed at the right database?
- is my configuration set and loaded in correctly?
I've never done that in my life
Software dev here,
It doesn't stop you from typing code, but it does drastically hinder the process. You often need to pull up technical documentation (for the language, framework, platform, etc), or search the internet for things, like "C# HttpClient how to serialize JSON with a different naming policy"
Not to mention, if any of your dev resources are online, no Internet prevents you from running your code. Like, if you need to connect to an S3 bucket, AWS instance, or Azure Database
I've been running Linux for 4 years, but this still hurts to read
Always copy what you have written, so you can paste it and continue typing where you left off
I mean, you just need to look at the conflicting files, fix up the code, then stage those changes and pop a new commit
There's no "special" merge conflict resolution commit "type"
As for fixing the code itself, I usually look at what changed between both versions, and then re-author the code such that both changes make "sense"
I'm at a loss for words