Saturday, June 8, 2019

German Testing Day 2019 - About First Times

German Testing Day 2019 is over and it was great. Now's time to reflect and relax.

First Times

When thinking back I realized that this conference brought lots of first times with it.
  • It was my first time at this conference. Was really happy I finally had the opportunity to experience it after hearing about for a few years.
  • It was the first time I offered diversity tickets with the wonderful help of the organizers, especially Thomas Rinke and Melanie Wohnert. Several people applied and in the end we could grant four of them free tickets, two of them even travel and accommodation support. At the conference day I finally met three of them in person which made me really, really happy.
  • It was the first time I met lots of people I only knew from Twitter. Agreed, that's a common theme at conferences, yet I am always happy to meet people in real life. Among them: Michael Kutz and Varuna Srivastav, and I also really enjoyed their talks.
  • It was the first time I listened to Pecha Kucha talks - what a great format! Really challenging, too.
  • It was the first time I tried to sketchnote short talks by putting them all on one page. This was a new challenge for me!
  • It was the first time I sketchnoted in a different language (English) than the talk was in (German). Good thing I am practicing sketchnoting for quite some time already!
  • It was the first time for Jessica Davis to speak at a conference. She did extremely well and enjoyed it - our community just gained an amazing new voice! :D
  • It was the first time I gave the opening keynote for a conference (not counting TestBash as one-track conference here).
  • It was the first time I gave a keynote in a second country (counts as first time, doesn't it?) Thomas said this made me now an international keynote speaker! :D

German Testing Night

The evening before the main conference started was labeled German Testing night. Workshops took place along with a series of Pecha Kucha talks. Afterwards we started into an evening of networking and socializing.

What I really enjoyed: the theme was inspired by a fun fair! Hotdogs, ice cream, popcorn, dart, can knockdown, and more. This was a great way to get to know some people already before the conference started.

The Sessions

After several conferences I now got used to doing sketchnotes of all talks I attend. It's a great method to stay focused during a talk, to condense the messages heard, to visualize them, to memorize them better, and to provide a quick reminder for my future self. Bonus point: You can share them with the community so people who could not attend the conference might benefit from them as well.
My personal highlights were the talks by Michael Kutz and Thomas Rinke. Michael had a great story to tell and used beautiful hand-drawn slides to underline it. I realized we have a lot to talk about regarding organizational development, architecture, quality and testing! Thomas was originally not on the program, but had jumped in spontaneously for a speaker who fell sick. Lucky me! Now I had the chance to listen to his personal experience as tester who went through an agile transition and shared his struggles and delights with it.

My Second Keynote

I was nervous. I always am before my session, especially if it's talk. Especially if it's opening the conference. Especially if it's a keynote. During the session the situation stays challenging but something I learned I can cope with; and afterwards I have no idea how the session was from a more objective viewpoint than my own, so I am really depending on feedback.

This time I received overly positive feedback, directly as well as on all kind of social channels, even via Facebook and Instagram (oh, that's yet a another first time for me!). People told me my talk was super inspiring and some even considered starting their own tour or introducing pair testing at their companies. What else could I want? :D

Furthermore, Tobias Geyer made a wonderful job live tweeting from the session, I'm super grateful for that. Now there's only one more conference waiting for me next week before a bigger break until October - and I am already super looking forward to Romanian Testing Conference which will be another first time for me!

Sunday, June 2, 2019

Nordic Testing Days 2019 - Seamless and Surprising

This year I had the opportunity to be at Nordic Testing Days for the first time. I had heard lots of good things about the conference and seen intriguing tweets about it. Therefore I was especially happy when my paper proposal got accepted for the 2019 edition!

Arriving in Great Company

At Tallinn airport I was lucky to run into Gwen Diagram, Ash Winter and Nicola Sedgwick. Super nice to meet them again! As it was quite late already we went for dinner (or rather tea, as I learned) together with Shey Crompton. Wonderful evening with lots of good food and great conversations!

Tutorial Day & Speakers Dinner

Showing up at the venue for the first time was a big revelation: what an amazing place for a conference! The venue was formerly a power station and got now transformed to host events like this. I heard people had mixed feelings about the venue - they seemed to either love it or hate it. I for one was absolutely on the loving side! I had registered for the Android Application Security Testing tutorial by Marko Belzetski. I wanted to extend my security testing knowledge, to learn about mobile apps and security specifics to broaden my horizon, and in general to practice - and I wasn't disappointed! All expectations were fulfilled. The tutorial was a great mixture of conveying knowledge and hands-on practice (I especially love the latter). It was well structured and instructed, the setup was working perfectly, and we received concise tips and concrete advice. The only downside: for the fourth and final part in the afternoon we had too much content left so we had to rush through and only receive a short demo instead of being able to practice ourselves. For a long day this felt a bit overwhelming, and yet it was very useful knowledge which I wouldn't have missed.

In the evening it was time for the speakers dinner. I knew that last year they had visited the TV tower together so I was curious where we were led this year. We started off to the lovely seaside (I really regret I did not take any pictures there). We went on - and ended up on a boat. Yay? Well, boats and I are not quite friends so I was skeptic how dinner on a boat might turn out for me. In the end it was okay and I could grab more than a bite. The best part of speakers dinner isn't the dinner anyway - it's getting to know speakers you haven't met yet and enjoy the reunion with speakers you know already. Like Alex SchladebeckLena WibergElizabeth ZagrobaGuna Petrova and many more. We had an amazing time!

The Conference Days

The program was packed full of awesomeness. When I realized that the workshops I wanted to go to were completely overlapping with three talks each, I had a hard time making choices. In the end I went to workshops only besides the keynotes due to their topics and my wish to practice my skills hands-on. Also, I learned that some of the talks got recorded so I hope I still get a chance to watch them later.
  • Keynote: Machine Learning from System Quality Perspective by Mikhail Iljin. Really interesting topic in general, yet the core message and takeaways of the talk stayed unclear to me. Unfortunately I could not relate to the talk and would have loved to have an inspiring, thought-provoking, or enlightening opening keynote to set the tone and atmosphere of the conference instead.
  • Workshop: Unit Testing for Non-Coders by Amit Wertheimer. Great session! Amit made a great effort with preparing not only the flawless tech setup (and even backup), but also preparing the people on what they can expect, to explain everything in a language all understand without assuming knowing or not knowing, and kindly supporting them throughout. The provided cheat sheets and exercises were really helpful also for people more comfortable with code to really reflect about things and gain a deeper understanding. The only pity was that we ran out of time in the end; practicing seeing the gap that's not tested, writing a test and discussing their quality would have really rounded up the great workshop.
  • Workshop: Explicit Exploring Using Testopsies and Microheuristics by Alex Schladebeck. Awesome session. Included the right amount of valuable information sharing and hands-on exercises. Ended shortly before time. Lots of energy and fun in the room. Awesome topic as well and really relevant, also for very experienced explorers! The only thing I missed a bit was a short individual debrief after the testopsy pairing session to learn about my own testing better and to practice providing my observations and feedback to another tester. All in all Alex did a great job, being smart, entertaining and engaging.
  • Keynote: How Come Testers Are so Incredibly Successful by Raimond Sinivee. Great speaker on a great topic! Was a really relevant call to action for everyone, perfect for a keynote. We all need to get out of our comfort zones and grow. Loved the personal stories to illustrate this message! Very well presented, with lots of energy and stage presence, while still being authentic - great after a long day to keep the audience focused. Very well done!
  • Keynote: Why Should Exploratory Testing Even Be the Subject of a Keynote? by Alex Schladebeck. Brilliant! The topic definitely deserved to be a keynote, especially presented this way. Lots of relatable stories, lots of energy on stage, lots of thought put in to the content, lots of very relevant and applicable messages. What else could I want? Together with her related workshop Alex was the best speaker of the conference for me.
  • Workshop: Testing with Jest by Blanchรฉ Carstens & Calvin Moore. Great workshop, providing basic concepts, usages, examples and approaches when using Jest. I only had two points that could have improved which I also told Calvin. First, the workshop started a bit slow. It's always difficult to plan for an unknown audience yet a mechanism to scale and cater for different experience levels would have been nice. Second, the workshop ended quite early; instead it would have been great to have the group implement their own tests to apply the gained knowledge. Still, all in all, I got a first introduction into Jest which was what I was coming for.
  • Keynote: Life After QA by Erik Kaju. Interesting keynote with good content, based on experience, well presented. Really relevant topic as well.
In the evening of the first conference day an evening program was announced, including party, game night, lightening talks, and Powerpoint Karaoke. All great! However, what had not been announced and came as a surprise, was that this evening got kicked off by an acrobatic duo of "two old ladies" - what a hilarious and astonishing performance! Love it.

My Workshop

On the last afternoon, just before the closing keynote of the conference, I facilitated a workshop I had done a few times already: Learning to Learn in a Mob. We had a great group of people who did really well and obviously enjoyed the session. It was fun facilitating and I learned a bunch! Joep Schuurkes had asked me upfront if he could join the session and just observe my facilitation of a mob, as he is doing a weekly mob with the testers of his company to share knowledge. Of course, he was very welcome! This turned out to be super valuable to me, as right after the conference we had a super interesting conversation about the observations he had and the ideas it triggered for both of us to improve our mob facilitation skills.

Post-conference Socializing

Part of each conference is conferring - especially during breaks or after the conference already ended. Several speakers had to leave early this time, and still we found a nice small group to relax and have a nice dinner with: Amit WertheimerElizabeth Zagroba and Joep Schuurkes. No wonder our conversations continued in the hotel lobby until early in the morning! We ended up talking about all things programming languages, tools, design patterns, what is "technical", beliefs we got raised with, what changed in tech since the 70s, learning on the job, essential fundamentals and in general educational approaches to teaching programming (by the way, Angie Jones' new free Java programming course just got released!), and many more.
The next day I had time to sleep in and do some sightseeing. In the evening I enjoyed a lovely dinner (or shall I say feast?) with Amit Wertheimer at the wonderful medieval-style old restaurant Olde Hansa where we could dive even deeper into further topics.

A Great Time

All in all: it was a wonderful conference. Huge thanks to the organizers, everything was seamless and smooth, and everyone was extremely kind and supportive. My special shout-out goes to Guna Petrova who supported me just as if she would have been my track chair - which she wasn't. In addition, my actual track chair did an amazing job as well! I loved to see so many awesome speakers. The best thing is that several of them will also be at Romanian Testing Conference in only two weeks!

Monday, May 27, 2019

#CodeConfident: Angular7 Example App

After my recently fulfilled challenge to implement a backend feature for an existing application, I now wanted to do the same on the frontend side. Once again, as soon as I had found my practice application to extend, I could not let go. What helped me accomplish my goal within one week in the end was to pair up, this time with the wonderful Mirjana Andovska! We had already paired on my Testing Tour last year which was a great experience. Now she saw my call for collaboration for my #CodeConfident challenge on Twitter and scheduled a session with me. It was super fun and enlightening and it definitely won't be the last! I feel really honored and lucky that even further pairing sessions are coming up Amitai Schleier and Parveen Khan. Can't wait!

May 19

May 20

May 21

  • small things are easy to change, like removing the GitHub link, removing the footer, etc.; looking for something bigger where I can learn more
  • learned about Firebase, the example app is using a cloud database for all instances, same for the deployed example
  • learned that even opening a hero detail page will result in POST requests to the Firebase database (interesting to follow up on!)
  • one of the first goals was to be able to open the detail page for newly created heroes instead of getting routed to the hero list itself --> found this decision is done in the heroes list page component html, just a basic case detection
  • feels now that this is the right practice project to work on, forked it
  • played a bit more with "default" and non-default heroes, adapted the search to include both, checked how to display default avatar images for detail page for non-default heroes etc.
  • feature idea would be the one from the project: implement material tables

May 22

  • recent feature idea were to implement tables
  • alternative feature idea would be to implement "Personal heroes", the heroes you liked
  • tried the latter, copy & paste & adapt

May 23

May 24

  • made first steps in Visual Studio Code, had not used it as IDE yet, got really popular at work for frontend development, even over IntelliJ
  • filtered list of heroes not displayed; debugging in Chrome shows that heroes is undefined
  • TODO: display list; write tests

May 25

  • cleaned commits to what is already working (without filtering for heroes that I liked)
  • tried to push, got error that translations are not configured correctly for spec file; lesson learned: run the tests first... -_-
  • found the culprit, fixed, now tests are passing
  • learned how git controls work in Visual Studio Code; yet lacking permissions to push
  • pushed again using IntelliJ UI, failed again due to quite cryptic message
    Push failed: 0% compiling�������������� 10% building 0/0 modules 0 active���������������������������������� 10% building 0/1 modules 1 active ...s! ...
  • using git push in command line finally revealed the prerequisites to push, like running tests in advance etc.; this explained why it took so long... and it worked in the end!
  • TODO: learn how to add authorization to VisualCode to be able to push from IDE as well
  • TODO: filter for heroes I liked only

May 26

  • paired with Mirjana Andovska
  • Mirjana already checked out my practice project and had a look how to filter for personal heroes
  • we found out that the live app URL runs into a timeout (522) for her, yet does work for me although be both shared the same browser versions; she's located in Skopje, would be interesting path to investigate in itself (yet not now)
  • we shared our approaches how to filter for personal heroes, by using the Angular filters in the html or directly in the TypeScript component like it's also done on the home page; I showed I tried to use the filter function there yet no personal hero was listed; Mirjana had found that the value was always reset to false by logging, so the filter would work it just did not list any as they were set again to false
  • in the hero model the attribute personalHero was set to false whenever we fetched them; we could confirm this by adding simple console logs; for now we just used simple console logs, yet for proper logging we would use the framework used; Mirjana: "logging is like adding adjectives in an essay"
  • we changed the constructor's attribute value to and it was working!
    this.personalHero = hero.personalHero || false;
  • when testing this in different browsers we found that now not only any likes are stored in the global database, but seemingly also the personalHero flag; which we did not intend to, to not interfere with the global database but keep things local for practicing
  • we started learning more about Firebase and how to verify whether we actually stored it globally
  • we found that we could log the values when subscribing:
    getHero(id: string): Observable<any> {
      const retrievedHero = this.afs.doc(`${AppConfig.routes.heroes}/${id}`).get().pipe(
        map((hero) => {
          return new Hero({id,});
        tap(() => LoggerService.log(`fetched hero ${id}`)),
        catchError(HeroService.handleError('getHero', []))

      const subscribe = retrievedHero.subscribe(val => console.log(val));
      return null;
  • this way we could verify it's really stored in the global database; when looking at the tests, we found the same way was done for the mocked databases! Lesson learned: should have looked at the tests in the beginning :)
  • we reset all values by setting the flag to false again, and then re-implemented it using the local storage of the browser instead, setting a new entry for each hero we liked; we tested things out, it worked! we noted for later to change this store a list of ids instead to avoid creating new entries and save memory (
  • we wanted to have our feature covered in the tests as well; added expectations that a hero should be a personal hero after liking them; wanted to test the filtering as well; learned to add a new fixture for a different test setup
  • shortly investigated how to run a single test but then skipped this for later; UPDATE: as we're using Karma & Jasmine here, we can just focus on one test or suite by using "fit" instead of "it" or "fdescribe" instead of "describe"; f = focused, x = ignored
  • we cleaned up files for commit and tried to push; yet TSLint checks failed; we ran the tests but forgot to run about them! fixed them; then the push was successful :D
  • the scope of my personal challenge is now fulfilled, yet we identified next steps we could do to improve and extend the code to practice further:
    1. store the personal heroes ids in an array in the local storage
    2. add proper logging using the framework used
    3. write e2e tests for our new feature
    4. show the user which heroes they liked, either by adding an icon or not allowing them to vote again for the same hero and marking the heart icon gray
  • Retrospective:
    • Mirjana: normally it's a great thing to go to the tests first, can learn a lot from them; now we rushed ahead due to time, but would have been valuable as well
    • Mirjana: we had to be reminded of writing tests; interestingly this would be the first thing we as testers would remark, yet when developing we often stay inside our little box, this is why it's crucial to have someone with a different perspective looking at it from a different angle
    • Lisi: learned there's so much more to learn, there are so many more question marks now in my head as it usually is with learning and trying to puzzle all bits and pieces of knowledge together; thank you so much for sharing your knowledge with me, learned a lot in this session!
    • Mirjana this whole challenge idea a super cool thing to learn outside of our work's boundaries! Would like to create a GitHub account herself and contribute to the project or future ones, we could create pull requests and also learn so much by reading code from each other
    • Mirjana: you reminded me how to learn! use a small project to practice, and especially pair! Lisi: pairing helps me so much, it keeps me accountable and also together we always generated new ideas so we did not get stuck, or at least quickly unstuck again
    • Looking back, we paired for nearly 4h instead of the originally planned 1.5h! It was fun and super enlightening, and afterwards we could fully enjoy our evenings :)

What else?

The great news is: I fulfilled now the promise to myself to have at least 5 repositories published on GitHub. Even in 5 months! Still can't quite believe it. The next and final step: build an application from scratch which will serve as my proof of concept. I'm really excited. And that's not the only thing I'm excited about these days. These are busy days, great days, and especially exciting days!

Sunday, May 19, 2019

#CodeConfident: Spring PetClinic

My last weeks were super busy. As a result, I had to neglect my code-confident challenge and was feeling sad about it. I knew already knew for longer what my next practice project should be about: extending an existing backend feature. I found, however, that getting it started was a lot more difficult than I expected. When I finally could start, I got intrigued yet realized I need to learn a lot more. In the end, I did the biggest part just on one day as I couldn't let go anymore!

April 27

May 12

May 13

May 14

  • pairing session with Amitai Schleier
  • presented him my current problem, first lack of time and now stuck in researching projects trying to decide which one to work on
  • told him about my criteria and desired tech stack
  • started to present my latest list of 5 candidates
  • Amitai: likes to look at tests first to see if they are readable and to see what the app is supposed to be doing
  • after the first project he stopped me and suggested a project he just found by using Duck Duck Go search "open source spring-based application": Pet Clinic, a Spring demo project
  • cloned the project
  • Amitai: let's try to run it first
  • ran it using the run configuration detected by IntelliJ; ran but did not find css
  • the readme showed how to run the app --> worked this time including building of css
    ./mvnw package
    java -jar target/*.jar
  • wanted to use IntelliJ and make it faster, found we could add the package step as Maven goal step before launch: "package"; tried out different variants, found we needed to keep the build step before
  • discussed general approach to tackle an existing app; I shared it depends what I am looking for, if I'm reviewing other people's code or if I'd like to contribute myself, etc.; Amitai: wants to see if he can quickly get something to change, see the cause and effect; he could read a lot and model and everything but rather prefers changing something as better test of understanding; wrote a tweet thread about cause & effect
  • we decided to change the pet picture on the welcome page to a different one; used this as valid reason to google for cute animal pictures ^^; replaced the image, replaced the image reference, verified the change got applied after application restart
  • before going further, we felt that packaging took too long as it was running all tests; wanted to comment them out, but could not find them in the pom; looked upMaven lifecycle ( and found that tests are included by default; found we can skip them by calling "package -Dmaven.test.skip=true"; startup now a lot faster, still a bit slow for actual fast feedback during development, yet doable
  • had a look at what the app already provided, like "find owner"; decided to add "find pets"
  • added a new menu item (copy & paste from find owners), restarted - nice, we land on the error page as expected
  • added a controller, copied over from owners; copied the owners html page, adapted as well; our "hopothesis" would have been that now we would be able to access a find pets page with a form to search for owners; yet we knew we probably missed something and indeed, we got the error page instead
  • we realized the relationship of owners and pets was not modeled parallel as assumed, but having pets subordinate to owners
  • Retrospective:
    • Lisi: thank you so much, you got me unstuck in a few minutes! Amitai: seems like my super power, as I have to always get myself unstuck: I know how to orient myself in my problem space, and know how to help people orient themselves in their problem spaces
    • Amitai stayed in the navigator role, Lisi as driver; both thought it went well, were not sure if it was okay for the other one but only addressed it in the end; Amitai: felt you picked up things, needed to instruct less and less, you already knew what I wanted; Lisi: when I want to learn, I try to keep myself on the driver seat; I also learn a lot as navigator, having to express my intent and decide where to go next, yet now it's about hands-on practice; Amitai: agree, it's always good to practice; agreed to switch roles next time
    • learned that copy & paste is not always working, we have to learn more; was a good reminder to think about the model and how we would want it to be; having pets subordinate to owners did not feel right; what if a pet changes the owner? We would not want to loose the record for the pet, or the past owners; also from a moral standpoint a partnership would be better
    • I will have to decide where to go next and define my scope for this practice project; Amitai: Gilded Rose is known as refactoring kata, but he likes to call it the "when to stop" kata; what's the cheapest thing you can do? It's about business, not about the cleanest code; it's really important to zoom out, zoom back in, zoom out again, and realize when to stop
    • Lisi: last session and this one as well I gained a lot of benefit from what you shared, bits and pieces of knowledge here and there, and especially from your approaches, how to tackle things; they work well for the concrete thing, but are also applicable in a generic way, will also help me later
    • Amitai: last time you gave me energy, happy to give it back this time!
    • agreed to do a third session end of June / July
  • TODO:
    • set up practice project
    • define scope
    • do it

May 15

May 16

  • tried to understand app better
  • need debugging to understand more
  • not much time today

May 18

  • debugging the owner controller: did not stop in debugger - why? still haven't found out; would be something to investigate in a pairing session
  • learned more about the demo project; provided lots of info, however, for an outdated version
  • found the community built a lot more versions: among them also one for Angular :) (could be the perfect target for my next challenge!)
  • learned more about MVC (Model View Controller):
  • saw our get mapping is a bit different, realized I need to look that up and learn more
  • learned more about Thymeleaf inputs
  • trying to adjust controller to have correct result collection for binding, adding results from search by first name to the results from search by last name; assumed the resulting collection will contain duplicates --> assumption was correct! keeping fields empty to get full list is now showing duplicates; also, existing first name is still showing full list
  • tried the Stream version and found it cannot be cast to a collection
  • used set instead of collection and it works! bye bye duplicates :)
  • found that when I provide values for both fields, search by first name does work now indeed! --> found I always list all in case one field is empty... o_O changed this to only show all in case both are empty --> still, one empty field will show the list of all owners
  • cases:
    • last name empty, first name empty => list all owners
    • last name exists once, first name empty => show owner details (does not work yet)
    • last name empty, first name exists once => show owner details (does not work yet)
    • last name exists multiple times, first name empty => list selection of owners (does not work yet)
    • last name empty, first name exists multiple times => list selection of owners (does not work yet)
    • last name does not exist, first name exists once => show owner not found (does not work yet)
    • last name exists once, first name does not exist => show owner not found (does not work yet)
    • last name does not exist, first name exists multiple times => show owner not found (does not work yet)
    • last name exists multiple times , first name does not exist => show owner not found (does not work yet)
    • last name does not exist, first name does not exist => show owner not found
    • last name empty, first name does not exist => show owner not found (does not work yet)
    • last name does not exist, first name empty => show owner not found (does not work yet)
    • ...
    • more cases:
    • both names exist, but for different records => show owner not found (now shows both records)
    • parameterless GET request /owners should still list all
  • feel the database query should already take care of filtering everything; implemented look up by full name for results list --> oh my it works!!
  • what about exact same full name, but different entries? should still list both entries --> and it does!
  • not flawless but worth to commit it :D
  • added tests for new controller feature; test for not existing first name fails, not sure why yet --> experimenting made me finally understand better what the "rejectValue" method does in the controller! added handling in case first name is not found; now error message is displayed twice! ^^
  • researched a lot more regarding Thymeleaf and error messages
  • found how to display an error for a specific field:
    <p th:if="${#fields.hasErrors('firstName')}" th:errors="*{firstName}">Error</p>
  • however, wanted to have a combined message if an owner is not found, not separated per field; found how to add and display global error:
    • Controller:
      result.reject("ownerNotFound", "not found");
    • Template:
      <p th:if="${#fields.hasGlobalErrors()}" th:each="err : ${#fields.globalErrors()}" th:text="${err}">Global Errors</p>
  • downside: the test for the global error is super generic, did not find a way to test for exact error
  • tested the tests, made them fail, added assertions; how to assert at least for the number of results found? haven't found an answer yet
  • still, the scope of this challenge is fulfilled for now, I implemented a small new feature :D can still extend it, improve it further and clarify the open questions when pairing with others

Friday, April 26, 2019

#CodeConfident: FizzBuzz

My previous challenges on my way of becoming code-confident felt too long. Granted, my Serenity Cucumber Practice (part 2, part 3) was my first challenge ever, and during Rest Practice I had a long period of travels. Still, right now I craved for a quick and simple challenge just to practice and learn just a bit more, not overdoing things. Last but not least, I wanted to go one level deeper regarding implementation and testing.

April 23

April 24

  • changed setup a bit to better suit the purpose
  • wrote test for second case, then wrote code to make it pass
  • agreed with myself that I will commit frequently, at least every time a new test is passing
  • had to remember to run test first, see it fail, then implement, run the test again, see it pass
  • baby steps and frequent commits (trying not to care about how elegant the solution is in the beginning as long as it's working) really helped get myself into a flow! Feeling I accomplish something and am on the right track
  • first implementation fulfilling requirements was done very quickly
  • personal observation: though doing quick commits (even when small) was at first still strange, it now felt a lot more natural to just create a repo and make several commits to it; was so scary in the beginning!!! A lot less already, can be proud :)
  • TODO: decide on what else to do, like reduce to required tests
  • TODO: finish challenge and seek the next one, this was meant to be a very small and short one

April 25