This has completely gotten rid of the wrist pain. The split keyboard opened up my posture and helped a bit with the neck pain.
Since I got a new job that didn't have standing desks, the neck pain has started to come back a little bit. It's mostly because your neck gets weak when you sit for so many hours a day. Getting a standing desk converter can help keep your muscles from atrophying. It's also not great to stand all day. You want to alternate.
A split keyboard is a huge win. When you sit with your hands in front of you, they don't naturally want to go in towards the center. They want to be offset a bit.
Below the desk keyboard tray -- Look up an ergonomics diagram. You aren't supposed to have your hands going up to get to your desk. It's supposed to be a 90 degree angle.
Going mechanical. I run Kailh Silvers, which are incredibly light and have a 1.1 mm travel distance before the key registers. It's like typing on air. I barely have to move my fingers. This, of course, takes some getting used to.
Going ortholinear. Staggered keys are just a remnant of old typewriters. Your fingers were built to go straight back and forth. Making them go sideways forces _a lot_ of extra wrist movement. Again, this takes some time to learn.
Curved keyboard well. Your fingers aren't all the same length. Couldn't we make something that puts all of the fingers closer to their keys in the resting position? Yes. See below.
After a little time with mechanical keyboards, I ended up just going all out and building myself a Dactyl. That's a split ortholinear keyboard with a curved keywell, and is basically as ergonomic as it gets. If you want advise on how to build one, I can help point you in the right direction. It took probably 10 hours. Otherwise the closest thing is an Ergodox or Kinesis Advantage. It only took a Sunday to get mostly used to it, and my typing speed has actually gotten way faster. I detailed the learning curve here: https://www.reddit.com/r/MechanicalKeyboards/comments/azkkpz...
The only disadvantage is that if you bring one of these into work, get ready to catch some flack :D
At this point I've got my own chair, standing desk converter, mouse and keyboard. I plan on coding for a long time, not just for the money but because I love it. So I look like a bit of a dumbass, but in 20 years I'll still be coding.
It took 4 hours or so of constant typing tests to get up to 60 wpm. It took another week or so of working with the keyboard programming 8+ hours a day to stop having stupid mistakes.
It seems like it's going to be extremely hard to learn at first. Especially when you're hitting 5 WPM every time, but trust me, your brain will adapt. I was helped out by the fact that after spending a few days _building_ the keyboard, I wasn't about to back down. I was pleasantly surprised when it only took 4 hours.
Since then, my productivity is through the roof. Tons of thumb keys that are entirely programmable = heaven for an Ergoemacs user like me.
I used to use bootstrap, or download themes on themeforest. But since discovering Semantic, I've had a much easier time building front ends. It also serves as a guideline -- when I can't find something I want in Semantic, I have to ask myself "Is there a better way to do what I'm trying to do that _is_ in semantic?"
Also, with anything, it's a matter of putting time into the frontend. If you spent as much time on the frontend as you do on the backend, it would likely look better. It's easy to rapidly prototype a frontend just to make your idea work. Once it works, you move on.
If you're an employee trying to purchase flights, you go to https://login.ual.com/oamsso-bin/login.pl?contextType=external&username=string&password=secure_string&challenge_url=https%3A%2F%2Flogin.ual.com%2Foamsso-bin%2Flogin.pl&request_id=-8483851944568476286&authn_try_count=0&locale=en_US&resource_url=https%253A%252F%252Fflyingtogether.ual.com%252FBut if you...