Working with Multiple Versions of Websites (Git)
I have a main template like website I have made that will allow me to quickly roll out and make new websites on demand when I need them, for my personal use.
Simple task framework – building software from reusable pieces
I’m writing a web service with several APIs, and they will be sharing some of the implementation code. In order not to copy-paste, I would like to ideally implement each API call as a series of tasks, which are executed in a sequence determined by the business logic.
Simple task framework – building software from reusable pieces
I’m writing a web service with several APIs, and they will be sharing some of the implementation code. In order not to copy-paste, I would like to ideally implement each API call as a series of tasks, which are executed in a sequence determined by the business logic.
Simple task framework – building software from reusable pieces
I’m writing a web service with several APIs, and they will be sharing some of the implementation code. In order not to copy-paste, I would like to ideally implement each API call as a series of tasks, which are executed in a sequence determined by the business logic.
Simple task framework – building software from reusable pieces
I’m writing a web service with several APIs, and they will be sharing some of the implementation code. In order not to copy-paste, I would like to ideally implement each API call as a series of tasks, which are executed in a sequence determined by the business logic.
Simple task framework – building software from reusable pieces
I’m writing a web service with several APIs, and they will be sharing some of the implementation code. In order not to copy-paste, I would like to ideally implement each API call as a series of tasks, which are executed in a sequence determined by the business logic.
TDD and Version Control
I am currently learning about TDD and trying to put it into practice in my personal projects. I have also used version control extensively on many of these projects. I am interested in the interplay of these two tools in a typical work flow, especially when it comes to the maxim to keep commits small. Here are some examples that come to mind:
Feature code + infrastructure code – how to structure the commits / JIRA issues?
Say that you work on a feature described by a single JIRA ticket and during the work, you:
Feature code + infrastructure code – how to structure the commits / JIRA issues?
Say that you work on a feature described by a single JIRA ticket and during the work, you:
Feature code + infrastructure code – how to structure the commits / JIRA issues?
Say that you work on a feature described by a single JIRA ticket and during the work, you: