I need to debug a thing that runs in CI. Part of the run is a tool that takes five minutes to run and this makes iterations slow. I could rewrite that to run in less than ten seconds, but doing that would take a week or two of full time work. What do I do?
@liw do the slow detour if it can be useful for other things than just that debugging
@liw how often will you use the tool after this round of debugging?
@valhalla Many times a day.
@liw detour! detour!
@liw I am in favor of sshing into the CI in this situation and just iterating in place. I don't care that this is not what CI is for or not how it should be used.
@liw
<evil grin> use an LLM to interpret the CI definition and ask it to generate an overengineered stub that simulates your CI environment and then call that every time?
(yes I've seen people do that 🤷)
<evil grin> use an LLM to interpret the CI definition and ask it to generate an overengineered stub that simulates your CI environment and then call that every time?
(yes I've seen people do that 🤷)
- replies
- 0
- announces
- 0
- likes
- 0
@liw Perhaps there is a less aggressive rewrite that could be done more quickly that would reduce the runtime to, say, two minutes, by just optimizing what is already there. I would check out that possibility first.