I use Siteground for a few wordpress installations - support is excellent and performance is reasonably good - plans are reasonably priced and haven't had any issues. That said, I don't run any intensive applications, just self-contained systems.
I would say support is excellent if you have a problem the rep already knows something about or you get someone who's interested in fixing your issue.
The problem I've just had hasn't been resolved because the rep jumped straight in with what he thought the solution might be. He obviously never read the error message that I pasted and continues not to read or listen to anything that contradicts his theory.
The fault has been marked as resolved by him 3 times now even though it isn't fixed.
This is a problem I have experienced with many well known hosting outfits.
It is why I don't recommend any shared hosts anymore because they are all competing on low price and just about acceptable customer service.
Siteground are one of the better options but the chances of having a similar issue can't be dismissed.
Automation replaces manual labor. As labor becomes more expensive and automated processes become more affordable, you'll see a shift in the food industry from basic labor to skilled labor (those who will develop and maintain the automated processes).
Okay but that might be a little simplistic, because automation can also complement manual labor and create more demand for it.
The example that comes to mind is about ATMs and bank teller jobs: when ATMs were introduced it actually increased the number of teller jobs because branch offices became cheaper and banks opened more of them.
I'm Justin and I work at LaunchDarkly. We built this microsite to collect content on feature flagging best practices and put it into one place. We also have suggestions for feature flag implementation, SDKs, open-source libraries. Whether you are looking to build from an open source library or buy a solution, it is important to understand the fundamentals of feature flag-driven development. We're also looking for any feedback about other best practices/guides/tutorials around feature flagging that we can include in the future. We welcome contributions to the microsite on GitHub: https://github.com/launchdarkly/featureflags.
Feature flagging/toggling is a method by which developers wrap a new feature in a conditional to gain more control over its release. By wrapping a feature with a toggle, it’s possible to isolate its effect on the system and to turn that toggle on or off independent from a deployment. This effectively separates feature rollout from code deployment. Feature toggling is a core component of continuous delivery that empowers software organizations to release quickly and reliably.
Ya revenue and ROI are typically the drivers that determine how budget and resources are allocated. If something is not seen as necessarily critical or customer-facing, then it can just be kept behind the scenes.
Then.. of course.. you face the issue of turnover and attrition. People leave and rarely do things transition smoothly from employee generation to generation.
"Vine’s business problems throughout the years – poor management from directors leaving every year, competitors such as Instagram implementing their own short video features, massive lack of innovations to keep users, and their biggest stars from jumping to other platforms." Seems to sum it up there: lack of innovation, adaptation, and forward thinking.
Not every model is sustainable and a great operating team may only be able to forestall the inevitable with some models. It's a duplicitous statement for @rus to speak for others in the sale of their company.
