Conceived in the 1980s, rapid application development, or RAD, was the first development methodology to challenge traditional waterfall development practices. Though often mistaken for a specific model, rapid application development is the idea that we benefit by treating our software projects like clay, rather than steel.
Software is a unique engineering structure because it is transient. With traditional engineering projects like bridge construction, engineers cannot begin to build a bridge then change their minds half way through the process—that’s pure chaos. But a bridge built in software? Engineers can change that every day. RAD takes advantage of this by emphasizing rapid prototyping over costly planning. (more…)
This is the fourth in a multi-part series that examines the negative reactions developers have to low-code platforms. If you’re a completionist like me, you will want to read the previous posts before you continue: Low-Code Replaces Developers, Low-Code is a Black Box Solution, and Low-Code is Not Code.
“Move fast break things,” is today’s de facto startup motto. The idiom implies that a few bugs are okay as long as you’re fast. Despite distancing the company from this belief in 2014, Facebook’s Mark Zuckerberg popularized this idea as a positive attribute of early product development. And the axiom remains: moving fast results in broken work. (more…)