> Even if the retailer took it back it would still be... trash.
Yes, but making them deal with it would create a massive incentive to either reduce the amount of rubbish they make, or to make it recyclable/processable.
Also, if you're a plane or a boat it's really important everyone knows where you are for general safety / rescue reasons. On a (consolidated and decently organised) railroad the railway operators can take care of all of that.
It's just a standardised way to represent data structures in text. You can then save that text to a file for storage, or send the text over the wire for data transfer. As long as everyone involved knows they're saving/loading or talking JSON then everyone knows exactly how to read/write the data.
It is a very literal representation of (specifically JavaScript, but generally any) data-structures in text.
Right. Now the problem for me is these structures don’t come with maps. They’re also like relational databases. If you have to add the mixin calls, how do you got them all? Or know you’ve reconstructed the data model correctly? Where’s the blueprint?
> You can’t be data driven and also blind to the data
"Tickets closed" is an amazing data driven & blind to the data metric. You can have someone closing an insane number of tickets, looking amazing on the KPIs, but no one's measuring "Tickets reopened" or "Tickets created for the same issue a day later".
It's really easy to set up awful KPIs and lose all sight of what is actually happening while having data to show your bosses
> All it would take is forcing an artificial CPU slowdown
Technically, yes. But for many large tech companies it would require a large organisational mindset shift to go from more features is more promotions is more money to good, stable product with well maintained codebase is better and THAT would require a dramatic shift away from line must go up to something more sustainable and less investor/stock obsessed.
I wonder what's going wrong in there
reply