In today’s API economy, we are always dealing with some piece of JSON in and out. We also prefer strongly typed serialisations/deserialisations for better practices. This not only helps overall programming experience, but also abstracts DTO in a very productive way. In this context, when it comes to productivity, I think one of the best … Continue reading Past as JSON
I think knowing what it isn't makes life much easier than trying to fit it in various bespoke definitions... DevOps is NOT… easily achieved nor implemented a product or tool chain a job title or role a cloud infrastructure provider a book a technology a programming language a marketing campaign CI/CD Kubernetes containers open source … Continue reading DevOps is not
I have been working on a small project that has some components which have some real-time inter-dependencies. Most of these dependencies are actually making sure a request with access token (JWT/OpenId) is from a genuine user and that user has correct access rights. Although the token and UserPrincipal have enough information, regarding the critical operations … Continue reading Resiliency Upgrade Is Now Easier Than Ever
Amazon’s “two-pizza teams”: The ultimate divisional organization Amazon’s “two-pizza teams” are well-known; they’ve been written about in Fast Company and the WSJ. But almost everyone misses the point. They aren’t about team size—they’re about autonomy and accountability. I have seen so many people, conferences, articles talking about this topic but never seen a better explanation … Continue reading It is not the size, it is the autonomy…
Yet another great article and I have to admit I have been working in feature teams a lot in my career... Product vs. Feature Teams | Silicon Valley Product Group — Read on svpg.com/product-vs-feature-teams/
I think I have always struggled the necessity and this thread is golden answer for this... twitter.com/andrewchen/status/1168249691919638529
I think I have seen and even written these 6 lines of codes in one way or another. However, this talk gives a great deal of how to organise a solution with a business language such that non-technical people can understand and suggest/agree on a potential solution.