• 1 Post
  • 49 Comments
Joined 2 years ago
cake
Cake day: July 2nd, 2023

help-circle
rss















  • You are making just such a weird argument and it sounds like you are retroactively trying to salvage a bad position because you made a mistake.

    1. If you care strongly about audio quality. A built-in doesn’t have any quality guarantees… why then does usb vs hat matter?

    2. If quality is your concern why bring up price in the first part? It is blatantly obvious that cheap parts *might" equate to cheap quality. This is blatantly obvious.

    3. Obviously there will be USB solutions that are equal or better solutions than prebuilt rpi dac hats since the primary dac hats are exceptionally niche.

    This response just sounds like you got caught out in your mistake/bad argument. Why be a dick about it?




  • Your mistake was giving them an answer instead of asking how the scale was setup before giving them a number. Psychologically, by answering first your established that the question was valid as presented and it anchored their expectations as the ones you had to live up to. By questioning it you get to anchor your response to a different point.

    Sometimes questions like this can be used to see how effective a person will be in certain lead roles. Recognizing, explaining and disambiguating the trap question is a valuable lead skill in some roles. Not all mind you… And maybe not ones most people would want.

    But most likely you dodged a bullet.


  • Self documenting code is infinitely more valuable than comments because then code spreads with it’s use, whereas the comments stay behind.

    I got roasted at my company when I first joined because my naming conventions are a little extra. That lasted for about 2 months before people started to see the difference in legibility as the code started to change.

    One of the things I tell my juniors is, “this isn’t the 80s. There isn’t an 80 character line limit. The computer doesn’t benefit from your short variable names. I should be able to read most lines of code as a single non-compound sentence in English with only minor tweaks and the English sentence should be what is happening in most of those lines of code.”


  • Below the 3.0 volt limit will reduce usable cycle count by 30-80% Everytime the cell drops that low. Charging over 4.1 will reduce usable cycle count as well.

    Example # of usable cycles if you stop discharge at 3.2 and stop charging at 4.0 for modern lipos can be 5000-10000 cycles.

    Charging to 4.3 every cycle (phone batteries are rated to 4.3 not 4.2… it’s why they have the larger than expected wh capacity numbers) will reduce that to 500.

    Discharge it to 2.5 and you will get 10-50 cycles.

    For those who are just looking at the SD or their phones… Most devices report 0% at 3 or 3.1v and 100% at 4.3 or 4.2 volts… So basically discharging to 0% doesn’t matter… It’s the charging to 100% that matters to most people.

    If you charge to 100% you will get about 500 charges (it doesn’t matter what the % is you start at is… 90% -> 100% is the same one cycle as 20% -> 100%). That’s about two years of use for most people before your battery starts to suffer and you will see noticable decrease in battery life.

    If you charge to 70% you will get about 10 years before you will see a drop in battery life. 80% will get you about 6-8 years.