Designing bfr coding, or coding bfr designing.

My english is not as good as I would like to so I’ll be very brief: I’ve explored both ways and certainly there are even and odds in both of them. Doing ‘the artwork’ before the ‘engineering work’ may deliver a good looking app, but perharps code will follow the form, and not the function; and doing the inverse process, will increase the ‘impedance mismatch factor’ between business logic and interfaces.

So my generic solution is: Work this two aspects independently and take your time to implement some flavor of ‘veiw helpers’ to short the distance between logic and interface. It works nice for me.

It has a second advantage: you can develop a method, which can be a very valuable tool for success replication.

That’s my point of view.

Great Blog!

Américo Patetta, Montevideo, Uruguay.

Reply

Please solve the math problem above and type in the result. e.g. for 1+1, type 2.
The content of this field is kept private and will not be shown publicly.
  • You can use Markdown syntax to format and style the text.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options

Back to top