14
MrCSharp
13d

A SW developer commiting an executable in his source repository, is an idiot.
A HW developer doing the same, is a wise man.

Comments
  • 0
    I don't get it. Please explain.
  • 3
    I'll say it again, committing executables is a bad idea. Putting executables in zip files and uploading them as releases is a great idea. It's literally 1 extra step, people. Figure it out.
  • 2
    @gronostaj Hardware developers have to deal with weird compiler toolchains that will fail compiling your code after a very minor change (adding a comment for example) for some weird reason so this is standard practice apparently to keep the compiled bits stored somewhere with the code.
  • 1
    @arcsector I agree, but hardware developers deal with different set of issues that warrant them storing the compiled bits in git.
  • 0
    I sometimes do it, when I have dependencies, which are executables, but not downloadable via a package manager or similar, and I have to use them for CI...
  • 0
    But what if I want to create an executable job on kubes in a repo? With CI etc?
Add Comment