An ode to houseplant programming 🪴

Summary

The author introduces "houseplant programming" as a metaphor for small, personal software projects. They contrast this with production-ready code, emphasizing the value of individual utility and enjoyment in coding. The article also defines "bouquet programming" as one-off code for specific, non-recurring use.

Key Takeaways

1. "Houseplant programming: tiny software just for yourself."
2. The author values personal software projects for their individual utility and the joy they bring, rather than focusing solely on production-ready code.
3. "Bouquet programming is still worth writing home about (!) and sharing generously in the same ways as houseplant programming—or agricultural programming!—but is even less likely to work off-the-shelf for a new application than houseplant code is, even if rerun by the same person who originally programmed it."

Statement Breakdown

• Claimed Facts: 40% of statements the article presents as facts
• Opinions: 50% of statements classified as editorial or subjective
• Claims: 10% of statements surfaced for additional reader evaluation

Credibility & Bias Reasoning

Credibility assessment: The article is a personal reflection on software development philosophy, with clear sourcing of ideas and examples. The author's claims are primarily about their own experiences and perspectives, reducing the risk of factual inaccuracies. The article is transparent about its subjective nature.

Bias assessment: Personal Philosophy. The article presents a specific viewpoint on software development, favoring personal, small-scale projects over large, production-ready ones. This perspective is presented as a positive alternative, but the author acknowledges the validity of other approaches. The bias is towards valuing individual expression and utility in coding.

Note: This article presents a personal perspective on software development. Interpret its claims within the context of the author's experiences and values.

Credibility flag: Reflective, Personal

Claimed Facts (6)

• This is presented as a factual event regarding the origin of the term.
• This is a statement of fact about the purpose of a specific software project.
• This is a factual statement about the creation of a resource.
• These are presented as factual examples of the author's work.
• This is a definition provided by the author.
• This is a statement of fact about the nature of code.

Opinions (7)

• This is a subjective assessment of the concept of houseplant programming.
• This expresses a personal preference.
• This is a subjective feeling and interpretation.
• This is a subjective statement about enjoyment.
• This is a subjective statement about enjoyment.
• This is a subjective statement about the author's feelings.
• This is a subjective statement about the author's feelings.

Claims (4)

• While soil gnats can be annoying, their origin is not truly unknowable, making this a slight exaggeration.
• This is a subjective and potentially exaggerated interpretation of someone's attitude.
• The claim that the assumption is 'false' is debatable and depends on the context and goals of sharing code.
• This is a statement of fact, but it is not clear if it is a common occurrence or a one-time event.

Key Sources

• Author — Blogger
• Ryan — Recurse Center peer
• Aditya Athalye — RC peer