zlacker

>>peteth+(OP)
> The fear is that these [AI] tools are allowing companies to create much of the software they need themselves.

AI-generated code still requires software engineers to build, test, debug, deploy, secure, monitor, be on-call, support, handle incidents, and so on. That's very expensive. It is much cheaper to pay a small monthly fee to a SaaS company.

>>latefo+G02
Atlassian tools for a client like mine (hundreds of employees) can easily cover the expense of internalizing it. It's Jira plus confluence mostly, it's not rocket science.

And that's just atlassian.

Start adding stuff that costs many many many yearly salaries (special software for managing inventories and warehouses) it starts making sense to prototype alternatives internally.

I came to the conclusion that if it's not Teams/SharePoint or the moat is on the extreme legal complexity side (e.g. payrolls), you can at least think of building an alternative that is good enough without needing to be perfect.

>>epolan+Rn2
I told to my colleague that it would take less time for me to vibe code jira that it would take him to configure it. Sounds crazy ? Not so much : factor the part of jira you use (maybe 10%), the many choices and dimensions you have to configure, the time it take and the complexity it bring. On the other side, the vibe code version have only the fields you want, most of the logic hard written in code (ie epic > story >task...), and that you could do anything any role, any authentication scheme.

>>julien+7t2
This reminds me of all the "i could turn the spreadsheet into a webapp in a weekend" type comments. Sure, you could get CRUD and a datatable working but then a user is going to ask you for a custom field and you'll say "ok let me vibe code that, update the database, and then deploy" but the user will say "well in Jira I could just to that myself...". Then the next thing they're going to ask is some kind of custom workflow utility which you'll then goto work vibe coding that feature and they'll say again "...but in jira that was already there". Meanwhile they'll ask you why they can't change the validation criteria on the custom field from before, they said it should be required but now there's a case where it's optional.

Pretty soon you're just re-implementing Jira while your users wait and get pissed because they could have just been using Jira all along. It's just like turning a spreadsheet into a webapp, inevitably you just end up trying to re-implement Excel.

>>chasd0+lB2
> but the user will say "well in Jira I could just to that myself..."

> "...but in jira that was already there"

Must be a different Jira from the one I'm used to, where obvious features are never there and even if you can find the button it doesn't work.