2,099 karma · joined February 15, 2012
[1] https://blog.codeship.com/kubernetes-namespaces-resource-quo...
Uh, I think you've got it backwards. Won't the updates mean it drives in 'test mode' (e.g. acceptable emissions that meet the standards) all the time? Meaning that it will result in some downside (which was apparently bad enough that they cheated in the first place)
> adding some sort of common utility to support it could mitigate the most obvious security issues.
Package managers are awesome!
Isn't this what you meant by 'let the market decide'?
AFAIK you can download Messenger from the Play store.
> Nearly everything sold on Amazon these days is 3rd parties. I'd wager somewhere in the 95%+ range
No, it's an incredible pain in the ass to get this working properly, when I could spend 20 seconds rebooting
Or many, many games.
There's much more to running a product than 'running a server'.
Eventually, the software is going to stop working on my SOE. Which means more and more boxes are going to be running non-standard deployments in my environment (or it costs me to update). Every maintenance window, infrastructure upgrade, disaster recovery exercise (and event), has to take those servers into account.
Perhaps I pay licenses for those servers to run - OS, support, databases, backup, whatever. Maybe I have a contract with an SI to run all this as a managed service and this costs. There's opportunity cost in terms of resources for keeping all these legacy products on as well - both infrastructure and resource related.
And that's just the technology related part of it. There's business and accounting impacts as well.
Try wearing a mask into a petrol station or convenience store. They've already performed the assessment of 'potential sale vs getting robbed', and decided the risk factor they'd like to accept.
These things are not marketed as toys to small children.
I imagine the intent of this is to cover 'informal' car sharing - e.g. you have a roadtrip with a friend and both pay for petrol, or you drive to work with your neighbour and share costs.
Not sure how it would apply to Lyft Carpool - I think initially your insurance company would push back on it.
The lead position in a large company (in any industry) generally requires little in-depth knowledge of the product. The lead positions (CEO, CFO) are there to report to boards, shareholders, and regulators. Sure they might know and be interested in the product, but the CFO of MS and Apple generally isn't going to be a software engineer, just as the CFO of Audi or GM isn't going to be a mechanic.
You've precisely identified the trade-off. You basically have three options. You can
1. Maintain a local repo of your dependencies (high effort)
2. No dependencies, include everything as 'first-class' code (lower upfront effort, but v. messy)
3. Rely on third-party repos (easiest, riskiest)
In Australia, I tip when a person provides exceptional service to me, and goes above and beyond what you would normally expect them to.
I do not tip them for doing their job.
EDIT: Unless your job is to invent a better bread recipe.
Uh, you're not really in a position to say that.
> We already converted the inlaws (yep, big family) few months ago and it works like a charm.
You're totally ignoring the network effect. Nobody I know who uses WhatsApp uses it only to contact me. So now you've just introduced yet another messaging app they need to have installed and use to message me.
> An 50 year old electrician was the first to show me Ubuntu back in 2006 and he was enthusiastic about it.
So? I can't run Linux on my desktop because of some of the applications I need to run.
While I'm a huge proponent of open source, if you force it on people when it's not suitable you're going to encounter a massive backlash and turn them off it, undoing all the hard work that people are putting in.
Humans also managed to live for centuries without electricity, cars, aeroplanes or ships, but take those away and the world would fall to shit pretty quickly. It's all about what you've adapted to and your daily routine. Sure, we could do without those things, but you couldn't transition to that overnight.
- The hours range between great and terrible (if it's quiet there's a fair amount of flexibility, if it's busy then you work like a dog).
- I get to work on a range of clients, doing different things. There's plenty of scope to try new things if I get sick of whatever I'm doing at that stage.
- Pay can be good or terrible, depending on what you do and how good you are at it.
- I work in a role where I don't have sales targets (thank god), but you can get pure sales roles as well.
- The people I have worked with are amazing (internally, client facing can be a different matter). In 5 years, there's literally only a handful of people I wouldn't work with again, and some of them are now some of my best friends. Most people are driven, incredibly smart, and hard-working.