![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
NASA also successfully flew a helicopter on Mars first try.
NASA also successfully flew a helicopter on Mars first try.
It’s barely waterfall planning either. Often there’s no planning, at least no coordinated one.
Currently at my current workplace we lack coordinated planning between teams. It seems like everybody is working in their own directions and it can take months until we get feedback from other teams. Mostly a product management problem.
The author is also hyping up waterfall too much. Agile was created because waterfall has its shortcomings (e.g. the team realizes too late that what they’re building isn’t what the customer wants).
But I also think it also represents how poorly implemented these ideas are. People say they do agile/kanban/scrum, but in reality they do some freak version of these.
If 0.999… < 1, then that must mean there’s an infinite amount of real numbers between 0.999… and 1. Can you name a single one of these?
I think this is a bit disingenuous. There’s no customer interaction in these panels.
So waterfall would be:
Customer says they want to go to Mars.
You spend years building a rocket capable of going to Mars, draining all the company budget in the process.
Customer then clarifies they actually meant they wanted to go to Mars, Pennsylvania, USA - not the planet!
7 by 7 matrix isn’t the optimal packing. The square shown is slightly smaller than 7 by 7.
deleted by creator
Omg
Force Awakens will be closer to Revenge of the Sith next year
Which doubles the maintenance work to keep docs in sync
When someone writes API docs, should they assume the reader knows nothing or can they assume the is already experienced?
It takes a lot of effort to write documentation towards newbies, at the cost of making it more difficult for already experienced to find the answer they need.
Whether they intend it or not, these engines are built to funnel you back into the lowest common denominator, most broadly appealing stuff, because that’s what the algorithm sees gets the most clicks from the average person.
That’s not my general experience. Spotify for example is good at recommending me songs with less than 10k plays which I vibe on. I’ve discovered many smaller artists thanks to Spotify recommendations.
Recommendation is part of the service. If they know I like something, then it’s reasonable they recommend me something that’s similar. It’s like going to a restaurant and asking for recommendations.
Advertising is when things are promoted outside the service. It’s like going to a restaurant and they tell me about Raid Shadow Legends. I don’t want that.
I think recommendation should be linked to usage data like watch history on that particular service. Location and other external information shouldn’t be used. I don’t want my recommendations depend on which friends I have or recent activity on a different service.
One grain of rice in A1
Normie numbers (aka natural numbers)
Only thing I can find is that it has 128-bit graphics-oriented floating-point unit delivering 1.4 GFLOPS.
Probably only for marketing reasons. Everyone was desperate not to be worse than N64.
My interpretation is that Jon starts talking about how division by 0 is not possible. Garfield then goes on about how we can use limits to assign values to such expressions, which we can use to calculate derivatives. I guess Garfield starts to question whether dy/dx really exists after all this.
Jon then changes the subject to be about integrals, which Garfield is immediately annoyed about the missing +C.
It’s super funny.
That’s fair enough. The common misconception is that waterfall is great for space missions, when in reality NASA is doing agile.
I agree that not everybody is NASA, so what works for them doesn’t necessarily work for everyone.