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.
You know, because digital information can take 2 days to travel from server A to server B I think this is really an eye opening case. Business deal with data and possibly storing and using Public Cloud Providers, they should change the mentality of how they server to their customers. I know that eventual consistency … Continue reading A Good Story of a Web Developer Publishing to Native World
I think with the popularity of microservices, this issue has become a more prominent discussion at code reviews, design meetings etc. There are obvious places like Contracts to be the best abstraction and even distributed in a private package manager feed so that you avoid duplication and don't repeat yourself. However, as mentioned in the … Continue reading Tight Coupling Made Easy In Microservices
I think the idea of text based only emails getting a seat on the table and even looking a good long term investment for Privacy! Once we allowed email clients to act as de facto web browsers, loading remote content from servers when messages are viewed, we opened up not just a can of worms … Continue reading Email Privacy
These are my notes from the book Beyond The Legacy Code by David Bernstein. I think most of the items here are always acknowledged by developers, managers etc. but really applying them in daily development activities take a lot of time to establish as a culture. Say what, why and for whom before how (turning … Continue reading Beyond The Legacy Code Book Summary
I firmly believe the centralization of infrastructure automation and especially terraforming are defeating the purpose of Devops and Continous Value Delivery. Every deployment/repo should have their own terraform scripts that can be run in every release atomically for that deployment/repo. This will make sure the blast radius of something going wrong contained to one repo/deployment. … Continue reading If you have a team called Devops, just stop!