Ask me to write about anything.

twitter logo github logo ・1 min read

Hi, I'm Bertil.
I have worked as a consultant, trainer and coach for about 14 years.
The roles I worked in include: scrum master, agile coach, programmer, tester, systems architect, requirements engineer, project manager, and others.

Here's the idea, it's a little twist of the original "Ask me anything" category.

Ask me to write about anything. Just suggest a topic in the comments that you are interested to learn more about.
I will pick one topic and write about it. Maybe more than one topic.

There's a caveat.
I am human, and it would be foolish to claim I know everything.
Chances are: in one or several of the roles I mentioned above, you have deeper knowledge than me. But I am always eager to learn.

So let's see how this little experiment goes.

twitter logo DISCUSS (9)
markdown guide

How to make a business case for switching to a new framework, using a different library, language, or technology?


Here are some ideas:

  • My ideal deployment process
  • The new language I'm most excited about
  • How (and why) to move from engineering to a management role
  • How to maintain long-term career satisfaction
  • How the software industry has changed in the last X years
  • How to get into software consultancy
  • What programming in BASIC was like
  • How to recognize when new software is all hype

How to recognize when new software is all hype +1


Hi Bertil, not sure if you are interested in this, but I would love to hear more people speak about testing software.
In particular I am lately thinking a lot about testing of systems in a time that everyone want to build micro services.
We can write unit and integration tests to ensure that each service works, but what approaches do people take to ensure their system is working as a whole? How do you create tests that have to deal with potentially hundreds of separate services at once? Do people run automated tests for this or do they spend a lot on QA in a dedicated staging environment?


Others have written quite extensively about this topic. One popular way to test microservices is by Consumer Driven Contract Tests. The basic idea is that when you test a microservice X, you make all the behavior expected by consumers of X part of X's test suite.
Look here for details:

Another thing to keep in mind is: for a microservice approach to work, you need technical excellence in operations. That's why Netflix for example pioneered their "Chaos Monkey" that randomly terminates services in production (in order to check how resiluent the whole system is). Look here: github.com/netflix/chaosmonkey.

Hope that helps.


Thanks, that article on Consumer Driven Contract Tests looks interesting! I put it on my list!
Chaos Monkey is definitely a good tool to test and harden your production system.
I still think there is room for more material in that space. There are just too many aspects that matter for ensuring a complex system is working properly.
I really like this article talking about staging environments and yet I think there needs to be more material and examples about setting up automated tests in an as realistic as possible staging env.
Testing in production is another big topic. There are many thing you can do around A/B and split testing. There are great tools like GitHub's scientist, that solve specific use cases and of course there is a lot to say about monitoring and observability.


The importance of software architecture and testing in small projects.


A walkthrough of the gorilla.bas program, I've always been in awe of that code

Classic DEV Post from Feb 9 '17

The 4-letter-word word that makes my blood boil

Bertil Muth profile image
Agile coach and developer

Sore eyes?

dev.to now has dark mode.

Go to the "misc" section of your settings and select night theme ❤️