Pie doesn't need to be original (unless you claim it so)
The article explores the contrasting expectations in creative fields like baking and software development, emphasizing the importance of personal enjoyment, clear goals, and understanding creators' intentions for constructive feedback.
Read original articleThe article discusses the differing expectations and values in creative endeavors, particularly in baking and software development. It uses the metaphor of baking a peach pie to illustrate how personal projects are often judged against the standards of originality and innovation, which can lead to confusion and discouragement for creators. The author emphasizes that baking a pie is a personal and enjoyable act, while academic settings, like the CRISP conference, require a clear understanding of how a project contributes to the community. The piece highlights the importance of setting clear goals for creative work, whether for personal enjoyment or academic contribution, and suggests that starting from a place of playful exploration can foster creativity without the pressure of harsh critique. The author encourages feedback-givers to understand the creator's intentions to provide appropriate support rather than criticism.
- Creative projects can be personal and enjoyable without needing to be original.
- Different contexts (personal vs. academic) have varying expectations for creative contributions.
- Clear communication of goals can help align feedback with the creator's intentions.
- Starting with playful exploration can lead to more innovative outcomes.
- Understanding a creator's goals is essential for providing constructive feedback.
Related
On having more interesting ideas
The article explores idea generation for writing, emphasizing reflection, engaging with others, reading, solitude, passion pursuit, note-taking, curiosity, and exploration to foster creativity. It highlights diverse influences on compelling ideas.
Ask HN: How did you break out from being a lone developer?
A software engineer with 15 years of experience seeks insights on transitioning from solo development to collaboration, facing challenges due to family commitments and slow community responses in open-source projects.
You should make a new programming language
Creating a programming language enhances understanding of design and execution, encourages learning through initial flaws, and fosters creativity. Guided projects and resources support beginners in this fulfilling endeavor.
Please Don't Idolize Me (Or Anyone, Really)
John Scalzi discusses the pitfalls of idolizing creative individuals, emphasizing their complexity and flaws. He advocates for appreciating their art without unrealistic expectations, promoting empathy and understanding instead.
On finishing projects
The author discusses challenges in finishing projects, emphasizing unclear goals and lack of accountability. Strategies like writing specifications and timeboxing can improve completion rates and foster accountability.
- Many commenters argue that while baking a pie is a personal and enjoyable act, software should offer something new or improved to be relevant.
- There is a distinction made between the consumption of pies and the duplication of software, with some emphasizing that software must stand out in a crowded market.
- Some participants suggest that the analogy fails because pies are consumed and appreciated in a different context than software, which can be easily shared and replicated.
- Several comments highlight the importance of understanding the audience's needs and intentions behind creating both pies and software.
- Overall, the discussion emphasizes the balance between creativity and originality in both fields, with varying opinions on the necessity of novelty.
But a slight change to the original scenario makes asking about originality much more reasonable:
Imagine you write a peach pie recipe over the weekend, and you give a copy of the recipe to your friend. They respond:
"Wait, how is this different from every other peach pie recipe that's ever been written? It seems really similar to another recipe I have."
That's not an unreasonable answer.
When I was in a band, one of the most valuable things my songwriting friends and I did for each other was tell each other when our work sounded like something that was already out there.
If you make a new piece of software and offer it to a friend to use, it's not unreasonable for them to ask how it's different from something that's out there already.
How well does this pie scale?
Sorry, it's a pie. If you want some, I'm sharing.
This is a good point. The comment section implicitly argues for novelty because it seeks a dopamine hit for something new -- after all, that's what people are looking for when they browse an aggregator! However, novel isn't everything even if you get more Internet points for it.
Is it original to execute something really well? Some would say yes, and some would say no. Lots of software that has had an outsized impact started out as very similar to other things, with "just" some improvements here and there. And I guarantee you there were over-eager commenters telling people to not be excited because it isn't new enough to them.
This isn't arguing for toxic positivity, either. Just a recognition that the bored/cynical users need for novelty is not something that everything listed on the Internet has to fill.
A pie is a physical object which enjoys a barrier to competition by being geographically near the consumer - other pies are not near your mouth.
A pie degrades quickly over time - last month's pie is not a competitor to today's pie.
A pie is destroyed during consumption - the pie your friend ate cannot be then eaten by you, no matter how delicious they say it was.
Software (and especially web/mobile/SaaS) is nothing like pies - your friend eats a delicious piece of software, telecommunicates this to you halfway around the world and you can put down the pie you were eating and instantly eat the same pie as your friend, then tell more friends. Pretty soon, nobody's eating the previous pies.
And there can be a lot of good answers - it is lighter, it looks cooler, the grip is more ergonomic, it is made of chinesium and cheap and if you are only building a shed - it will get the job done without using the unholy trinity of docker, ansible and terraform, and it will be in your hands in 5 min and not require overnight delivery by amazon.
And you can see this here on hnews - when someone shows us something that is entertaining, no asks how it differs from Heroes 3 or Quake. But we do for the next cloud synced postman clone that is on it's way to becoming as worse as Postman when they get the VC money.
What does this person want with your peach pie — why is it relevant to them? What do they get from the interaction
Why pay you, a person with this as their resume, when I can pay someone with 10 other 'hits' on their resume and their software also does this?
Why pay the newb is a great question to ask.
The answer to 'How is it different' is a whiteboard interview problem. If the developer cannot immediately extol the virtues of their product, do you want to give them money? Are they confident in their skills? Were they just copying other's recipes?
You'll know the answer to that and many other questions the minute the developer has to think and answer this fundamental question.
You'll also know if they're full of shit almost immediately.
It doesn't matter what the developer's prior relationship to you was. When they hand you software, and expect others to pay for it they need to be asked this question. Their answer will assist them in understanding their product and how to sell it to others.
Playing a classical piece music. You’ll never be anywhere near the top musicians, but people still do it because it’s enjoyable. They also share it with others.
Painting: you’re not a professional, but creating and sharing your works is still a joy.
The word CRISP? Will show up once, when I hit "add comment".
This has brought out the worst of Hacker News in a very obvious way. I suppose it was damn near guaranteed to, but you didn't have to literally every one of you bring a CRISPer to a pie fight.
"As a peer reviewer for the CRISP organization (ok, three times) the author is very obviously wrong about pie. It is a moral duty that pie be original work, properly cited, and advance the state of the art. I stopped reading after the second paragraph."
Software, on the other side, is duplicated on a whim. If you are not offering me new solutions that I need, I'm not even going to bother looking at it.
When you bake a pie, it gets eaten, so who cares if it's just like another pie, in fact it's probably great if it is. And the more people baking peach pies, the better!
The analogy should be with pie recipes. In that case, your pie recipe really should bring something different to existing ones. It doesn't need to be 'better' necessarily, but if it's essentially identical, there's no real point to the recipe, except for you to practice writing out recipes.
> Baking a pie is a creative act. It's personal, it's inherently delightful, it's an act of caring for others. It's also a craft that one can improve at over time. Just buying the "best" pie would defeat the point.
Not sure author realises the irony here. Creating "the pie" is not art. It is not even craft. It is baking ingredients, and people did that bazilions times before.
Related
On having more interesting ideas
The article explores idea generation for writing, emphasizing reflection, engaging with others, reading, solitude, passion pursuit, note-taking, curiosity, and exploration to foster creativity. It highlights diverse influences on compelling ideas.
Ask HN: How did you break out from being a lone developer?
A software engineer with 15 years of experience seeks insights on transitioning from solo development to collaboration, facing challenges due to family commitments and slow community responses in open-source projects.
You should make a new programming language
Creating a programming language enhances understanding of design and execution, encourages learning through initial flaws, and fosters creativity. Guided projects and resources support beginners in this fulfilling endeavor.
Please Don't Idolize Me (Or Anyone, Really)
John Scalzi discusses the pitfalls of idolizing creative individuals, emphasizing their complexity and flaws. He advocates for appreciating their art without unrealistic expectations, promoting empathy and understanding instead.
On finishing projects
The author discusses challenges in finishing projects, emphasizing unclear goals and lack of accountability. Strategies like writing specifications and timeboxing can improve completion rates and foster accountability.