Usually both, it’s easier to check some assumptions using the IDE
18.08.2023 15:05
👍 1
🔁 0
💬 0
📌 0
Usually both, it’s easier to check some assumptions using the IDE
Here is the talk by the way.
https://www.youtube.com/watch?v=2LSOqikNqxM
There are many other cool features that Flix has, and I think I should totally give it a try soon, maybe write some article with the practical example for it.
It was sort of the same feeling as when I was coding in Java long time ago and was introduced to Scala which made a lot of routing stuff much easier and expressive at that time.
Just finished watching the GOTO tech talk about
@flixlang
lang. What I can say, after years of programming in Scala with cats-effect it feels so natural to have a language where distinction between pure, impure, and effectfull is built in.
Highly inspirational show
#cowboybebop #datadog #anime
Saw two dogs in the park today, one named Ninja and the other named Sushi, can you guess their breeds?)))
Spent 6 hours setting up my new laptop yesterday, this is what happens when you don't update your dotfiles repo for 2 years 😬
Watched Dune (2021) for the 3d time yesterday. It is simply amazing movie. Such attention to details, colors, light, music, etc, everything contributes to the thick, captivating atmosphere. Probably my favourite modern movie.
In my opinion, it is an absolute banger, 9 out of 10.
It covers most of the main topics of algorithms, at least all of those you will need in 99% of situations. After reading it, you will have a good intuition for solving algorithmic tasks. You can even find something useful for yourself outside the job!
The book is comparatively short-238 pages. Usually, books about algorithms are not so paper-stingy). But IMO, that's a good thing! Both from the perspective of ecology and grasping! Besides concise explanations with real-world examples, It is full of illustrations and exercises.
Had a detour from Software Architecture the Hard Parts and decided to read Grokking Algorithms instead. Firstly I wanted to refresh my knowledge of algos; secondly, it was a more lightweight read. More thoughts in the 🧵
Nice blog post on the unreasonable effectiveness of Merkle trees https://joelgustafson.com/posts/2023-05-04/merklizing-the-key-value-store-for-fun-and-profit
I just finished reading “grokking algorithms” today and was wondering why it didn’t mention that fun algorithm that alllows you tell if the contents of directories are different, but I couldn’t recall the name. And then I opened the bluesky and this is the first post I see, nice!)))
Finally got an offer! It was a long journey and somewhat exhausting, but I’m going to work for a company that I’m interested in, finally, phew 😅🎉🎉🎉🎉
Modeling uncertainty is focused on pushing business rules and constraints into the domain model, and involving domain experts in decision-making is crucial.
Overall, the section highlights the importance of business-motivated solutions in reactive DDD.
Explicitly Modeled Uncertainty:
This section discusses an example of modeling an uncertainty in the SaaS product business that matches clients with skilled workers for household jobs.
The main insight is that attempting to solve these problems through technology can be difficult and error-prone, ultimately failing to address the underlying business problems. The section states that the pursuit of certainty in an uncertain environment often leads to brittle technological solutions
The Challenges of Distributed Computing:
Section highlights the complexities involved in implementing a message deduplicator, such as data persistence, caching limitations, and the need for event identification. The uncertainty surrounding event handling, failures, and redelivery is emphasized.
The section further highlights that uncertainty is a manageable state and that there are ways to reason about the consistency or inconsistency of a system's state.
The Actor Model section:
This section discusses the goal of creating a reactive microservice as part of a larger reactive system.
It emphasizes the importance of modeling uncertainty in the system to avoid potential issues.
From "The Benefits of Using Strong Types" section:
It suggests using strongly typed IDs instead of raw UUIDs to ensure compatibility across programming languages.
It recommends modeling money as a Money Value Object to standardize rounding and scaling rules.
Here I will put some interesting excerpts from the article called "Reactive DDD: Modeling Uncertainty" by Vaughn Vernon, author of "Implementing Domain-Driven Design" and "Domain-Driven Design Distilled", a 🧵
The conclusion is that to flawlessly pass the behavioural interview you should have a bunch of good stories prepared beforehand, written down in some format (I use a table questions/projects) preferably using the STAR methodology.
It feels so good when you ready for everything on the interview.
Next was about a situation in which the team had a 1w before the deadline, but one of the team members sucks. I asked in what ways they suck? Interviewer said "their code is awful" but then quickly realized that wasn't really a valid question since everyone is using code reviews.We laughed about it)
This answer I think surprised them because they red this book and they were happy to hear I have also red it. The next question they were going to ask actually was to recommend them a book, so I have just killed two birds with one stone.
Then they asked me a couple of questions that I didn’t had an answer beforehand. Like when they asked me to teach them something I looked around my table and found a book - "Atomic Habits", I showed it to them and told them the things about habits and the power of 1% improvement every day.
Today's achievement:
I have nailed the behavioral interview with one of the companies.
The interview went really well, they asked me some generic questions, like conflicts, mistakes, and achievements. I had answers prepared already for this kind of questions. 1 / 🧵