|
|
|
|
|
by johannesboyne
4107 days ago
|
|
It is a difficult question, and actually not quite clear in what context you want to gain speed. Is it the pure coding or is it the development of solutions? I'll go for the later ;) Structure your work and try to develop a strategy. So think about (w)hat, (w)hy, ho(w), (w)here, (w)hen.
- What: What is the core problem to solve?
- Why: If it is a 'problem', why is it a problem, is there an existing solution? If not, why is the feature important - empathize with the feature request.
- How: What is your strategy, how do you want to conquer this task?
- Where: Where does the solution has to be implemented to fit best?
- When: Programming is a process (a timely and logical sequence of activities which are required), thus define what step has to be done before the next. Example: one should not start with the development of a "user scores database" if the main objective is to build a jump-and-run game. These steps are helping myself to be more productive. |
|