New answers tagged

0

There's nothing wrong with sitting down, thinking about what you will need, developing the API for this, then developing the GUI to consume that API. If you find your API is deficient whilst developing then you didn't think about the overall system well enough. You could go back to the API and add the missing bit and then return where you were in the GUI ...


-1

I don't think that one can accurately predict how much you can save on development time by hiring another programmer, except that there are going to be /some/ time savings - people simply differ too much. You can try a guess by asking a potential hire about the time it took him to complete a project (and what 'complete' meant for them), and compare that to ...


7

Not only is it hard to say, but the answer is not very useful. Even highly experienced developers find it difficult to estimate how long a given project will take them. This is largely because the programming process consists mainly of understanding the problem fully, and elaborating a solution. The hard part is the full understanding. Writing the ...


0

The real issue seems to be I'm too easily distracted at my computer. This is something you are going to have to learn to overcome as outside of the university course you won't have the liberty to dictate to a drone programmer. There are ways of forcing this by blocking (eg in the hosts file) sites you find distracting, other ways of working such as the ...


0

"and not go into tedious detail" sounds like a peasant worker doing all the hard work while the boss stands back and directs. If tedious detail is getting in the way of coding, you need to stop coding and start designing first. This is how we used to do it - sit down and think about what you want to do before you start doing it. Use paper, storyboards, ...



Top 50 recent answers are included