antholeole

I’d like to say I’m a vscode power user - I use a huge amount of shortcuts, keystrokes, etc. To the point where when peers watch me code I get comments on my proficiency with the IDE. Time and time again, though, I’ll stumble across YouTube videos or some form of media explaining that vsc skill ceiling is far lower than vim/eMacs.

I don’t have a problem with anything on vsc - in fact, I use it when I ssh into servers because I like the nice “at a glance” file UI, and I don’t have to cd & ls to see where and what everything is.

Unlearning all the vsc keystrokes, shortcuts, and tools is going to be a serious time commitment, but I’m a young guy and have a long career ahead of me. If vim is really that much faster, I’d be willing to take the performance hit for long term growth.

I have a hobby side project, which I’m quite close to shipping. I started off going for 90% unit tests, but since I’m hacking alone, it ends up taking a bunch of time to keep the tests up to date.

Im thinking of keeping all the old unit tests, but switching to a full integration E2E testing system. This way, I can just text features as opposed to code paths.

By day I work at <insert tech giant here>, and I would never push up code without it being unit tested, so it feels a little painful to ship with only integration tests.

Thoughts? For those of you who’ve shipped small projects, what tests did you find had the most benefit?