设计还是原型？ [英] Design or prototype first?

问题描述

第一次接近一个项目最好退后一步，思考一下，或者只是潜水，稍后开始进行编码和抛光。本质上，您先设计或尝试快速原型吗？

我已经被两种方法烧毁，有时我会尝试思考一切，但是当我实际上下达到我遇到的问题，我没有考虑到，有时候，当我首先编写代码，需要重做，以配合更好的整体设计。许多我的问题源于缺乏经验，但任何建议都是值得欢迎的。

解决方案

逐步和迭代地执行

设计一下，实现一点。

从设计开始，您可能会遇到一个隧道效应，在您实际执行某些操作之前，您无法获得任何真实的反馈。

开始没有设计，你可以做出你会后悔的决定。

理想的情况是能够实现一个非常骨架的端到端版本的系统，可以进行测试，并向客户展示。

When first approaching a project is best to step back and think through everything or just dive in and start coding and polish at a later date? Essentially, do you design first or try to rapidly prototype?

I have been burned by both methods, sometimes I try and think everything through but when I actually get down to the nitty gritty I encounter problems that I didn't take in consideration, and sometimes when I code first I end with code that needs to redone to fit in with a better overall design. Alot of my problems stem from inexperience, but any advice is welcome.

解决方案

Go incrementally and iteratively.

Design a bit, implement a bit.

Starting with a design you can suffer from a tunnel effect where you cannot have any real feedback before you actually implement something.

Starting without design, you can take decisions you'll regret.

The ideal situation is to be able to implement a very skeletal end-to-end version of your system that can be tested, and demonstrated to the customer.

这篇关于设计还是原型？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！