• 0 Posts
  • 43 Comments
Joined 1 year ago
cake
Cake day: August 2nd, 2023

help-circle


  • I hated yaml with every fiber of my being when first had to use it, but I really wanted to use HomeAssistant and see what I could do with it. I hated it a bit less when I started using docker compose. I started loving it when I started using it as a way to explain json to non-programming IT types, trying to explain it without braces and brackets seems to get across easier. I guess its more human readable, but as a result formatting has to be spot on (those indents and spaces replace the need for brackets and braces).

    One useful trick if you truly hate it but need it, write it in json, then just use a converter to change that into yaml.


  • It will all boil down to what kind of maintenance is required. A robot for $50k would pay for itself in saved wages in under a year, even less if it collected tips. A lot of smaller diners (Waffle/Huddle/Waddle/etc) typically have super low staffing requirements (line cook + 1 or 2 servers per shift, occasionally more) and could totally use robots due to the simple layout and standardization of the restaurants.






  • Sounds good, but it essentially means you would then have to buy and maintain the method of power generation and delivery back to a company to sell it to someone else. I totally get remaining grid connected is important, but those grid connected systems are supplying a whole lot of power back to the grid. Perhaps if you generate more than you use, the power company should pay you to maintain your generators and infrastructure.

    Transparent pricing and not itemized billing could help a lot (and allow for better application of fees based on use case).