Cyril Cathala

Top 20 AI Concepts You Should Know

I keep reading diatribes about how you must trade off quality for development speed, so I thought I'd write my own diatribe :-). This speed vs. quality dichotomy is absolutely false. Buggy code is hellish to work on. Even small changes (or bug fixes) take vastly longer than it would have taken to write a few tests before you wrote the code (or in the case of unit tests, while you're writing it). If it takes longer to write tests than it does the code, you're either doing way too much work between commits or your code is too large and complex. Work small. Test small. (I'll make an exception to this more-tests-than-code rule for code that can kill people.) Check the tests into version control at the same time that you check in the code itself. It takes only a few hours to st up Jenkins or equivalent to run those tests automatically with every check-in, and you do that only once. Claiming that you don't have time for quality is just wrong. In fact, you don't have time to ignore quality, and you don't have time not to test. Bad quality, poorly tested code slows you down (and in the case of a startup, will bring down the company). Don't even think about doing it. If you really want to increase your speed, stop building cr**p nobody wants or needs. You do that by building very small, getting constant feedback and input, and paying attention to both.

HTTPS, SSL Handshake, and Data Encryption Explained to Kids. HTTPS: Safeguards your data from eavesdroppers and breaches. Understand how encryption and digital certificates create an impregnable shield. SSL Handshake: Behind the Scenes — Witness the cryptographic protocols that establish a secure connection. Experience the intricate exchange of keys and negotiation. Secure Data Transmission: Navigating the Tunnel — Journey through the encrypted tunnel forged by HTTPS. Learn how your information travels while shielded from cyber threats. HTML's Role: Peek into HTML's role in structuring the web. Uncover how hyperlinks and content come together seamlessly. And why is it called HYPER TEXT. Over to you: In this ever-evolving digital landscape, what emerging technologies do you foresee shaping the future of cybersecurity or the web? -- Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): bit.ly/bbg-social

Move from .NET 4.8 to .NET 8 = $$$ savings 😁 reddit.com/r/dotnet/comme… #dotnet

"Microservices first" indicates that the person advocating that idea isn't thinking like an architect. No single architectural pattern is appropriate in all contexts. An architect will first identify the essential system characteristics and then pick an architectural pattern with pros and cons that match the characteristics. Microservices are fault-tolerant, highly elastic and scalable, incremental-development friendly, and support hot deploys into running systems. They are also slow, complex, and network-based (I see that as a huge negative). Use the pattern if those characteristics (pros and cons) work for you. If they don't, use a different pattern. There's also a third choice. A very simple microservice system can run as threaded components in a monolith, thereby giving up the elasticity but also lowering the complexity quite a bit by getting rid of the network issues. In other words, you can meld patterns to create new patterns. It's all about identifying characteristics and choosing (or inventing) appropriate patterns.

🌱 Thank you, @github, for highlighting the Carbon Aware SDK as one of the ten best tools for greening your software, along with other exciting resources. #greensoftware Check out the full list ➡️ github.blog/open-source/so…

@Evilznet Hell yeah! NO excuses 😆

@CyrilCathala Let's go back to simple exception flow then

.NET 9 RC1 🚀 My highlights: ✅ [C#13] params collections ✅ [Blazor] constructor injection ✅ [SignalR] polymorphic type support ✅ [ASP.NET] OpenAPI doc generation ✅ [.NET] faster exception handling (x2-4) devblogs.microsoft.com/dotnet/dotnet-…

Verifying estimates

@Piskariov Congratulations!! 🥳🕺

Renewed as MS MVP for the fifth time thanks to #dotnetmaui and Sharpnado🎉🤘 #MVPBuzz

L'anomalie des températures prévues ces 7 prochains jours est, de nouveau, très révélatrice sur la distinction "local" versus "mondial". Si la France est sous influence maritime depuis plusieurs mois, l'Europe de l'est et sud-est crame. Pour 2024, Bucarest en est déjà à sa 3ème canicule (soit déjà 5 semaines cumulées depuis le 1er juin). Au niveau mondial, quand on somme toutes les anomalies, début juillet 2024 est d'ailleurs le 2ème le plus chaud jamais observé tout juste derrière... 2023 ! Excellente cartographie de @climatebookgr, un très bon compte de suivi grec que je vous conseille.

A Thousand Suns, a new anthology of sci-fi shorts, is pretty good: aftermath.site/a-thousand-sun…

That’s a wrap! #devtalks Thanks everyone for showing up, great time together!!

Let’s get the DevTalks .NET meetup started with Benoit Herbigniaux talking about how to integrate a new feature into legacy code! #devtalks cc @onepoint

@JamesMontemagno And lastly @jfversluis to bring .NET MAUI + Blazor together🔥 #devtalks

Followed by @JamesMontemagno talking about .NET Aspire 🚀 #devtalks

Oui c'est un vendredi. Oui c'est en anglais. Mais ce n'est pas tous les jours qu'on reçoit @JamesMontemagno et @jfversluis à Paris. Checkout this Meetup with DevTalks .Net about .NET Aspire and .NET Maui Blazor ! Bonus: Some Q&A at the end. meetu.ps/e/N2m5g/vrbnJ/i

@jeromegiacomini @Fnac J'ai déjà eu un litige avec la Fnac, tu peux signaler ton cas sur signal.conso.gouv.fr : ça prend 5mn et c'est hyper efficace pour leur mettre une grosse pression. Avec de la chance, ça évitera que ça se reproduise pour d'autres...

A la @Fnac l'uruspation d'identité est quelque chose de normale. Le weekend dernier je suis allé m'acheter un téléphone à la Fnac. Le vendeur me dit que ma carte Fnac est expiré qu'il a besoin d'un RIB. 1/5

Double Loop of Value buff.ly/3vdE7pu

Prefer test-doubles over mocking frameworks buff.ly/3SNLa03