Do not sketch Finite State Machines on a first date

Size: px

Start display at page:

Download "Do not sketch Finite State Machines on a first date"

Leonard Wiggins
5 years ago
Views:

1 Previously on Do not sketch Finite State Machines on a first date

2 : Dude, where is my code? Wydział Matematyki i Nauk Informacyjnych Politechnika Warszawska

4 What is a code repository? wikipedia In computer software engineering, revision control is any kind of practice that tracks and provides control over changes to source code. Software developers sometimes use revision control software to maintain documentation and configuration files as well as source code.

5 Do we need repositories? The reasons for code repositories: Code backup Code sharing (inter-team and external) Code organization

6 A brief history of code repositories Centralized client-server Concurrent Versions System (CVS): Apache Subversion (SVN): present day Distributed BitKeeper: present day (license changes during the way) mercurial: present day git: present day

7 git commits are a series of code patches

8 git loves branching

9 git loves branching

10 10 reasons why you might hate git 1 Complex information model (especially for svn users) 2 Crazy command line syntax (eg. git-am - Apply a series of patches from a mailbox) 3 Crappy documentation (eg. git-rebase { Forward-port local commits to the updated upstream head) 4 Information model sprawl 5 Leaky abstraction 6 Power for the maintainer, at the expense of the contributor 7 Unsafe version control 8 Burden of VCS maintainance pushed to contributors 9 Git history is a bunch of lies 10 Simple tasks need so many commands Source:

11 Do we need package repositories? wikipedia Dependency hell is a colloquial term for the frustration of some software users who have installed software packages which have dependencies on specific versions of other software packages.

12 Popular package repositories.net nuget: <PackageReference Include="Newtonsoft.Json" Version="10.0.3" /> Java maven: <dependency> <groupid>org.postgresql</groupid> <artifactid>postgresql</artifactid> <version> jre7</version> </dependency> R CRAN: install.packages("randomforest")

13 Do we need to version applications?

14 Major.Minor.Update.Build notation Major Should be changed when: API contracts are broken, external data model is changed, functions have different effects etc. Minor Should be changed when: new functionality is added, performance is optimized, internal data model changes Update Should be changed when: bugfixing has been performed Build Should be changed automatically with each build (e.g. after code refactoring or new tests have been added)

15 Versions and code repositories A few tips: Single commit should consist of a minimal sensible amount of code resulting in a complete functionality Code in repository should be compilable (some branches may be an exception) Code in develop and master branches must pass tests at all times Every maintained version needs to have its own branch Every stable release needs to be tagged Supporting multiple customers with custom, yet similar, products needs a separate repositories for common and custom features

16 A few case studies

17 A few case studies Consider the following cases: One developer fixes a bug and one developer delivers a new feature (both happen on the same piece of code) You have multiple versions of similar (but not identical) custom products and a bug has been detected in a common functionality

18 Further reading 10-things-i-hate-about-git/ Linus on git: Git For Ages 4 And Up: https: //danielkummer.github.io/git-flow-cheatsheet/

19 Quick survey Who has heard about......solid principles?...design by Contract?...Aspect-oriented Programming?...Redmine, Jira, bugzilla etc.?...unit Tests?

20 Quick survey Who has heard about......solid principles?...design by Contract?...Aspect-oriented Programming?...Redmine, Jira, bugzilla etc.?...unit Tests?

21 Quick survey Who has heard about......solid principles?...design by Contract?...Aspect-oriented Programming?...Redmine, Jira, bugzilla etc.?...unit Tests?

22 Quick survey Who has heard about......solid principles?...design by Contract?...Aspect-oriented Programming?...Redmine, Jira, bugzilla etc.?...unit Tests?

23 Quick survey Who has heard about......solid principles?...design by Contract?...Aspect-oriented Programming?...Redmine, Jira, bugzilla etc.?...unit Tests?

24 Quick survey Who has heard about......solid principles?...design by Contract?...Aspect-oriented Programming?...Redmine, Jira, bugzilla etc.?...unit Tests?

25 Takeaway message Version your code, for your own sake

GIT TUTORIAL. Creative Software Architectures for Collaborative Projects CS 130 Donald J. Patterson

GIT TUTORIAL. Creative Software Architectures for Collaborative Projects CS 130 Donald J. Patterson GIT TUTORIAL Creative Software Architectures for Collaborative Projects CS 130 Donald J. Patterson SCM SOFTWARE CONFIGURATION MANAGEMENT SOURCE CODE MANAGEMENT Generic term for the ability to manage multiple