performance goal concerns a focus on demonstrating competence. P
A performance goal is a goal of demonstrating competence--i.e. on the demonstration.
performance goal concerns a focus on demonstrating competence. P
A performance goal is a goal of demonstrating competence--i.e. on the demonstration.
Some useful discussion on file size costs of a React + Relay app
This is a good short overview of how change detection works in Angular 2.
It fixes the fundamental algorithmic complexity problem that change detection has in Angular 1.x by making it possible to prune parts of the component tree from change detection if the inputs have not changed.
Unfortunately the zone.js implementation involves some horrifying monkey-patching of various DOM APIs.
wring out every ounce of performance
Now think of it with a learner in mind.
Join Darin Fisher, VP of Chrome as he talks the past, present and future of the web.
RAIL - Reaction (<100ms), Animation (<16ms), Idle (<50ms), Load (<1000ms)
The machine, of course, is not complete without a third party, the (human) operator, and it is within this triad that the text takes place.
It reminds me of the machine performance, the human performance and the idea of the text as a performative event (as in Johanna Drucker's theory of performative materiality).
It’s known that Angular becomes slower with around 2,000 bindings due to the process behind dirty-checking. The less we can add to this limit the better, as bindings can add up without us really noticing it!
From some preliminary testing it looks like we get close to hitting the 2000 watch count on the /stream view - which explains the lag.
Here are a few handy tips on measuring your project’s performance profile:
In particular, see this section on recommendations for setting up tests that reasonably simulate "real world" conditions.
Web performance article from a couple of the Chrome team developers / (developer advocates). Mentioned on Twitter - https://twitter.com/aerotwist/status/649877465079390209
Some interesting slides on CSS styling performance on GitHub, particularly focusing on their diff pages.
Several slides have direct references to WebKit internals explaining the impact on rule resolution performance.
Mentions a useful tool for understanding CSS selector performance implications, css explain
If your timeline graph is dominated with the color green after recording
Green is used to denote time spent painting
there does not seem to be a general rule for how many workers to spawn. Some developers claim that 8 is a good number, but use an online calculator and suit yourself
Web workers are very heavy objects as they include an entire JS VM instance. 8 sounds like a lot.
The $digest loop keeps iterating until the model stabilizes
cf. React where an event triggers an event handler, which can trigger state changes and calls to React.render(). These are then batched together resulting in a single re-render, a DOM-diff and the application of the result to the DOM. Consequently you can't have an infinite state update loop. The exception is if a state change happens asynchronously, and that state change triggers another async state change (and so on...)
The value function should return the value which is being watched. AngularJS can then check the value returned against the value the watch function returned the last time
Ah, so since the input is a scope, this means that Angular needs to call every watch value fn that might be affected by a change. Should look into whether it has any optimizations to avoid that for common watch expressions.
Both accessibility and performance are invisible aspects of an experience and should be considered even if they aren’t explicit goals of the project.
So instead we introduced the loading spinner on each widget. Nothing is actually any faster, but the whole experience feels more responsive
Simply reducing some CSS transition times from 500ms to 250ms, and cutting others out entirely, made the whole dashboard feel snappier and more responsive.
This means content is served from the nearest possible geographic location to the user, cutting down request latency from as high as 2500ms (in places such as Singapore) to tens of milliseconds
We eventually came up with a compromise solution based on Addy Osmani’s basket.js, using a combination of server-side script concatenation and localStorage for caching. In a nutshell, the page includes a lightweight loader script, which figures out which JS and CSS it has already cached and which needs to be fetched. The loader then requests all the resources it needs from the server in one request, and saves all the resources into localStorage under individual keys. This gives us a great compromise between cutting down the number of HTTP requests while still being able to maintain cacheability, and not re-downloading code unnecessarily when it hasn’t changed. Addtionally, after running a few benchmarks, we found that localStorage is (sometimes) actually faster than the native HTTP cache, especially on mobile browsers.
Is Your Performance Review System Outdated
High performing teams have well-defined goals, systems of accountability, clear roles and responsibilities, and open communication.
I feel these are good defining characteristics of high-performing teams.
Instead of cheerleading, people in my profession should think of themselves as businesspeople. What’s good for the company? How do we communicate that to employees? How can we help every worker understand what we mean by high performance?
I replied, “Why bother? We know how this will play out. You’ll write up objectives and deliverables for her to achieve, which she can’t, because she lacks the skills. Every Wednesday you’ll take time away from your real work to discuss (and document) her shortcomings. You won’t sleep on Tuesday nights, because you’ll know it will be an awful meeting, and the same will be true for her. After a few weeks there will be tears. This will go on for three months. The entire team will know. And at the end you’ll fire her. None of this will make any sense to her, because for five years she’s been consistently rewarded for being great at her job—a job that basically doesn’t exist anymore. Tell me again how Netflix benefits?
Trying to remedy a situation where someone has "been consistently rewarded for being great at their job" and then working on a PIP with them really is a miserable process.
HR people can’t believe that a company the size of Netflix doesn’t hold annual reviews. “Are you making this up just to upset us?” they ask. I’m not. If you talk simply and honestly about performance on a regular basis, you can get good results—probably better ones than a company that grades everyone on a five-point scale.
Traditional corporate performance reviews are driven largely by fear of litigation. The theory is that if you want to get rid of someone, you need a paper trail documenting a history of poor achievement. At many companies, low performers are placed on “Performance Improvement Plans.” I detest PIPs. I think they’re fundamentally dishonest: They never accomplish what their name implies.