This is a feed of links I've run across and found interesting or noteworthy. The images, content and opinions in them are owned by their respective authors.
“Well I’m a senior engineer so we’ll do it my way.” I always hated conversations like that as a junior engineer but they seem to be a natural consequence of titles. Keep titles private and the best…
This month's .NET Foundation Project Spotlight
A simple, fluent, extensible, and fully customizable library for throwing exceptions for projects using .NET 6+ - GitHub - mantinband/throw: A simple, fluent, extensible, and fully customizable library for throwing exceptions for projects using .NET 6+
Run a SQL Server container with database initialized from a script using docker-compose.
HashiCorp Vault — This product is currently running in many big enterprise companies. I have seen a lot of people complain about the complexity of it and the pain of setting it up. I think this…
Estimates are waste, in that time spent estimating is often time that could have been spent producing something with business value. The first of the 5 laws of software estimates, this one is easy to demonstrate in the context of software developers. However, like so many things in software, it doesn't always hold when that context shifts.
Coming from a customer facing team that was responsible for over a dozen different applications, our team relied heavily on end-to-end testing to ensure that everything hung together correctly before…
Guillermo Rauch tweeted this a while back. Let's take a dive into what it means.
Don't use actors for concurrency. Instead, use actors for state and use futures for concurrency. A common practice I've seen in scala code is to use actors for concurrency. This is encouraged by Akka and a lot of writing about Scala, the documentation of which is highly actor-centric. I assert â¦
In this tech talk, John Murray, Senior Software Engineer at AppNexus, serves up an introduction to Actor Model principals and concepts and gives a look at ho...