That's only because the former already implies much of the latter, so they don't need to repeat it
Kache
joined 1 year ago
In a sense, money represents all the future goods and services it can buy, and those goods and services ultimately resolve down to someone's time and effort. Money was conceived as a formalization of IOU's, after all.
So it's similar to asking whether there's a limit to how much time and effort from (i.e. influence over) others one would want.
I've heard of publishing software to design photo albums/scrapbooks/cards etc. Is there a photo collection manager for archiving, sorting and filtering?
Given access to a large set of personal photos, say tens of thousands, it should be able to group, categorize, tag, and sort along a myriad of dimensions.
Example dimensions would be time, people and places. It would need some facial recognition/image classifier/similarity scoring capability.
There definitely are some cloud offerings today that do similar things, but I'd want it to work locally for privacy and practical reasons.
Yes, and that's the point -- to accomplish the task using only what would otherwise be insufficient memory
If it takes 1+ hours of work to remove a feature flag branch in an area of code, I wouldn't trust the correctness of anything the AI writes and would be super skeptical about anything the humans had written.
The synchronization problem (flakiness and all the waits) is tricky to get right. Browsers are concurrent systems, and programming around one is specialized enough that many devs don't do it well, e.g. IMO if you're adding ad-hoc waits or nesting timeouts, you've already lost.
It refers to a male cousin that is NOT in the same paternal line, so maybe not too uncommon?
Must be proprietary, bc TOTP shouldn't be blocked by age of the device
Good code is code that's easy to delete.
I'm not a game dev, but it's got a reputation for being more of a software engineering shit show than other software industries, which your story only reinforces.
What are the numbers for?
I agree with the author overall, and I think it can be more straightforwardly stated. IMO it's the idea that wrong abstractions are even worse than other ills like duplication or god classes/modules. It's also reminiscent of "modules should be deep".