Rest is for the dead

Previously Baguette@lemm.ee

  • 0 Posts
  • 54 Comments
Joined 2 years ago
cake
Cake day: February 1st, 2024

help-circle
  • If you suddenly developed it without any major accidents (like your eardrums burst from pressure) or continued harmful noises (construction is a big one). You should probably get it checked

    Could be a symptom of an underlying issue and it might go away if you fix that

    If you come back from that and it genuinely is tinnitus, then I recommend:

    1. Keeping your mind distracted. Mostly easy if you are doing day to day stuff, hard when you’re trying to sleep
    2. Play ambient noises. I like ocean waves if I have problems with mine, it helps drown out the static
    3. Exercise. Doesn’t actually help reduce it, but it does help make your body ignore it IMO, and makes it easier to fall asleep.


  • You might have scalp psoriasis. I always thought I just had bad dandruff and tried shampoo and leave in treatments and they didn’t really work. I got it checked and it’s actually just psoriasis (plus regular dandruff too, but the dandruff was exponentially worse because of my psoriasis). You could maybe get a dermatologist to prescribe a topical steroid. It helped for my case (you might still need a dandruff shampoo to go along with it)






  • Test driven development is moreso

    1. You know what real life scenarios you’re solving for. Basically, this is the problem statement of your design.
    2. You write out these tests to say your service must pass these tests in order for it to be considered working. In order to consider problem x solved, the service must do y.
    3. You make the first iteration of your service to just repeat exactly what the tests want it to output (basically to create a skeleton with a bunch of magic numbers)
    4. You make the second iteration. What magic numbers can you remove and actually implement for? What workaround can be fixed? Are they still passing the test? If they start failing the test, you should relook at what you wrote and debug from there (this assumes your tests are rightfully written).
    5. You keep continuing with that process until you have a service that fits your test cases and without mocks

    The obvious flaw is that 1 is almost never truly accurate. Scope usually changes, and assumptions made probably invalidate your test. It is a valid way of thinking though, because it helps define your expectations, and reduces the likelihood of you making something that misses the target.



  • The thing is that there are real measurements of the market share of windows dropping. The only reason why adoption of w11 overtook w10 user size is because they made w10 end of life (although there are still ways around)

    Unfortunately, some business idiot mathed up that losing users is fine as long as the others get forced onto w11

    Windows could have done so much differently. More seamless integration with xbox and cross platform for gaming. Different, easily swappable profiles (windows) for different tasks (basically overhauling desktops, like for art, dev work, etc). Optimizing microsofts enterprise software suite without all the bloat. Not deprecating the idea of android support.

    But like all big tech companies, they only see money now