Hacker News Reader

Comment by ranger_danger | Hacker News Reader

I assume it's mainly targeted at devops people who absolutely know what CI/CD is and use it all the time.

Every person involved in software engineering should be aware of CI/CD and use it all the time, not only "devops people".

Agreed. However, I still believe explaining acronyms is good practice.

Every person who should be aware of CI/CD needs to learn it at some point.

I'm in software engineering and I'm aware of continuous integration but rarely use it and when I see CI its not the first thing that springs to mind. Any questions?

This case is a special though, as Bob CD is not a 100% complete package for doing CI/CD, it is one fundamental building piece for building your own CI/CD solution on top of.

So devops people would use Bob CD to build their in-house solution for it, and everyone would be using that, without actually using Bob CD directly.

For anything to do with embedded development, this is not reasonable.

Maybe try https://bobbuildtool.dev/ ?

Perhaps I should have been clearer.

Having an automated process to check out the most recent revision of the codebase and compiling it is just as easy as with other development.

Doing anything with that in an automated process is usually far more difficult. Suppose I'm developing a WiFi thermostat. The flashing process for that may require manual intervention, but let's leave that aside.

So the new code runs, now what? I need a webcam to look at the display, a robot to press the buttons or turn the wheel, and further fixtures to see if it is turning on the furnace appropriately.

Or we could simulate all the hardware in software... do I need to explain how much of a project that in itself is? Sure, it can be done, but it is the old question of time and cost.

Reply on news.ycombinator.com