Comments for silk and spinach

Comment on initial observations on kanban introduction by Shaquandra

Shaquandra — Tue, 07 Feb 2012 05:40:29 +0000

I like hrbiyds where there are pooled segments chained together e.g. fuzzy-front-end -> engineering -> operations.

Comment on “refactoring” is unhelpful jargon by Nita

Nita — Tue, 07 Feb 2012 02:12:10 +0000

Hello.This post was relaly motivating, especially because I was browsing for thoughts on this subject last Sunday.

Comment on gravity and software adaptability by anonypalm

anonypalm — Thu, 19 Jan 2012 23:37:38 +0000

Thank you, I’ve recently been seeking for facts about this subject for ages and yours is the best I have found so far.

Comment on the saff squeeze by Tests Aren’t Just For Testing: Stop Using The Debugger « Paul Shannon – Agile Software Development

Wed, 18 Jan 2012 22:36:23 +0000

[...] their efforts, and briefly looked at the code, but immideiately thought back to my days spent with Agile Coach Kevin Rutherford. Kevin used to tut disapprovingly every time we started the debugger, suggesting that we were just [...]

Comment on better tester, worse code by My response to A Testers Commitments from James Bach | Duncan Nisbet

My response to A Testers Commitments from James Bach | Duncan Nisbet — Tue, 10 Jan 2012 22:44:29 +0000

[...] own feet. An interesting observation on that point has been made in a post by Kevin Rutherford here My role as a Tester isn’t just to check the software being written by the Programmers (the [...]

Comment on turning requirements into user stories by Stephen

Stephen — Tue, 13 Dec 2011 15:38:56 +0000

This is whole concept of User Stories is nuts – providing ambiguous desriptions of requirements to development and expect them to deliver what the customer wants!! really!! – get real… you must discuss and model the customers requirements and produce a Business Process Diagram (BPD)/ Use Case (high-level at least) and then a flow of events – its been my experience that gaps in functionality and poor customer satisfaction arises from poorly spec’d requirements and leaves you open to scope creap whereby the functional requirements from an users perspective are not met because the user story is not completely fleshed out. User Stories are ONLY useful if considered as a high-level 4-line paragraph that descripts a use case. Modelling BPD’s and Use Cases ensure that the complete end-to-end view of a customers requirement can be met – a small paragraph doesnt achieve this.

Steve

Comment on Don’t inherit code by Saager Mhatre (@dexterous)

Saager Mhatre (@dexterous) — Tue, 11 Oct 2011 22:51:35 +0000

Good ol’ http://c2.com/cgi/wiki?CompositionInsteadOfInheritance ! :)

Comment on hexagonal soup by Conditionals on the edge « silk and spinach

Conditionals on the edge « silk and spinach — Mon, 19 Sep 2011 20:33:16 +0000

[...] code. Most conditionals are duplicates, and the only “genuine” conditionals are at the system boundaries, where they test external state and input information. But I discovered recently that, even at the [...]

Comment on if… by Conditionals on the edge « silk and spinach

Conditionals on the edge « silk and spinach — Mon, 19 Sep 2011 20:33:15 +0000

[...] you know, I have a thing about conditional code. Most conditionals are duplicates, and the only “genuine” conditionals are at the system boundaries, where they test [...]

Comment on the anti-if campaign by Conditionals on the edge « silk and spinach

Conditionals on the edge « silk and spinach — Mon, 19 Sep 2011 20:33:12 +0000

[...] you know, I have a thing about conditional code. Most conditionals are duplicates, and the only “genuine” conditionals are at the [...]

Comment on more on the muda of multi-tasking by Muda 7 Wastes

Muda 7 Wastes — Wed, 14 Sep 2011 14:45:15 +0000

+1 like

Comment on tabular unit tests by Marylada

Marylada — Thu, 01 Sep 2011 14:54:12 +0000

Cheers pal. I do appreciate the wrtinig.

Comment on Faster Rails controller specs by rapindRapin

rapindRapin — Tue, 23 Aug 2011 02:30:33 +0000

Gold. I’ll be using this in one of my projects. Thanks.

Comment on Why I don’t use spork by A Smattering of Selenium #58 « Official Selenium Blog

A Smattering of Selenium #58 « Official Selenium Blog — Mon, 15 Aug 2011 14:50:49 +0000

[...] Why I don’t use spork reminds us that pain is [sometimes] a good thing. [...]

Comment on Why I don’t use spork by Nicolás Sanguinetti (@godfoca)

Nicolás Sanguinetti (@godfoca) — Thu, 11 Aug 2011 03:07:26 +0000

One way to avoid this is to avoid Bundler’s “require by default” and change the line in config/boot.rb from `Bundler.require` to `Bundler.setup`.

Once that is done, only require files/gems as you need them. (At the top of models, controllers, helpers, or in spec/support/whatever)

Obviously when you run `rake` you’ll end up requiring them all anyway (if not you’re doing something wrong :P) so you won’t see gains there, but this will speed up running `rspec spec/some/file.rb:14` *so much* you’ll be happy.

And as a side benefit, since things are lazily loaded in production, the first boot after a deploy will be much faster as well (which is a boon if you use passenger :))