3 ms·

I dont understand the point of this CI argument. Is he arguing CI is bad in principle? For environmentalism reasons or something? I dont use Github, but I stil

I dont understand the point of this CI argument. Is he arguing CI is bad in principle? For environmentalism reasons or something? I dont use Github, but I still run CI for all my projects even if the build is a single line. Its a requirement. Its the only way to get past 'works on my machine'. Honestly I'm not even sure what the author is suggesting here.

Tainnor 6y ago
Yeah it seems like they seem to be opposed to CI for some reason. I mean, I guess most people that use CI are glad they have it (because it fixes exactly that "works on my machine" problem that you mentioned), but who knows.
hobofan 6y ago
> Honestly I'm not even sure what the author is suggesting here. Did you miss the point about writing "good & efficient code"TM? Just write good code and you won't every need to think about CI again!
- injidup 6y ago
  You won't ever need to think about CI again. Or will you?
fxtentacle 6y ago
He's arguing that you only need CI after a lot of other things already went wrong. If your code is portable, clean, readable, easily maintainable and contains tests, the benefits from CI over running the build locally are negligible. So CI distracts from fixing the issues that people face when building locally.
- dgrin91 6y ago
  How do you enforce test being run without CI? I forget to run tests locally all the time.
  - pan69 6y ago
    Set up a pre-commit or pre-push hook that will run your tests. https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks
    - slooonz 6y ago
      And how do you test that your tests pass in other environments ?
      - pan69 6y ago
        Depends on what you're building, you might not have other environments as such, but I get the point (I'm pro CI for the record). My comment was aimed at: > I forget to run tests locally all the time.
    - dgrin91 6y ago
      This doesn't solve the problem. New person joins the team, doesn't do this. Now what?
      - pan69 6y ago
        In JavaScript projects we're using Husky [1]. I'm sure other environments have their own equivalents of it. [1] https://github.com/typicode/husky https://github.com/typicode/husky
- jhanschoo 6y ago
  > If your code is portable Yet how do you know for certain if your code is portable if you only build locally?

Tainnor 6y ago

Yeah it seems like they seem to be opposed to CI for some reason. I mean, I guess most people that use CI are glad they have it (because it fixes exactly that "works on my machine" problem that you mentioned), but who knows.

hobofan 6y ago

> Honestly I'm not even sure what the author is suggesting here. Did you miss the point about writing "good & efficient code"TM? Just write good code and you won't every need to think about CI again!

injidup 6y ago
You won't ever need to think about CI again. Or will you?

fxtentacle 6y ago

He's arguing that you only need CI after a lot of other things already went wrong. If your code is portable, clean, readable, easily maintainable and contains tests, the benefits from CI over running the build locally are negligible. So CI distracts from fixing the issues that people face when building locally.

dgrin91 6y ago
How do you enforce test being run without CI? I forget to run tests locally all the time.
- pan69 6y ago
  Set up a pre-commit or pre-push hook that will run your tests. https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks
  - slooonz 6y ago
    And how do you test that your tests pass in other environments ?
    - pan69 6y ago
      Depends on what you're building, you might not have other environments as such, but I get the point (I'm pro CI for the record). My comment was aimed at: > I forget to run tests locally all the time.
  - dgrin91 6y ago
    This doesn't solve the problem. New person joins the team, doesn't do this. Now what?
    - pan69 6y ago
      In JavaScript projects we're using Husky [1]. I'm sure other environments have their own equivalents of it. [1] https://github.com/typicode/husky https://github.com/typicode/husky
jhanschoo 6y ago
> If your code is portable Yet how do you know for certain if your code is portable if you only build locally?