Ahoy, fellow software pirates! As the tech industry continues to evolve, it's important to consider the benefits of unionizing to protect our collective power and work towards a more ethical future. Here are three potential reasons why unionizing in tech is important:
Protecting worker rights: Unionizing provides software engineers with a collective voice to advocate for their rights and interests. This can include better pay, benefits, and working conditions. A 2018 survey by the Communications Workers of America (CWA) found that 74% of tech workers would be interested in joining a union to improve their working conditions.
Building more ethical products: Unions can help push for more ethical product development by advocating for data privacy, transparency, and fair labor practices. According to a 2019 report by the Tech Workers Coalition, unionizing can provide a counterbalance to the power of large tech companies and help ensure that workers have a say in how their products are developed.
Addressing power imbalances: The tech industry is known for its stark power imbalances, with a few large companies controlling a significant share of the market. By unionizing, software engineers can help level the playing field and negotiate on more equal terms with their employers. A 2018 survey by the International Brotherhood of Electrical Workers (IBEW) found that 71% of tech workers believed that unions were necessary to balance the power between employers and employees.
So, while unionizing may not be right for everyone, there are good reasons to consider it as we navigate the changing waters of the tech industry. Let's remember that by working together, we can build a more equitable and just future for all."
Sources:
"Unions and America's Changing Workforce: Results from a Survey of Workers in the Gig Economy and Other Non-Traditional Jobs" (CWA, 2018)
"Building Power in Tech: A Guide to the Tech Industry" (Tech Workers Coalition, 2019)
"The Future of Work in Tech: A Labor Perspective" (IBEW, 2018)
We Invested 10% To Pay Back Tech Debt; Here's What Happened
- Alex Ewerlöf
tl;dr: Alex discusses how "Tech Debt Friday" started at his org, what was learned and how it's executed: (1) We spend 10% of our time to deal with tech debt. (2) The first rule is not to create debt in the first place. (3) The PR that creates tech debt should come paired with the issue to deal with it. And more.
How We Improved DNS Record Build Speed By More Than 4,000x
- Alex Fattouche
tl;dr: "Our network now spans over 270 cities in over 100 countries, interconnecting with more than 10,000 networks globally. According to w3 stats, “Cloudflare is used as a DNS server provider by 15.3% of all the websites.” This means we have an enormous responsibility to serve DNS in the fastest and most reliable way possible."
Resilience And Waste In Software Teams
- Jessica Kerr
tl;dr: Jessica explains resiliency in the context of the Southwest Airlines software failure. "When software is brittle, it falls over in production, and that falls to people to fix. While software can be robust to anticipated conditions, only people handle unexpected events. When software can’t even handle stuff that happens all the time, then people suffer the strain."
Examples Of Floating Point Problems - Julia Evans
tl;dr: Julia wanted specific examples of floating point bugs in real-world programs and asked folks for "examples of how floating point has gone wrong for them in real programs." This post shares 8 examples of such problems. Julia writes programs to highlight the problems and ways to solve them.
Git Commands You Probably Do Not Need
- Martin Myrset
tl;dr:
The empty commit.
Pushing locally.
Commit ranking.Cat file.
Orphan commits.
Filter branch.
Octopus merge.
Rounding off.