Swing details in KITE

[economiconed]

@cvs , please try to get the context, which was said in light of long todo list with zerodha and fast changing regulation, technology, market structures and userbase. Didnt mean to say someone to act/work on something without knowing (that way no one is ever encouraged to switch to a new job profile).
Agree that it takes time for a new recruit or even experienced to understand the design philosophy of a team. But thats not going to take years (If t does, then the design is complicated and not modular, scalable-etc). Also not asking for hiring overdrive to bench valuable skilled personnel (your hotel and baby example is a bit of an off topic here. Everything does to appropriate probability distribution of utilization… if you do more, or less than required, it could be less optimal)

I didnt mean to also belittle zerodha’s design and achievements so far, which I also mentioned as robust (highlighted). It was just suggestion to speed-up product/feature timelines by getting more help.

[cvs]

@asen

Using your analogy in the context of the original discussion, 9 women can most likely give birth to 9 babies in 9 months.

Exactly! Well said.

The point to focus on is to identify whether there are 9 babies or 1 (or some number in between). i.e. to first identify the stuff that can be independently worked-upon and delivered, and ONLY then consider scaling the workforce accordingly (if necessary).

Alternately, re-architecting the existing stuff to reduce tight-coupling, and enable more independent work, can help speed-up development by creating more independent blocks for additional folks to simultaneously work upon without blocking/hindering each other.

Let us do all this first and then check if adding more people will speed-up further development.

(Of course, after OP’s subsequent post above, it is evident now that OP had all this in mind when they posted their original msg however it was an unwritten assumption, that i felt the need highlight. )

---

@economiconed thank you for describing in detail some of the concerns i was hinting at.

@economiconed

But thats not going to take years (If it does, then the design is complicated and not modular, scalable-etc).

Looking at the evidence we have,
(seemingly “small changes” taking ages to develop, test, and deploy)
this appears to be the case here.

@economiconed

It was just suggestion to speed-up product/feature timelines by getting more help.

…and the counter-point i was trying to highlight is that
there is not much evidence to suggest that
“getting more help” is going to improve the development time or quality.

Instead let us suggest to improve the design to make it more modular/scalable first?

While we are at it,
the recent mis-steps with UI might (again no evidence) be due to adding more people.
And continuing to add more people, might it even worse.

PS: I have no more of internal visibility than any other individual here on this forum.
Looking at the same publicly available info that we all have access to, we all have different opinions of where the challenges might be.