Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Find a need, fill a need.
As Demolishun said.
My creativity comes from my everyday frustration on stupid processes I need to speed up or make easier.
for the first question, I think an easy solution is getting paid to do something.
for the second, I guess designing skills come by doing many bad designs
I built a few crude tools for a networking cause I attended and when my mother complained about their backwards receipt->revision procedure I made her a program to help catalog and gather the receipts.
Other than that, I've mostly worked on work-related stuff, though I was lucky to have hands free to assault whatever case was bothering me when I started.
Find something that makes you tick or makes you rich ;-)
Read up on design patterns for your chosen language too, it's not so broad design-thinking, but it helps supplying building blocks when trying to piece something bigger together. Don't know what you do for higher-level design tbh, I usually just winged it back when I designed new apps
Ranchu9135dFun Fact :D
> How do you all come up with project ideas
Wander around the world aimlessly, bumping into random things until something grabs your attention.
Easier these days with the internet, YouTube, google images, the news..
Some of us are gifted and ideas just pop into our heads like every minute of every day..
But if you do those things too, its like being on crack. :-)
Look at one screenful of images, and suddenly a dozen ideas hit you at once !
> how do you deal with not knowing how to
> design something?
Start with a single starting point, a bit.
Like I'm designing a vehicle at the moment, never designed one before, know practically nothing about vehicles..
How many wheels do I want, 1, 2, 3, 4, 5, 6, 8..
Actually, that is rather a difficult design area to be honest !
For now, its 3, but next vehicle, it will be 4.
After that, I'm not sure, maybe 2..
One of these would be nice:
> EDWARD - Electric Diwheel With
> Active Rotation Damping
Just difficultly in getting big enough tyres for it !
Example, I wanted a shelf.
Where do I start.
What do I want to put on the shelf ?
Ok, lets measure all the books and find the tallest one.
That will be the max distance between shelves.
How many shelves could I fit on the wall in the space I want the shelves ?
How deep should they be ?
How heavy are all those books going to be on the shelf, how strong should the material I use be for that so it doesn't bow ?
Maybe I can support it every so often so I can use a thinner material..
How am I going to hold the shelf to the wall ?
(One shelf I designed, I used a cantilevered solution for the bottom shelf !)
If I use wood, am I going to paint it, varnish it, or just leave it as it is to get dirty..
Do I use nails or screws to hold it together ?
Or fancy joints that take skill and time to make..
If I'm screwing it to the wall, what is behind the wall that I should avoid screwing into..
What's the cheapest screws I could use ?
One reviewer of the book put things well:
The title of this book may deter some people from reading it and that would be a mistake because, as its subtitle correctly indicates, Ralph Heath explains how the power of taking bold but carefully calculated risks and making mistakes while pursuing what Jim Collins characterizes as BHAGs (i.e. Big Hairy Audacious Goals) can achieve success of a magnitude and value that would otherwise be impossible. Heath really does not advocate celebrating failure per se; rather, he advocates celebrating the process by which to leverage failure as a means by which to succeed.
One of this book's greatest strengths is Heath's strategic use of quotations throughout his narrative. For example, here is a statement by the late Bill Walsh, American Football Hall of Fame coach of Stanford University and NFL Hall of Fame coach of the San Francisco 49ers. I also highly recommend his book, The Score Takes Care of Itself.
Page 1 of 5
"When you are determined to use failure as a school for success, you'll find that it's easier to hold a strategic course and refine the plan, rather than constantly second-guessing yourself. Panic subsides, along with depression, humiliation, and all the other unhappy byproducts of perceiving failure as an unmitigated disaster." The phrase "failure as a school for success" indicates what, in fact, Heath proposes to celebrate: appreciation of the lessons to be learned from failure that will guide and inform the journey to ultimate success. That is precisely what Thomas Edison had in mind when correcting a research colleague who had been frustrated saddened another "failure" in the laboratory: "That's not a failure. It's a very valuable development because it provides additional evidence of what won't work."
Page 2 of 5
Edison also observed that "vision without execution is hallucination" and Heath clearly agrees with him because the most productive "students" who use failure "as a school for success" are results-driven. Throughout the 30 brief but substantial chapters that comprise this book, this is one recurrent theme is that pursuit of success is a journey and that some of the most important progress is the result of failure if - HUGE if - what it reveals is recognized, understood, appreciated, shared, and acted upon. Time and again, Heath strongly emphasizes the importance of creating and then sustaining a culture in which constant and bold but prudent experimentation is encouraged, supported, and (yes) celebrated. Heath calls this an "idea-friendly environment." It must also be a failure-friendly environment, for reasons previously indicated.
Page 3 of 5
I commend Heath on his skillful use of several reader-friendly devices, notably the "Chapter Insights" checklists of key points such as the one in Chapter 17, "Continuous Improvement." Here is the first of three:
"Small celebrations: Progress should be celebrated as a significant accomplishment. If you're shooting for a big goal, congratulate yourself and others on the team along the way. Whether you ultimately succeed or fail, your accomplishments deserve recognition and praise."
That's not a head-snapping revelation, nor does Heath make any such claim for it, but it does correctly stress the importance of celebrating efforts throughout a process and, I presume to add, celebrating each dead-end, dry well, blind alley, etc. along the way as a valuable learning opportunity. It is important to remember that perfection is a journey, NOT a destination.
Page 4 of 5
This book will be especially valuable for those preparing for a career in business or have only recently embarked on one. It will also be valuable for middle managers who may need a reminder of certain basic principles. Finally, I think this would be an excellent book for senior managers to purchase in bulk quantity for their direct reports.
Ultimately, of course, workers should be rewarded for the results of their efforts but those efforts include taking full advantage of what is learned from mistakes, errors, etc. That is the core insight in Heath's book and one that more supervisors need to keep in mind.
Page 5 of 5
how do i come up with ideas?
not important. the important question for me is how do you do it that you DON'T constantly get bombarded by ideas and get depressed by knowing you'll never have enough time to realize even half of them?
(weed tends to put my idea factory into overdrive, though, so it might help you(?))