I built Excel for Uber and they ditched it (basta.substack.com)

Article summary

The article's content is not available, but the discussion reveals it's about someone who built an Excel-like tool for Uber, which the company later abandoned. The story sparked a conversation about the emotional reality of being detached from one's work and the blurred lines between personal and professional projects. The discussion delves into the complexities of code ownership, copyright, and the ethics of reusing personal code in a work setting.

Main themes

• code ownership
• copyright and licensing
• personal vs professional projects
• ethics of code reuse
• employer-employee agreements
• open-source software

What commenters say

• Some argue that code written outside of work hours belongs to the individual, regardless of its potential use in a work setting.
• Others claim that using personal code at work can be considered a violation of the employer's rights, especially if the code was created using company resources.
• There is a debate about the enforceability of contracts that grant employers ownership of employees' personal code, with some arguing that such contracts are unenforceable.
• The use of open-source licenses and public repositories can affect the ownership and reuse of code, adding complexity to the issue.
• Some commenters believe that reusing personal code at work without permission is unethical, while others see it as a practical solution to common problems.
• The line between personal and professional projects is often blurry, and the ethics of reusing code depend on the specific circumstances and agreements in place.
• Employers may have different policies and expectations regarding code ownership and reuse, and employees should be aware of these before using personal code at work.