• 1 Post
  • 31 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle


  • Another translation of OP’s opinion: walking on the street without looking at storefronts is unfair. Stores pay a substantial rent to be there and a lot of money to renovate and pay people to put up stuff for you to look at. Anyone not looking at these store fronts are robbing people of their money. There should be traffic stops where people have to describe exactly the location, size and content of every ads on the street. Failing to do so should be punished by law.








  • Same here. I still prefer single narrator. There are a few cases when there are just too many characters but it’s still much easier to listen to than multiple narrators.

    I have also noticed sound effects in audiobooks. I like it at the end/start of a chapter, but it need to be subtle. I listened to Fractal Noise, which has audio effect for the thumbing sound, very quiet at the beginning but turned very loud at the end of the book. While it’s new and interesting at the beginning, I quickly grew tired of it. I’d rather only the narrator reading the book than hearing the sound effect.

    I think it’s a matter of imagination. Reading/listening for me is not only about the story but also about my imagination. The sound effects removes this, sadly, despite the huge effort by the team.




  • After many failed attempts at TDD, I realized/settled on test driven design, which is as simple as making sure what you’re writing can be tested. I don’t see writing the test first as a must, only good to have, but testable code is definitely a must.

    This approach is so much easier and useful in real situations, which is anything more complicated than foo/bar. Most of the time, just asking an engineer how they plan to test it will make all the difference. I don’t have to enforce my preference on anyone. I’m not restricting the team. I’m not creating a knowledge vacuum where only the seniors know how yo code and the juniors feel like they know nothing.

    Just think how you plan to test it, anyone can do that.




  • There are already some attempts but I don’t think it will work, harmful even. Best case scenario, the AI can understand the code as well as a senior engineer from another company. All they can know without the context is what was changed, which is useless. We need the reason why the commit was made, not what was changed. The info is not there in the first place for the AI to try to extract.


  • Let’s say YouTube has a video and 2 ads:

    1. The video is served from videos.example.tld/video.mp4.
    2. The first ads is served from videos.example.tld/ads/ads1.mp4.
    3. The second ads is served from ads.company.tld/ads2.mp4.

    PiHole will be able to block only (3) because DNS applies at domain level, as in videos.example.tld. DNS requests only send the domain part and re-use the response for all addresses using that domain.

    Browser extension, on the other hand, sees a request to .../ads... and block it since it handled each HTTP/S request and know the full URL.