Niko Heikkilä 💻 @nikoheikkila@mastodon.technology

I heard a fantastic description for a text editor from a colleague: the Columbo editor, or the one you open when you have one more thing to do.

All editors are good candidates, whether they are nano, vim, emacs, helix, or micro. They only need to be fast to get the shit done.

My current Columbo editor is helix, with vim as the fallback choice. When I overstay my welcome while editing, it's still VS Code.

Oh yes, I forgot to mention it requires fzf – the fuzzy finder for command-line. If you live in the terminal but are not yet using it, you're missing out on a great deal of productivity.

https://github.com/junegunn/fzf

I realized what the Taskfile project is missing... an interactive task picker/runner!

As a lazy shellist, I made this Fish shell function for it. Enjoy.

#taskfile #fishshell

https://gist.github.com/nikoheikkila/f8f6d707102e186b790bc3efb5bd70c2

Additionally, if you're developing tests in VS Code, don't forget to install the official extension for fast debugging and recording inside the IDE.

https://marketplace.visualstudio.com/items?itemName=ms-playwright.playwright

Playwright version 1.22 ships with experimental support for testing React, Vue, and Svelte components. Having fought and been frustrated with React Testing Library and friends, this is a blessing given Microsoft and contributors do it well.

Being able to render a component and interact with it using the real browser while harnessing the power of Node.js for tests is an exciting promise for test execution.

https://playwright.dev/docs/test-components

It's not rubberduck debugging, it's toxic brogrammer debugging.

PSA: anything done async will require a resync, so it's better to stay sync.

My reaction when someone in my team is enthusiastic about implementing a feature that no one asked for.