Are you writing enough tests? Are you writing too many tests? Are you striking the right balance between high-level acceptance and integration tests, versus low-level unit tests?
I’ve heard from many programmers who struggle with these questions.
In this episode, you’ll see a real, unrehearsed example of how I typically do test driven development. You’ll see how to arrive at the right balance of tests I rely less on rules and concrete guidelines, and more on careful attention to my current level of unease.
I really think you have put a lot of work and effort into making an amazing website full of very helpful videos and topics that are relevant for Ruby programmers. I find that they are too fast and sophisticated for my skill level. Would you be interested in creating a menu for less skilled developers who are still learning Ruby and could do with examples of best practices or good solutions to common problems but at a pace and depth that would appeal to us lesser mortals? I would buy that in a second.
I will definitely keep that in mind!
—
I am a lapsed Tapas subscriber; too much good stuff. Seriously good examples; I just transcribed this Brunch (Outside-In). This is my 2nd or 3rd Ruby Tapas transcription. I am looking for work. I find the 8 minute bites take me about the 3 hours; I follow along with you until you start testing, then I have to stop the video, change screens, type in half a sentence. That is the pace right now, to grasp wtf I would be doing day-to-day, looking at legacy code etc. My first good transcription is “Refactoring for Interviews”. I find this is the only way I can get “Avdi fingers”…a poor euphemism for “solid working skills”. Thanks and don’t change a thing.
Very much enjoyed this episode! Thanks!
You’re very welcome!
—
Avdi Grimm
> Sun, Jul 30 at 03,35 PM, null wrote:
> RubyTapas
> jrubisch > added a comment in reply to Episode #120: Outside-In.
> jrubisch
> Very much enjoyed this episode! Thanks!
> Reply to this email to reply to jrubisch. > You’re invited to respond by replying to this email. If you do, it may be published immediately or held for moderation, depending on the comment policy of Episode #120: Outside-In.
> Recently in this conversation…
> Mitchell Gould
> July 6, 2017 1:31 am
> I really think you have put a lot of work and effort into making an amazing website full of very helpful videos and topics that are relevant for Ruby programmers. I find that they are too fast and sophisticated for my skill level. Would you be interested in creating a menu for less skilled developers who are still learning Ruby and could do with examples of best practices or good solutions to common problems but at a pace and depth that would appeal to us lesser mortals? I would buy that in a second.
> Reply
> jrubisch
> July 30, 2017 3:35 pm
> Very much enjoyed this episode! Thanks!
> Reply
> Reply to this email to reply to jrubisch. > Please note: Your reply will be published on Episode #120: Outside-In.
> You received this email because you’re subscribed to discussion of Episode #120: Outside-In. unsubscribe > Sent from RubyTapas. Delivered by Replyable – Two-way email commenting for WordPress.
Top class episode, thanks!
I am curious:
What if you end up finishing up an entire feature/task just with an acceptance test?
Meaning that during the entire flow you kept getting valuable, fast feedback about what you were doing, until a point where you actually completed the task.
Would you go the unit level anyway?
That’s an easy one: nope! I’d just move on to the next feature.
—
May I suggest: start transcribing ruby programs (and posting them to a generic repo you can share). Avdi’s are uniquely perfect for this. Transcribe one program from a book or web, then watch a Ruby Tapas (Brunch) Once you get hands, eyes and mind on the step by step code you won’t feel the need to master 575 videos; you will know what to work on. I lost a month feeling as you describe, I push myself to dig, dig, dig. start digging. Good luck!