The workaround was using a collection wrapper inherited from CollectionView class, usually ListCollectionView or CollectionViewSource. So you could create a collection view, bind it to the list control's ItemsSource property and that was enough. That's few additional lines of code in a view model.
What is the author suggesting? To write software using infinite loops changing global state? Makes sense for video games but not for the custom enterprise software where clean code practices are usually applied.
The enterprise code must be easy to change because it deals with the external data sources and devices, integration into human processes, and constantly changing end-user needs. Clean code practices allow that, it's not about CPU performance and memory optimizations at all.
>The enterprise code must be easy to change because it deals with the external data sources and devices, integration into human processes, and constantly changing end-user needs. Clean code practices allow that, it's not about CPU performance and memory optimizations at all.
There are no good metrics that measure how "clean code" (atleast the given rules) make the code easier or harder to change and maintain.
All the Java style "enterprise type code" from my experience is bloated, full of boilerplate getters and setters and all sorts of abstractions that often make things harder and not easier to understand/maintain, etc.
However CPU performance is easy to measure, and sticking to "clean code" rules as given in the video demonstrably sets you back a decade in hardware progress/makes the code run 10x slower.
> Clean code practices allow that
This is what you believe, not something you can actually measure as far as I know
Well it is the management’s job to make your work aligned with the company’s best interests.
It is possible that you’re already doing what you’re getting paid for. In that case you shouldn’t go out of your way to increase the company’s profits (and nobody expects you to).
(In my original post I didn’t say that as a developer you should code thinking of quarterly results, I just stated the obvious that you are employed for the shareholders to get money back)
But these guys develop their programs in isolation and they deploy to users only the final result or a limited number of beta versions. They almost never evolve their code bases to a second version. They work on video games.
If I work in isolation from the users, don't have external requirements, don't care about future versions of the software - sure, their advice might be useful to me.
> They almost never evolve their code bases to a second version.
This isn't necessarily true, a lot of code can and is reused between games (math, physics, audio, etc.)
In terms of isolation from the users, that isn't really true either -- the users are the rest of your team. You have to build tools for the team to use and they better be at least somewhat usable, and you need to have something workable quick so you're not blocking your artists and level designers, etc.
For me, it is a gentle stop to the internal monologue by transferring attention to my own breathing. What is the end goal? Less thoughts, more stable the emotions.
ftp://ftp.adobe.com/pub/adobe/reader/