You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please create / link to sub-issues if wanting to discuss a specific topic.
Notes 1
Is the test fair if you're not familiar with ruby?
Could we test in people's preferred language?
Should people be expected to be able to perform tdd in ruby?
...or to apply tdd to the unfamiliar?
Notes from running assessment with X
Rails really made this hard for X, and probably introduced a lot of stress, so I provided some assistance around Rails.
Feel like recognising fast feedback cycles should be giraffe or wolf.
I showed X how to skip the other tests because watching him wait was too painful.
Saw some good spiking around Rails to get their head around it (although no marks, sorry)
We hit the twitter rate limit and couldn’t run make serve for a period of time
Also provided some assistance around rspec
Writes only the simplest test
Initially was attempting to checking for 1 list item in the markup, which can be tricky. I asked some questions around this and they used string.includes? Instead of something more heavyweight
We hit the twitter rate limit and couldn’t run make serve for a period of time
Potentially worth faking the actual twitter API with a simulator from another docker container? Maybe simulate latency there to keep web request time realistic (see: slow)
I'm wondering how fair the current assessment guide is against people with most of their background in statically-typed languages.
Could you simply not think about some of the things from the marking guide because you’ve spent your whole life watching how the compiler does that for you? Should we then have some statically-typed languages in a mix as well? With a marking guide different a bit?
I don't have any specific examples in mind yet, I put that comment here just to be wary of that.
Activity
craigjbass commentedon Jun 28, 2018
Notes from running assessment with Y
craigjbass commentedon Jun 28, 2018
Under well-written tests: something about Hierarchical tests.
craigjbass commentedon Jun 28, 2018
Under well designed tests: Something about conciseness.
MeliaBurnley commentedon Jun 28, 2018
Potentially worth faking the actual twitter API with a simulator from another docker container? Maybe simulate latency there to keep web request time realistic (see: slow)
naliwajek commentedon Jun 28, 2018
I'm wondering how fair the current assessment guide is against people with most of their background in statically-typed languages.
Could you simply not think about some of the things from the marking guide because you’ve spent your whole life watching how the compiler does that for you? Should we then have some statically-typed languages in a mix as well? With a marking guide different a bit?
I don't have any specific examples in mind yet, I put that comment here just to be wary of that.