Skip to content

Commit

Permalink
Tweaks to links for week 344
Browse files Browse the repository at this point in the history
  • Loading branch information
floehopper committed Aug 21, 2015
1 parent fecba98 commit 8a4cc01
Showing 1 changed file with 10 additions and 5 deletions.
15 changes: 10 additions & 5 deletions soups/weeknotes/week-344-links.snip.markdown
@@ -1,9 +1,14 @@
Week 344 - Interesting links
============================

###[git_snip](https://github.com/htanata/git_snip)
### [The Language of Modular Design](http://alistapart.com/article/language-of-modular-design)

I haven't tried this out in anger yet, but it's supposed to safely clean up obsolete branches on your Git repository. In particular it's supposed to cope with branches which have been merged on a remote (e.g. GitHub). Apparently it does this by using [`git cherry`](https://www.kernel.org/pub/software/scm/git/docs/git-cherry.html), a useful looking Git command which I hadn't come across before. {by james-mead}
Chatting to [Chris Lowis](http://chrislowis.co.uk) over lunch today reminded me about this excellent article by [Alla](http://www.craftui.com/). She talks a lot about the importance of coming up with good names for UI components and making sure your team has a [common understanding of those names](http://martinfowler.com/bliki/UbiquitousLanguage.html). Great stuff! {by james-mead}


### [git_snip](https://github.com/htanata/git_snip)

I haven't tried this out in anger yet, but it's supposed to safely clean up obsolete branches on your Git repository. In particular it's supposed to cope with branches which have been merged on a remote (e.g. GitHub). Apparently it does this by using [`git cherry`](https://www.kernel.org/pub/software/scm/git/docs/git-cherry.html) (as opposed to [`git cherry-pick`](https://www.kernel.org/pub/software/scm/git/docs/git-cherry-pick.html)), a useful looking Git command which I hadn't come across before. {by james-mead}


### [ActiveSupport::Testing::TimeHelpers](http://api.rubyonrails.org/classes/ActiveSupport/Testing/TimeHelpers.html)
Expand All @@ -13,19 +18,19 @@ I hadn't noticed that these [Timecop](https://github.com/travisjeffery/timecop)-

### [ruby-values-traversals](https://github.com/npryce/ruby-values-traversals)

In this library, [Nat Pryce](http://www.natpryce.com/) has extended the [Values gem](https://github.com/tcrayford/Values) with first-class traversals. He also had a fork of the Values gem in which he'd implemented Haskell-esque Lenses, but that seems to have disappeared now. Anyway, I'd never heard of these things before and so I plan to learn about them. Apparently [this video](https://www.youtube.com/watch?v=cefnmjtAolY) is a good crash course. {by james-mead}
In this library, [Nat Pryce](http://www.natpryce.com/) has extended the [Values gem](https://github.com/tcrayford/Values) with first-class traversals. He also had a fork of the Values gem in which he'd implemented Haskell-esque Lenses, but that seems to have disappeared now. Anyway, I'd never heard of these things before and so I plan to read up about them. Apparently [this video](https://www.youtube.com/watch?v=cefnmjtAolY) is a good crash course. {by james-mead}


### [git-remote-dropbox](https://git.io/dropbox)

> This [Git remote helper](https://www.kernel.org/pub/software/scm/git/docs/gitremote-helpers.html) makes Dropbox act like a *true* Git remote. It maintains all guarantees that are provided by a traditional Git remote while using Dropbox as a backing store. This means that it works correctly even when there are multiple people operating on the repository at once, making it possible to use a Dropbox shared folder as a Git remote for collaboration.
This looks interesting, but I'm not sure what I'd use it for! {by james-mead}
This looks interesting, but I'm not sure what I'd use it for! Maybe backups of my GitHub repositories...? {by james-mead}


### [Deft](https://github.com/npryce/deft/wiki/Quickstart-Guide)

This is an issue tracking tool which stores issues in plain-text files so you can keep them in the same repo as your source code. I've seen it before, but I came across it again, because someone has released a primitive OSX GUI app for it called [Tracksuit](https://github.com/kingsleyh/tracksuit). {by james-mead}
This is an issue tracking tool which stores issues in plain-text files so you can keep them alongside your source code i.e. in the same repo. I've seen it before, but I came across it again, because someone has released a primitive OSX GUI app for it called [Tracksuit](https://github.com/kingsleyh/tracksuit). {by james-mead}


:render_as: Blog
Expand Down

0 comments on commit 8a4cc01

Please sign in to comment.