Swing details in KITE

Hi @nithin,

Good Day,

Can we have a dashboard with following details. This shall help to track monthly swing of Nifty & BankNifty.

Thanks,
Anirban Chatterjee

May not be possible on kite but will see if we can add it somewhere in our ecosystem.

1 Like

Can you please name them all? I can discuss this with our team based on your feedback.

These are on our to-do list.

I believe you’re referring to multiple exits from a position that should automatically slice orders beyond the freeze quantity. This is also on our to-do list.

Noted. We’ll discuss this

Instrument grouping with customizable colors will be introduced in Marketwatch soon. Given this update, would a color flag still be necessary?

This is now available on the technical widget, and we plan to integrate it natively with the additional options you mentioned. It’s already on our to-do list.

This is currently in the testing phase and will be released soon.

We’ll reevaluate this to see if it can be made possible in the near future.

TFC will be implemented soon.

Thank you for taking the time to share your feedback. We appreciate your input and are committed to addressing the missing areas to meet your expectations soon.

3 Likes

The other most important point is once we place a fund withdrawal request, the funds get credited the next day whereas at Dhan and Angel One, funds get credited the same day.

I have reopened the account again with Angel One and surprised to see the way they pivoted themselves to the tech. They are almost on par in the features with Dhan. However, Dhan has a work to do on it’s web home page. The fonts there are too thin and make me anxious.

I can compare zerodha similar to Nokia where they were behind the line in adaptation and continuous improvement.

2 Likes

Can we have orderflow charts please

i think Zrodha tech team is small, compact (less than 40 person, i think).
They dont hire enough and expand the team, or outsource some non-critical parts saying everything(well, almost everything) needs to be inhouse.

Hence they have a long list of TODOs which never gets done and the partial progress on any of these features gets upended by faster changes in regulatory or tech/software world. So they have to redo this allover, wasting time.

They are lost in a loop of analysis paralysis, though heir intentions are good. For a third person like me, intentions means measurable, perceivable action on the ground which is entirely missing.

One thing which is appreciated is their load/traffic handling strength which could have not been tested properly with other brokers which handle less volumes than Zerodha (I think SEBI should have a load testing grades like in ADAS automation lever 1 to 5, 5 being robust and 1 being vulnerable, where almost all brokers including the big-bank-broking houses like hdfcb, icicib, sbin and their clumsy interfaces would secure less than level 3)

Hope zerodha will start realizing this sooner, add people and resources in right places (viz. tech team) and start galloping sooner from the current crawling state.

3 Likes

Without knowing the details of the tech stack,
i.e. how tightly-coupled the various parts are,
i don’t think we can assume that adding more people is going to speed things up.

That old program management parable of
9 women does not mean a baby can be delivered in 1 month :sweat_smile:

Source: The Mythical man-month by Fred Brooks.

@thisisbanerjee You’re missing the point again.
That’s a well established quote in software development / project management circles.
But, hey today’s your lucky day. :+1:

Anyways, please refer to the Mythical man month by Fred Brooks for the original quote.


[ Source ]

None of that is written or implied.
Please don’t let your own thoughts / vendetta, cloud what others write.
and yes, please do stay on-topic :slight_smile:

Perhaps not knowing/understanding the significance of Fred Brooks’s quote, leads one to misread the whole comment. :man_shrugging:
Point taken. Updated the orignal comment with the reference.

Again, i hope anyone reading the comment focuses on the point of the analogy -
Adding people is not necessarily going to speed-up development.

Also, how dare you say women are not related to tech or Zerodha? :open_mouth:
(i know what you probably meant to say.
so, am not going to try to take your words out of context
and stir controversy to try to win an argument.
I hope you don’t do that again here on TradingQnA either.)

Cheers big fella! :+1:

Since your responses are measured, if you are interested in learning more about the tech side of things, here are some links.

Also, for their tech “approach”, "philosophy ", what have you… you can also follow their tech team here (infrequently posted, though)…

If you already do, I’m sorry to be preaching to the choir :joy:

2 Likes

Thanks for sharing.
Very relevant to where this topic-thread was/is heading.

Yes. I do remember that upon reading this last blogpost (which you shared above), it left me with the distinct impression that a lot of blocks in the stack were getting coupled with clickhouse in some way or the other. I am curious how that’s turning out. :thinking:
If someone from Zerodha’s tech team is reading this, please do dedicate some time in the next post on how going “all-in” on clickhouse is panning out.

Next, based on the responses of front-end folks who occasionally chime-in on this forum, I believe it is extremely unlikely that the front-end UI will “improve” anytime soon.

  • Part of my belief is due to what comes across on this forum as inability to take criticism of some brain-dead UI decisions in recent times.

  • Another reason is my personal belief that the current UI is the best that can be without triggering major changes to the entire infrastructure including the back-end. Any potential changes to the front-end ends-up exposing bottlenecks in the current architecture / back-end. And personally i would take the current compromise instead of an “improved UI” with a flaky back-end.

Every time i see someone whining on this forum about something in the UI, but not switching to other brokers (for months/years) who they believe/claim are offering a better UI, i think that all such folks eventually come to the same realization that switching is not worth the “costs” - monetary, reliability, … and other such.

2 Likes

It’s quite tempting to pull popular quotes out of context and use them as a blanket statement. Using your analogy in the context of the original discussion, 9 women can most likely give birth to 9 babies in 9 months.

But again, all this is just for the sake of putting the point out - which is that maybe few of the things in the to-do list are independent of each other and can be worked upon parallely. If wasn’t the case, you’ll never need more than 1 developer and create all the babies that are to be made…

PS - not at all suggesting that zerodha isn’t already at that optimal headcount level.

1 Like

@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.

1 Like

Exactly! Well said. :clap:

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. :sweat_smile:)


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

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

…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. :sweat_smile:

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.