3 ms·
Yup, I think is very common, I'm in a similar position and feel the same way. Partly it feels like a game; filling in holes in knowledge is like locating piece
by RobertKerans 10y ago
Yup, I think is very common, I'm in a similar position and feel the same way. Partly it feels like a game; filling in holes in knowledge is like locating pieces that fill gaps in a jigsaw. And partly it feels like a scrabble up a hill - the more you learn, the more you realise how little you know, so you try to grab more and more knowledge.
And it does lead very often to bad programming, I appreciate the GP point - reinventing wheels, NIH syndrome, overuse of clever techniques etc., but that's not necessarily the case; a big chunk of the knowledge you grasp is [or should be] best practices, testing, clean code etc v0v
- epalmer 10y agoAll good points. I'm not a NIH person so that has never been a problem. But I can be distracted by personal projects and work projects that are optional. I have been focusing my learn at work activity on: - learning the languages I use better - learn the tools better (IDE, etc.) - and improving our software development processes We have a long way to go on software development processes (best practices) because we are 100% self taught team that covers a diverse but not uncommon set of technologies (linux, apache httpd, javascript, jquery, angular, sass, java, bash, php, etc.) and we are always slammed with priorities for senior management of the university. I do love filling in the gaps with learning. Sometimes I find something I learned a long time ago causes something else to fall in place and I think to myself "that is why I needed to learn that". Maybe a bit of serendipity.