Sébastien Jousse

@deltakosh Mais oui ! C'est commanded 😉

Today is the day!!! Valianara is available amazon.com/gp/product/B0G… And for those who want to get back into or discover the lore, I created a companion site: cycleofthetitans.com #fantasy #book

The #1 mistake I see .NET developers make is using NULL everywhere. But that's a billion-dollar mistake. NULL reference has caused loads of errors, vulnerabilities, and system crashes. Here are 4 ways you can minimize NULL in C# code: 💰 Return empty value from the method - if possible, return an empty list instead of null - for example, use Enumerable.Empty 💰 Eliminate nulls with C# nullable reference types - introduced in C# 8.0 - it forces you to use null more carefully 💰 Use the Null Object pattern - this is an object that defines a "do nothing" behavior - can eliminate null checks 💰 Use the NullConditional operator - allows you to safely access a class property - when the instance is null, the whole assignment will return null Want to reduce crashes? Give the above suggestions a shot.

The hidden cost of enterprise .NET architecture: Debugging hell. I've spent 13+ years in .NET codebases, and I keep seeing the same pattern: Teams build fortress-level abstractions for problems they don't have. IUserService calls IUserRepository. IUserRepository wraps IUserDataAccess. IUserDataAccess calls IUserQueryBuilder. IUserQueryBuilder finally hits the database. To change one validation rule, you step through 5 layers. To fix a bug, you open 7 files. The justification is always the same: "What if we need to swap out Entity Framework?" "What if we switch databases?" "What if we need multiple implementations?" What if this, what if that. The reality: Those "what ifs" don't come to life in 99% of cases. I've seen exactly zero projects swap their ORM. But I've seen dozens of developers waste hours navigating abstraction mazes. New developers are confused about where to put a new piece of functionality. Senior developers are debugging through the code that has more layers than a wedding cake. The end result? You spend more time navigating than building. Look, good abstractions hide complexity. Bad abstractions create it. Most enterprise .NET apps have way too much of the second kind.

Toujours un sketch avec @DPD_Fr et @ChronopostSAV . Le livreur m'appelle, il est à une mauvaise adresse dans une autre ville, je lui dis, il livre quand-même et c'est moi qui ai déménagé et qui dois batailler avec le vendeur pour un nouvel envoi ?

@madewithlayers @OpenSauceLive Glados ! We are actually trying to train it's voice in french for home assistant. I'm waiting for your project too 👍🏻

I'm building a little something to bring to @OpenSauceLive 🎂

@NetworkChuck Just post what you want so we can discover about things we didn't think of

So, I received a few messages on my Discord server that people are tired of seeing all the AI videos on my channel. Genuinly curious if this is how ya'll feel? Given my most recent video views.....feels accurate.....but you never know.

@deltakosh J'espère que la voix a un petit accent toulousain 😁

Le livre audio de l'Héritage de Zeus est dispo sur Audible!! amazon.fr/gp/product/B0D… Si vous voulez un code pour l'avoir gratuitement pingez moi! je serai ravi de vous faire découvrir la belle voix de Megara

My MINI network RACKs are "done". youtu.be/Ghuc1vfiLiM

Please help amplify! We cannot allow a company to destroy physical goods because of their bugs!!!

Please share this far and wide. As far and wide as you can. NIST Password Guidelines for 2024 are in the process of being updated. This is a HUGE pet-peeve of mine (when vendors in particular are still operating like its 2017 and keep changing passwords every 60 days, STOP DOING THIS, it's outdated and has been shown to put you MORE at risk than less -- NIST explains why it does in this document, meticulously outlining user behavior**) so I'm sharing this in the hopes all of you will pass it along to your bosses. The Special Publication series governing passwords is SP 800-63 "Digital Identity Guidelines". The 2024 version is 800-63-4. Here: pages.nist.gov/800-63-4/ The companion docs are also on that link. They are 800-63A, 800-63B and 800-63C. These are different documents for different scenarios in play at your org. The previous update was in2020. The changes in the 2020 version from the 2017 version were numerous but one of them was that the password verification method should NO LONGER require passwords be changed at specific intervals (i.e. every 60 days) but in the following circumstances instead: 1. After a breach/compromise 2. User request 2024 repeats this and adds a bunch more guidlines but here is a screenshot of page 13 of the new 800-63-4 (note the # 4 after it) which outlines how your systems should now and moving forward, be handling passwords. This goes for Active Directory, too. All your systems which have passwords should align with these guidelines provided there isn't another standard or framework you must adhere to which overrules this. Most frameworks, however, have moved away from arbitrary password resets and complexity rules. **We cybersec researchers and hackers use wordlists from breaches in a variety of different ways. Hackers use them in tooling to crack passwords whereas researchers use breach dumps to see the kinds of passwords users are creating and the psychology behind them. Using complexity rules gets you the user psychology of: Password1 Password2 and so on Use phrasing instead and allow for spaces, which is important. Humans type phrases with spaces. They also mention phish-resistant methods and most vendors are on-board with MS going to be turning off all Legacy Auth next month, across all free accounts and tenancies. I'm so excited for the new changes! Ok I'm off my soapbox. Share the love! Thank you!

Les banques françaises qui n'acceptent toujours pas les accents en 2024, ça me tue @cic @CreditMutuel #Monetico #Unicode

The most dangerous thing in tech is a semi-technical person in a technical leadership position. They know something is bad (or good) but lack the ability to create good guidelines. End result: LINQ can be bad. No LINQ anywhere! Interfaces can be good. Interfaces everywhere!

@shelly_IoT @Light_Building Hello team @shelly_IoT I see a beautiful Dimmer Pro in the video. What's its ETA please ?

Be among the first to see our latest Shelly additions @Light_Building! Our newest products are exclusively available for a sneak peek during the event. Introducing Shelly's New Products, featuring the Shelly Qubino Wave Mini Series, new Blu Line editions, & Pro Line accessories.

@troyhunt And they were warned month ago 🤦🏻‍♂️ twitter.com/bluetouff/stat…

Geez France, that’s a biggy:

@davrous Et 1 petit épisode spécial de la confrérie ? 😉 Bon vol

Voyage vers Redmond pour le vaisseau mère Microsoft. Je vais pouvoir enfin voir mon chef et mon équipe complète pour la première fois depuis 3 ans !!! Les 11h de vol ne me réjouissent pas... Du coup, j'ai pris un compagnon pour m'aider à les tenir. J'espère voir mes copains frenchies et quelques MVP sur place aussi ;)

🆘 Tour Eiffel 🆘 Petit fil 🧵 sur la Tour Eiffel, qui n’a jamais autant mérité son titre de symbole de Paris …et de la gestion municipale calamiteuse dont elle est aujourd’hui victime. À dérouler 👇

Dès aujourd'hui, France Identité est accessible à toutes celles et ceux qui possèdent la nouvelle carte d’identité. Pour télécharger l’application : france-identite.gouv.fr

Alors @mondialrelay , on voulait voir ce que j'avais commandé ? C'est vilain la curiosité 😉

@VeloCamion @provelo_idf @Florent_Giry Je me doute ;) C'est surtout les idées des villes qui m'étonneront toujours. Et je constate qu'ils ont toujours un gros budget peinture blanche ou jaune :D

- La Ville n'entretient pas les chaussées c'est scandaleux, il n'y a que les grands réaménagements qui l'intéresse 😡 ! La Ville : refait à neuf le révetement des rues. - La Ville refait des routes sans les réaménager en entier, c'est scandaleux 😡 ! Fatigue.