Whenever I have worked with teams or Scrum Masters there has always been one book that I have recommended them to read. And now I'm happy to see that it has been updated.
I stumbled over this document dating back to World War 2 where the predecessor to CIA, the Office for Strategic Services issued a field manual on how to sabotage. Especially interesting are the sections on general interference with organizations and production.
The microservice hype where every application that uses a service should be implemented as a series of microservices is a little unhealthy. Like most technologies; if you don't know what you are getting yourself into there will be problems...
Testing things where you need to fake time is not hard given the right abstractions. That is why when I read this article I felt really sad. Because while the article describes one way to fake time it does so by breaking three fundamentals which is pretty hard in three lines of relevant code...
Almost 2 years ago I wrote about this problem with accessing data from Azure and returning it in a LINQ friendly way. Well not long ago the discussion came up again only this time it was in regard to access data in a Cassandra cluster.
I think it is safe to say that anybody who is serious about security will tell you that security through obscurity is no security. Yet a lot of people think obscuring is a great way to increase security like for example return 404 rather than 403 on REST APIs when the caller does not have rights to retrieve an existing resource.