Computing Reviews
Today's Issue Hot Topics Search Browse Recommended My Account Log In
Review Help
Search
Git recipes : a problem-solution approach
Gajda W., Apress, New York, NY, 2013. 420 pp. Type: Book (978-1-430261-03-2)
Date Reviewed: May 13 2015

All software developers need to know about code subversion. As an instructor in software engineering this year, I have been trying to teach students that software is very much a team effort, where work is distributed and efficiently managed in order to deliver the product on time to the clients.

Subversion plays a key role here. In a team where you have multiple developers, each implementing separate classes, it would be cumbersome and time consuming if the programmers had to work on only one computer or transfer files to each other via email. Subversion allows programmers to “check in” code from their respective computers, regardless of where they are physically located. This effectively allows multiple developers from around the world to work together on the same projects.

Git has been revolutionary in code development and software engineering practices. It allows developers to post their code online and form teams to allow multiple developers to work together. However, this process could be confusing for a newbie coming to grips with what each term and command does.

This book acts as an excellent guide for any new software developer entering the scene. It discusses the common terminology, what repositories are, and how one can set up his or her own repos for use. Subversion allows files to be managed efficiently, with a logging history documenting changes made to them and creating branches.

Detailed recipes are provided on each of these topics. The book is great in that it gives example code on installation guides for Git on various platforms, showing how code can be pushed or checked in, merged, or managed. It provides details of what each input is going to do in terms of the project.

After covering the basics, the book covers more complex examples in detail, such as tracking and modifying branches, resolving conflicts in files (if multiple users have pushed the same file on the server, for example), and how projects can be manually managed via the command line or the Git web portals to view changes.

I found the book a necessary starting point for students and developers and will be adding it to my recommended textbooks for the software engineering course starting next year.

More reviews about this item: Amazon

Reviewer:  Mariam Kiran Review #: CR143438 (1508-0656)
Bookmark and Share
  Featured Reviewer  
 
Version Control (D.2.7 ... )
 
Would you recommend this review?
yes
no
Other reviews under "Version Control": Date
Distributed version management for read-only actions
Weihl W. IEEE Transactions on Software Engineering 13(1): 55-64, 1987. Type: Article
Jan 1 1988
RCS--a system for version control
Tichy W. (ed) Software--Practice & Experience 15(7): 637-654, 1985. Type: Article
Apr 1 1986
Version control and separate compilation in Ada
Dausmann M.  Ada-components: libraries and tools (, Stockholm, Sweden, May 26-28, 1987)1701987. Type: Proceedings
Jan 1 1989
more...

E-Mail This Printer-Friendly
Send Your Comments
Contact Us
Reproduction in whole or in part without permission is prohibited.   Copyright 1999-2024 ThinkLoud®
Terms of Use
| Privacy Policy