stories

RSpec Stories and Specs: When to use what?

So I want to start using RSpec stories, but I am not sure where writing controller, model and view specs fit in. For example, you have the story "Logging in" with "User provides wrong password" scenario, don't you end up testing the same stuff than controller/model specs (response.should render..., user.should be_nil, etc.) So my ques...

I want to read the source code of a real compiler. Suggestions on which & how? Any experiences to share?

In order to continue my dive into reading real code, I'd like to read and understand the source code of an actual in-use compiler. Is there one that you think is particularly well-written, elegant, and perhaps, still relatively small? Any suggestions? Any experiences? Resolution: I've decided to read the Lua source code. I've been bookm...

Scrum-board / Task Board and Color Coding

What would you recommend as far as a good color-coding for use on a Storyboard? Is this a good pattern from your experience? http://maxheapsize.com/static/ScrumBoardCheatSheet.pdf What is the most standard color-coding? ...

How to write stories / scenarios in BDD ( Behavior Driven Design )

I am about to use BDD (Behavior Driven Design) for the first time and am trying to get used to this different way of approaching a problem. Can you give some stories / scenarios that you would write for say a simple login application using BDD? For example, from what I have read, it seems that: “When a user enters an invalid user...

What world-changing programs that just didn't change the world have you tried to write as a newbie?

A recent answer on the topic of compression reminded me of something I did when just getting into the world of computers and programming: I had found out that in QBasic, a long uses 4 bytes of memory, as does a single (float). However, a long can only take on about four billion different values, while a single can have magnitudes of 103...

Is it bad practise to work on multiple stories concurrently?

In a scrum team, how important is it to complete a single story before moving on? Our scrum master is fairly dogmatic about bringing a single story to completion before moving on. I can see that development would appear to be more "controlled" in this scenario, plus the scrum master would have a very accurate picture of what team member...