When I pick up work after a long weekend, it reminds me what I'm even supposed to be working on now.Writing journal entries like this has a lot of potential benefits: I don't hit all of those points every day, but they're all common things I cover. What tasks I need to prioritize the next day.Problems I ran into, and (hopefully) how I solved them.Conversations with other developers on my team and what topics we covered, or key takeways from discussions outside the team.Tasks I worked on and what specific things I did for those.At the end of every workday, I take 10-15 minutes to write down a few paragraphs covering what I did that day, such as: Tip #1: Keeping a Daily Work Journal □︎Īt the start of 2013, I started keeping a daily work journal. There's a ton of valuable info in there, and it's totally worth the purchase. Note: For a much more extensive set of career advice on many topics, I strongly recommend Shawn Swyx Wang's book The Coding Career Handbook: Guides, Principles, Strategies, and Tactics from Code Newbie to Senior Dev. But, writing them down means I've got somewhere to point people to in the future, and maybe they'll be new to someone who hasn't seen these thoughts before. None of these thoughts are particularly new, and in fact I'll try to link to other resources that say similar things. I've frequently shared some of these thoughts with other developers on my team and various folks I've chatted with online, so it's worth trying to write these down so I can share them more widely. Starting topic: the value of daily notes on work progressĪs I've progressed through my career as a developer, I've learned a bunch of useful things based on my experiences. Although it still doesn't cover every API yet, you can access the basic folder and document management.This is a post in the Coding Career Advice series.įirst in a series of tips on things I've found useful in my career as a dev. DevelopmentĬurrently, we provide the frontend source code only so you cannot host our backend server by yourself.īut you can participate in development via mock backend mode. Then, we will give you more instructions. If you find any interesting issues but their specs are not clear or you don't know how to fix them, please leave a comment on the issues. Some of them might have a small bounty so you can get a cup of coffee from it after hacking. We have left the "help wanted" label to some issues which external contributors could try to resolve. You can write it in General discussion page, external developer community (Dev.to or Reddit) and your blog if you have one.Īlso, you can help other users by answering their questions in here. You can share how you're using our app by writing an article. ![]() There are many ways to help our community. If you have any, please create a discussion in Feature Requests category. To improve the app, we need your idea! It could be a new feature or an improvement for existing features. Read our contributing guide, to learn about our development process, how to propose bugfixes and improvements. If you're interested in our project, you can participate in many different ways. If it is urgent or private, please join our Slack channel and send a direct message to □ Wanna contribute? ![]() ![]() If you find a bug, please create an issue to our GitHub issue tracker. If you don't know how to use the app, please create a discussion on our Q&A discussion page. Boost Note is a document driven project management tool that maximizes remote DevOps team velocity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |