569 karma · joined February 27, 2015
We're all quite used to having problems described in the least threatening way but I'm thankful that I've never had to do so about something that could result in people dying.
There are lots of people paying for things they don't need or could save money by switching subscriptions on & off as needed. This is one of the reasons why the subscription model is so popular with companies, not consumers.
(Adding a link to a news source from the other side of the aisle to the Mail.)
In Tallin apparently some of the funding needed came from an increase in municipal taxes. You have to be registered as living in or around Tallin to get the free transport, and a lot of people updated their registration to addresses in Tallin. As a result tax income moved to Tallin (but at a loss to other places).
So a large factor in the cost effectiveness of a free transport policy is the amount that the transport system is subsudied and the ratio of that amount to the budget. In places where the transpost system is mostly funded by taxes (most places in the world, especially Europe & the US) it's easier to introduce as there's less of an impact on the budget.
The benefits & beneficiaries of this policy aren't clear and easy to define as they vary place to place. There's a lot of thinking that it's better to provide free or cheap transport for those who earn less and have to make long public transport journies to work as they're priced out of living in cities.
That's not much of a surprise as Paypal has never been strong on customer service for sellers. They seem to see the relationship as adversial, often claiming it's for the buyers' benefit. But both buyers and sellers are customers to value.
Also, I'm not in the market for this right now but I keep a list of products I've seen and liked. The need to sign up for your demo stopped me looking at it. Consider if you can remove that crucial barrier to people seeing your app. Something like read only, a preset user, or generate an account automatically with a disposible email address.
- "Abuse or excessively frequent requests to GitHub via the API may result in the temporary or permanent suspension of your Account's access to the API. GitHub, in our sole discretion, will determine abuse or excessive usage of the API."
Utterances uses the GitHub API and its demo page makes 4 requests to api.github.com. The API docs state a limit of 5000 requests per hour. That's quite a lot and within what a low volume blog would get, which I think is the main use case for this app. But if your blog gets really popular then you might ring alarm bells at Github.
- "Responsibility for User-Generated Content" As this is all user generated content you, as GitHub account owner, are responsible for it not breaking GitHub's content guidelines and you had GitHub permission to do with it as they see fit. GitHub are the ultimate decision makers about your user's content, not you or Utterances.
I'm asking honestly what other people's opinions of this are because whilst it looks good it: 1) looks like the kinda of hacky solution I try to avoid building when trying to fit together incompatible data objects and data storage. 2) uses Github's systems for purposes other than they were intended, which seems slightly unethical or at least impolite to me.
"hired the vendor based on a cool demo & vendor size" It is common that companies don't chose the right people to assess vendors and review the suggested approach. Often the consultancy sends in sales teams to pitch to the boardroom with demos and "we're Big Company X and know what we're doing". However it seems that Hertz knew enough to ask for specific functionality that didn't get delivered.
"did not have a Hertz employee as Product Owner" Part of leading a project is making sure that your client, internal or external, is properly educated and involved in necessary decisions. Accenture shouldn't have accepted the PO role as it is a conflict of interest.
"tried to go big fast instead of taking an iterative approach" I don't recall reading if this was Hertz's decision, it could well have been Accenture's suggestion and in the early stages of this relationship Hertz would have trusted their "expert" recommendation.
"did not implement proper tests & validation" This would have been Accenture's responsibilty.
"spent $10M without building internal skills" It was $33M and you're right, although we don't know what skills they built internally. They might have been better off building a team internally but often companies prefer to hire "expert" as it's often easier from a cost centre and administrative view.
All their standardised templates and processes mean that the Accenture 'experience' for clients is consistent but it does seem to reduce the capacity for creativity and flexibility in approach.
Sure it shows you've got capabilities for shooting down really low satelites, but it also shows you don't have consideration for the effect this will have. If we don't cooperate globally and stop so much space debris being created some orbital ranges could become impractical to use and manned space flight becomes even more dangerous.
Just because there's more than one obvious problem doesn't mean that you can ignore the others.
More to the point, this isn't just about a single disease or drug, the same story applies to a lot of medication, including those that have zero lifestyle causes.
EpiPens are another example mentioned in the article. In the US if your child is born with a deadly allergy you have to carry around very expensive EpiPens that can cost hundreds of dollars due to co-pay and whatever. In Europe these will cost you directly less than $10 and even to the state will cost a lot less than it does to many US patients. One of the company's responses to hiking the price from $50 to $600 for profit reasons was to introduce a cheaper generic version, which as this article points out, is BS.
There is a scaling issue but my point stands, that demand & its growth are stable and predictable. These are companies with at least 5 & 10 year plans, so they’re able to match production to demand long term.
The article is about how companies are trying to avoid anticompetitive investigations by putting the exact same product in a different box and selling it for less but only to a smaller market.
The definition of socialism is complex and fluid so finding a perfect match is tricky but I do agree that in principle there are many practices between states and businesses that would be, in the US at least, shouted down as “socialist” if they were instead between the state and individuals.
If anything the larger market, which is stable over time, with a product that is known and doesn’t require a lot of development & research, should be driving the price down as competitors should be pricing to gain more market share. But that’s not what’s happening, the companies are engaged in anticompetitive pricing.
The article fails to mention the average price to the end patient in both countries, but this would still show a gap as in Germany the cost to the patient for their prescription insulin is, I think, about 10 euros.
Rate of demand per country makes little difference due to global distribution but apparently Germany has 8.31% of adults with diabetes and USA has 10.79%. Many economists will tell you a larger market should equal more competition and cheaper prices, and not having those is a sign of unhealthy anticompetitive practises.
The exercise comment would only apply to some diabetes patients. It is possible to spontaneously develop diabetes whilst being in peak physical health and diet.
But, more importantly, the cause of a disease does not effect the price of the drugs to treat it.
The bigger difference might be FWD vs RWD. I do seem to see RWD cars getting stuck more (as evidenced by which wheels are spinning uselessly). For the model Y Tesla might well mimic the model 3 options of RWD or AWD, in which case AWD would definitely be the wiser choice.
The challenge I see most is getting the right level of understanding and design freedom to the developer level, where they know why they're being asked to do some work but without burdening them with extraneous detail or processes.
A lot of developers get annoyed at project managers and architects but they dislike project politics even more.
As someone else said, the individual phases can be huge, which is why in large projects the first step is often to break down large business needs into more manageable chunks, each of which can be worked on seperately, either linelarly or by multiple teams. In a healthy process as the work progresses it is used to reevaluate previous decisons & designs. So basically agile.
But ultimately I think it's culture as much as policies. The US, and lesser extent the UK, has a culture of submitting to work over life (as do other countries, so not singling out the US or UK here). In the UK I had to nag people to take holidays and there was usually a holiday crunch at the end of the year when lots of people took time of just because they had to.
Whereas, living in Norway now, the Scandinavian ethic of maintaining a good work/life balance means there's not really a problem of people not using all their holidays. Or work much overtime either.