Bank holidays would be really awkward. You start wort at 23 and the next day is off so you would just have to work that one hour.
Office workers could probably move hours around. It would get complicated for shift workers though. Paying overtime for work on holidays?
All I see is you being toxic. You're not leading people anywhere. People will want to stay away from your way of thinking because of all the hatred in your tone. Dial it down a bit if you want to have any impact.
Love the coupon analogy
I dunno but we have this dish in Sweden called blodpalt. Bread with blood. I guess you can't sacrifice those.
19 “The first offspring of every womb belongs to me, including all the firstborn males of your livestock, whether from herd or flock. 20 Redeem the firstborn donkey with a lamb, but if you do not redeem it, break its neck. Redeem all your firstborn sons.
Wow. What does that even mean?
Sure, I just wanted to put more attention to the level of detail, as pointed out in another thread.
That's not true at all, mathematically. That's why we have a measurement for co-variance or correlation. If two dimensions are 100 correlation, they can most definitely be reduced to one.
I'm not French nut usually the price of transmission is omitted, netting in a positive cost for end consumers. If it was really negative, there would be businesses just burning energy to make money.
Battery business should be good in the future though.
To be fair, most of these apps were made before the notification categories were invented and they don't keep the consultants that made the initial app, or want to pay for the change.
Agreed but someone actually tried it - did the research.
That's just what we call people spending some time to figure something out. Security research is basically just trying to learn the technology and then trying to break it.
Vespucci is awesome. I've used it extensively for years. It's only for editing though, not for navigation. I use OsmAnd (free pro features on f-droid)
The resolved ones get removed so the harder and harder notes remain. The main obstacle is usully that someone needs to actually go to the location, take notes and edit the map. It's a lot of work.
I'm Swedish. I see it sometimes, as well as just "t", which is even worse because is can be mistaken for Tera.
No thanks. It's way more fun to be part of the decision process. If a manager can anticipate all of the requirements and quirks of the project before it even starts, it's probably going to be a really boring, vanilla project at which point it's probably just better to but the software.ä somewhere else.
Creating something new is an art in itself. Why would you not want to be a part of that?
Also: Isn't it cheating to compare the two approaches when one of them is defined as having all the planning "outside" of the project scope? I would bet that the statistics in this report disregard ll those projects that died in the planning phase, leaving only the almost completed, easy project to succeed at a high rate.
It would be interesting to also compare the time/resources spent before each project died. My hunch is that for failed agile project, less total investment has been made before killing it off, as compared to front loading all of that project planning before the decision is made not to continue.
Complementary to this, I also think that Agile can have a tendency to keep alive projects that should have failed on the planning stage. "We do things not because they are easy, but we thought they would be easy". Underestimating happens for all project but for Agile, there should be a higher tendency to keep going because "we're almost done", forever.
Maybe this is why pi was chosen for half of the circumference of a circle.