"We should have built the absolute minimum and then manually maintained transactions through the backend if need be.
"We should have built the absolute minimum and then manually maintained transactions through the backend if need be. To hell with formality. We were in the business of proving a hypothesis yet we acted as if it had already been proven" We do this at my company when we add a new feature that we are not sure will take off. You can get something running quickly that looks good enough to the customer, but behind the scenes is all smoke and mirrors. Then if the amount of traffic starts to grow you start putting in your automation. It's really hard to resist the urge to build out all of your automation, scaling, etc up front. But, most of the time the new feature goes unused and it winds up being a waste of time.
Posted by jakejake on Feb 28, 2015, 7:06 PM
Tags
Related issues
- To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
- > The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
- Custom trigger IDs are not displayed in the new 2026.10 trigger selector
- I hate that too, but I think it’s more the ux than the concept of a default.
- > The biggest problem with UX developers is they know better than you AND force you into their paradigm.
- "Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
Raise real-world problems, find people facing the same issue, and discuss solutions.7,500 issues0 comments
ux (Other)
To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
> The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
Custom trigger IDs are not displayed in the new 2026.10 trigger selector
I hate that too, but I think it’s more the ux than the concept of a default.
> The biggest problem with UX developers is they know better than you AND force you into their paradigm.
"Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
The biggest problem with this is if the target URL doesn't load but also doesn't quickly error out, like e.g.
Google wants to build up a private web here.
"We should have built the absolute minimum and then manually maintained transactions through the backend if need be.
"We should have built the absolute minimum and then manually maintained transactions through the backend if need be. To hell with formality. We were in the business of proving a hypothesis yet we acted as if it had already been proven" We do this at my company when we add a new feature that we are not sure will take off. You can get something running quickly that looks good enough to the customer, but behind the scenes is all smoke and mirrors. Then if the amount of traffic starts to grow you start putting in your automation. It's really hard to resist the urge to build out all of your automation, scaling, etc up front. But, most of the time the new feature goes unused and it winds up being a waste of time.
Comments (0)
No comments yet. Start the discussion.