Comments by "Daniel Sandberg" (@ddanielsandberg) on "Computerphile" channel.

  1.  @BarelyGoodTV  Lol. Sad, but true. :D
    2
  2. You learned version control.
    1
  3.  @ZT1ST  In CI/CD we don't have "QA branches", "staging branches" or "production branches"...
    1
  4.  @ZT1ST  I was unclear so I think there was some misunderstanding... In CI/CD we don't associate a branch with an environment. An environment is a set of resources, configuration, applications and processes - not a branch. We build it *once* and stamp a "version-number/commit-id/build-number/whatever" on the package we just built (or at-least create a tag). We then deploy that SAME build/tag to every downstream environment as it *progresses* through dev, staging, prod. We don't have a "QA-branch" that we deploy and test, and then merge that to a "staging branch" and rebuild and deploy it (which is now untested) and then merge that again to a "production-branch", rebuild and deploy (which is still untested).
    1
  5. Do CI/CD and always push to main.
    1
  6. Yes. It's called pair programming and Continuous Integration.
    1
  7.  @Ermude10  I'm sorry, I was unclear. I never argued against Git. I commented about your comment about convoluted processes and "requirements to review even the most mundane changes" and that there have to be better ways to collaborate. None of which has anything to do with Git. There are probably tools out there that achieve the same things as TBD/CI without the overhead of Git but I don't know... OK?
    1
  8. Yay, try using tabs in YAML files. PS. Use .editorconfig
    1