pixelrevision
Joined 8 years ago
Joined 8 years ago
Out of curiosity why is writing everything as a single element type more ergonomic? I’ve not done frontend web dev in a while and using <p> <h1> and so on seems like it would be more ergonomic to express intent.
We use ui tests specifically for testing accessibility, analytics and data passed along during navigation.
We use fixtures for all of this.
None of these tests really help with bugs. What they do help with is:
- Making sure the ui stays really decoupled from the business logic. This helps a lot with getting the data unit tested which does help a lot with bugs.
- Making sure that analytics and accessibility are not forgotten about. This helps a ton when refactoring.
- Making the intent of the code really clear during review.
It takes a bit of practice and being ruthless about removing/fixing stuff that’s not helping. I have found it makes it much easier for new developers to work, review code and understand how the code is organized. YMMV.
Alfred can either replace spotlite or run along side it. I’ve found it much faster and easier to use. You can customize it pretty well. (Just don’t download the Mac App Store version as it’s multiple versions behind)
There’s a ton of windows managers out there that help you setup hot keys or modify windows to work how you want. Mac overall is much better with native software not doing its own thing than windows so changes tend to be pretty consistent. I’m using MOOM because it’s on the app store and lets me hotkey all my windows into specific sizes but there’s plenty of other stuff out there depending on what you want to do.
The bonus of doing things like this is that if you are constantly changing your code then it becomes battle hardened to accept change. This gives you better ability to keep up with the changing demands of both customers and technology.