Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Week 5 Challenge 4 Review #1

Open
celeen opened this issue May 4, 2014 · 0 comments
Open

Week 5 Challenge 4 Review #1

celeen opened this issue May 4, 2014 · 0 comments

Comments

@celeen
Copy link

celeen commented May 4, 2014

Hey Josh,

Your code is super succinct, and I love that. I would say that maybe the final commit is too succinct, though. It took me just a little bit longer to understand what was going on here without any driver tests.

Also, just two other small things. If you wanted to, you could be more specific about what exactly the source variable represents. Yeah, it's a source, but is it a board_array? Is it a boggle_board? Variable names is often a matter of preference; in simple exercises like this one, I often find it helpful to me to name my variables after the pieces of data they represent (array, hash, number, etc...) but I know our review guidelines specify that variables should be more specific to their context in the program than that.

The reason I ask is because, I started wondering, as I was looking at your code, in the #row method, why you have #to_a after getting the row. Isn't that row already an array?

But that's it. This seemed like a suspiciously simple exercise to me, and what you came up with looks really DRY and ultimately, easy enough to understand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant