Do you remember a time when you learned something so quickly because you had an afternoon to experiment and a way to find out whether something worked? Riding a bike? Solving a puzzle? Learning to cook?

By adopting cloud computing, us developers place trust in service providers that our code and data is not manipulated once deployed - but how can we make sure?

Monorepos store everything in a single repository, whether it’s code, documentation, or any other asset that has to do with the system you are building. This leads to a large number of commits and stakeholders, so how can you mitigate plunging it into chaos?

Do you remember the good old days when SSH, manual tuning, and shell scripts were considered a solid base for running a Linux server? Often I couldn’t remember how I configured something just a day later…

One reason to like the Rust ecosystem is testing. No test runners need to be installed, no reading up on 10 variations of unit testing frameworks, no compatibiltity issues…

The AzureML SDK is Microsoft’s machine learning support framework that comes with several examples, docs, best practices etc. However, working on a simple ETL-type scenario, I learned a few key insights that I wanted to share. First, let’s clarify what AzureML Services are.