I kept most of my bindings the same as the normal QWERTY keyboard, so I don’t have much of an issue swapping between them. I had debated a lot about changing to other keyboard layouts and I’m really glad that I didn’t.
I kept most of my bindings the same as the normal QWERTY keyboard, so I don’t have much of an issue swapping between them. I had debated a lot about changing to other keyboard layouts and I’m really glad that I didn’t.
I love my Moonlander. I’ll never go back.
I’ve found that one of the best things to do when making a library for something that is going to have a web interface is to first have it work in the terminal. You can much more quickly play around with the design and fix issues there instead of having to work with a more complex web interface.
You just create a simple menu system, like input("1: Feature A\n2: Feature B\n>")
and just start trying out all of the different scenarios and workflows.
I had a coworker who would sometimes not create a method as being static to the class and would therefore need to create a default instance to call said method. “It’s domain-driven design.”
What game is this?
When I learned Python I thought that not having a statically typed language was the way to go, but then it just became an issue when I was trying to ensure that everything was at least something like what I was expecting. Going back to statically typed languages even harder with Rust has been a dream. I love it.