Hacker News new | ask | show | jobs
by jamiecurle 30 days ago
I see the point but, I'm not really sure the analogy holds up here. If i was in a cabinet shop and had to joint, plane and resaw and cross cut a pile of timber fresh from the saw mill for the next job I'd be very grateful for the jointer, the planer, the bandsaw and the table saw. I'd also be very grateful for the dust extraction.

In in total agreement with you though, forcing tools on employees is very dumb and is terrible leadership. Ask your people what they need to be optimally exceptional and go get them it. Then let them get on with it.
1 comments
andsoitis 30 days ago
> In in total agreement with you though, forcing tools on employees is very dumb and is terrible leadership. Ask your people what they need to be optimally exceptional and go get them it. Then let them get on with it.

Some employees want AI tools, others don't. Standardizing SDLC workflows > each person does their own thing. So now you have to choose: do you require AI tool use that fit into a new SDLC? Or don't you?

link
jamiecurle 30 days ago
I don't see why they have to be mutually exclusive. Assuming the vendor risk profile is acceptable to the infosec people and procurement are happy with the AI tools vendor relationship, then it's a tool inside the information security perimeter.

As long as there's evidence that work meets quality gates for any required customer audits, and your customers are happy and in the loop that AI is a thing that may or may not be used to produce the service, then those engineers that want it can have it and those that don't, don't.

Feels like a revision to an SDLC rather than a new one. Without seeing the SDLC it's hard to find common ground though. It really depends on how it's written and implemented and of course: culture. In the example we're working from sounds like the tools are being forced on people, and that's less infosec, SDLC and more unbearably bad leadership.

link
andsoitis 30 days ago
Not sure why you bring in "vendors" and "infosec". I'm simply talking about the situation of a software engineering team building something together needing to have similar workflows (supported by tooling/software) in order to work together effectively.
link