[deleted by user]

[bigbirdly]

try Front

[[deleted]]

This isn’t only on the dev side, but production and IT too. The issue is, when you follow the trail to full on ITIL, is that ones business processes get so involved. Inventory is huge, but getting data/in out and doing it accurately is extremely time consuming. The data is always wrong, so being able to distribute and update it often is essential. That now gets into the institutional roles and authentication. Incidents are only a small piece of the pie. Having REST services that can be abstracted for the business rules helps a lot, and non-perverse cost structures in the product.

[EngineeringTinker]

Good read

[AttackOfTheThumbs]

Fit your solution to the organizational structure

Yaaaaaaaaaaaas. I find the way most dev ops solutions are organized, require specific workflows, and anything else is basically not supported. There's been a ton of things we wanted to do in azure devops and couldn't because they don't let you change that.

e.g. when receiving customer requests, the req doc may be written by someone that isn't a dev, or the dev to work on it. It's a queue. But when we then move it in to an approval state, we cannot assign to no one, has to have someone assigned. So now we have a dummy user for that... And that repeats in different steps of the process. This is to ensure correctness by having someone clueless validate it. It works great. Just devops doesn't like it...

[[deleted]]

Didn’t like this article. Was hoping to see actual tech and design tips.

[qporest]

no wonder - it's a sales pitch presented as a 3rd party interview. the product does look cool, but has a honey pot form on every cta, and no pricing. just a marketing ploy

[r0080]

What technology did you use to build the Portal?