Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
Graceful degradation is cool, but progressive enhancement is where it’s really at. The difference is that instead of working around the lack of capabilities, you design simple and robust core system, and then improve around it based on available capabilities.
The proper term isn’t graceful degradation, but fault tolerance.
It just describes how many core systems or components can fail before the device itself stops working.
For example, a jet will have multiple redundancies for almost all major systems which allows many of them to fail in the air without causing the plane to crash or force an emergency landing.
Graceful degradation is cool, but progressive enhancement is where it’s really at. The difference is that instead of working around the lack of capabilities, you design simple and robust core system, and then improve around it based on available capabilities.
The proper term isn’t graceful degradation, but fault tolerance.
It just describes how many core systems or components can fail before the device itself stops working.
For example, a jet will have multiple redundancies for almost all major systems which allows many of them to fail in the air without causing the plane to crash or force an emergency landing.
That’s how you end up with Frankenstein scope creep.
No! Frankenstein is the name of the designer!
You say scope creep, the client says added value
They can call it whatever the fuck they want…show me the signed change order and I’ll implement it.
Then get remove later because it sucks. Might pop up later and get added again. Infinite money glitch.
You say scope creep, the client says the product is 10x over budget and the deadlines have long passed