• 0 Posts
  • 58 Comments
Joined 9 months ago
cake
Cake day: February 14th, 2024

help-circle



  • What a great point to make about language in situations that are not technical! Like how theory is used differently outside of scientific contexts, which is language naturally evolving.

    But this is like someone trying to use the lay definition of theory, which is the equivalent of a hypothesis in acience, in a scientific context. A scientist saying “that is just a theory” to dismiss the theory of relativity in a scientific context would be rightfully corrected by their peers.

    Using legacy software wrong is like using API to describe something other than an API.







  • The user is always right about what they are willing to spend money on. That doesn’t mean they know what they want, although a lot of people don’t want to change.

    That doesn’t mean all change is good, and it isn’t like any UI will ever meet everyone’s preferences. For example, I hate adaptive design interfaces that are significantly different in confusing ways on different resolutions. Like I understand switching a static menu to an expandable menu, but not moving the relative location of certain buttons from the bottom of the screen to the top or vise versa. But that might make sense for some use case that isn’t how I interact with it.






  • Like the startups that ‘disrupt’ the established system by ignoring laws and breaking the parts that worked and selling it like an improvement.

    ‘Ride sharing’ (unregulated cabs) was only cheaper because of investor funding allowing them to undercut on pricing, abusing the concept of contract workers, and the companies ignoring laws. That isn’t ‘disruptive’ by being innovative, that is cheating the system.


  • Like all sayings, there is context for moving fast and breaking things.

    The saying means that when creating something new for profit, don’t worry too much about trying to figure out all the details beforehand and figure it out as you go. This will inevitably cause things to break, but being able to quickly fix that when it happens is the same skills needed to create new features as you go.

    The saying does not work with large and complex established systems where breaking things wreak havoc.