enterprise

We do this with enterprise software, except we don't call it a "time bomb"." We've deployed your installation with a provisional, expiring license.

In other words, it should be a lot harder to "Accept" these profiles outside an enterprise setting, because it sounds exploitable. What else can you configure "so easily" I wonder?

Google is dependent on their ad revenue to fuel their behemoth enterprise. They are sacrificing their own product in an escalating fashion.

Together with SAP, Microsoft has the most complete enterprise stack imaginable. All of a sudden even Windows Phone would have a place in this world as a BlackBerry successor.

He will not be remembered for transforming Microsoft into one of the most important enterprise software companies. Not for introducing .

The only time we ever used Cisco, outside of large enterprise clients with 1000+ seats, was with public school tenders. The private school would get a $500 white-label router, the public school s would get a $6-15k Cisco router with additional VPN module costs.

The search warrant used in the raid said Stuart and his wife were engaged in money laundering, operating an illegal enterprise and engaging in the promotion of gambling. Stuart has tried to obtain a copy of the affidavit used to get the search warrant, but its currently sealed.

It is in the business apps, BB messenger, unique keyboard, enterprise features etc. It seems like they would be much better off adopting Android as their base and building proprietary features on top.

I don't like the enterprise sales process being on either side of it, and I have to be on both at times. But the reason I'll do it is because our customers demand it and folks at that level, when a deal closes, pay enough to make it worth it. It's the same on payment methods, actually. We got dragged, grudgingly, by our enterprise customers to allow paying by purchase order / ACH because that's how their purchasing departments expect to do things.

And it used those copies in a for-profit enterprise to enhance its business and advance its profitability. Taken as a whole, such factors would have allowed a court to conclude that the uses Google made of the copyrighted works readily failed to meet the requirements of the fair use defense and thus left the book industry, in effect, frozen in an early 20th century analog world.

I don't think James Gosling envisioned the mess that "enterprise Java" became when he designed the initial simple language. Most developers do many of the things he cites, like adding "unnecessary" hierarchies to their project, because they believe it will help them in conquering complexity, and leave something simple and powerful for others to use down the line.

Emotionally I felt pretty liberated, feeling like Sun was too clueless trying to protect their enterprise accounts to see the low hanging fruit right above them. The only place I have felt truly bad about leaving was Google, not because I was leaving, it was clear to me that Google and I had incompatible goals, but because I felt like I had failed the folks who were fighting the good fight and I left them there to suffer.

The talk was about APIs, but Amazon views APIs as a general term: "Fulfilled by Amazon" is an example of a non-technical API. Likewise, I think Amazon's self-funded retail operations are largely a break-even enterprise. Other businesses have been successful with this -- Costco comes to mind -- but the scope of capabilities Amazon is looking to develop is staggering. If they can build a completely vertically integrated retail platform from procurement to payment to delivery, basically they're operating a retail enterprise without taking any inventory risk on themselves.

Nothing that Watson learned from the Urban Dictionary could possibly be any dirtier than what I hear from enterprise people all the time: "We use our deep subject matter expertise to deliver value through actionable advice that enables our clients to harness the power of best practices in order to shift their paradigms and achieve 10X deltas against competitive industry metrics."

We're in the enterprise space. While I'm constantly amazed at how much we're able to charge for our product, I'm equally amazed at the reasons deals go sideways. In the consumer space, you're working with averages over large quantities. The number of potential buyers is huge, so you need to build a product that, on-average, will result in more sales than non-sales when the customer reaches the point of making a decision. This decision point might happen tens of thousands of times -- sometimes millions -- a year for consumer products. In the enterprise world, the number of sales opportunities are smaller by orders of magnitude. Every sale becomes a huge gamble, and as a result you tend to throw an immense amount of resources at every sale. This is also one of the primary reasons enterprise software ends up so bloated and unmanageable. On the front-end, the decision making process for purchasing enterprise software is driven by checklists and "due diligence" procedures that are horrible at accounting for software quality. You're more likely to win an enterprise contract by saying "sure, we'll add that feature" than you are carefully explaining how maintaining product focus results in a more usable product. This makes enterprise software a high-stakes game. A sale results in windfall revenue, but a non-sale can severely strain cash-flows. At the end of the day, you're still trying to beat the averages, but you're working with a much smaller number of opportunities, so wins and losses move the needle in a big way. I think this is a significant incentive for small shops and independent devs to avoid the enterprise space. You need a larger bank roll to attack the enterprise market.