I build (quickly, usually always hardcoded stuff) it and show to user. Before I start coding something, I start with paper and pen and find a user. I eventually learned (the hard way) to start getting users from day 1. People like their specialised GUI -) Org-mode/MD just doesn't do it for a lot of people. I've not really lured anybody away from Trello, though. However, in doing that, your master branch has a TODO file for every branch that it in active development, so it's not really that bad. The only real downside that I've found is that if you want to take the TODO items out of the master branch when you are working on them, it requires another commit to master, which is unfortunate. I've mostly done it just for myself, but have occasionally tried it with 1 or 2 other people. This will cause occasional merge conflicts, but since you should probably inspect the priority of close items, it's not really a problem. You work on that TODO and when you are finished with the branch, you move any not-DONE items into the main TODO file. You move the TODO items that you are going to do into the new file (and add extra details). When you open up a new branch, you create a new TODO file named after the branch in the TODO directory. For example, you have a main TODO that has the general things you want to do. I've been experimenting with a TODO for every branch and then merging the TODO into the main TODO when you merge to master. Restore active, reader-mode, or pinned tab as fully loaded tab, no lazily loading for them. #BUG Error when a pinned tab is restored with the 'discarded' flag set, for lazily loading. #BUG All the dialogs are not showing, due to the missing custom components in the distribution package. #FEATURE Package the custom Web Components with the addon distribution. ** TODO #FEATURE session push to remote devices. ** WORKING Add light theme, dark theme, and default theme. ** WORKING #FEATURE dark theme mode support. ** DONE #BUG cancelled dialog causes double event firings on the next dialog action. ** DONE Add command "Optimize Tab Favicon" on the Utilities tab in Preferences. ** DONE Filter out Export Panel page when doing session snapshot. It's pretty simple.īelow is a sample from one of my side projects (solo dev). When canceling a todo, record the reason, so in case if it comes up again, you have a record of decision. The order of the todo items is the priority. The Todo section manages the current tasks and the Release section captures the history.Īdd new feature or ideas to the end of the todo list. The done features are moved under the Feature list and other done items are moved under the Changes list. A release has two lists: Feature and Changes. When a release is made, the done items are moved to the Release section. Todo's have a life cycle of TODO/WORKING/DONE/CANCELED. The Todo section has the todo items some are marked as #feature for high level functionality and as #bug for bugs. I use an org-mode text file for simple project management. Wondering what will be the next one I'll use after Clubhouse. It's just my personal taste and experience of the last ~ 10 years of software development and project management (am a Product Owner in a software company). Note that I have no affiliation of any kind with any of theses software. The software seems really progressing well and the UX is polished and well thought. Their support team is on Slack and reactive to feedback. But with Clubhouse am using Iteration to define the big picture and the planning of the upcoming weeks and it just works great. It was always hard to keep the big picture while going into details with theses software. None were as simple to use and clean as clubhouse. Asana, JIRA, Trello were all tested alone and with small or medium sized teams. Since developers are rarely in a situation to determine that for themselves, you have to become comfortable again with asking for feedback.Īs many other have suggested, I found ClubHouse to be the best balance for solo dev. At that point, your objective is not merely compliance with the spec (if there even is one) but that the code solves the problem as intended. Maturing to the next stage requires that you be comfortable working in situations where the requirements are not clear or set in stone. Part of maturing out of that initial stage comes from when you can autonomously take a well defined task, break it down into steps, and execute it. If QA found no bugs, then it's good.Įven when things really are that clear cut, junior developers still often need a lot of feedback that they are on the right track. A lot of devs that I have worked with (and this includes me at times) come with the expectation that they will be handed a task with a list of requirements, and all they have to do is check off the boxes and turn in the code. This is really good advice even if you are not a solo dev.
0 Comments
Leave a Reply. |