Who should be responsible for the development of tools? Citizen developers or professional developers only? Or maybe a combination of the two is the right answer. Back to help hash out the pros and cons of this hot topic, Mark Pendergast joins Craig and Thom on this episode of The Digital Enterprise Society podcast. Without their usual polar opposite views, Craig and Mark highlight the strengths of both citizen and professional developers and share their recommendations for working toward coexistence to promote better innovation.   On today’s podcast, you will learn:   Citizen developer vs. professionals only Mark has been a citizen developer most of his career. Anyone who has a day job but also writes code is a citizen developer. These developers may be trained, or they may be hackers. Professional developers may also be trained or may also be hackers. Professionals aim to fill the demands of the IT department while citizen developers meet the needs that are left unaddressed by IT. IT faces constraints while citizen developers are free to address whatever they’d like. Citizen developers don’t always possess the level of skill that the professionals do.   Advantages and disadvantages of the citizen developer Citizen developers are generally quite close to the business need. They understand what’s missing and how to address it. The best citizen developers are free from the constraints of the IT department. Citizen developers rarely have a long-term focus and tend to build non-scaleable products. A lack of understanding of the professional craft reflects poorly in their work.   Advantages and disadvantages of the professional developer Professionals are better trained to handle the scaling problems. Professionals tend to know what is coming before it hits the company. However, very few professionals really understand the full scope of the business. A clearly defined division of responsibility would benefit both the professional and the citizen developer, as well as the end product. Management doesn't always support the cooperation of professional and citizen developers because it limits innovation.   Craig’s rules surrounding the development of software Don't’ share (if you're the citizen developer). If the product is attached to the IT network of the company, it’s the company’s responsibility to keep it safe and scaled. Phototypes can come from anybody and should be in the hands of the people that use them.   Mark’s rules surrounding the development of software When the rules become oppressive, tyranny ensues. IT is too powerful and readily available to overcome. The more IT tries to shut apps down, the more they will be shared. Rules need to be reasonable all around so they don’t force citizen developers underground.   Final words and takeaways Mark argues that there can be peaceful coexistence but recognizes that it won’t be easy to achieve. Improving the craft is key to success. IT needs to work together with citizen developers to provide tools and offer support. Craig agrees with Mark — the more knowledge any developer brings to the problem the better they can solve the process. If IT can solve the problem, find a citizen developer who can. Coexistence is the answer to better innovation.   Continue the conversation with us within the Digital Enterprise Society Community at www.DigitalEnterpriseSociety.org.   Digital Download: Virtual Round-Table Series