Clearly during COVID-19, Slack became more mainstream. I was wondering how they cope with that scale and found this article. They shared how they deploy. These are the interesting points from the article. Deploys require a careful balance of speed and reliability. As understand from their article, although they are available globally, they still mainly operateContinue reading “Always Fail Forward and Pull over Push”
Category Archives: Blog
Tracking Request Body via Application Insights
Application Insights is a great monitoring tool combines tracing, monitoring and even logging via custom events in one place. For any application running on Azure, it is the native way of doing and especially for .NetCore applications (.NetFramework is still supported?) so much easier to integrate. As most of the tracing tools in the marketContinue reading “Tracking Request Body via Application Insights”
Back to the Future
This is a really interesting take on app architecture. Although it doesn’t unfold a lot of details, it still gives a perspective. A BFF to handle client-server sync An SQLLite DB for state management Using OS UI to reduce boilerplate Using perf budgeting to keep things under control Project LightSpeed: Rewriting the Messenger codebase forContinue reading “Back to the Future”
More browser based workflows…
I have been using Sketch for a long time and been really happy with its native Mac performance. However, one of the problems between dev and designer was the handoff. I used tools like Zeplin but again it was just too much of a ask for designer to upload the Sketch file to another toolContinue reading “More browser based workflows…”
Paying bills on time!
link.medium.com/Q9ZeO3a9x3 This is no different than having a good financial independence, paying bills on time! Not paying bills on time punishes you with services being cut, reduced comfort and increased levels of stress for everyday. This analogy is no different when it comes to tech debts in architecture, code base and even at the productContinue reading “Paying bills on time!”
Always keep moving forward!
Avoid working half of the product!
link.medium.com/SWRzVXupN2 I think, this article explains really well how not to scale an engineering team. I really liked this analogy. When a team only works and be responsible half of the product, everything else falls apart. Especially introduction of microservices as an architecture and organisation pattern, to avoid above issues, it is also better toContinue reading “Avoid working half of the product!”
