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

help-circle




  • My experience with maintaining open source projects (though mine are very much smaller) is that it’s quite similar to a business: you just have to deal with stakeholders and people who think they are stakeholders.

    I had all the same experience at work:

    • Some unknown person from an unrelated team contacted me because something that my team does not manage broke. I tried to help a few times and I suddenly became their personal IT support team.

    • Another time someone not even working at my company demanded that I drop everything and fix their problem, because my name appeared in 3rd parties libraries.

    It’s sad that open source authors don’t always receive the recognition that they deserve.










  • 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.



  • I afraid Microsoft will ban me for reading news articles copied from websites without permission, or just having a pirated game on my Windows partition.

    Or maybe Chrome (I use FireFox, just an example) ban me for visiting “unclean” websites.

    Maybe even the landlord of my rental will kick me out for keeping book post due from the local library.

    It’s a scary society we live in.




  • 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.