An Isolated Developer Setup with Docker – oooops.dev
A setup to run any kind of application on a developer's laptop in complete isolation - powered by Docker containers| oooops.dev
In this article, I want to challenge where software testing happens and suggest that most manual verification (desk checks, QA, demo) that is part of a team’s delivery lifecycle should happen in production itself, rather than in some staging or UAT environment. I have used this approach in several teams within medium to large organisations&ellipsis;Read the full post »| oooops.dev
A setup to run any kind of application on a developer's laptop in complete isolation - powered by Docker containers| oooops.dev
DevOps is hard| oooops.dev
DevOps is hard| oooops.dev
How to attach remote profiler to JVM in AWS EC2 instance| oooops.dev
Generate distance from the main sequence and Clean Architecture metrics for Java codebase| oooops.dev
DevOps is hard| oooops.dev
tl;dr They are often broken in pipelines and that might be because they are broken as a concept. A typical issue in a microservices architecture is ensuring that the integration between services wo…| oooops.dev
We have all been warned not to use ES6 classes. Perhaps by our colleagues, or perhaps by the endless amount of scary blog posts that show up if you dare Google the subject. However, if you thought …| oooops.dev
A lot of us are practising Trunk Based Development and/or Continuous Deployment. I'm also a big fan. But, as cool and shiny as these practices are, I believe they do present some risks. In this article, I want to share my approach to incremental, safe releases during everyday story work.| oooops.dev
