Re: Confused about programming tendency..
- From: nick_keighley_nospam@xxxxxxxxxxx
- Date: Thu, 26 Feb 2009 05:18:14 -0800 (PST)
On 25 Feb, 13:58, Ed Prochak <edproc...@xxxxxxxxx> wrote:
On Feb 20, 5:19 am, nick_keighley_nos...@xxxxxxxxxxx wrote:
On 19 Feb, 15:03, DocuMaker <documa...@xxxxxxx> wrote:
Is this an acceptable programming strategy?
"Have final result or picture in mind (think of schema and that damn
date graph where you needed to get certain values to match), and then
code program until it looks that way or gets the answers you want??"
I don't like that strategy but I've used it twice and it solved
problems.
ultimately isn't that the only criterion to judge a design technique
by?
perhaps it depends on what we mean by "solved"
Are you familiar with the classic triangle of quality-speed-price?
Well it gets quoted a lot. Often as the Print Shop
"quick, good, cheap - pick any two"
I'm not convinced they trade off against each other in any simple
fashion.
Software Engineering is being able to make the trade off between those
factors. Otherwise, all you are doing is hacking.
I'm not convinced he is, or wants to be, a software engineer.
He might just want to write better programs.
It solved your problem. Hurrah!
There's a real problem with the solution... it doesn't seem
planned.
why should it look planned. You mean it looks hacked together?
A mess?
Just "try this and try that" till FINALLY it works/looks the
way it needs to.
ah, hacking
In all the frustration, I don't think I learned anything. I feel like
I *hacked* my own stuff just to get it to work!!! :-(
perhaps you did.
You are really asking about program design and like any other design
there
are no easy answers. If there *were* easy answers then someone would
have
coded them up by now and we'd all be out of a job!
Read some or all of these
"The Mythical Man Month"
"Design Patterns"
"Refactoring"
"Structured Analysis"
"Computer Architecture A Quantitative Approach"
"Structure and Interpretation of Computer Programs"
oo. and http://www.amazon.com/Quality-Software-Management-First-Order-Measurement/dp/0932633242
Ah, finally someone mentioned that you can learn some programming
techniques in a more disciplined manner.
and anything you can find about design in other fields
(boat design and VLSI are both interesting)
I'd suggest taking a class or two at your local university. As Nick
mentioned, learning something about other fields is helpful too. But
getting some grounding in the theory of Computer science & Software
Engineering will help. It is like other engineering fields, a mixture
of art and science. The art is easier the more you know the science.
GUI's are interesting because (IMHO) they
are usually so badly done.
Agree, though I don't like doing a GUI.
Finally, if you like, joining IEEE or ACM might help.
.
- References:
- Confused about programming tendency..
- From: DocuMaker
- Re: Confused about programming tendency..
- From: nick_keighley_nospam
- Re: Confused about programming tendency..
- From: Ed Prochak
- Confused about programming tendency..
- Prev by Date: Re: Things to avoid typing at a command prompt
- Next by Date: Re: Things to avoid typing at a command prompt
- Previous by thread: Re: Confused about programming tendency..
- Next by thread: Re: Confused about programming tendency..
- Index(es):
Relevant Pages
|
