Content deleted Content added
m Date maintenance tags and general fixes, removed Stub tag |
criticism |
||
Line 52:
* Overall quality of the applications produced
==Criticism==
===Inefficiency===
A major drawback with the implementation of end-user development is that it removes the end-users away from their daily task, decreases productivity and efficiency. Commentators have been concerned that end users do not understand how to test and secure their applications. Warren Harrison, a professor of computer science at Portland State University, wrote:<ref>{{cite journal|url=http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=01309636 |title= The Dangers of End-User Programming |last=Harrison |first=Warren |journal=IEEE Software | volume=21 | issue=4 | date=July/August 2004 | format=pdf | doi=10.1109/MS.2004.13 | accessdate=2009-03-02 }}</ref>▼
Management somtimes views end-user development time as time taken away from their daily task, decreasing productivity and efficiency.
Colleagues of end user developers sometimes view them as slackers, who don't contribute to productivity while hacking.
===Security===
▲
<blockquote>It’s simply unfathomable that we could expect security... from the vast majority of software applications out there when they’re written with little, if any, knowledge of generally accepted good practices such as specifying before coding, systematic testing, and so on.... How many X for Complete Idiots (where “X” is your favorite programming language) books are out there? I was initially amused by this trend, but recently I’ve become uneasy thinking about where these dabblers are applying their newfound knowledge.</blockquote>
| |||