Few things that I adopted, which has helped me to be better developer. To be honest, I forget things quite fast. Journaling becomes more than just a thing to me. Helps me to keep whatever I did on check. Of course, readME files are one of the things that strikes in our mind at first.
What inspired me are the daily scrum calls which are involved when most of us report to our seniors. Here is one typical format:
DAILY STANDUP RECORDS
...
...
...
DAY 5 (31 May 2026)
OBJECTIVE: resolving JIRA-19
WINS:
1) added a props functionality to the interface
2) the prompt given to the LLM has been updated
BLOCKAGES:
1) the LLM still halucinates
This is used for daily scrum. I even keep a track on weekly updates to pick the crux of the sprint I performed for the last 7 days in the following manner:
### Sprint 2: Gateway service designing skeleton (Week 4 - May 2026)
**Jira Epic:**
1) RAG-8 adding loggers and dockerfile def in a gateway
2) RAG-6 sketch system diagrams
**Sprint Summary Wins:**
1) updated cls, package dia of ingestion
2) created activity dia of ingestion
3) updated package dia of gateway
4) logger file and docker file for gateway service has been added
5) dockerfile of gate3way is deployed to dockerhub
**Sprint Summary Blockages:**
1) No blockages found
As the fragment, shown above says JIRA-19, one thing I use for sure is JIRA, especially the scrum dashboard. No issue with using Kanban dashboard. I make sure that appropriate GitHub repo has been integrated to JIRA.
Notice that RAG-6, RAG-3 and so on are termed as JIRA ticket ID or simply ticket ID.
If you hover over the small vertical symbol you can track the committed message and the date when you did. This can be done using a trick called as smart commits, often used in git command.
First you create JIRA task under To Do column after clicking at + CREATE, add a bit of description as well, a unique JIRA ticket ID shall be assigned. The small vertical button wont be visible yet.
To connect to that JIRA task, commit messages need to be framed as followed. But make sure that you stage the changes you did in your workspace using git add command.
git commit -m "RAG-7 #to-do #comment started working on documentation"
This is for local commits. For updating the same to the remote server, where your JIRA account is hosted, git push command needs to be used.
Now you will notice that, that button has appeared. Often due to latency, the button wont be readily visible. Since there is a space between TO DO, a hyphen is added and dont forget # symbol. Internally regex operation is involved where it checks for ticket ID, the status which you are in.
Similary when the task is in progress then
git commit -m "RAG-7 #in-progress #comment docs on loader finished embedding initiated"
The card under To Do shall shift automatically under In Progress.
This helps to visually track my progress.
As as alternative YOUTRACK is also a good option, a product of JetBrains. Whereas, JIRA is a product of Atlassian.
Third is using docker. I really adore the following docker command:
docker run -it --name my-container --mount type=bind,src="$(pwd)",target=/app my-image:latest
it flag is the interactive terminal, my-container is the custom container name, which is optional, mount helps in making changes in your container, which gets reflected back the directory where my project originally is located, this is why pwd is used which stands for print working directory and my-image:latest is the image name. Make sure to create an image at first using docker build command.
docker build -t <image_name> .
'.' includes everything which I stated in my dockerfile, often recommended the avoid cache and virtual env files, to keep it light.
After a few days when you are done with building a particular phase of project, you can deploy the docker image to DockerHub in order to keep a track on which version you are working on.
Right before deployment, make sure a repo is built where the local image will be stored. For checking whether your DockerHub account is connected to your local machine, use:
docker login
If some error occurs related to docker hub account is not connected, just check it out in Google.
For connect to the remote repo using docker tag command:
docker tag my-image:latest rik7/ingestion:v1
here :latest and :v1 are the tags you give, by default if no tag is assigned then :latest is assigned. rik7 is my account username, ingestion is the repo name where v1 is storing the version-1 of the local docker image.
Lastly use docker push command, to save it in remote server where your dockerhub account is hosted.
For testing purpose, I pull the required docker image and use docker run command.
To conclude, this helps me to revise what i did and keep a track on whatever changes I did.
Top comments (0)