I worked with many teams at many companies. I trained a lot of developers to become a good tech lead. Most of them didn't know how to operate a team, what to do and what to expect. I extract the essential parts for daily tasks for a tech lead and share how it works here https://ruzig.com/answers/2024/06/19/how-to-run-a-sprint-as-...
This is the daily workflow, practical, no theory. There are a lot more details when you run a team, and you need a coach to help you do it correctly. There is no silver bullet solution for these questions. The important thing you need to know is that you should follow good practices like doing science: predict, experiment, retro => make changes and keep following the loops.
Here is a success story from a unicorn startup. They started a traditional business; there was no IT at that time. The business was good, and they had already made a lot of money.
They want to create a digital product for the business. They first hire a local person and freelancers. Then they work together to build the product. The local person acts like a CTO and product lead. Freelancers are developers. Then they want to speed up the project, they hire an offshore/outsourcing company - a quality one from a developing country. They worked very hard, with fast responses.
After a while, the product is really working; they start in-house devs. The original local person became CTO. They hire product people(product managers, product owners) locally(cause they know about business requirements...). And they grow massive devs in developing country without visiting that OR just only 1 or 2 on some year.
No, from Asia. I'm a part of this story. Now they hire massively there to scale the business. From the time they reached unicorn status, the budget engineer was about 3M, around 100 engineers.
I use https://www.bridgetownrb.com/ and it works pretty well. Very easy to use and deploy. Blog posts are listing line by line, like "index". I didn't customize much from the generated code(only logo and header). You can take a look: ruzig.com
I hope one day AI can transform ULM to a codebase. It would be a big change for devs cause we spent a lot of time writing tech solution, discussing about pros and cons, designing... AI should help us finish the rest.
Scrum is to protect the team. The team just works at their cadence, and the velocity will help the team not commit too many points for the next sprint. The communication is the same with Kaban; I didn't see any difference.
1. Start making the first dollar
2. Pretty straightforward. Offering some APIs for web scraping. 0 pivots
3. Right now, 40USD/month, 1 client
4. Still a full-time worker
5. Solo
6. There are many web scraping websites which are very expensive or slow. I try to focus on fast and reliable with reasonable prices.
There are a lot of mobile proxies providers out there. You can quickly search and ask for a trail. The key is to retry the requests with different proxies. Otherwise, you have to pay for captcha resolver services. You should negotiate with proxy providers to ask them for quality proxies, so you don't need to manage captchas(they will manage for you).
if you want to scrape popular website like google, bing,... You should sub to some SASS. They provide you the APIs.
This is the daily workflow, practical, no theory. There are a lot more details when you run a team, and you need a coach to help you do it correctly. There is no silver bullet solution for these questions. The important thing you need to know is that you should follow good practices like doing science: predict, experiment, retro => make changes and keep following the loops.