• 216 Posts
  • 1.41K Comments
Joined 3 years ago
cake
Cake day: June 11th, 2023

help-circle

  • Participating countries and territories: Angola, Argentina, Austria, Bahrain, Bangladesh, Bolivia, Bosnia and Herzegovina, Botswana Brazil, Brunei, Burkina Faso, Burundi, Cameroon, Colombia, Democratic Rep of Congo, Eritrea, Eswatini, France, Gambia, Georgia, Greece, Guatemala, Guinea, Guinea Bissau, Guyana, Honduras, Iceland, India, Iraq, Ireland, Israel, Japan, Jordan, Kazakhstan, Kenya, Kuwait, Latvia, Lebanon, Lesotho, Liechtenstein, Macao (China), Madagascar, Malaysia, Maldives, Moldova, Mongolia, Niger, Nigeria, North Macedonia, Oman, Pakistan, Palestine, Paraguay, Philippines, Poland, Qatar, Singapore, South Africa, South Sudan, Spain, Sri Lanka, Switzerland, Tanzania, Togo, Türkiye, Uganda, Ukraine, United Arab Emirates, United Kingdom, Venezuela, Zambia, Zimbabwe.

    Impressive list of countries participating






  • if I could stay later when there’s broken things in prod

    In general, or on this instance?


    Do you have team retrospectives? That’s where I would bring it up in my team. Raise my concerns, explore and understand what team consensus is around this topic, around risks, quality, etc.

    If the team consensus and/or management consensus is YOLO - then I try to protect myself from personal investment and going beyond contractual obligations. Because I already know what will come and how it will negatively affect me personally.

    It’s possible a honest discussion with management about goals and risks could lead to clarified guidelines, requirements, and goals. If it doesn’t, I’d probably be looking for a better job/environment. Because I’ll be miserable if colleagues YOLO, no matter how careful I am personally.



  • Some people are more receptive to these kinds of things than others. Not only in terms of open mind but also how they are able to apply it (or capable of applying it?).

    I wish agreeing on intentions and improvements in terms of scoping and description would be met. Same with unnecessary, obvious issues showing up costing review time and iterations. I just don’t get how these are issues - but they are - for or with some people.


  • I never thought I would move away from FOSS/AGPL by default. The more I read about this issue, the more I consider providing free services instead of FOSSing. It’s a shame.

    FOSS is still important and necessary to a degree, for auditability and self-hostability, very important for security and control, even as a conscious/careful user.

    Maybe this puts us more towards “pay to free the code” or something, so there is at least some compensation. Won’t make verbatim regenerated AGPL to MIT any less hurtful though.

    If you publish a free service, at least they’re not feeding from your code too.

    Tragic.