Clay & Code

Hello peers in wisdom, I hope you had a wonderful week. Todays topic consist on exercising a non technical part of software. Domain-Driven Design DDD is a set of tools that makes easier to understand business experts and then translate their knowledge domain to our domain (software). I encourage you to learn more by reading and watching the resources I found useful, they are at the bottom of the post. Pricing goods The definition of the problem is on this  kata . The goal, basically, is think about functionalities, edge cases and implementation for pricing goods at a supermarket. Steps I followed     Event Storming . This method helped me to start defining what where the things I expected to happen in this system. In the image you can identify them by the salmon color. Its important to note that at the bottom right is defined the meaning of each box color.           Commands and actors . The next step was to ask who makes what . In this case ...

 Hello peers in wisdom, One month ago I found myself reading The passionate programmer by Chad Flower, here the author gives valuable advises for building a strong career as a software engineer (is not easy by the way).One of his insights inspired me to write this brief blog to share with whoever read this. The more or less I learn this week.  As the title suggests, the advice is READ CODE. What kind of code? The good kind. So... after dedicating around 100 hours to read the Rust book and resolve some basic exercises   I felt prepared enough to tackle some real code. I decided to search in the popular section of crates.io, and I found serde, a rust library for data serialization/deserialization. After 5 minutes of cloning the project and reading I was completely lost. Are people who wrote this geniuses or did I just lose 100 hours of my life? Fortunately (or not) it was a mix of both. Anyway, the next day I am back at crate.io and this time I chose something less popular....