This post is not going to be about the chrome developer tools (although you should totally read about it).
No, this post is about some developer tools I found along the way, which I use to enhance my projects.
First, let’s start with some not quite common tips, that no one tells you about when you begin.
Things I’ve learned
It’s going to be tough. Embrace.
Learn how to use the computer without a mouse. This is where I put a shameless self plug to another blog post of yours truly, about going mouse-free.
- Comments aren’t always necessary.
Use them with caution1, as
- They aren’t read by compiler or almost anyone, and
- They get old.
Get rid of validation as soon as possible in your code, so you can get to your happy flow. Your happy flow is where everything is guaranteed to be good.
For example, I reviewed a code that could return 200, then 438 then 200. This means that something is off and you should second guess your initial assumptions.
Think through your abstractions - avoid leaky abstractions. For example, Ruby on Rails (along with some other web frameworks) implements a hack: it tries to route HEAD requests to the same place as it would route GET requests. Then it runs the controller code, and just omits the response body. This is one hell of a leaking abstraction - and it made one hell of a security headache over at GitHub.
- Someone else thought about it before you. Use the open source community.
If you really can’t find what you’re looking for, code it and call it a startup.
Some useful tools
- render for deploying apps
- koyeb for deploying apps
- ngrok domain for testing
- nutjs for automations
- LICEcap for screen recording gif
- Figma for design
- tsup for creating (small) react components
- np for publishing npm packages
- obsidian for your second brain thoughts and ideas
- lottiefiles for lightweight, scalable animations
- undraw for free, open-source, high-quality svg drawings