Josh Goebel

Yeah, that would have been my guess. :)

> providing the stubs "gave the game away". I feel like I didn't include stubs where the stubs were the whole exercise... (resistor enums, etc)... but most of the time...

> I can't say I recall the lack of forward declarations for some exercises to have been much of a problem for myself or others I can only say I...

> I think it has to be to be inconsistent We're overloading the word. _It can be both._ It could be consistent _period_ (always the same) or a consistent policy...

> Perhaps the declarations for some exercises could be put in the Hints section. That's a reasonable compromise I think.

> there is some discussion that should probably come up with the public method being introduced Agreed. With a local variable instead: ```ruby class Raindrops FACTOR_TO_SOUND = { 3 =>...

> make: *** [makefile:22: test] Segmentation fault (core dumped) I saw this **often** when trying to get started the C track online. So much so that I think something is...

@SleeplessByte I don't understand this test at all... It seems wholly at odds with the problem specificiation: - prev (move the focus to the previous child of the same parent,...

To me I see 3 levels of abstraction here... 1. the underlying node data in memory 1. the JavaScript reference to a node (variable, object key, etc) 1. the Zipper...

This also seems a direct contradiction of the immediate prior test: ```js test('up returns a new Zipper', () => { const up = zipper.right().up(); expect(zipper).not.toBe(up); }); ``` These *are the...