When I started writing High-Performance Java Persistence, I realized I needed a GitHub repository to host all the test cases I needed for the code snippets in my book, and that’s how the high-performance-java-persistence GitHub repository was born.
The high-performance-java-persistence GitHub repository is a collection of integration tests and utilities so that you can test JDBC, JPA, Hibernate and jOOQ features with the utmost ease.
Continue reading “A beginner’s guide to the high-performance-java-persistence GitHub repository”
The proprietary software shaped the Version Control Systems (VCS) to fit its requirements:
- the project has a strict release schedule
- the team is collocated
- the sprint goals are well-defined and the focus goes to a limited number of stories
- branching is usually reserved for releases or risky development features
- the centralized server is hidden from the outside world
This is the context in which centralized Version Control Systems (e.g. Subversion) have emerged, but that’s not a good fit for open-source projects because:
- releases are not imposed by deadlines
- the contributors may be scattered all over the globe
- new ideas are welcomed, even if radical or time-consuming
- branching becomes mandatory as developers work on features rather than sprints
- the code is available to the whole world
Continue reading “A beginner’s guide to Git feature branches”
I’ve been searching for the most suitable tools I’d use for my book writing process and I’ve settled for Asciidoctor.
In the first place, I decided to use a markup text language that’s implicitly supported by GitHub, and after reviewing Markdown and Asciidoc, I opted for the latter for it offers a richer syntax.
Continue reading “Asciidoctor for collaborative book writing”