Marco Santulli

I just received the notification that the book "Network Programming in Elixir and Erlang" by Andrea Leopardi is now out of beta. This is a great addition to The Pragmatic Programmers catalogue. Congrats Andrea 👏 The book covers TCP, UDP, and HTTP with clear, practical examples from the Erlang and Elixir world. It also includes an entire chapter dedicated to DNS, plus an appendix with details of the DNS protocol. 👌 At DNSimple, we've found that Erlang pattern matching works amazingly well to map and destructure packet data. The book even gives a shout-out to Erldns, the name server we've developed and maintain at DNSimple. A fantastic opportunity for readers to explore a real-world example in action. 👉 Get it now https://lnkd.in/daRrybed 👉 We recently published Erldns v8 https://lnkd.in/d2nT7igk

319

5 commenti

"We are now confident we know how to build AGI as we have traditionally understood it" - this is the statement from Sam Altman's blog published two weeks ago: https://lnkd.in/d6UESmy2, which is certainly worth reading. In this post, Sam summarizes OpenAI recent progress on AI and points to the next steps. In my opinion the most striking statement is about the step very soon to come "We believe that, in 2025, we may see the first AI agents “join the workforce” and materially change the output of companies". Here, at MIM Fertility we are at the same quest, i.e., creating AI tools that will aid IVF clinics in daily work taking over some burdensome tasks. We believe that the future is in collaborative AI where tools like EMBRYOAID or FOLLISCAN help us make quicker and better decisions. Furthermore, we are working on new ones that will aid doctors in some more tedious tasks.

31

1 commento

  I was recently given a pre-launch copy of the book: Domain Driven Refactoring – A Practical Guide to Refactoring Legacy systems using Domain Driven Design and Modern Architecture patterns. By Alessandro Colla and Alberto Acerbis I have not read the book in full, but the chapters that I did dive into make me want to read more. The book takes the reader on a journey that starts with the history of Domain Driven Design through patterns for refactoring and all the way to going from a monolith to microservices. As someone that often works with legacy systems, I wonder about those systems designed (or evolved) without using DDD principles, does it make sense to “Refactor to DDD”? If yes, how can that be done? This book seems to provide answers. Refactoring can happen for many reasons. We refactor because the code became too hard to maintain and understand, that type of refactoring is often the reason behind refactor patterns of decoupling, these are covered in the chapter called “transitioning from chaos”. We refactor because of some business need such as the need to scale. That is why we might for instance take a well written monolith and refactor it to microservices. Or we might refactor to a design that is more DDD friendly. Chapter 10 - “When and Why You Should Transition to a Microservices Architecture” explains that micorservices when done properly not only offers scalability and resilience, but can reduce complexity. A goal of its own. For me, part 3 is the highlight of the book. This section covers the topic of when and how it is appropriate to transition to a Microservices Architecture. This is a great chapter that is worth reading on its own. The book has lots of good examples and all code available in git. Thanks Alessandro and Alberto for a great addition to the DDD library.  I look forward to reading it in its entirety. The book can be pre-ordered at: https://lnkd.in/dy2unqw7  https://lnkd.in/dDuCQaX2

23

1 commento

#ProductThinking The ability to ask customers the "right questions" is probably the most crucial skill in a product company. Often, customers speak in terms of features instead of problems. The biggest mistake is to take the customer's requirements as-is without understanding what problem they are trying to solve. This article highlights the same. https://lnkd.in/dunynMmd

17