What are the design principles of software design?

If I'm an industrial designer, could I just hire software engineers to develop any software I needed to develop? (because, I'm not a computer programmer, and would prefer to stick to art, and product design tasks)

  • I'm intending to become a product designer/industrial engineer with a focus on Art, Design and perfectionism, because that's what I'd do best. If I am not a software engineer/computer programmer, and don't intend to learn coding either, could I just hire them (Software engineers) to create any software programs, websites, etc I need, seeing as I'm not a software engineer/computer programmer by profession? NOTE: I intend to start a Product Development & Manufacturing company someday, doing what I love - Product Design with my focus being the Art & Design and perfectionism side of my business of coming up with ideas for actual physical products - and I'd need software engineers (Because, I don't have a clue, nor have passion to care to write the software myself) to write any software I'd need for my products? Would I be best to just stick to what I know and do best (Art & Design perfectionism) and hire software engineers instead, seeing as that's not my skill set?

  • Answer:

    "Product Development & Manufacturing" is a broad description. Product development is so much more than a pretty design and a niffty concept, save that for the "inventor" adds on late night talk radio. Everyone has ideas. Execution is the key to success. "Creating" a webpage or software is a complex and iterative process. You don't make something right the first time. Throughout the development process itself you learn things that feed back into the product definition. (Product design management and feature creep is a whole new topic.) The work performed by contract resources will NEVER be as good as you need. In fact, it will often be poor and much of it will have to reworked or totally redone. Depending on the product complexity, this may be fine for a prototype or proof-of-concept of a simple product. The quality of work deficit is inherent in the contract relationship. You don't want to pay the contractor any more than you have to. They need to do the minimal amount of work to get paid. Your product needs to work well in order to make money on the the long haul. They need to meet the minimal contract requirements to make a profit. Contract resources typically do not have a significant stake to do anything more, unless you have a long-term relationship. Often the contractor also doesn't have the depth of knowledge on the subject to add any significant value, increasing your need for oversight and management. Contracting critical tasks because you (or your company) don't want to understand them is one of the worst reasons to do so. If you can't hire an employee to do the work, find key skill resources to join you as partners. This might start out as a contract relationship, but might involve other arrangements as the project progresses. After many experiences with contract resources, outsourcing is a last resort. I would never hire out critical skills/knowledge. You need to own the key knowledge for your products or services. Nevertheless, there are successful companies that are only a name plate. Eugene

Eugene Bodrero at Quora Visit the source

Was this solution helpful to you?

Other answers

Given unspecific goals for when you become your own boss, and finally are in position to commission development of target software, I would say you definitely NEED to acquire enough knowledge of systems analysis, and software development (not the same as mere »coding« quite a bit above it in abstract terms) in order to communicate your requirements, be able to guide the development along the way, and evaluate quality of the final product (runtime object code - look it up). Initially, before first line of code is even written, half the work is defining,  describing, and then breaking down (and eliminating some of) your perceived needs. You therefore must have a common language with the people who'll be executing it for you, or else they'll run rings around you.             If you do not possess such basic skills, the hired hand programmers will @ best assemble what they think you asked for/ most probably in the first iteration misjudge your needs, and you'll be left with a half-finished, maybe even not debugged outside initial parameters, pricy so-so-working code for your Artsy-Fartsy designed hardware. Even then in all probability you'll first have to hire a capable software development manager and later a quality assurance/ testing service to make sure the commissioned code answers your requirements.             Maybe you better stick to such instances of "Art & Design" that do not require custom software component?

Stan Deen

I have a design and manufacturing company. I had the idea that I could hire folks to do the software side, but found I needed to learn programming myself in order to write the specifications for the project. By then it was a small step to write my own stuff.  Being able to specify the project will take you much deeper into the programming world than you will want to, but I think it is necessary for you to be able to work with programmers efficiently.  --Karl

Karl Walter

Just Added Q & A:

Find solution

For every problem there is a solution! Proved by Solucija.

  • Got an issue and looking for advice?

  • Ask Solucija to search every corner of the Web for help.

  • Get workable solutions and helpful tips in a moment.

Just ask Solucija about an issue you face and immediately get a list of ready solutions, answers and tips from other Internet users. We always provide the most suitable and complete answer to your question at the top, along with a few good alternatives below.