villeez
Softagram is located on https://softagram.com
Please share you feedback and experiences.
Shell scripts and Python based automations are good to perform repetitive tasks. Python 3 is everywhere and easily installable, which makes it a good base for writing automations.
Cron helps ensuring the automations are executed on time. This is nice for some backup activities.
Automator (on OSX) is a good tool to connect key events to your automations.
"Say" (the shell command to perform text-to-speech synthesis) is nice way to stay up-to-date on the executions.
I also utilize macro capabilities of editors when working with larger data files.
The trend is that the existing tools are continuously being made more and more powerful which also reduces the need for extra scripting on top of them.
Finally, I'd like to mention that the company I work for, Softagram, https://softagram.com is also offering a tool to boost productivity when working with larger or more risky code changes. The tool automates dependency/risk analysis and offers the output in nicely integrated visual report right to the comment field of pull request in GitHub, GitLab, etc. systems.
Would visual diff for dependencies make sense?
Visual diff is useful for seeing text changes in code files and resources. But for the architecture level, what do you think would it make sense to see how dependencies have evolved?Example case in my mind is especially situation where new connections (dependencies) have been made to bind two classes together (e.g. association), and some other dependencies cut away. Usually this sort of...
Visualization of the changes is based on a webhook triggered code analysis, comparison and visualization pipeline. The idea is to make pull request more reviewable by showing the context of the change in just few seconds. Also any new dependencies (that might screw your current design) are shown. It supports multiple repositories making it suitable for large projects.
With last one year we have had major transformation to better integrate Softagram into pull requests (of Azure, Github and Bitbucket) and merge requests (of GitLab). This is to make it easily utilized within the current developer workflows.
The major challenges is to make pull request code change visualization very understandable while keeping it also sufficiently detailed to have it useful. There is an additional detailed dependency visualization that will pop up below the main visualization if your code changes are larger.
We would really love to get feedback on if it helps you and if it provides the report fast enough, and generally if this approach is something that you like or not.