Don’t skimp when it comes to buying a good setup to use for development, especially if you spend most of your time developing. Â A few years back I was lucky enough to work for a company that provided better than needed equipment. Â I had been using a small keyboard with flat keys that came standard with the Mac machine, and made a comment about missing the full keyboard, number pad, among the flat keys that felt like a laptop.
The following day they replaced the keyboard with a mechanical keyboard from Razer, a BlackWidow. Â Never having used a mechanical keyboard before I thought this was both overkill, that keyboard costs a fair bit, and assumed there was just a hype around mechanical keyboards. Â How wrong I was. Â The audible and tactile feedback from the mechanical keyboardÂ was amazing.
Now working from home, both professionally and personally, I’ve recently upgraded my PC to have that same keyboard. Â Within a week I documentedÂ almost all of the reference level documentation needed for TurtleBrains, I think, because it felt awesome to type. Â Otherwise I was just on some other motivated wave of documenting the framework. Â My old Logitech G15 was a nice keyboard for many years, it was moved over to my MacBook Pro setup which I use mostly for professional development. Â While this was magnitudes better than using the laptop keyboard, my fingers were itching to get back on the mechanical keyboard. Â I decided to buy a second one, so both of myÂ workstations have this equipment.
Which leads me to the final point, it was a fair bit of money to spend on keyboards and development equipment. Â ButÂ given this blog post has taken at least 3300 key strokes, I’d say it is worth making each one feel good. Â There will always be situations where you will have to make do, and in those situations, you make do. Â For other situations where you can reach around a little bit, make sureÂ to extend yourself towards the things you really use often.