@VeraxMusic
This IBM channel is so underrated when it comes to teaching.
@samueljung6920
This was great. People always talk about CI/CD together and I love how you separated these two. Definitely will look for more vids from you. Thank you!
@aldolunabueno2634
(Active recall) Core principle: Continuous integration is oposed to: Benefits of continuous integration: ---------------------------------------------------------- 3:23 Core principle: "If it hurts, do it ofent and it won't hurt so much." 5:43 Continuous integration is oposed to the old way of infrequent integration. 5:53 Benefits of continuous integration: 1. Avoids merge hell. 2. Constantly gives us a testable build. 3. Keeps the developers productive.
@deckardcheung1824
This is the first time I got a clear explanation of what is CI, good job!
@hanielgaali
Best explanation that made it super simple to grasp for network engineer! Thank you
@HoldenMadagameTenor
Very clear explanation of CI. It can be hard to find a clear definition of this that doesn't go into the various kinds of CI/CD pipelines that are possible, so thank you for this.
@MrBlueSky1203
This was an extremely helpful video. Thank you.
@shandou5276
This entire mini-series is excellent!
@charlesopuoro5295
Thank you so much. You took the time and made the effort to help yoir audience understand just what Continuous Integration is including its premise, that answers the why and the resulting benefits. Salute!!! Thank you for your charitable contributions.
@NamLeThanh
I love how there's a video explaining CI as a single concept then another CD video. Usually you're always faced with CI/CD as a single "concept" and showing the clear border and what is what is extremely helpful to understand these 2 concepts better.
@ghtegnerlitt
I used to always mix what does what, but your video easily clarified it for me, thank you so much!
@pixelart0124
3:30 that... that just changed my life. Wise words. Wiser have never been spoken.
@carlosvillarreal7989
Love this video! Thank y'all so much for posting.
@crictune8820
An exceptional explanation of the topic, Thank you.
@erika210792
Great Erick! Very helpful video to understand the basics.
@Ernani910
Great job on that video, Erick—you really knocked it out of the park!
@Mohib3
best explanation on the internet
@kumailn7662
Super and easy... keep going posting such videos, really need guys with very clear on subjects.
@natetolbert3671
My solution has always been pull-push on EVERY commit. And I commit often; probably too often. Example: if I am working on a story/feature and I notice something trivial like a typo in a comment, I will stash or commit my feature-related changes up to that point, fix the typo, add and commit it in its own commit, and get back to feature-related changes. I would push and pull for each of these commits. Obviously, I wouldn't need to pull twice within like 2 minutes, but I would do it anyway, just because it would bug me otherwise. Honestly, just doing it inside the same branch as the feature bugs me, but I just bite the bullet there, because that is when coworkers start to get annoyed. But if I was working on a solo project, I definitely would. Rule #1 & Rule #2 for me: A place for everything and everything in it's place.
@cacurazi