Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My experience is the opposite.

Teams that are knowledgeable jury rig their own custom solutions without all the enterprise cruft. They make solutions that fix their problem and they do it faster than the teams who use bloated enterprise solutions.

I am tired of seeing over engineered enterprise solutions that that are implemented and never used because they can’t be integrated into the dev workflow easily. Simple bash script that does the task it was designed to do beats any enterprise crap.



The wisdom of pipes! I'd share these workflows the exact same way we share others [ie: BASH, Ansible]: Git. Needs nothing more than a directory, though an SSH daemon is quite nice.

Those of us who can survive without desperate monetization plays are worth quite a lot, actually. They say 'jury rig', we say 'engineer'.


The main problem with enterprise crap is portability. It only runs under very specific circumstances.

Bash and Perl scripts run, truly, everywhere - so you get real collaboration. I can share it with anyone on my team and they can use it.


Well written bash will run anywhere. Amateur bash will only run on the version of Mac OS it was written on, and even then only after the correct collection of random homebrew packages installed has been installed.


I agree, which is why I think most bash scripts should actually be Perl scripts. There, I said it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: