Live data from Hacker News

After 15 years, I use Outlook as my build pipeline

iwriteaboutcode.blogspot.com

71–73 of 73 posts

Re: After 15 years, I use Outlook as my build pipeline

#71
post #5

Earlier quoted context omitted.

Yeah, this is textbook "shadow IT" that could easily lead to something going seriously wrong. It's a fun example, but not something to aspire to. Ultimately the problem is that in a lot of big corps, IT is basically unaccountable for setting things up wrong. Their only KPI is tickets closed, not the quality or success rate of their fixes.

I've always felt that if business types can get over their fetish for trying to measure absolutely everything, we wouldn't have problems like these that stem from poorly thought out KPIs. They default to tickets closed, uptime, SLA adherence as KPIs because you can't effectively measure "is it set up correctly?" and because the business absolutely must measure everything, they come up with bullshit KPIs so they can h…

Ticket closing and KPI chasing is alive and well in small companies too. I have a client (less than 100 folks) that has a JIRA reporting process on par (and as bad as) as F500 company.

Seems to geared towards tracking work and increasing accountable behavior.

But then the consultant overseeing it (not me) sent a Claude generated report with some sort of JIRA ticket dump as input. All the tickets closed were in fact not done or not relevant. But they were “closed” in JIRA. Same thing with completed tickets.

Embarrassing work product and embarrassment for the company.

Re: After 15 years, I use Outlook as my build pipeline

#72
post #12

[flagged]

If your build pipeline is anything more than a monkey scratching bits into a spinning disk using a needle, you are a fraud.

> If your build pipeline is anything more than a monkey scratching bits into a spinning disk using a needle, you are a fraud.

Obligatory XKCD cite: https://xkcd.com/378/

Re: After 15 years, I use Outlook as my build pipeline

#73

[flagged]

There are so many issues with what you have here… where to start… You aren’t running tests, unless you put them in the dockerfile which is a bad idea… You aren’t running security scans. how do you deploy manifest changes? Using Latest as a tag has so many issues. This is a trivial and niave pipeline I would expect from a junior or intern. Build pipelines are becoming more complicated because software is more complex.…

Adding steps for code quality scanning, dependency vulnerability analysis and a license scanner certainly makes it look like you actually achieved something in the next performance review, I will give you that.
Post reply on HN