pgAdmin vs. Sourcetree

We use pgAdmin to develop and test database schemas, write and debug SQL queries. The debugging and profiling tools are particularly useful in this context Instead for applications requiring real-time data processing and minimal latency, pgAdmin might not be suitable due to its potential performance limitations. Idem with large database

Incentivized

I prefer to work visually and use the tool for merge and rebase operations. It helps when managing a large number of repos.

Incentivized

• interface user friendly
• export query result in mani format (xls,csv)
• fast

Incentivized

• Allows to manage GIT repositories in an intuitive and simple user interface
• Visually represents complicated workflows and branching
• Integrates with most well known GIT repository managing services

Incentivized

• Connection profile can be improved
• With large Database can result too slow

Incentivized

• Refreshing of the interface after a commit or merge
• All elements being consistent with the repo status
• Select all button on Trach status on different branches

Incentivized

Interface is almost user friendly and can be improve on connection management

Incentivized

We help new users onboard quickly and then use Sourcetree to handle their day-to-day SCM needs for managing CIs (Configuration Items). We can visually show management the branching and commit history to show the flow and pace of development.

Incentivized

I tried GitHub Desktop for a couple of days, but it is just not visual enough for me. It has no graph display for branches. Too much clicking is required to get info that the Sourcetree UI shows by default. Sourcetree gives you that "Big Picture" dashboard. GitHub Desktop seems unfinished to me due to its lack of this overview screen.

Incentivized

• query tool to go inside log and search for unauthorized access
• view in real time statistics data growth

Incentivized

• In my experience, using Sourcetree actually slows down development if you're the average developer needing to do simple git actions. Getting set up is fast, but the learning curve to use the tool is just too steep if you're just looking to push, pull, commit, branch etc.
• Sourcetree is not implemented by default at our company, but is recommended as we primarily use Atlassian products. However the lack of integration with other Atlassian products means that this git GUI doesn't give any more or less ROI for your Atlassian ecosystem compared to another git GUI tool.
• For auditing and exploring history Sourcetree can be very helpful. Having all of this information in one place with a plethora of actions and tools at your disposal means you can audit repos much quicker than any other git GUI or online repo explorer.

Incentivized