YesWeHack’s Post

Introducing Olly: Providing Observability Tools for OCaml 5 https://lnkd.in/gRYPdin6 #OCaml @tarides_ #Observability

Dependency Injection I came across a video about dependency injection by #CodeAsthetics. This is the far best explanation of DI. Do watch the video.

Ready to take your CTF skills to the next level? 🏆 Advanced CTF players know that the game isn't just about solving challenges. It's about using the right techniques to uncover hidden vulnerabilities and outsmart the competition. 🔍 Here are some tips for advanced techniques: - Dig into forensic tools for deeper analysis. - Master scripting to automate repetitive tasks. - Explore reverse engineering to understand software from the inside out. Stay curious and keep pushing the boundaries! 🚀

Hot off the press, here's a blog post about how we've been using property-based testing to test OCaml 5: https://lnkd.in/dvPRb-We

Dependency Injection (DI) is a technique by which the collaborating objects are passed to the class that needs to work with them, and the class itself codes against an interface or base class, rather than a specific implementation class. Learn more about DI on #DevIQ: https://bit.ly/3YAnbDX #SoftwareDevelopment #ProgrammingPractices

The best video I have ever seen about dependency injection. Every person working with code should see this video https://lnkd.in/eYrCx_eV

A Practical Approach to SBOM in CI/CD Part III — Tracking SBOMs with Dependency-Track Read more: https://lnkd.in/gieEX7Ay

I've learned that my superpower is debugging. Looking at a problem objectively to answer one of two questions: "Why is it working this way?" or "Why is it NOT working the way I expect?" Dealing with multiple systems or systems that work together can quickly compound the problem. We had a case yesterday. System A sends a message to System B, and System B sends messages to Client X, Y, and Z. In 99% of cases, all the messages would pass through fine, but there was a weird 1% case where messages would get "lost." We found an old version of System B (which was supposed to have been decommissioned) that was grabbing 1% of messages and sending them into the ether. That's not a problem you can reproduce locally. It was only discovered because we were pouring through logs and noticed a couple of log entries that we "swore we changed the format of that entry." Walking backward from that, I discovered the "rogue" System B. Shut down the "rogue" System B, and 🥳 everything worked perfectly.

Days of 108 #365daysofinfosec Intro to Detection Engineering room from TryHackMe Introduce the concept of detection engineering and the frameworks used towards crafting effective threat detection strategies. #detection #rule #framework

Maybe the best explanation of dependency injection I have ever seen as well as clean code. Check out CodeAesthetic's latest video https://lnkd.in/gZmtKfPS #dependencyinjection #cleancode #testing