And how come much larger numbers have already been solved? Based on that information one cannot strictly assume that the current solution required improvements to the strategy or hardware, no?
428 karma · joined January 8, 2019
And how come much larger numbers have already been solved? Based on that information one cannot strictly assume that the current solution required improvements to the strategy or hardware, no?
I've always wanted this for mail-in voting. E.g. print a random secret on the voting form I receive per mail. Afterwards publish the complete vote-count on the web, with the choice and a hash of the secret. So I can check that my vote was recorded, and only once, and correctly.
I understand there might be a lot of reasons for why it could fail in practice, but it would be a start.
> Second, microwave cooking fell victim to the same curse that threatens every new easy-to-use technology: it became low-status tech.
HN comments sway me more than any other source nowadays. Reading comments not directed at myself probably makes it easier because my ego does not feel attacked.
In my opinion, a system that has been stable for years isn't 'mature' in a good sense. An exceptional system is one that can still change after many years in production.
I believe this is almost impossible to achieve for enterprise software, because nobody has incentive to make the (huge) investment into longterm maintainability and changeability.
For me, consistent systematic naming and prefixes/suffixes to make names unique are a hint that a person is thinking about this or has experience with maintaining old systems. This has a huge effect on how well you can search, analyze, find usages, understand, replace, change.
- "Not-Boxes": Negatively formulated text (disable... / don't...)
- "Button-Checkboxes": Checkboxes with verbs that trigger actions
- "Radio-Checkboxes": Radios that are actually checkboxes (not mutually exclusive)
- "Toggle-Checkboxes": Checkboxes that are actually toggle buttons and can't decided wheter the text should show the current state or the state that will happen when you click.
I think this person would be very satisfying to work with, because decisions would be based on a discussion of tradeoffs, and an awareness of similar technologies and approaches throughout computing history.
Only when the immediate answers become completely useless will I want to look into slower alternatives.
But first "show me what you've got so far", and let me decide whether it's good enough or not.
Imagine waiting for a minute until Google spits out the first 10 results.
My prediction: All AI models of the future will give an immediate result, with more and more innovation in mechanisms and UX to drill down further on request.
Edit: After reading my reply I realize that this is also true for interactions with other people. I like interacting with people who give me a 1 sentence response to my question, and only start elaborating and going on tangents and down rabbit holes upon request.