How Big Tech Ships Code to Production

แชร์
ฝัง
  • เผยแพร่เมื่อ 22 ธ.ค. 2024

ความคิดเห็น • 51

  • @gekkogordon
    @gekkogordon ปีที่แล้ว +11

    I'm an Agile project manager at a major financial institution, and it's incredible to witness our daily operations summarized in an impressive and efficient SDLC flow. Thank you!

  • @alwinsebastian7499
    @alwinsebastian7499 ปีที่แล้ว +47

    Often times convincing that a issue is fixed takes more time than actually fixing it.

  • @christophermaile3842
    @christophermaile3842 6 หลายเดือนก่อน

    One of 'BEYOND THE BEST' , YET RARE tutorials about Software Architecture. May you abundantly expand further in all aspects of your life. I much appreciate your effort and time you have put into all your visual presentations. Mega appreciation from all the way in SOUTH AFRICA!!!

  • @prashantjain9988
    @prashantjain9988 ปีที่แล้ว +5

    Quite close to what we do, just a small change, instead of deploying main/master to production, we create Release Branch with a cutoff of 1 week before rollout for UAT, stress testing and Marketing SignOff, then deploy that package.

  • @ApplyIT2021
    @ApplyIT2021 ปีที่แล้ว +5

    Concise video with the required information for newbies in less than 5 minutes.

  • @TheTacoReview
    @TheTacoReview 10 หลายเดือนก่อน

    We automate our unit testing on PUSHes. So that PR only happens on tested code. We have automated functional tests and fuzzing on pre-prod code, before pushing to production. Good video!

  • @dasnohvit
    @dasnohvit ปีที่แล้ว

    This is an excellent video to show AI-Advocates the real complexity of the software industry, especially as an answer to the new mainstream phrase "IA will replace developers".

  • @tarikkranda
    @tarikkranda ปีที่แล้ว +1

    Wondering if it is a typo in Release Step the environment labeled as "Development Environment" which is supposed to be "Production Environment"?

  • @dushyantchaudhry4654
    @dushyantchaudhry4654 ปีที่แล้ว

    every single word you said is gold!!! nothing extra said nothing missed out

  • @TheRavageFang
    @TheRavageFang ปีที่แล้ว +1

    In our case, merge to the main branch is only done after all the testing is done and all the tasks run on the PR branch first, only then it gets merged to the main branch, otherwise everything seems very familiar ✌😊

    • @sourandbitter3062
      @sourandbitter3062 ปีที่แล้ว

      You have a staging environment for each branch? Or do you mean you have a ci pipeline?

    • @grustyn
      @grustyn ปีที่แล้ว

      Same here, only merged to master when fully tested in QA env.

    • @grustyn
      @grustyn ปีที่แล้ว

      ​@@sourandbitter3062In my case we use a CI pipeline with multiple instances. QA1, QA2, QA3 and so on.
      The QA Analyst pushes the branch to one of the nodes and test it isolated.

    • @jora5483
      @jora5483 ปีที่แล้ว

      Is the main branch pushed to ci/cd pipeline? Do env variables reside in main?

  • @mohitamgaonkarmv
    @mohitamgaonkarmv ปีที่แล้ว +1

    You are doing great work sahn lam.
    Most of the seniors in the IT field are not aware of this.

  • @rupeshsingh2203
    @rupeshsingh2203 11 หลายเดือนก่อน

    I learned so many concepts from you

  • @nigh7swimming
    @nigh7swimming ปีที่แล้ว +2

    Don't use feature branches, use small self-contained incremental stories which can be tested and delivered using CI approach. This is more agile and gives early feedback and reduces chances of merge conflicts.

    • @MikeZadik
      @MikeZadik ปีที่แล้ว

      I don't see how those techniques are exclusive?

    • @nigh7swimming
      @nigh7swimming ปีที่แล้ว +1

      We tried both approaches on a large scale project and found feature branches cause more problems then small increments. When trunk is evolving fast it's hard to keep branches in sync and merge.

    • @MikeZadik
      @MikeZadik ปีที่แล้ว

      @@nigh7swimming Above, you say "don't do this". Then you say you tried and "it didn't work for you".
      I don't see how you get from it didn't work for us to nobody should do it. Maybe there is even a skill issue involved.

    • @nigh7swimming
      @nigh7swimming ปีที่แล้ว

      @@MikeZadik it didn't work for us, a big American corporation full of pros. But sure you know better, suit yourself. We tried and it didn't work is what I'm saying.

    • @MikeZadik
      @MikeZadik ปีที่แล้ว

      @@nigh7swimming it works for plenty of other big international companies full of pros.

  • @joelmathew5655
    @joelmathew5655 ปีที่แล้ว +1

    Should we merge to main branch before QA testing is done ? Also, do big tech companies follow a release cycle ? Also there should be multiple deployable environments in dev if they are following a release cycle

    • @Steelrat1994
      @Steelrat1994 ปีที่แล้ว +3

      There is no single way or solution. Every company and sometimes even teams within a company do it their own way. Some follow release cycles, some ship code continuously. Some have development/testing/integration/preprod environments, while others might only have a testing environment for QA to check end to end functionality. There are different approaches to maintaining your git repos as well, he described a trunk based development, where everything gets merged into master(trunk). Some people might still follow git flow with its merging hells.

  • @rupeshsingh2203
    @rupeshsingh2203 11 หลายเดือนก่อน

    Thanks Sir
    You are great explained very clear

  • @ChadRStewart
    @ChadRStewart ปีที่แล้ว +2

    Awesome video!
    Wanted to ask if you could make a video or newsletter issue about how a RFC / Design Document gets created and is used? Would really love to see how Big Tech works through this specific part of the process!

  • @Fer_S.
    @Fer_S. ปีที่แล้ว

    Great explanation!👏🏼👏🏼👏🏼
    Thanks Sahn 🎉

  • @agilemindset247
    @agilemindset247 หลายเดือนก่อน

    A sprint is typically 1-4 weeks long not 1-2 weeks as stated in this video, with 2 weeks sprint being the most popularly used cadence.......

  • @rossalexenderwilson
    @rossalexenderwilson ปีที่แล้ว

    Great video, though at the bottom shouldn’t that say “Production environment” rather than “Dev environment”?

  • @quanghuy9854
    @quanghuy9854 11 หลายเดือนก่อน

    That's great, we are applying that as well.

  • @monarch.war2024
    @monarch.war2024 ปีที่แล้ว

    How do we draw such maps ? What software do we use ?

  • @custard131
    @custard131 ปีที่แล้ว +5

    whats this "testing" you talk of? :p

    • @TheForge47
      @TheForge47 ปีที่แล้ว

      Overrated bs i guess 🤪

  • @mirzasohailhussain
    @mirzasohailhussain ปีที่แล้ว

    What tools you use for presentation and animations? Anyone have idea?

    • @pratiyush123
      @pratiyush123 ปีที่แล้ว

      I want to know this too

    • @zeektm1762
      @zeektm1762 ปีที่แล้ว +1

      It’s in the description

    • @mirzasohailhussain
      @mirzasohailhussain ปีที่แล้ว

      @@zeektm1762 thanks. I didnt notice that.

  • @AmeerHamza-cy6km
    @AmeerHamza-cy6km ปีที่แล้ว

    thanks now i can change the color of button for our production site. thanks

  • @ziaurrezajoy
    @ziaurrezajoy ปีที่แล้ว +1

    Thank you

  • @STONEcreator999
    @STONEcreator999 ปีที่แล้ว

    Nice work!!!

  • @InterfaceTrading
    @InterfaceTrading ปีที่แล้ว

    That's nice, but can you make the logo bigger?

  • @rafaelvschneider
    @rafaelvschneider ปีที่แล้ว

    Nice video, well explained!

  • @rizkiinsankamil1742
    @rizkiinsankamil1742 ปีที่แล้ว

    well explained!

  • @raj_kundalia
    @raj_kundalia ปีที่แล้ว

    thank you!

  • @gdthegreat
    @gdthegreat ปีที่แล้ว

    Title is changed 👍

  • @FaintArt
    @FaintArt ปีที่แล้ว

    I miss those long in depth videos..

  • @Jevinrandhawa
    @Jevinrandhawa ปีที่แล้ว

    Cool video

  • @sagancobra6402
    @sagancobra6402 ปีที่แล้ว

    Funnily enough i knew one company that didn't do any sort of 'staging'. Code was directly deployed into prod.no CICD even configured. Literally uploading code to prod hosts. Insanity

  • @jeanc.7w7
    @jeanc.7w7 22 วันที่ผ่านมา +1

    terrible lo que pasara en gestion xd

  • @Tony-dp1rl
    @Tony-dp1rl ปีที่แล้ว

    Jenkins .... urggghh