Extensive shoutout to @ElliottLMz and @Cinema_Sin for sharing their experiences with the shiny object syndrome with me.
Developmental proficiency and productivity are unofficial prerequisites in the development industry. Often, the most industrious of developers can fall victim to the notorious shiny object syndrome. The shiny object syndrome is a often categorized as a cycle or loop where a developer actively develops a flawed game idea within weeks, months, and occasionally years, and eventually replaces it with another flawed game idea concurrently. Kind people were interviewed to evaluate unhealthy practices individuals with the shiny object syndrome routinely perform, as well as share personal anecdotes about their experiences with the notorious syndrome.
Hard work beats talent when talent does not work hard.
— Kevin Durant
What determines the shiny object syndrome as negative? Generally, evaluating the provided circumstances assists in identifying methods to prevent it. The shiny object syndrome can drastically hinder developmental productivity and competence. Ultimately, productivity would be invisible along with valuable work. Concurrently discarding effortful assets and projects may raise stress levels to specific individuals. Two interviewees, @ElliottLMz and @Cinema_Sin both frequently experience the shiny object syndrome, and it substantially effects their working environment.
When I feel tired or burnt out, I usually just get no developing done.
— @ElliottLMz, Discord
As a general rule of thumb: always evaluate the provided circumstances
The shiny object syndrome - Its impact on you
Through the dialogues of multiple individuals experiencing the shiny object syndrome, it’s conclusive that the impact is drastic. Both interviewees struggled through unnecessary stress; @Cinema_Sin sacrificed time for study and homework because of the shiny object syndrome. Additionally, both interviewees set a lenient restriction that ensures development must end after few hours in a day. Fortunately, methods were developed to interrupt the cycle of the shiny object syndrome.
The shiny object syndrome - Methods to prevent it
Originally encountering the syndrome could potentially be frightening and overwhelming. Evaluating all the circumstances is a very accurate decision. This refers to evaluating fundamental ingredients to success: evaluate potential collaborations; evaluate what’s trendy on Roblox; evaluate advertisement alternatives; evaluate potential game audience. Such factors are fundamental but ensure the game is compelling, thus ensuring development is unanimously valuable. Additionally, evaluating time and development capabilities are vital.
…external “professionals” who have “experience” are fundamentally penalized by a simple problem: they don’t understand the audience. You guys do. This makes all the difference in the world.
— zeuxcg, In response to Developer’s Feedback on Developer Exchange
As a general rule of thumb: evaluate all potential circumstances and how to utilize them
Directing a game without assistance is difficult, but developing a game in full without assistance is practically impossible. Collaborating with others reduces the feel of being obliged to develop. This feeling is strong, and automatically resolves multiple family-development balance tensions. Collaborating additionally improves development proficiency and quality. It’d be kind of arrogant to close all collaboration opportunities. There’s rarely a valid excuse.
Two brains > one; collaborate in development stages
Allocate time to spend with family and real-life interactions. Ensure development doesn’t consume into the real-life contents of a developer. Set a developmental restriction (x hours) daily to limit one’s self from developing constantly. Remember that when going through the shiny object syndrome, development can be procrastinated consequently.
Regressing in development stages to allocate real-life time is effective
Brief recap
Evaluate and identify fundamental factors such as advertisements, development capabilities, and expected audience.
Collaborate in development stages to drastically reduce stress while increasing development productivity and quality.
Regress in development stages if developing is evidently consuming family and real-life time. Apply daily restrictions to prevent this from occurring.
Establish priorities such as family, real-life and schooling.
Personal Testimonials: @ElliottLMz & @Cinema_Sin
Both interviewees coincidentally experience(d) the shiny object syndrome. Through conclusive evidence, the shiny object syndrome is clearly damaging and disliked. @Cinema_Sin described it as an “eternal loop I can’t break out of.” They also stated that it is damaging and decreases productivity. Similarly with @ElliottLMz, their productivity is hindered as well when experiencing the shiny object syndrome. @Cinema_Sin went days procrastinating homework to push a game update which ultimately transitioned into dust. However, they never sacrificed family time for development.
@Cinema_Sin stops developing a game at random times for no specific reason. @ElliottLMz stops developing when the complicated stages must receive their attention. There are various methods to prevent inherent consumption of the shiny object syndrome. Both interviewees restrict themselves for a general amount of hours daily, albeit they’re partially lenient.
I have a rough schedule. I usually start each day with a notepad writing down my realistic goals programming wise (e.g. finish coding the XP system). When it comes to family time, I usually spend the evenings and certain holidays with my family.
I live with only 2 other family members, so I don’t spend weeks at a time just catching up with people. Generally, I spend a lot of time programming as it’s something I enjoy doing
either programming nonsense or consuming content (like gaming, youtube, tv)— @ElliottLMz, Discord
Not really a schedule, I do take my dog out for walks in the evening though.
— @Cinema_Sin, Discord
I can’t confirm if all effective methods were discussed about in this article. Fortunately, I have never experienced the shiny object syndrome. Although the text was brief, it included insightful methods. If critical content was missed, please attach it in the replies section or contact me @ monorust#4750.
