Unfortunately, a single developer carrying an entire software team is a common pattern in the industry. I've been in both your situation and the situation of your team mates. If left unaddressed, the organizational momentum will perpetuate this situation. Stakeholders will continue to consider you the trusted party to get things done. This is not only a problem for you, but the organization as well, because your departure could create significant problems stemming from a loss of knowledge.
You may deserve more compensation, but it doesn't solve the problem in the long-term. As you have said, "There is little to no confidence in the others carrying on successfully if I suddenly stopped." Rendering that statement false is the solution. As the lead, it is your responsibility to improve the productivity of your team mates and build trust between them and the organization. It can be a slow process, but one that creates a more sustainable and harmonious situation for both you and your team. As long as you continue to absorb all the work, the situation will never improve.
Here are a few suggestions I've seen work in the past:
- Spend time on an extended vacation. This forces your team members to pick up the slack. It's better than quitting, giving everyone an opportunity to experience you being a single point of failure without the long term catastrophic consequences. Have a frank discussion about how to fix things upon your return.
- Offload yourself as a point of contact for various projects. Hand over initiatives to your fellow team mates. Force stakeholders to meet with them instead of you. Make yourself available to help them succeed.
- Make tasks more digestible for your team mates. Aggressively document things, make tickets easy to understand, set up knowledge sharing sessions.
- Hand new initiatives to your team mates. Let them specify the details.
- Talk to your manager, see if they have any thoughts on how to improve the situation. They are the last person who wants to deal with the fallout of your departure.
- Talk to your team mates, see what motivates them. What do they think they can do to improve the situation? It's not uncommon for team members to feel resentment for you absorbing all of the work.
I definitely recommend checking out Steven Black's unified hosts file [0] for DNS-level adblocking outside of one's local network. It's the default block list in Pi-Hole.
Did the demand for products from polluting industry disappear in the developed world or did the factories just move overseas? Shifting blame to "underdeveloped and corrupt nations" does nothing to address the fact that developed countries still demand goods from polluting industry and do little to promote more sustainable forms of economic development.
I love asyncio! It's a very well put together library. It provides great interfaces to manage event loops, io, and some basic networking. It gives you a lot of freedom to design asynchronous systems as you see fit.
However, batteries are not included. For example, it provides no HTTP client/server. It doesn't interop with any synchronous IO tools in the standard library either, making asyncio a very insular environment.
For the majority of problems, Go or Node.js may be better options. They have much more mature environments for managing asynchrony.
YaCy is a great tool! Haven't used it all that extensively since 2012. Very good for setting up simple crawls with minimal configuration or for crawling intranets.
This looks very possible. It would only require a two modules for analysis and frontier management. It would be great to collaborate on something like this!
I've been developing web crawlers for the better half of a decade. They are used for various purposes such as cataloging sentiment/bias in news media, finding new tv shows to watch, or mapping out the Tor hidden service directory.
Currently, I am writing a web crawler application framework in golang. Always looking for help or new ideas on what to crawl next!