Wishful thinking on my part that an alternative solution for JSDoc based type checking exists :)
95 karma · joined February 6, 2022
Wishful thinking on my part that an alternative solution for JSDoc based type checking exists :)
It’s a very sad history of oppression and corruption that has forced many Venezuelans to pull up their roots and risk their lives leaving their own country. It would be a dream come true to see this dictatorship overthrown and replaced by a democratic system of government that serves the people.
If I had to rewrite a Python project, I would consider Rust or another statically typed language before choosing to continue in a dynamic language with types bolted on. I hope the situation improves for dynamic languages with optional types, but it still feels weird and bolted onto the language because it is.
Putting too much responsibility in the ci environment makes life as a developer (or anyone responsible for maintaining the ci process) more difficult. It’s far more superior to have a consistent use of the build system that can be executed the same way on your local machine as it is in your ci environment. I suppose this is the mess you find yourself in when you have other teams building your pipelines for you?
For example, by doing X this will improve our efficiency in performing Y by 80% and help us achieve our goal by reducing time wasted on Z.
I believe in making yourself invaluable, but would caution against falling into a niche. Especially if you want to avoid getting caught up in a layoff. But as long as you have valuable skills you will be able to find other work. Some companies are better at hiring (talent acquisition) than others.
This whole project is a work of art.
I’ve been using it for a couple years now and it’s worked well for me across multiple machines.