Skip to main content

Learning to Script

 

This morning I attended How I Learn New Scripting Languages, a webinar by Rob Sabourin hosted by the Test Tribe. In it, Rob laid out general principles and specific steps that he recommends for anyone new to scripting, or to a particular language.

His general points included:

  • Don't get tied to a particular language or platform; it'll get in your way at some point.
  • Don't sweat the syntax; you can always look it up.
  • Do learn how to learn; this will serve you well everywhere, not just in picking up a new language.

I don't think I'd argue with any of that but I'm less sure that my specific steps would be the same as his. For example, he recommends several foundational topics be reviewed before opening up a text editor. I wouldn't make that a precursor to starting. It's not that his ideas have no merit — they absolutely do, and to testing in general — just that they can be learned later, and tied to practical programming concepts.

As it happens, I'm learning Kotlin at the moment. My background in coding is that I did a little BASIC as a boy, a little Pascal at college, a little Modula-2 and Prolog at university, and Java, bash, and Perl predominantly at work. I've also tinkered with awk, Tcl, Python, Groovy, and others on odd occasions, usually when trying to debug or repurpose someone else's code. That might sound like a lot but, in all honesty, I have a limited repertoire of pretty basic skills.

Kotlin provides functional and object-oriented paradigms, both of which I'm familiar with more in concept than execution. I did join a lunch club working through the classic SICP in Scheme for a while but the rest of the group were (real) developers and I got quickly out of my depth on the functional side. I have also never used an IDE for any of my programming, so I'm taking the opportunity to become familiar with IntelliJ IDEA at the same time as Kotlin. 

I have approached this learning as I do with most learning: I've leapt in and cycled through different kinds of activities, looking to build on what I already know each time through. I don't worry if I don't get a concept first time, I'll move past it and try it again later. I'll visit the same material more than once because, once my personal context has changed, there's a chance I can see something new in it.

For the record, here's some of the things I did in those cycles:

  • Read and watched background material on Kotlin (e.g. How to Kotlin, Wikipedia, Joyful Kotlin). 
  • Followed along Youtube videos (e.g. Kotlin in Three Hours, Using TDD to Learn Kotlin) pausing the video to type and run whatever the presenter just did, and any variants that occurred to me.
  • Read and/or worked through various online exercises (e.g. Kotlin Examples, Kotlin Koans, Kotlin Hands-on).
  • Used background knowledge I have from elsewhere to find the Kotlin equivalent, for example "switch statement Kotlin" got me to when.
  • Explored the IDE to get some of the common shortcuts into my fingers so that compilation, or running tests, or commenting a block, or reformatting for syntax are all straight from a thought to an action and I don't lose whatever fragmentary flow I've managed to work up.
  • Taken the opportunity to explore the Kotlin doc and Stack Overflow entries when I've got some kind error, so that I build some intuition about what a particular compiler message is really telling me.

If I wasn't doing this alone, at home, I'd also be looking to pair with people who know what they're doing. This can be a major accelerator for learning although in my experience it pays back more handsomely if you can demonstrate that you're putting effort in yourself, and that you're taking notice of what you're being shown, either deliberately or in passing. 

Recently, having built up a thin foundation of knowledge, I've begun working through the 80-odd Kotlin programming puzzles on Exercism. I like these because the material is provided as a set of unit tests and stub functions. My task is to implement functions that pass the tests. Even better, once I've submitted my solution I get access to solutions from other students.

I've done 22 of the exercises so far and each time I've taken three other solutions at random to explore. Looking at other people's code is a major learning opportunity, particularly when using the IDE to show documentation for the built-in functions that someone else has used. I often need to search for examples of those functions online because I don't have enough depth yet to be able to understand quite what the doc is telling me.

Learning is not linear, in my experience. Testing is also not linear, and the skills from both areas overlap significantly and complement each other well.

Comments

Popular posts from this blog

Can Code, Can't Code, Is Useful

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "If testers can’t code, they’re of no use to us" My first reaction is to wonder what you expect from your testers. I am immediately interested in your working context and the way

Meet Me Halfway?

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "Stop answering my questions with questions." Sure, I can do that. In return, please stop asking me questions so open to interpretation that any answer would be almost meaningless and certa

Not Strictly for the Birds

  One of my chores takes me outside early in the morning and, if I time it right, I get to hear a charming chorus of birdsong from the trees in the gardens down our road, a relaxing layered soundscape of tuneful calls, chatter, and chirrupping. Interestingly, although I can tell from the number and variety of trills that there must be a large number of birds around, they are tricky to spot. I have found that by staring loosely at something, such as the silhouette of a tree's crown against the slowly brightening sky, I see more birds out of the corner of my eye than if I scan to look for them. The reason seems to be that my peripheral vision picks up movement against the wider background that direct inspection can miss. An optometrist I am not, but I do find myself staring at data a great deal, seeking relationships, patterns, or gaps. I idly wondered whether, if I filled my visual field with data, I might be able to exploit my peripheral vision in that quest. I have a wide monito

Testing (AI) is Testing

Last November I gave a talk, Random Exploration of a Chatbot API , at the BCS Testing, Diversity, AI Conference .  It was a nice surprise afterwards to be offered a book from their catalogue and I chose Artificial Intelligence and Software Testing by Rex Black, James Davenport, Joanna Olszewska, Jeremias Rößler, Adam Leon Smith, and Jonathon Wright.  This week, on a couple of train journeys around East Anglia, I read it and made sketchnotes. As someone not deeply into this field, but who has been experimenting with AI as a testing tool at work, I found the landscape view provided by the book interesting, particularly the lists: of challenges in testing AI, of approaches to testing AI, and of quality aspects to consider when evaluating AI.  Despite the hype around the area right now there's much that any competent tester will be familiar with, and skills that translate directly. Where there's likely to be novelty is in the technology, and the technical domain, and the effect of

Postman Curlections

My team has been building a new service over the last few months. Until recently all the data it needs has been ingested at startup and our focus has been on the logic that processes the data, architecture, and infrastructure. This week we introduced a couple of new endpoints that enable the creation (through an HTTP POST) and update (PUT) of the fundamental data type (we call it a definition ) that the service operates on. I picked up the task of smoke testing the first implementations. I started out by asking the system under test to show me what it can do by using Postman to submit requests and inspecting the results. It was the kinds of things you'd imagine, including: submit some definitions (of various structure, size, intent, name, identifiers, etc) resubmit the same definitions (identical, sharing keys, with variations, etc) retrieve the submitted definitions (using whatever endpoints exist to show some view of them) compare definitions I submitted fro

Testers are Gate-Crashers

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "Testers are the gatekeepers of quality" Instinctively I don't like the sound of that, but I wonder what you mean by it. Perhaps one or more of these? Testers set the quality sta

Vanilla Flavour Testing

I have been pairing with a new developer colleague recently. In our last session he asked me "is this normal testing?" saying that he'd never seen anything like it anywhere else that he'd worked. We finished the task we were on and then chatted about his question for a few minutes. This is a short summary of what I said. I would describe myself as context-driven . I don't take the same approach to testing every time, except in a meta way. I try to understand the important questions, who they are important to, and what the constraints on the work are. With that knowledge I look for productive, pragmatic, ways to explore whatever we're looking at to uncover valuable information or find a way to move on. I write test notes as I work in a format that I have found to be useful to me, colleagues, and stakeholders. For me, the notes should clearly state the mission and give a tl;dr summary of the findings and I like them to be public while I'm working not just w

Build Quality

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "When the build is green, the product is of sufficient quality to release" An interesting take, and one I wouldn't agree with in general. That surprises you? Well, ho

Make, Fix, and Test

A few weeks ago, in A Good Tester is All Over the Place , Joep Schuurkes described a model of testing work based on three axes: do testing yourself or support testing by others be embedded in a team or be part of a separate team do your job or improve the system It resonated with me and the other testers I shared it with at work, and it resurfaced in my mind while I was reflecting on some of the tasks I've picked up recently and what they have involved, at least in the way I've chosen to address them. Here's three examples: Documentation Generation We have an internal tool that generates documentation in Confluence by extracting and combining images and text from a handful of sources. Although useful, it ran very slowly or not at all so one of the developers performed major surgery on it. Up to that point, I had never taken much interest in the tool and I could have safely ignored this piece of work too because it would have been tested by

The Best Laid Test Plans

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "What's the best format for a test plan?" I'll side-step the conversation about what a test plan is and just say that the format you should use is one that works for you, your coll