Don't somehow release | Handling the Social Pressure | Architect 101

In this video, we explore the critical importance of resisting client pressure when it comes to production releases. Rushing a release just to meet client demands can lead to disastrous consequences, including bugs, system failures, and long-term damage to your software's reputation. We'll discuss strategies for managing client expectations, ensuring quality over speed, and maintaining the integrity of your codebase. Learn why it's essential to prioritize thorough testing and proper timing over a hasty "somehow release" approach. Protect your code, your project, and your peace of mind by sticking to a solid release plan.

[@codekids99]

Thank you and keep it up!

[@sachithlakmal6578]

Always on point. Good talk krish 🔥

[@csatanarachchi]

Good point. Let's consider a scenario where you don't have a viable workaround that the client might accept. If the client disagrees with the proposed solution and no alternative is available, how do you ensure the protect the interests of your team, company, and client?

[@krish]

good point. ill take this as topic

[@csatanarachchi]

@@krish Thanks in advance!

[@alexwanigasekara5886]

That is excellent advice. Thanks. And I have a small request. Could you please create a video about estimation techniques also?

[@user-sj7bp2ms3u]

This is also something important if you can talk about Krish

[@asankasanjaya7532]

Good advice that is!

[@DJJimboSlice]

Is he talking to me directly?

[@HasiniDayanandaGPlus]

Is posting your project decisions on social media ethical?

[@csatanarachchi]

Dude , take these guidelines as general advice-you won’t really understand their value until you’re in the thick of the problem. We should appreciate him for sharing his experiences on social media platforms. Otherwise, you’d only come across this kind of insight in paid sessions.