If you work on multiple projects, you’re probably familiar with the returning questions you keep asking yourself when picking up where you left. 🤦
If you’re doing client work and changes have to be made to a project, the same questions can pop up:
- What did I or my colleague did again the last time?
- What was the workflow of this project again?
- What is the fastest way to get up and running again?
Last time the ship has been left ⚓️
The first question is probably simple. I think most of us are using Git these days, so then it might be just a matter of pulling in or fetching the latest version of the project. If you (or your team/company) are having conventions about the commit messages, it should be directly visible what the latest commits did. Otherwise you have to manually check the files to see what’s going on.
For people who don’t use Git, I really recommend using it but I’m also curious how you’re doing this (let me know in the comments).
This might be a bit more difficult. If your projects are all of the same type (websites e.g.), it would be most efficient to always work with the same structure and conventions. But from my own experience, sometimes if you start a new project you want to apply things you’ve learned in the past. Maybe a new framework you’ve been learning lately, or another Design Principle you want to apply; the way you look at things change over time.
“Older” projects might become very huge and complex and restructure or refactor might take a huge amount of time that’s not there or it’s simply not necessary.
I’m still looking for a way to gain quick insight in a ‘project specific workflow’. I’m going to focus on this thing the upcoming months. So if you have a way to quick gain the insight for yourself, maybe a tool or special way of thinking, let me know in the comments.
Fast take off 🚀
Sometimes (easy) changes have to be made in a project. You just want to start ASAP. But, (scenario:) unfortunately you’re not running the latest versions or even haven’t the project on your local machine. You need to clone the project, set your local environment, install all dependencies and then you’re (hopefully) up and running.
For more complex projects you maybe have to do even more, for example run specific commands.
I’ve been struggling with this multiple times. Every time I pick up a older project, it’s the same old story: why can’t I take off faster? I just want to push a button and start working right away.
I discussed this with a couple of (nerd) friends. They also have been struggling with this, but also created their own habits. One just saved commands who are difficult to remember in a Note file on his Mac.
We started thinking about this and came to the conclusion there’s nothing out there which organises commands. So we started building this tool called Terminaid (in beta right now) that should do this exact thing. You can create your own ‘bundled commands’ called recipes. For now the commands are public, so you can look into all commands people are adding to the tool. You can bookmark or fork them to make changes that will work for you. In the pipeline we have a native version so you can *for real* push the button and let the recipe do the work. The potential of this can been seen in a wider perspective:
- Add all projects in Terminaid
- Add bundled commands in recipes per project
- Click the recipe you want and the project is in the state you want
- Easy and fast workflow
For big companies:
- Add specific users/developers to specific teams or projects
- Make it easy to switch projects for your developers
- Get new developers up and running very fast
- Time efficient