Hacker News new | ask | show | jobs
by rhizome31 5349 days ago
> The problem is, 'programming' as such is the end of a process.

In a lot of cases it's probably more accurate to say it's one part of the cycle. If programming really ends up being the end of the process, something might have gone wrong with the project.

1 comments

Yeah ok ;-) The programming part itself is a whole different process, including a lot of communication with the customer. It is not really the end of the process in that sense - it's the last process in the big overarching process.
What I meant is just that after programming usually comes feedback, bug fixes, improvements, new features which need to be discussed, spec'd and developed and so on. In the sectors I've worked in (web and enterprise software), programming is part of an iterative process, so if the project is successful, it's not really the end of anything. It can be different in "heavier" sectors with projects that span over several years and that don't change much after the initial release.