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

My "favorite" is when I see people go all in, writing thousands of lines of Jenkins-flavor Groovy that parses JSON build specifications of arbitrary complexity to sort out how to build that particular project.

"But then we can reuse the same pipeline for all our projects!"



I think that is pitfall of software devs.

For me it was an epiphany as software dev - not to write reusable extensible scripts - I am so much more productive after that.


> "But then we can reuse the same pipeline for all our projects!"

oh god just reading that gave me PTSD flash backs.

At $priorGig there was the "omni-chart". It was a helm chart that was so complex it needed to be wrapped in terraform and used composable terraform modules w/ user var overrides as needed.

Debugging anything about it meant clearing your calendar for the day and probably the following day, too.


I can rarely reuse the same pipeline for the same project 6 months down the road, much less reuse for anything else.

The few bits that end up getting reused are the externalized bash scripts.




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

Search: