This is why we use continuous integration

preview_player
Показать описание
Рекомендации по теме
Комментарии
Автор

I really like how you describe things in a "real" way. I always thought that there's something missing I didn't understand about CI, but it turned out to be just the limitations of it. There is no single conrrect way to implement it.

abdulazeez.
Автор

I look at CI as a mechanism that enables keeping environments in sync, by generating env artifacts based on code changes as soon as those changes are ready to be merged which is a consequence of your view on what CI is. I never had to deal with feature flags, so I appreciate you including it in this video and emphasizing that there is no "right" way of doing things; you usually do what works for your team/project/feature and go with the flow and adjust continuously.

Thanks for the informative video!

dehman
Автор

Really interesting to see how you manage this from a 10 person Dev team perspective. At this size I'd expect a reasonable level of autonomy as to the exact process, but simpler is better. Working in larger teams that I've experienced, there is a greater clarification of module or platform ownership and priorities agreed by a model of assessing the impact to customers and business requirements. We moved to automated verification testing, that included qualification based on that priority model. There are at times areas of overlap and there would be a system team or bod that would resolve these questions with the developers or teams in question.

colbr
Автор

Looks interesting. Will be trying it next time i work on a bigger project!

viktoras.buivydas
Автор

Great video. Interesting topic. How would you handle commits in this context? How does ci relate to commits?

stln
Автор

Hi, what about feature revert in your team approach? I mean, for example, I pushed lots of subtasks of my feature to dev branch, and for some reason business declined the feature and I need remove all code I already pushed. Is there some sort of life hack how to do this ?

Personally I prefer to make a feature branch and merge changes from dev branch once/twice a day (I think it depends on size of the team). Also proper code splitting across different files helps to reduce merge conflicts.

QesOrwuMqN
Автор

Could you make a video about SSR vs CSR in Next JS, differences an when should which be used? Thank you.

strahinja
Автор

Awesome content
++Keep Going for ever

hardikganatra
Автор

Can you do basic CI/CD integration for front-end dev?

gen_ninety
Автор

Hey Cody, nice video, unrelated, i saw a video about a tool called codeux or something whicj is a visual tool for creating a site that outputs react code and has vscode integration, if you try it please make a video

omomer