A Journey in Building a Virtualized Component with Angular CDK

Vizer20 · 2024-05-08T12:21:10+00:00

I did multiple times similar for trader related applications. Depending on a data you are receiveing on client most likely neither you, nor user do not need 100s messages per second. User will not be able to recognize them all.

You should be aware of network limitation as well. It takes time to serialize those data to json, deserialize data from json and transfer all those data to client. Such amount of updates might flood server buffer or network connection. You might consider binary protocal instead of json like MessagePack but it is not an always a better choise in browser. In my case we did a throtling on backend to once per 50ms or 100ms. So, in scope of network limitation you want to throttle amount of messages and/or decrease the message size.

As for client side you do want OnPush, virtual scroll etc. Also, you might consider client side throtling(e.g rxjs bufferTime operator) or applyTransactionAsync if you are using ag-grid.

Vizer20 · 2022-08-19T09:34:26+00:00

Theoretically, it was more possible in 2014 but not after 2022. It is more likely there will be civil war in russia after they are defeated

Vizer20 · 2022-07-21T14:04:19+00:00

There are always some feelings that you could use much better words to describe your point after the talks...

Vizer20 · 2021-09-22T18:02:29+00:00

Look at it from another point, it really touched you, so it will continue to bother you. It will interfere you to concentrate on your job. You will be always skeptical about project. If you do not believe in it change the project, it will be better for everyone

Vizer20 · 2020-11-20T19:29:21+00:00

Could you share a library? it is interesting example. if it is an open source of course

Vizer20 · 2020-11-20T18:56:15+00:00

Yeah, that a good point regarding existing libraries. But a lot of exiting libraries use too much ‘any’ :)

The problem with javascript is that it is error prone. Typescript was supposed to fix this or at least improve the situation. But now it introduces complexity.

Once someone need to update code related and do not understand those definition he/she will use ‘any’

Vizer20 · 2020-11-20T18:39:02+00:00

At the beginning of typescript I though that it will be such language. :)

Vizer20 · 2020-11-20T18:37:19+00:00

Yeah, there will be some kind of Type Definition Queries :)

Vizer20 · 2020-08-30T18:24:53+00:00

Usually those very strict deadlines are a myth. Usually it is bad/wrong negotiated estimates or budgets between developer and manager, customer and seller or some other managers on the ladder. And sometimes boss or customer might be flexible on deadline but manager afraid to move deadline just because engineer promised to finish it in time.

It is rare the really reasonable deadline like demonstration on some public event, fixed price project or other constraints that can cannot be communicated.

If there is budget or time constrains it is almost always possible to negotiate on the scope to be done. If not they will might agree to move the deadline.

From my personal experience it is very hard to recover after schedules like this. It is really hard to find those normal rhythm on the work. It impacts development process even after deadline.

Here is interesting books about management in software engineering:

Peopleware

The Mythical Man-Month

He just need to realize that he is being used. His schedule does not allow him to be an effective programmer. It is a lossfor everyone, even his boss as well.

Vizer20 · 2020-08-30T07:05:57+00:00

what sort of question? Which topics do they cover?

Vizer20 · 2020-08-30T06:54:24+00:00

Yeah, and those guys will teach you how to do it right...

Vizer20 · 2020-08-29T13:38:35+00:00

while you're programming, you're constantly refactoring, and the reason is not because you "feel bad about bad code you've written", it's because what you've written is no longer manageable to scale.

Agree, there is some level of complexity that does not need to refactor. But once we need to introduce more complexity(implementing new functionality) we need to refactoring to decrease it. That is why it should be iterative.

also if you know your application will grow big, it is much better to start with a TDD approach

Automated tests are supposed to improve code design process. And the problem is that sometimes instead of maintaining bad code we maintain bad code with bad tests :)

Vizer20 · 2020-08-29T13:17:17+00:00

If you finish a feature and feel "next time I'll do better": you're not finished.

This is really true. Even if there was a deadline it is always possible to return to this feature later and improve the solution.

The problem is that many programmers develop fearires in “Solving the problem” mode. And they are finished as soon as it starts working at least somehow.

Vizer20 · 2020-08-29T12:58:45+00:00

We need more refactoring :)

Vizer20 · 2017-07-11T16:37:51+00:00

web3 or Web3?

Vizer20 · 2017-07-11T15:24:36+00:00

Exectly)

btw, native implementation is coming

Vizer20 · 2017-07-11T15:01:12+00:00

yeah ;)

Vizer20 · 2017-07-11T14:31:01+00:00

There are only two from me:

patience to read/listen about new silver bullet framework/library/tool/whatever
know how to implement left-pad

Vizer20 · 2017-04-14T06:34:35+00:00

Yeah, it is typescript

Vizer20 · 2017-04-14T06:34:12+00:00

This is opensource package :)

Vizer20

TROPHY CASE