This short presentation was a 20 minute talk for Barcamp 4 in Ghent (2011). The talk is about how to work better with GIT. Some tips and tricks and must-do's for people who already use git
How many times a day do you switch from mouse to keyboard and viceversa? Do you still use BASH? Are you taking advantage of GIT or is GIT fooling you daily? In this talk I’ll show your how to dramatically boost your productivity just by enhancing your development toolset. You will learn many OSX tweaks that get rid of stupid-proof features and give you an extra performance boost, alternative shells that will aid you and enrich your experience when working with the console, application launchers/window managers that will make you forget about your mouse and, finally, how to automate many of your GIT/GitHub development workflows.
The talk is primarely focused on the development of Rails apps on OSX but many of the tricks are also applicable to other OSes and languages.
"Infrastructure as Data" by Nick Lewis, Software Developer, Puppet Labs.
Presentation Overview: We all know the benefits of infrastructure as code - version control, reusability, shareability, documentation, and so on. Another popular notion is that of code as data, by which code can be introspected, modified, and used for decision making. Combining the two ideas, the natural implication is that infrastructure is also data, and can be similarly introspected, modified, and used for decision making. In other words, we can do math on infrastructure. We'll look at some interesting ways this data can be filtered, combined, and applied to achieve results which would be difficult to describe directly in code.
Speaker Bio: Nick Lewis is a software developer at Puppet Labs and one of the co-authors of PuppetDB.
This short presentation was a 20 minute talk for Barcamp 4 in Ghent (2011). The talk is about how to work better with GIT. Some tips and tricks and must-do's for people who already use git
How many times a day do you switch from mouse to keyboard and viceversa? Do you still use BASH? Are you taking advantage of GIT or is GIT fooling you daily? In this talk I’ll show your how to dramatically boost your productivity just by enhancing your development toolset. You will learn many OSX tweaks that get rid of stupid-proof features and give you an extra performance boost, alternative shells that will aid you and enrich your experience when working with the console, application launchers/window managers that will make you forget about your mouse and, finally, how to automate many of your GIT/GitHub development workflows.
The talk is primarely focused on the development of Rails apps on OSX but many of the tricks are also applicable to other OSes and languages.
"Infrastructure as Data" by Nick Lewis, Software Developer, Puppet Labs.
Presentation Overview: We all know the benefits of infrastructure as code - version control, reusability, shareability, documentation, and so on. Another popular notion is that of code as data, by which code can be introspected, modified, and used for decision making. Combining the two ideas, the natural implication is that infrastructure is also data, and can be similarly introspected, modified, and used for decision making. In other words, we can do math on infrastructure. We'll look at some interesting ways this data can be filtered, combined, and applied to achieve results which would be difficult to describe directly in code.
Speaker Bio: Nick Lewis is a software developer at Puppet Labs and one of the co-authors of PuppetDB.
Aligning Continuous Integration Deployment: Automated Validation of OpenStack...Atlassian
Ever think to yourself...how can my team automate the processes for my complex system? How does Continuous integration and Continuous Deployment fit in? In this talk by Teyo and Dan you will dive into world of automation using Puppet and OpenStack. Start off with brief overview of Puppet and OpenStack, then dive into examples of how you model complex deployments of OpenStack using Puppet.
Introduction to PCA, the underlying math and some applications. Understanding of basic linear algebra is assumed. For the original HTML5 deck please go to http://benmabey.com/presentations/pca-tutorial/
Git en el mundo real . 17/nov/2015
En el grupo de usuarios de Git se ha hablado mucho del uso de Git y pocas veces de cómo se ha implantado en diferentes empresas; en esta charla, ha llegado el momento de estudiar tres casos distintos.
En esta presentación contamos cómo hemos evolucionado en Acilia en nuestro uso de esta plataforma:
- evolución,
- adquisición de comprimisos: git-hooks,
- caso de uso: sincronización de la BDD con Git
Ponentes: Ángel Roldán y David Pordomingo.
Enlace a la descripción de la charla:
http://www.meetup.com/es/Spanish-Git-Meetup/events/226300816
Web development, from git flow to github flowCaesar Chi
software development, website development, we move develope way from git flow to github flow.
what is github flow's advantage and who we change it, check it out.
Aligning Continuous Integration Deployment: Automated Validation of OpenStack...Atlassian
Ever think to yourself...how can my team automate the processes for my complex system? How does Continuous integration and Continuous Deployment fit in? In this talk by Teyo and Dan you will dive into world of automation using Puppet and OpenStack. Start off with brief overview of Puppet and OpenStack, then dive into examples of how you model complex deployments of OpenStack using Puppet.
Introduction to PCA, the underlying math and some applications. Understanding of basic linear algebra is assumed. For the original HTML5 deck please go to http://benmabey.com/presentations/pca-tutorial/
Git en el mundo real . 17/nov/2015
En el grupo de usuarios de Git se ha hablado mucho del uso de Git y pocas veces de cómo se ha implantado en diferentes empresas; en esta charla, ha llegado el momento de estudiar tres casos distintos.
En esta presentación contamos cómo hemos evolucionado en Acilia en nuestro uso de esta plataforma:
- evolución,
- adquisición de comprimisos: git-hooks,
- caso de uso: sincronización de la BDD con Git
Ponentes: Ángel Roldán y David Pordomingo.
Enlace a la descripción de la charla:
http://www.meetup.com/es/Spanish-Git-Meetup/events/226300816
Web development, from git flow to github flowCaesar Chi
software development, website development, we move develope way from git flow to github flow.
what is github flow's advantage and who we change it, check it out.
Short talk about Git best practices I held during a Lunch&Learn in our Milan office @Gild.
The session was interactive with lots of examples.
AGENDA:
- Using aliases for git commands
- Stats: my most used commands
- Useful list of git aliases
- Work scenarios
"Puppet at GitHub / ChatOps" from PuppetConf 2012, by Jesse Newland
Video of "Puppet at GitHub": http://bit.ly/WVS3vQ
Learn more about Puppet: http://bit.ly/QQoAP1
Abstract: Ops at GitHub has a unique challenge - keeping up with the rabid pace of features and products that the GitHub team develops. In this talk, we'll focus on tools and techniques we use to rapidly and confidently ship infrastructure changes/features with Puppet using Puppet-Rspec, CI, Puppet-Lint, branch puppet deploys, and Hubot.
Speaker Bio: Jesse Newland does Ops at GitHub. His favorite hobby is SPOF wack-a-mole, followed closely by guitar and piano. Prior to GitHub, Jesse was the CTO at Rails Machine where he ran a large private cloud and managed several hundred production Ruby on Rails applications using Puppet. To the delight and/or chagrin of the Puppet community, Jesse is to blame for Moonshine, the Ruby DSL for Puppet before Puppet had a Ruby DSL.
Working with Git – a simple introduction for those used to working with a VCS like Subversion. Explains concepts and shows examples. Feel free to steal slides for your own purposes.
This introduction to Clojure was given to the Utah Java Users Group Aug. 15. It's main focus was on Clojure's time model and how the design of Clojure separates (decomplects) many concepts which are all implemented onto of Objects in Java, and other OO languages. This is the abstract for the original talk:
Tony Hoare famously said "There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." Clojure is a functional Lisp that targets, among other platforms, the JVM and strives to enable the former approach to building software.
In its pursuit of simplicity Clojure encourages the use of pure functions, sequence abstractions which allow for lazy and parallel processing of data, persistent (immutable) data structures, and a novel way of dealing with state as a succession of values. While these concepts may sound intimidating for those unfamiliar with functional programming, they are actually less complicated than many programming constructs that programmers use everyday.
This talk will cover these concepts and the motivation behind them. You will learn the basics of Clojure programming and will be given a taste of what developing an application in Clojure is like.
Describes Outside-In development and Behvaiour Driven Development. Illustrates basic Cucumber usage within a Rails app and then goes over more advanced topics such as JS as web services.
Cucumber is a BDD tool that aids in outside-in development by executing plain-text features/stories as automated acceptance tests. Written in conjunction with the stakeholder, these Cucumber “features” clearly articulate business value and also serve as a practical guide throughout the development process: by explicitly outlining the expected outcomes of various scenarios developers know both where to begin and when they are finished. I will present the basic usage of Cucumber, primarily in the context of web applications, which will include a survey of the common tools used for simulated and automated browser-testing. Common questions and pitfalls that arise will also be discussed.
Disconnecting the Database with ActiveRecordBen Mabey
Short presentation about how I use NullDB in my ActiveRecord projects. I generally use this approach on projects that I know will be large and will merit the tradeoffs that come with disconnecting the database. I will typically use Cucumber when taking this approach as well.
3. $ gem install github
Tuesday, September 14, 2010
Lots of nice shortcuts... Like browse, pull, etc.. Also, look at the ‘hub’ CLI tool.
4. $ gem install gitty
http://github.com/timcharper/gitty
Tuesday, September 14, 2010
Gitty allows you to share local hooks in your git repo. One really useful one we always use is one that always updates the submodules after you
checkout a new ref. We also use it to prevent evil whitespace from entering a project. :)
5. ash
th B ion!
Wi et
Co mpl
$ brew install git-flow
http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/
Tuesday, September 14, 2010
7. $ git flow feature start super-duper
Summary of actions:
- A new branch 'feature/super-duper' was created, based on 'sprint'
- You are now on branch 'feature/super-duper'
Now, start committing on your feature. When done, use:
git flow feature finish super-duper
$
Tuesday, September 14, 2010
8. Based on development branch
$ git flow feature start super-duper
Summary of actions:
- A new branch 'feature/super-duper' was created, based on 'sprint'
- You are now on branch 'feature/super-duper'
Now, start committing on your feature. When done, use:
git flow feature finish super-duper
$
Tuesday, September 14, 2010
9. Pivotal Tracker Hook
$ git commit -m “[#12345678] WIP ...”
Tuesday, September 14, 2010
To automatically finish a story by using a commit message, include "fixed", "completed" or "finished" in the square brackets in addition to the story ID. You may also use different cases or forms of these verbs,
such as "Fix" or "FIXES", and they may appear before or after the story ID. Note: For features, this will put the story in the 'finished' state. For chores, it will put the story in the 'accepted' state
10. $ git flow feature
checkout diff finish list
publish pull rebase start
track
Tuesday, September 14, 2010
See, I told you it had bash completion.
11. $ git flow publish super-duper
Tuesday, September 14, 2010
14. $ tig
2010-09-10 16:26 Ben Mabey + [feature/404-super-duper]
removes blah method in favor of foo
2010-09-10 16:25 Ben Mabey * adds blah blah
2010-09-10 16:18 Ben Mabey * [origin/feature/super-duper]
removes dead TODO file- not using anymore
2010-09-10 16:17 Ben Mabey * WIP
2010-09-10 12:06 Ben Mabey * [origin/sprint] [sprint] commit
where branch started from
Tuesday, September 14, 2010
16. $ git flow feature rebase
Will try to rebase 'super-duper'...
Current branch feature/super-duper is up
to date.
Not interactive! Need to squash WIP commits.
Tuesday, September 14, 2010
17. $ git rebase origin/sprint --interactive
(-i)
Tuesday, September 14, 2010
18. pick 5e78cef WIP
pick 3165c4d removes dead TODO file- not using anymore
pick 24e7bff adds blah blah
pick 162133d removes blah method in favor of foo
Want to get rid of WIPs and false starts...
Tuesday, September 14, 2010
19. pick 5e78cef WIP
s 24e7bff adds blah blah
s 162133d removes blah method in favor of foo
pick 3165c4d removes dead TODO file- not using anymore
Tuesday, September 14, 2010
20. $ git rebase b4472f60 -i
Protip: rebasing locally before can prevent pain
Tuesday, September 14, 2010
21. Pivotal Tracker Hook
$ git commit -m “[Fixes #12345678] ...”
Tuesday, September 14, 2010
To automatically finish a story by using a commit message, include "fixed", "completed" or "finished" in the square brackets in addition to the story ID. You may also use different
cases or forms of these verbs, such as "Fix" or "FIXES", and they may appear before or after the story ID. Note: For features, this will put the story in the 'finished' state. For
chores, it will put the story in the 'accepted' state
22. $ git flow publish super-duper
Tuesday, September 14, 2010