J'ai rencontré un développeur qui savait tout. En passant mon temps avec lui, j'ai fini par comprendre comment il fonctionnait.

Chaque page était TOUJOURS structurée de la même façon.

1 – Modèle Mental

Une phrase pour comprendre l’idée ou le concept. Une explication rapide du fonctionnement de quelque chose. Souvent une forte simplification. Presque à chaque fois une métaphore. Car le cerveau est étonnamment efficace à retenir des concepts sous forme de métaphores.

2 – Aperçu

Trois à quatre phrases qui donnent un aperçu de l’idée ou du concept. Ça doit être simple à comprendre et facile à retenir. Plusieurs phrases permettent d’être plus précis et de limiter les simplifications.

3 – En profondeur

Plusieurs paragraphes d’explication sur le sujet qui approfondissent l’idée ou le concept. C’est aussi long que nécessaire. Presque aucune simplification n’est admise ici.

4 – Schéma

Une image, un schéma, un graphique du concept ou de l’idée. Car une image vaut 100 000 mots. Comme la plupart des gens, JF comprend mieux les choses avec un schéma. C’est très efficace.

5 – Quizz

Une succession de 8 à 10 questions autour de l’idée ou du concept pour tester les connaissances autour de celui-ci. Très important, il utilisait la balise details pour cacher la réponse de chaque question. Le but étant de forcer la personne à aller chercher la réponse dans son cerveau. On va y revenir.

In this series I've been unpacking various facets of Elixir. Mostly this has meant trying to explain Erlang and the BEAM through the lens of Elixir. Now we are moving into the domain of the web framework. This is where I dare say that Elixir has much more to say than Erlang. Erlang has to my understanding never landed fully on a canonical preferred web framework. Elixir has Phoenix and this post will be unpacking Phoenix. The Elixir web framework.

Graphical representation of Elixir functions.

How do you avoid becoming a Brilliant Jerk? Read this article to learn practical tips on communication, honesty and psychological safety.

shared by Alysa at Mural

Community driven, articles, resources, guides, interview questions, quizzes for DevOps. Learn to become a modern DevOps engineer by following the steps, skills, resources and guides listed in this roadmap.

An intuitive 2D game engine. Fast, cross-platform, tiny, hot loaded.

I don't know if I ever will build a game, but if I do this is where I'd get started.

The official site of Zhenghao He, a software engineer and a TypeScript/JavaScript enthusiast.

Finding datasets

The easiest way to do this is using Papers With Code, an excellent resource for finding the latest scientific papers by task that also have code repositories attached.

source

tl;dr

Start a terminal as administrator then copy/paste

reg add HKCU\Software\Policies\Microsoft\Windows\WindowsCopilot /v TurnOffWindowsCopilot /t REG_DWORD /d 1 /f 

Then sign out and sign back in again.

681+ engineering blogs that will help you improve at system design:

1. Engineering @ Meta: https://lnkd.in/gc9xnZQ8
2. OpenAI Software Engineering: https://lnkd.in/g3wFsZk7
3. Nextflix Tech: https://lnkd.in/gq-SWapT
4. Stripe Engineering: https://lnkd.in/g4JqgY39
5. Uber Engineering: https://lnkd.in/gvga-NEg
6. Airbnb Tech: https://lnkd.in/gy3RF5ih
7. Figma Engineering: https://lnkd.in/gFbvV8Mk
8. Dropbox Tech: https://dropbox.tech/
9. LinkedIn Engineering: https://lnkd.in/g5eMavet
10. Instagram Engineering: https://lnkd.in/grE9bRCy
11. Spotify Engineering: https://lnkd.in/gje__jGu
12. MongoDB Engineering: https://lnkd.in/grsAiuvS
13. Twitter Engineering: https://lnkd.in/gVVcSYNf
14. Engineering @ Ramp: https://lnkd.in/gw_kd2Vj
15. Instacart Tech: https://lnkd.in/gdGN9SrY
16. Stack Overflow Engineering: https://lnkd.in/gENW-7Wh
17. Paypal Tech: https://lnkd.in/gxj9Mx64
18. Rippling Engineering: https://lnkd.in/ge6K-UkG
19. Notion Tech: https://lnkd.in/gCUUi2UC
20. Pinterest Engineering: https://lnkd.in/gnfrme2Z
21. Engineering @ Spotify: https://lnkd.in/gje__jGu
22. Canva Engineering: https://lnkd.in/gRHZtDCa
23. GitHub Blog: https://lnkd.in/gKNBpb7V
24. Slack Engineering: https://slack.engineering/
25. Lyft Engineering: https://eng.lyft.com/
26. Yelp Engineering: https://lnkd.in/gBWEyaHK
27. Gusto Engineering: https://lnkd.in/gyqBr_CW
28. SoundCloud Backstage Blog: https://lnkd.in/gNDUUreD
29. Medium Engineering: https://lnkd.in/g3ASQbbB
30. Heroku Eng Blog: https://blog.heroku.com/
31. Etsy Engineering: https://lnkd.in/gS6UwNN9
32. Grab Tech: https://lnkd.in/gfhcUM5y
33. Longer List Here (remaining 600): https://lnkd.in/g3xqDpg6

TIL about CRDT

A Conflict-free Replicated Data Type (CRDT) is a data structure that simplifies distributed data storage systems and multi-user applications.

A arctic, north-bluish color palette

Curry? # Currying is a technique that translates a function of arity N into a sequence of functions that all have the arity 1. Function arity means the number of arguments a function takes. # The add function has the arity of 2 add = fn x, y ->... | Patrik Storm | Svbtle

TIL of it
M=must, S=should, C=could, W=won't

Intéressant comme tests

Another example from Brazil at Silicon Valley

Use AI to change art into functional QR Code (quite impressive).

Solução completa para investimentos alternativos! Se seu backoffice te coloca em apuros, corra para as montanhas.

This is from Collaborative Fund article about Brazil at Silicon Valley (BST)

Currying is when you break down a function that takes multiple arguments into a series of functions that each take only one argument. Here's an example in JavaScript:

['1', '7', '11'].map(parseInt) doesn’t work as intended because map passes three arguments into parseInt() on each iteration. The second argument index is passed into parseInt as a radix parameter. So, each string in the array is parsed using a different radix. '7' is parsed as radix 1, which is NaN, '11' is parsed as radix 2, which is 3. '1' is parsed as the default radix 10, because its index 0 is falsy.

And so, the following code will work as intended:

['1', '7', '11'].map(numStr => parseInt(numStr));