Sono d'accordo con un'altra risposta , che devi trovare il tempo per scrivere del codice.
Un altro approccio che richiede meno tempo di fila rispetto alla scrittura di un progetto consiste nel fare una serie di catas e metterli su un sito web (o flash drive che porti con te.) I Catas sono brevi e facili da fare. Se trascorri 15-30 minuti al giorno, avrai un sacco di codice in una settimana o due.
How do you get to be a great musician? It helps to know the theory, and to understand the mechanics of your instrument. It helps to have talent. But ultimately, greatness comes from practicing; applying the theory over and over again, using feedback to get better every time.
How do you get to be an All-Star sports person? Obviously fitness and talent help. But the great athletes spend hours and hours every day, practicing.
But in the software industry we take developers trained in the theory and throw them straight in to the deep-end, working on a project. It’s like taking a group of fit kids and telling them that they have four quarters to beat the Redskins (hey, we manage by objectives, right?). In software we do our practicing on the job, and that’s why we make mistakes on the job. We need to find ways of splitting the practice from the profession. We need practice sessions...