Mine and my bosses opinion on Development, it should be a paint by numbers.Not sure how i missed the last part about wild west in your post. My company has the shittiest form of Agile I have ever seen. Snowflake devs/architects everywhere. half the reason data lake ingestion is so shitty is because the team which isn't great, has to constantly come up with one off solutions cause you know patterns are awful and confine them "man". I spend a good deal of my time playing wackamole.
Caveat: I don't really do Visual Studio or Windows.Do any of you c-folk use llvm? I've given it a decent shot and found it somewhat unusable.
The compiling / linking works but debugging is a mess. Most of the vs code extensions either do nothing at all, or want lldb-mi which somehow got removed from the distro!?
Now that I read your post again: You could try to build LLVM within Visual Studio:So, just build it right? There's a github. It's cmake based, and if you try to build it with llvm it needs nmake, so you have to install several gigs of random visual studio junk to get it. Then it fails missing some cmake garbage that also used to come with the distro but no longer does.
Substitute SaaS for UCaaS and this is my personal hell every day.Wind the clock back a year or so. One of our accounts asked for a peculiar way to package our SAAS product that is outside of how we usually do it.
Substitute SaaS for UCaaS and this is my personal hell every day.
We sell cloud-based phone/contact center/unified communications solutions as a service to some of the largest companies you can think of. They all start off as being very standardized. But under the hood, they can actually be highly customized and integrated with nearly any enterprise product you can think of. So the scope of every project goes from something very narrow to something very broad very quickly as the customer keeps adding requirements and change orders for other products they want to integrate with the phone system, and the sales people keep saying "SURE WE CAN DO THAT."
However, we are really only staffed to implement and support the very standardized systems as they're originally designed out of the box, but none of them ever go live that way, and they just continue to get more complex as the customer continues to want to add things over time long after the project compltes, and the sales people just keep saying yes to everything the customer wants (though somehow these same sales people take weeks to generate a quote for any significant change.)
So ultimately, we have all of the responsibility of cloud, owning the entire environment/platform and anything that could possibly go wrong with it, but none of the actual advantages of cloud, like standardized features or even adherence to contracted maintenance windows.
AT LEAST THEY PAY ME A LOT.
Hi my name is mist. You have a tech incident because your ci cd pipeline is garbage? Ok give me the name of the unencrypted network share that has the everyone group permission assigned with your API keys and other secrets.
Manage, possibly.What are you making your managers do?