Noel Rappin Writes Here

2009/11

The Point of it All

In true blog form, a declarative statement: Hear ye, hear ye! Any so-called Agile team that ever tries to translate “points” into actual units of time is presumed dysfunctional until proven otherwise. You’ve done it, I’ve done it, we’ve all done it. Doesn’t make it a good idea. In the spirit of my last post, allow me to over-explain. A typical Agile project handles estimation by splitting the project up into smallish user stories and assigning each one a point value, typically between one and five, though different teams have different standards.

For Example

Having shifted from editing on the book back to actual writing for a few new chapters, I’m back to obsessing about examples. (The book, of course, is Rails Test Prescriptions coming soonish to a bookstore or computer screen near you. Tell your friends.) I feel like I spend way more time obsessing over whether I’m picking good examples than the question actually merits. Or to put that another way, I’m pretty sure there’s a difference between a good example and a bad example, I’m much less sure there’s a difference between a great example and a good example.

RSpec and Mock Design Question

Here’s a little RSpec design question. As I’ve probably mentioned in various spots, I don’t naturally take to the RSpec massively-mocked style of testing. However, I’m currently on a Rails project that is using that style – unit tests don’t touch the database, functional tests don’t touch the models. It seems to be working for them, they certainly seem to have stuck with it over the course of this rather complex application.



Copyright 2024 Noel Rappin

All opinions and thoughts expressed or shared in this article or post are my own and are independent of and should not be attributed to my current employer, Chime Financial, Inc., or its subsidiaries.