• 2 Posts
  • 29 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.









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




  • I worked as engineer for 15 years and then management for the last 2 years. The urge to go back to engineering never stop. What keeps me in management is seeing how I can create the environment where engineers are able to do their work.

    If I go back to being an engineer, I won’t be able to make sure product requirements are clear, priorities are correct, team members will have a chance to practice skills they don’t get to do at work. At the minimum, protecting my engineers from stupid back to office policies that were enforced just because the CEO felt lonely one day. Would someone who has not worked as an engineer understand the feeling of stairing at the screen for 8 hours not able to start anything due to burnout is the worst feeling ever? Will they hear the grinding wheels when soneone used the wrong term during meetings?

    There are just so many things that I can do for MY engineers, exactly what I wanted when I was still an engineer. I don’t trust others to provide that so I take it on myself to do it. Granted, I need support from upper level for this to happen so it’s an important aspect for me when I apply for jobs.