• 0 Posts
  • 116 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle
  • I highly recommend Stephen Tetlock’s book, super forecasting, who is the sponsor of the project you mention.

    One method of forecasting that he identified as effective was using a spreadsheet to record events that might occur over the next 6-18 months along with an initial probability based on good judgement and the factors you quoted. Then, every day look for new information that adjusts the forecast up or down by some, usually small percent. Repeat, and the goal is you will trend towards a reasonable %. I omitted many details but that was the jist.

    Now, that’s for forecasting on a short ish timeframe. There is a place for more open ended reasoning and imagination, but you have to be careful not to fall prey to your own biases.

    This particular forecast of OPs feels like it is ignoring several long running trends in technology adoption and user behavior without giving events that would address them, and forecasts something they care about doing better in the long-term, a source of bias to watch. I tend to agree with you that I think elements of this forecast are flawed.





  • I was unfamiliar with misophonia so I went looking into it. I know it is a poorly studied issue, but I wasn’t able to find any peer reviewed research where children’s noises in general were used or reported as a trigger. I found lots of discussion forums, but that is anecdotal.

    The reason I went digging is because the op describes all children’s noises, happy, sad, whatever, whereas what I read in the literature was very specific noises were reported as triggers. E.g, lip smacking, chewing, pen clicking, etc. In one study, they even used videos of children and dogs playing to help participants calm down and establish a baseline. https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0227118

    While I’m admittedly ignorant, it seems OP may have a more general aversion to children than I would expect of misophonia given what I’ve read from medical sources.

    I only mention this as a counter suggestion to help op avoid self diagnosing and maybe going down the wrong track.

    I think counseling is warranted to help sort it out.






  • I use a terminal whenever I’m doing work that I want to automate, is the only way to do something such as certain parameters being cli only, or when using a GUI would require additional software I don’t otherwise want.

    I play games and generally do rec time in a GUI, but I do all my git and docker work from the cli.


  • Right. Which gets us full circle, to never give investment advice, lol. That being said, at some point someone may sincerely look too you for guidance and you need to make a call as to whether you want to take that risk, what advice you give, and are you sure it is good advice.

    I used to mentor student employees years ago, and when they wanted advice I always told them to max out workplace matches first, and then after that if they can save more, put it in tax advantaged savings programs that let you buy into indexed funds and never sell. In those cases you usually can’t even sell unless certain conditions are met and you sign disclosures, unlike most brokerages. Now, students you are giving them advice for the rest of there life and they likely don’t have $40k to panic sell/buy/sell to zero.




  • Yes, times a thousand. But I would go even further.

    Never give investment advice. You might explain what investments you have made and why you made them, but never give advice and never urge or prompt someone to invest. You should also end every conversation with “but that’s not advice and I’m not an expert.” It is too easy for either the investment to not work out, or for them to do it wrong (wrong timing, panic sale, misunderstood the options, etc).

    The last thing you want on your conscience is someone investing a life changing amount of money just for it to go down in flames. I might invest $1000 in something that I think might pay off, tell someone they should invest, and next thing you know they drop in $40k and panic sell on a dip in two weeks, when I was planning to hold for five years. You never know.




  • Like I said, because the percent doesn’t change with the volume served. If you are an 1800s brewer you can calculate the ABV from samples, and subsequently sell kegs of various sizes, bottles, which in turn can be served in various amounts and the percent doesn’t change. And the industry never changed, nor the laws written. So it’s the way it is because that is how they used to do it and how laws were written and there hadn’t been a motivation for people to change that.



  • I haven’t seen anyone really answer the why of it, which is that the industry developed using a floating glass tool called a hydrometer which measures the specific gravity, or density, of liquids.

    When you boil the wort to prepare for fermentation, you end up with a sugary liquid that is denser than water or alcohol. Water has a specific gravity of one, and the specific gravity of the wort is increased by everything you dissolved into it. You would float a glass hydrometer in it and lets say you get a reading of 1.055.

    After fermentation the yeast has converted much of the sugar to alcohol and decreased the specific gravity. You measure a second time, and multiply the difference by a constant factor to get ABV. let’s say after fermentation you got a reading of 1.015.

    1.055 - 1.015 = 0.04
    0.04 * 131.25 = 5.25% ABV

    We label with ABV because that was how it was calculated, and remained the same regardless of the quantity served.

    There is a similar process for distilling as well. Before these methods people didn’t know the exact amounts, which led to fun things like navy and admiral strength.

    Edit: also the 131 figure really should vary based on temperature since it is derived from the ratios of the density of ethanol and water. The higher the ABV the more important it is to factor temperature, and distilling requires more sensitive measurements and tools. But for beer, using 131.25 is fine and has about 0.2% error up to around 10% ABV.