Looking back on 2019 - 7 Lessons Learnt
Tags: webdev, productivity, writing
Published: 2020-01-02 12:14:29

Cross post from [tcollins.dev](https://www.tcollins.dev)

### 1. Learning shouldn’t always be about your job
In the past, I’ve always tailored my learning outside of work to what is relevant to my current work projects. I feel an important part of being a developer is to keep the passion for learning alive. For me, recently, that has meant stepping outside my comfort zone of Front End Development. This year I’ve spent time learning design principals, how to set up a web server on a VPS, and doing some writing. Of course, these do broadly relate to my field. They compliment my current skills and have the potential to open doors to other areas. 

I believe continuous learning is more important than the subject matter you study. Keeping variety in my learning has helped me stay interested and motivated.

![Alt Text](https://thepracticaldev.s3.amazonaws.com/i/tmhgivnjznq3hadd0t36.png)

### 2. We should all ask more questions
If you are a Junior Developer, ask more questions. Learn as much as you can in this early part of your career. Know that imposter syndrome happens to all of us. Every developer starts off in your very position.

If you are a Senior Developer, ask more questions. You may not know as much as you think and you can always learn more. Challenge your assumptions and learn from your team.

If you are a Jedi Developer/Coding Savant, ask more questions. This will encourage more junior members to ask more questions. Discussions you start will help you, and others around you, learn.

### 3. Writing good code is only part of it
Clean performant code is only one piece of the puzzle. A huge part of successfully writing software is coordinating people. Having a great process around how you develop and deploy software is crucial. Motivating a team of developers will impact code quality. Organizing and coordinating a group of developers to write code in a scalable way is the cornerstone of the entire process.

### 4. Statically generated web pages are a great option
Static site generators are a game-changer. Frameworks like Gatsby, Hugo and Jekyll allow the advantage of automating the generation of pages without the overhead for a web server. There is often a need to have dynamic data that does not continually change, but changes according to some semi-regular event such as a blog post or a product launch. For these, statically generated pages are ideal.

![Alt Text](https://thepracticaldev.s3.amazonaws.com/i/pjamx290s7ijeg0qs0il.jpeg)

### 6. Writing takes much longer than I expected 
Planning, researching, and writing articles take far longer than I expected. As soon as I sit down to write an article, I see where the holes in my knowledge lie. This invariably leads to further research and diving down rabbit holes. Not being a natural writer, the proofreading and various drafts are somewhat onerous. Next year, I’m going to try to work on a few articles at once, in different stages, in an attempt to increase the cadence of new articles.

### 7. Use apps to boost my productivity
This year I’ve started using Notion and Bear for note-taking and todos, Insomnia for testing API endpoints, and Grammarly to bolster my writing skills.