Interesting typo. Almost like a Freudian slip but with melting batteries instead.
Interesting typo. Almost like a Freudian slip but with melting batteries instead.
It’s actually the company’s problem. They usually opt to add more debt though, rather that wade through the old stuff.
In the end, all software sucks and should be replaced as soon as possible. Code quality is a lie we tell ourselves so that we can sometimes be proud of our work. It’s usually the code we are most proud of that is the worst. Design patterns everywhere making the vode overly convoluted and “future proof”. The only future proofing that happens is that no-one will understand it, so they won’t change it. Trying to design for the future usually makes it harder in the future.
“Never install, carry or handle”. OK but what are they for then?
That’s the usual open source way. The config probably came later so they just added the option without changing the default because that would break backward compatibility.
And there would be too much boring work to build a migration.
I guess that wouldn’t help the deaf people though. (:
Maybe competitors are only up to 200 per year and these guys finally achieved 300 per year?
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?
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.
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.
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.
Plus, the news of this would already be priced into the stock, so if anything the price is already low and these companies would need to pivot their business (which would increase the value again) or die (which would lower the price marginally, to zero). Either way, shorting is a bad strategy in this case.
Yes. The whole post is a trick with statistics. Web pages have a limited lifespan. You can do the aame trick with human life spans.
“50 % of humans that lived 60 years ago are now dead”. You would tweak the numbers to be factual but something like that makes sense to me.
If you only keep the samples you started out with, of course it’s going to decline over time. The data is guaranteed to not grow since nothing is ever added.
It’s right there in the name . WINamp
I don’t think n64 did. They even had major frame drops in many games.
It’s worth noting though, that Spotify has been bleeding money since the start. I know they may be wasting a lot of money on side hustles but still. They’re not raking home any money. The only way the founders got rich is by the overinflated stock price.
E: typo
Exactly! All applications can be shit, not just web sites.
People screw up CLI’s all the time (looking at you Google Cloud). They (used to) insist on using my installed python which automatically upgrades and breaks the CLI. Good job python. Good job Gcloud.
Yes you should. I think most comments here are about products that have millions of users where it’s actually worthwhile spending all that extra time and money to perfect things.
For most development, it isn’t worthwhile and the best approach is to wing it, then return later to iterate, if need be.
The same goes for most craftsmanship, carpentry in particular. A great carpenter knows that no-one will see the details inside the walls or what’s up on the attic. Only spend the extra time where it actually matters.
It triggers me immensely when people say “I could have made a better job than that” about construction work. Sure maybe with twice the budget and thrice the time.
It’s even worse when you can tell they really tried and still end up with spaghetti. Even mid- to senior developers do this. Rhe more senior they
claim to beare, the more embarrasing when you have to get the stick.Some people try to be so clever with fancy design patterns or bit-tricks, instead of just solving the problem, you now have two problems and a solution to one of them.