• 0 Posts
  • 285 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle


  • My email provider allows for unlimited aliases. So, while I have 600+ email addresses, emails to them all end up in the same mailbox.

    I do this too. The unique email address I create for each is identifiable to the place I’m using it. This has other benefits. If an organization you created and account with sells or has a data breech you know exactly which company it was when you start receiving spam or phishing email directed to that address. This is also nice because you can “black hole” that email address and all the spam goes with it even future spam not sent yet.








  • I don’t know much of Warhammer lore, so I had to look up tech priests:

    "No longer the master of its creations, the Cult Mechanicus is enslaved to the past. It maintains the glories of yesteryear with rite, dogma and edict instead of true discernment and comprehension. For instance, even the theoretically simple process of activating a vehicle’s engine is preceded by the application of ritual oils, the burning of sacred resins and the chanting of long and complex hymns. "

    Its clear to me the author of this block of text was having trouble starting his vehicle’s engine, and was pissed off when he/she was asked to put in a ticket before help would be rendered to the him/her.





  • So far, speaking from experience, we saved loads of money DIY’ing it, even when deploying to the cloud, and we saved loads of time, in the long run.

    First, I’m glad its working for you up to now. I’ve been in similar orgs. It works great, until it doesn’t. Have you had an production outage yet from a datacenter or hardware failure yet?

    Should I ask home much did your Broadcom licensing renewal cost you this year?

    If you hire talented workers, you save money and time, by DIYing the approach, as long as it’s done in a sane, and controlled manner.

    Talented workers that know the systems are great, and if you’ve built your own systems and processes finely tuned to your specific applications performance needs and profiles, it also means you’ve got a highly specialized infrastructure and app stack. You’ve possibly built yourself a scaling problem because the skill needed to understand and maintain your well performing one-off solution isn’t ubiquitous. As your organization’s needs scale it will be tied directly to the additional limited specialized and expensive staff needed. Again, this may not be an issue with your org today, but it may not have hit this need yet. This is the “Only time will tell” component that is so important. As in, your sample size may not be large enough to know if your org made the right decision or not yet.







  • Wise companies have limited themselves to the basics

    “Wise” is subjective here. Using a cloud vendor’s implementation can yield many times more efficiency, simplicity, stability, scalability, and agility vs rolling you own. Does it come with the cost of vendor lock-in? It absolutely can. Will that make migration to another vendor difficult? It will.

    So for organizations that never embraced the cloud alternatives have had to maintain their own infrastructure or use commodity solutions, as you mentioned, to deliver their IT needs. How much more was spent using a general purpose approach with higher portability to deliver the same result vs a cloud providers proprietary version? Then include the time component.

    Only time will tell.