hackerstyle

https://drive.google.com/file/d/1mZ_S3R53bmVpvxixavkMPmMorCj...

NET

You shouldn't build anything, start with Airtable and basic Typeform. Connect people using email until you validate some hypnosis

What about Laravel?

Master might keep you busy for 1-2 years

Do you record when employees come and leave? we currently don't and it's pretty flexible and that's one of the questions that I don't have an answer for. Should it kept flexible and team can come and leave when they need to or set some rules to manage that.

You are right about my team, they are not seniors but they are smart and getting the required experience. I am feeling good that we're building a solid ground and in the near future we would be operate in a better and faster rhythm. I am very technical and can understand their code and plans easily but it's not scalable, so I am looking at a way to make it run systematically although this will require middle managers.

Thanks for the great feedback, much appreciate it.

Managing output alone is hard, how do you do it without setting unrealistic goals? Do you have a place where I can read more about this?

Usually everyone in the team knows what's required, and we have the tools, and the reports to measure things but usually things might take less or more than expected and the question here is really the actual software challenges that delayed the work or the actual time and effort spent on a problem?

Agree on games.

I find it hard to manage output alone, it's a combination of both.

Do you count hours where you work?

How do you manage output?

To me output is challenging, because any engineering task can take less or more time that what's estimated and thus how to set a realistic goals for the team members without making them go crazy.

Regarding games, read the comments above. It provided so much good information.

Can you share your experience in managing engineering team output?

Thanks for your honest feedback, much appreciated. Usually each team member knows the plan, and what should be finished and when. We have the right tools to generate reports and KPIs but the issue in software development is that things change easily, for example:

a. on a specific day, the expectation is to finish task A, but then, the engineer discovered that it depends on unplanned task B and now we need to finish B before being able to complete A and deploy it.

b. an engineer is working on a specific task, and he's investing a lot of time and effort but it was not finished on time because the actual plan didn't work out and needed additional time.

That's why it's kind of hard to manage output alone.

your example at the beginning was excellent, can you give me more details to how you like to be managed in terms of output? if you have a place where I can read from would be awesome.

Thanks again.

Thanks for comment, it makes sense. Do you do anything to increase people productivity? for example: I hate to see people playing games in the office, but I know at the same time that it might be healthy to have this kind of freedom.