Evolution is a continuous random branching and selective pruning process.
And there is not a lot of pruning going on in the current human explosion.
So unless ADHD is an old branch and we see other mammals survive because of their distractability, I remain skeptical.
A REST framework for FastAPI and SQLAlchemy, creatively called "fastapi-alchemy". A bit on the ambitious side, but I had the opportunity to open-source work I did for an employer.
It is running in production, but it needs extensive documentation and testing still before I'll package it and offer it to PYPI.
A little late to the discussion, but what I missed in the comments was to properly try to reestablish the relation with your co-founder at least once more.
It sounds like it will take a lot more than a meeting. The two of you should go on a three day retreat to discuss the company situation and strategy deeply and to repair the connection between you two.
If you have completely different views, in a way that is really interesting and you should both strive to fully understand and learn from each other.
Who knows what lies underneath the difference in views?
Once you know that you can make a much more informed decision and if you still leave it will likely be on much better terms.
In the conversations I had with my cofounder about possibly going our separate ways he threatened to kill me, which really made it easier to know what to do and would have made the rest of a retreat awkward.
Another solution would be a React-native machine translation implementation that updates the TextNodes without replacing them. It would still have the issues of merging adjacent nodes to get a proper translation, but at least it could update on any state change.
One idea that crossed my mind while reading the article: for websites that already use react-intl, have react-intl implement an API to allow supplying machine translations of messages into languages otherwise not supported by the app.
The problem with this is that it will only help sites that already put in effort to internationalization. Whereas the main target of Google translate are the sites that do not bother with i18n.
Still, it'd be quite valuable to the sites early in their internationalization journeys to get support for tons of languages right upon introducing internationalization.
I agree that recovering from VCS is something that never actually happens. Mostly because the code is forgotten.
Still, commented-out code is generally worthless and should be deleted. Unless it is actively being worked on and only commented out to achieve some short-term goal. In which case it should also not be commented out but instead live on a branch.
Occasionally you might have two flows and you're not sure which is best. But in that case keep them in separate functions and one of those will not be used but can still be covered with tests. And all static analysis tools will work on it. Just needs a comment about why this unused code is there.
