![]() So I started worrying that inefficiencies in my work environment were encouraging me to take an approach that was, overall, less optimal. I might favor a failing test over firing up a debugger more often. I might use inline assertions more often. I might start writing more exploratory tests. If I could add methods, remove classes, rename variables and add new statements in the blink of an eye, I would make different choices about how I code.I don't think it would just be the same thing done faster. I wondered how I would write code differently if all my modifications had zero cost. ![]() The problem is, what's efficient in your editor might not be the best thing for your codebase. It encourages efficient actions and discourages inefficient ones. As a result, your development environment has a direct effect on how you write code and what code you write. They tend to repeat actions that are efficient, and avoid those that aren't. I started to think that this was holding me back, not in the actual time it was taking, but in the way it affected how I write code. But I still had moments where I thought to myself "I'm wasting time with this", and I had no clear way to make them better. I had installed all kinds of bundles, and even made a few. I had learned the majority of the useful shortcuts. ![]() I started to investigate vim because I had hit a productivity plateau with TextMate. In fact, aside from editing configuration files through ssh for the occasional sysadmin work I'm call upon to do, I'd hardly ever used vim before.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |