I am not a big fan of pushing the code on the same day(excluding Hi-Pri issues), no matter how small the feature or defect fix is. I have seen teams and managers pushing developers to push every feature on the same day just to earn some brownie points from customer, only to backfire with a Prod Hi-Pri Incident. The focus should instead be on process and due diligence. If the process is so bullet proof that it can push features to Prod on te same day without developers burning themselves, go for it. Otherwise stick to the process and take the time it justifiably requires
Great questions. Thanks a lot for this video. However, as Koushik mentioned.. pls don't take it too objectively. Although these are data driven but can be very subjective to the industry/domain. For example in a Healthcare IT project where Regulations are so stringent.. we need to go through a lot of quality, verification and validation phases and checks before we ship something to production servers. So Commit to production can be high. However in the same industry the Incident response time can be super fast. Thereby not every commit ships to production at the same speed.
1) Time from commit to production - 2:58 - ruclips.net/video/2fZszuimOEw/видео.html
2) Core review turnaround - 5:52 - ruclips.net/video/2fZszuimOEw/видео.html
3) Incidence response time - 8:39 - ruclips.net/video/2fZszuimOEw/видео.html
4) Deployment frequency - 11:01 - ruclips.net/video/2fZszuimOEw/видео.html
5) Average onboarding time - 14:16 - ruclips.net/video/2fZszuimOEw/видео.html
Dear mr Brains
I've sent you a couple of emails already without reply so far.
Could you please have a look. I love your teaching style.
thanks!
Please make a deep dive course on Java 9 to Java 21 features.
That would be awesome
I am not a big fan of pushing the code on the same day(excluding Hi-Pri issues), no matter how small the feature or defect fix is.
I have seen teams and managers pushing developers to push every feature on the same day just to earn some brownie points from customer, only to backfire with a Prod Hi-Pri Incident. The focus should instead be on process and due diligence. If the process is so bullet proof that it can push features to Prod on te same day without developers burning themselves, go for it.
Otherwise stick to the process and take the time it justifiably requires
Great questions. Thanks a lot for this video.
However, as Koushik mentioned.. pls don't take it too objectively.
Although these are data driven but can be very subjective to the industry/domain.
For example in a Healthcare IT project where Regulations are so stringent.. we need to go through a lot of quality, verification and validation phases and checks before we ship something to production servers. So Commit to production can be high.
However in the same industry the Incident response time can be super fast. Thereby not every commit ships to production at the same speed.
We ship code fast. Cause we have no standards. 😂
sir please give me access to the courses I sent email to you but no reply Thank you
Morphis, the master!!
The best! Thank you.
😂
fresh video
U best