Les vidéos de KurzGesagt sont toujours excellentes

Comme d'habitude, on ne saît pas comment sont alloués les aides aux entreprises, ainsi que leurs montants?!

Imaginez MacDonal's pour les cantines. Pourtant c'est Microsoft pour l'éducation nationale.

sometimes when you get down to implementing a measure, you find an endless maze of increasingly confusing corner cases.

How to find real human visiting the pages?

The best experience made by the author is to use a setTimeout of 3 seconds that pings a log endpoint.

The more you want to calculate at query time, the more you want views, calculated columns and stored or user routines. The more you want to calculate at normalized base update time, the more you want cascades and triggers. The more you want to calculate at some other (scheduled or ad hoc) time, the more you use snapshots aka materialized views and updated denormalized bases. You can combine these. Any time the database is accessed it can be enabled by and restricted by stored routines or other api.

Until you can show that they are in adequate, views and calculated columns are the simplest.

The whole idea of a DBMS is to store a representation of your application state as the database (which normalization reduces the redundancy of) and then you query and let the DBMS implement and optimize calculation of the answer. You haven't presented a reason for not doing that in the most straightforward way possible.

The truth is uglier: developers burn out because of the system around coding, not the coding itself.

1. Unclear priorities
2. Constant interruptions (lack of possible focus)
3. Politics
4. Context chaos

Protections: draw hard boundaries, make priorities visible, limit your context surface, build allies, document the cost, know when to walk

A small web UI ? #idea #project

Nines are a measure of system reliability, expressed as how many nines appear at the left of the availability expressed as a percentage.