Nobody's stupid because they're not sure about something. It's totally cool to ask for help or opinions when you're thinking through a hard problem.
To answer your question you should understand what creativity and practicality mean in your context. I would generally think that being practical and creative aren't at odds with each other.
When working through a problem for work I tend to err on the side of practicality. We could be coming up with a new way to do data transformations, building out distributed tracing tools, or trying a new way of scaffolding our projects. Each of those solve a real problem and have practical implications. They also require creative thinking to imagine and design new tools and workflows.
These projects are practical in the sense that they need to solve an actual problem (e.g. deliver a net benefit to customer UX or development velocity). Contrary to how they sound, they often aren't obvious projects to take on or straight-forward solutions. It usually required days or weeks of lateral thinking to cook up one of these. In this context, creative thinking complimented practical thinking and produced a better result than one of those modes taken in isolation.
Sometimes it's helpful to circle around the problem you think you want to solve to better understand what your actual problem is.
Be careful reading other's ideas since it will affect the way in which you see the problem. Your view of the problem may be skewed after reading other information. OTOH, it's common that you can piggyback on existing ideas (see taco bell/duct tape programming).
To answer your question you should understand what creativity and practicality mean in your context. I would generally think that being practical and creative aren't at odds with each other.
When working through a problem for work I tend to err on the side of practicality. We could be coming up with a new way to do data transformations, building out distributed tracing tools, or trying a new way of scaffolding our projects. Each of those solve a real problem and have practical implications. They also require creative thinking to imagine and design new tools and workflows.
These projects are practical in the sense that they need to solve an actual problem (e.g. deliver a net benefit to customer UX or development velocity). Contrary to how they sound, they often aren't obvious projects to take on or straight-forward solutions. It usually required days or weeks of lateral thinking to cook up one of these. In this context, creative thinking complimented practical thinking and produced a better result than one of those modes taken in isolation.
Sometimes it's helpful to circle around the problem you think you want to solve to better understand what your actual problem is.
Be careful reading other's ideas since it will affect the way in which you see the problem. Your view of the problem may be skewed after reading other information. OTOH, it's common that you can piggyback on existing ideas (see taco bell/duct tape programming).
There are lots of good resources on this subject: John Cleese talk linked elsewhere - https://www.youtube.com/watch?v=y70nbDJI5Uk
Rich Hickey Hammock Driven Development is a more direct application to software development.- https://www.youtube.com/watch?v=f84n5oFoZBc
Another good Alan Kay talk from YC - https://www.youtube.com/watch?v=id1WShzzMCQ
A Mind for Numbers
How to Solve It
Psychology of Intelligence Analysis is interesting too but less applicable (eschewing the Einstellung effect) - https://www.cia.gov/library/center-for-the-study-of-intellig...