Stratégie de cache et de rendu à étudier.
Stratégie de cache et de rendu à étudier.
Diátaxis is a way of thinking about and doing documentation. À lire
À suivre
$ docker ps -aq | xargs docker stop | xargs docker rm
Accédez, depuis un point unique grâce à Captvty, aux directs et à une multitude d’émissions proposées au rattrapage par différentes chaînes de télévision. Je l'avais oublié celui ci à voir
Exemple de makefile
Code officiel géographique au 1er janvier 2024 Téléchargement des fichiers
A specification for adding human and machine readable meaning to commit messages
NES maker, à tester
à faire dans mon bookmarklet !
Towards the end of Wim Wenders’s excellent Perfect Days, the protagonist Hirayama is drinking beer under a bridge after he has seen a Businessman courting his crush. Suddenly the Businessman joins him under the bridge. As it turns out, things aren’t actually that simple but the point is their conversation takes them to some fundamental questions:
A lire, une meilleure DOC block
Ressources utiles pour le CSS (moderne) !
Webring à explorer
Coloration syntaxique sans javascript, avec les couleurs directement dans la police de caractère OpentrueType
DORA is the largest and longest running research program of its kind, that seeks to understand the capabilities that drive software delivery and operations performance. DORA helps teams apply those capabilities, leading to better organizational performance. Important à lire.
DORA is the largest and longest running research program of its kind, that seeks to understand the capabilities that drive software delivery and operations performance. DORA helps teams apply those capabilities, leading to better organizational performance.
We are often faced with trying to test software that is closely coupled to some kind of framework. Examples include visual components (e.g. widgets, dialogs, etc.) and transactional component plug-ins. Testing these objects is hard because it can be expensive or impossible to construct all the objects that our system under test (SUT) needs to interact with. In other cases we have objects that are hard to test because they run asynchronously; examples include active objects (e.g. threads, processes, web servers, etc.) and user interfaces. Testing these objects is hard because the asynchronicity introduces uncertainty, interprocess coordination and the need for delays in tests. Faced with all these issues developers often just give up on testing this kind of code.
How did we get from 'Program to an interface, not to an implementation' to 'Just slap an interface on there, it's the fashionable thing to do'?
Approche fonctionnelle pour un parser. À étudier
Retour sur l'excellent ouvrage : Unit Testing Principles, Practices, and Patterns de Vladimir Khorikov
Principe du moindre étonnement en P.O.O.
Très bon blog de Mathias Verraes. Il y a même un flux RSS
Bonne idée.