This! The problem is also that as our apps grow the server side part of it and the client side part of it grow at pretty much the same rate. For each new functionality added on the backend we end up writing more UI code. This is a problem. We need start thinking of how a UI frontend can be implemented as a separate app completely independent and agnostic to the backend. To the extent that I can simple take the same frontend code and plug it to any compatible backend and things will just work. We need to develop a frontend client that can work with any backend (your app, my app, her app). The UI across all apps is mostly the same and we keep rewriting the same JS/HTML (albeit using different JS libraries) each time we build a new app. This is the problem. Let's start thinking of how we can build a general-purpose frontend client which doesn't work on low-level details (JS/HTML) but on higher level abstractions.
I worked in Gaza for close to 3 years and led a team of 6 software engineers. We worked on a pretty complicated business app (UN project). We were a very quality-focused team and did some pretty cool and advanced stuff.
What I can say from my time in Gaza is that there are many very driven, talented software engineers there. Some of the best engineers I ever worked with were Palestinians (and I don't say this lightly).
Very useful list and I kind of like the idea of having "tech lead" be a project-based role, rather than your job description. It will definitely force more accountability.
[link redacted] - a site I've made with a friend back in 2008. It requires absolutely no maintenance and earns a few hundred bucks a month. Tried selling it, but the best offer we got was somewhere around 10k $, which is way below our expectations. Now actually working on renovating it and probably adding some new content and features.
Assuming a few hundred == 300, 10k seems fair, if not generous. At the absolute most I'd expect it to fetch 20k. My guess is that your expectations might be a tad unrealistic.