Ah well, fortunately for me I'm in the business of helping people with the "practice"!
However, I do think that a lot of the issues you allude to in convoluted build processes stem from a lack of consideration of the "theory". It's all too common to see organisations that start by downloading Jenkins (or similar), aren't sure what to do next, so proceed to create a rat's nest of interlinked jobs with a few manual processes along the way.
It might be more helpful to draw the distinction between the "why" and the "what" rather than between the "theory" and the "practice" - and it is the "why" that informs the process of doing the right "what"!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Ah well, fortunately for me I'm in the business of helping people with the "practice"!
However, I do think that a lot of the issues you allude to in convoluted build processes stem from a lack of consideration of the "theory". It's all too common to see organisations that start by downloading Jenkins (or similar), aren't sure what to do next, so proceed to create a rat's nest of interlinked jobs with a few manual processes along the way.
It might be more helpful to draw the distinction between the "why" and the "what" rather than between the "theory" and the "practice" - and it is the "why" that informs the process of doing the right "what"!