- Sets constraints on how we write code - like a combination of a powerful linter and templates or patterns.
- Visualizes code-base and flow of code - quickly navigate to the relevant code as well as show the available functions in the code-base so newly onboarded devs can more easily re-use code than write new functions.
- Press record to capture 3rd-party requests and store as json mocks to use with a Mock Service Worker (msw)
Anything that improves the feedback loop, visualizes code-base, reduces context-switching or simplifies flow of code.
Storybook keeps impressing me. It's often misunderstood as a documentation tool but it's more than that. It let's you:
- develop components in isolation, greatly improving the feedback loop and sets constraints on what the component takes in as props and what it renders.
- testing for visual, accessability, interactions etc.
For templates and patterns, we started Codiga [1] where you can define smart code snippets [2] that depends on your environment and can be parameterized by the user when being inserted.
We have a collection of existing snippets user can already use in their IDE on the Codiga Hub [3]. Developers can define their own snippets and share them with their team.
We are still developing the product. It works with IntelliJ and VS Code and we have already a lot of users on the platform. Would love to hear your feedback!
Intellij Ultimate does the first two already. You can create new inspections using structured search and then mark any matches as errors. I've done this to make usage of one or two awkward APIs safer. Or you can quickly write a bit of new inspection logic if your inspection can't be expressed using a structured search. Those can be stored in tree.
- Sets constraints on how we write code - like a combination of a powerful linter and templates or patterns.
- Visualizes code-base and flow of code - quickly navigate to the relevant code as well as show the available functions in the code-base so newly onboarded devs can more easily re-use code than write new functions.
- Press record to capture 3rd-party requests and store as json mocks to use with a Mock Service Worker (msw)
Anything that improves the feedback loop, visualizes code-base, reduces context-switching or simplifies flow of code.
Storybook keeps impressing me. It's often misunderstood as a documentation tool but it's more than that. It let's you:
- develop components in isolation, greatly improving the feedback loop and sets constraints on what the component takes in as props and what it renders.
- testing for visual, accessability, interactions etc.