I just wrote pure garbage for the last two hours hoping that if I crank it out fast enough it will have been worth it.

You already know what happened next.

"Pixel Art" Games with differently sized and rotated pixels are a disgrace.

Late night ramble warning.

I like to fix issues. I like to roll up my sleeves and fetch my keyboard or soldering iron on a mission to build a custom solution for whatever real world annoyance that has just triggered my problem solving caveman brain.

I have prided myself in that. I am the kind of guy who doesn't shy away from getting my hands dirty, I tell myself, and it's good because it makes my life easier, I tell myself. But increasingly, I've been wondering if this is really so. Am I really making my life easier? Am I fixing the world or just scratching an itch?

Example 1:
Instead of using conventional backup methods for my personal files like a commercial cloud based service or buying a Synology NAS or something similar, I decided it would be better to build my own linux server and set up a rather obscure configuration in order to address things like parity, ECC, bit-rot and the likes while staying cheap.

Learning a lot? Sure. Fun? Sure. Never have to worry about backups again? The opposite, of course.

While I set out to build the perfect bespoke solution to all my personal backup needs - it's as if I, by putting my time and effort into the nitty gritty of technical implementation, placed a vote for my future to contain more of that stuff. In reality this project has burdened my little brain with many new things to consider in regards to storing my files.

Example 2:
Qwerty and the conventional staggered keyboard layout are relics of past technical limitations and both of them inefficient and bad from an ergonomic perspective.

Possible solution: ignore and carry on or possibly transition to Colemak on a somewhat more ergonomic full size keyboard.
My solution: well, let's also hand build a tiny-ass super obscure ergo keyboard and spend two days to come up with my own layout for all special characters, numbers and function keys.

Fun? Somewhat. Learning a lot? I guess. Never have to think about keyboard layouts again? Lol.

I'm living in a world of pain with various key commands in various apps and edge cases. Could I fix it? Probably make it better but not without quite a bit of effort.

Anyways, it'd be interesting to hear if anyone can relate to this feeling of wanting to fix something once and for all only to find yourself deeper in it then ever before. Idk might be a just me thing. Anyways, goodnight lovely people.

Should I try to learn functional programming or focus on a lower level language?

My strongest language is C#.

I'm looking at F# or Rust atm.

Thoughts?

Tips for staying focused and productive?

My friends diets: healthy.

My diet: syntactic sugar.

I've been coding for fun since before I was a teenager (I'm 28) but, excluding two small freelance projects, not in a professional capacity as I've pursued another career.

To help land my first real programming position I'm now building my portfolio. (http://daglundberg.se)

Any tips, feedback, thoughts?

Thanks

It's fascinating to see C# mentioned as a "lower level language" now days. Times change.

C# was my first language when I started out learning about programming as a kid (I still think it's a great language) and I remember searching the forums for information about any commercial games written with it hoping it was possible to build something "cool" and "3D". Back then that was pretty much just a dream, or so it seemed. C# was, I understood, way too high level for anything like that.

Today it wouldn't be totally baseless to call C# the game dev industry standard.