Git Workflow & Branching – An Aftermath

Git is such a masterpiece tool that programmers use for collaboration work with others. Use it carefully and it will help you very much. Careful you not will trigger a wildfire in the codes. In our implementation of git workflow and branching, we have faced some problems. Actually, I don’t know what to write, so let’s just pretend this is a serious problem.

btw, Git 2.13.0 just released by our Savior, Torvalds
Continue reading “Git Workflow & Branching – An Aftermath”


Connect to the Data

When developing an applications, developers need a way to save modify and query the data. The application may use the a database management system (DBMS) to store the data but how to modify and retrieve data in the DBMS? DBMS has a set of raw commands to run operations on the system, for example SQL commands. We could use it in raw but it will make the codes look dirty.

Continue reading “Connect to the Data”

Changes to Integrate

Collaborative coding, you code and submit your code to your “branch”, but there must be a time when you need to integrate your code with other programmers’ code. Git is one tool that can make life easier, by providing seamless ways to join codes.

Wait… there are more than one ways to do that? Yeah, for joining codes git has command merge and rebase. In git experiences, programmers must have been used merge before, but what rebase really is? Continue reading “Changes to Integrate”

Write Tests First, Write Code Second

Our group project, “Phrogress” relies heavily in phabricator data. These data can be retrieved by using phabricator conduit API. To make things simpler, we would like to implement our own API wrapper to encapsulate conduit API. The wrapper will be implemented using Ruby on Rails (RoR) and placed on backend side, connecting frontend side of our application to phabricator data.

To ensure the correctness of our own endpoints, unit test is required throughout every aspect of the API wrapper. Moreover, TDD (Test Driven Development) is a mandatory for all groups in PPL class.

Continue reading “Write Tests First, Write Code Second”