3,368 karma · joined March 5, 2010
https://streets.mn/2016/07/07/chart-of-the-day-vehicle-weigh...
It would seem that it may make more sense to make up the difference in other consumption taxes as transport of goods is probably a good chunk of the road wear.
Increasing the cost of EVs at a time of climate crisis seems pretty short sighted.
I mean sure it's bad, but I find it hard to take this statement literally for any HN reader.
*Note that is not a comment about HN UX, just that anyone who uses software and technology extensively has to have used some pretty terrible software products in their lifetime.
There is no one clear process anymore.
Last week I went to board a flight and checked in using the phone app. At the airport I needed to get a baggage ticket so I used the machine there for that, but it basically had me go through the whole check-in all over again. On top of that the first machine errored during the step to pay the baggage fee so I ended up doing that again with another machine.
Afterwards I went to drop off my bag and was told the tag was not "active" and I'd have to go to the desk.
What the hell is the point of any of these electronic options if at the end of it all I still have to wait in line for an agent, stand there while they "mmm-hmmm" at their computer and avoid eye-contact with me for 5 minutes just to finally scan the tag I had printed and attached myself?
I'm not sure what can really be done about that though. It isn't my industry so my understanding of the problem is pretty peripheral.
Problem: The Washington Monument is deteriorating
Why? Harsh chemicals are being used to clean the monument
Why? The monument is covered in pigeon droppings
Why? Pigeons are attracted by the large number of spiders at the monument
Why? Spiders are attracted by the large number of midges at the monument
Why? Midges are attracted by the fact that the monument is first to be lit at night.
Solution: Turn on the lights one hour later.
This is a massive over simplification of the 5 whys process. The author seems to be implying that this is the core of the process when it is not, it is merely a simplified example what the process would look like to someone unfamiliar with it.Without getting into a massive amount of details the following things are important to note about 5 whys in lean.
5 whys isn't meant to arrive a a single conclusion or solution, it is meant to provide deeper analysis so that an appropriate and proportional set of countermeasures can be proposed and considered. The key concepts being a "set" of countermeasures and "considered".
5 whys does not need to exist in a vacuum as a problem solving tool. It is often just one such tool in a more thorough approach such as the A3 process
There is no reason to limit the number of whys to 5 or even go that far in some cases.
The countermeasures that come out of a 5 whys analysis are not expected to be implemented and immediately forgotten about. They are part of a plan that expects follow-ups, measurement and observation of the results.
The underlying causes of the analysis are not assumed to be the only causes or problems. The purpose of 5 whys is to limit over analysis. This may not make sense in life-or-death situations, but for most business processes it is appropriate and efficient to make decisions at a reasonable point in the analysis and move forward rather than investing a disproportionate amount of resources in that analysis.
The concept of a "proportional response" is important to lean. If the outcome of a problem is a patient's death, then the proportional response can be expected to be considerably more significant that just doing 5 whys.
If all a team does is ask 5 why questions then propose and implement a solution based on the last answer, this would be a pretty textbook example of a lean cargo cult.
I would guess that cost is much higher than they think.
Ember's 1.0 release was 2013 which is the same year React was announced. Yes Ember has earlier history as Sproutcore going back to 2011, but Facebook was using React internally since 2011 as well. I'd also argue that Ember 2.0 was pretty different from 1.0.
Angular is older, going back to 2009, but as 2.0 is a total rewrite as well as departure from where they started out I'm willing to let that one go. (It is also a complete tire fire so let's just ignore it altogether).
VueJS is arguably the "new kid". But really only just barely. The first release was Feb 2014. I'd hardly consider Vue immature at this point though.
I really don't see how one can argue it has a tangible maturity advantage here. I also think that most of the newer generation of SPA frameworks have learned lessons both from the previous generations and their peers (with the exception of Angular perhaps).
https://www.clearly.ca/sunglasses/ray-ban/ray-ban-rb3025-58?...
He offered to pay people who kept the package on their porch if the package was taken. They then asked their friends to take it so they would get paid.