Join us on Wednesday, July 24th at noon Pacific for the Crowd Supply Hack Chat with Josh Lifton!
When you’re ready to take your Next Big Idea from a project to a product, you face problems that don’t normally present themselves to the hobbyist. Building one of something is quite different from building many of them, and soon you’re dealing with issues with parts suppliers, PCB fabrication, assembly, packaging, shipping, marketing, and support.
It takes a lot to get your idea to market, and a guiding hand would be most welcome to the budding hardware tycoon. That’s the logic behind Crowd Supply, the Portland-based crowdfunding and mentoring company. Josh Lifton is its CEO, and he’ll drop by the Hack Chat to answer all your questions about how crowdfunding works, what Crowd Supply offers to help creators, and what the fundamentals of a successful project are.
Our Hack Chats are live community events in the Hackaday.io Hack Chat group messaging. This week we’ll be sitting down on Wednesday July 24 at 12:00 PM Pacific time. If time zones have got you down, we have a handy time zone converter.
Click that speech bubble to the right, and you’ll be taken directly to the Hack Chat group on Hackaday.io. You don’t have to wait until Wednesday; join whenever you want and you can see what the community is talking about.
[Photo credit: Jon House, Portland Tribune]
Hardware hacking is a way of life here at Hackaday. We celebrate projects every day with hot glue, duct tape, upcycled parts, and everything in between. It’s open season to hack hardware. Out in the world, for some reason software doesn’t receive the same laissez-faire treatment. “Too many lines in that file” “bad habits” “bad variable names” the comments often rain down. Even the
unsafest silliest of projects isn’t safe. Building a robot to shine lasers into a person’s eyes? Better make sure you have less than 500 lines of code per file!
Why is this? What makes readers and commenters hold software to a higher standard than the hardware it happens to be running on? The reasons are many and varied, and it’s a trend I’d like to see stopped.
Software engineering is a relatively young and fast evolving science. Every few months there is a new hot language on the block, with forums, user groups, and articles galore. Even the way software engineers work is constantly changing. Waterfall to agile, V-Model, Spiral model. Even software design methodologies change — from pseudo code to UML to test driven development, the list goes on and on.
Terms like “clean code” get thrown around. It’s not good enough to have software that works. Software must be well commented, maintainable, elegant, and of course, follow the best coding practices. Most of these are good ideas… in the work environment. Work is what a lot of this boils down to. Software engineers have to stay up to date with new trends to be employable.
There is a certain amount of “born again” mentality among professional software developers. Coders generally hate having change forced upon them. But when they find a tool or system they like, they embrace it both professionally, and in their personal projects. Then they’re out spreading the word of this new method or tool; on Reddit, in forums, to anyone who will listen. The classic example of this is, of course, editors like the vi vs emacs debate.
Continue reading “Don’t Be A Code Tyrant, Be A Mentor”