<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Anwesha Chatterjee on Medium]]></title>
        <description><![CDATA[Stories by Anwesha Chatterjee on Medium]]></description>
        <link>https://medium.com/@anweshachatterjee?source=rss-1dac059d06dd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EzH1SHeBRLllyojULSv-wA.jpeg</url>
            <title>Stories by Anwesha Chatterjee on Medium</title>
            <link>https://medium.com/@anweshachatterjee?source=rss-1dac059d06dd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:18:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anweshachatterjee/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Asking yourself if U R OK]]></title>
            <link>https://medium.com/@anweshachatterjee/asking-yourself-if-u-r-ok-39a8b0525375?source=rss-1dac059d06dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/39a8b0525375</guid>
            <category><![CDATA[resilience]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[mental-health-awareness]]></category>
            <category><![CDATA[self-awareness]]></category>
            <category><![CDATA[self-help]]></category>
            <dc:creator><![CDATA[Anwesha Chatterjee]]></dc:creator>
            <pubDate>Fri, 21 Sep 2018 06:26:16 GMT</pubDate>
            <atom:updated>2018-10-02T07:46:41.178Z</atom:updated>
            <content:encoded><![CDATA[<h3>(And what you can do if the answer is “no”)</h3><p>4 months ago I moved interstate from Queensland to start my new job at REA Group Melbourne, and with that move came a lot of changes. I started adjusting to life in a new city, a new job, new workmates, new friends. I had just gotten out of a 4 year relationship, and it was hard to have lost that support alongside the network of friends I had in Brisbane. My parents aren’t based in Australia, and with that comes another layer of isolation.</p><p>After 4 months of change after change after change, I was burning out. I found it hard to cope, and I was almost in denial about this. I hadn’t settled into my new life yet, i still had a lot of new friends to make, restaurants to dine at, coffees to taste, art to appreciate, hobbies to pick up. I hadn’t even cleared probation yet — how could I be burning out already! So I tried to pretend that I was okay.</p><p>Needless to say, that was not sustainable. And then a few weeks ago i had an anxiety attack. I hadn’t had one in years, and it was terrifying. I didn’t know what to do to make it better, and I didn’t have the energy to find out.</p><p>But around this time I noticed that there was something interesting about the way I thought about mental health.</p><p>Firstly, I had waited until my panic attack to do something about my mental health. And secondly — even then i was ashamed to admit that i was struggling. When telling my teammates that I took a sick day because of the flu, I could do that without thinking twice. But when it came to talking about needing a mental health day — I hesitated. Even for someone who considers herself fairly rational, I had a weird judgement of myself for needing to tend to my mental health. I perceived myself as weak for having to take time off to recover, or needing to speak to a counsellor. How bizarre is that? I wouldn’t dream of judging anyone else for any of those things. Especially because some ridiculous percentage of people in Australia suffer from anxiety or depression at some point in their life.</p><p>If you broke your arm, you wouldn’t feel ashamed of needing to give your arm some rest.</p><p>But still for some reason a certain taboo existed in my head regarding talking about this thing that the vast majority of people around me have either gone through, or are currently going through.</p><p>Mental health can be a tricky conversation — because it is such a deeply personal and sensitive topic. Luckily there are some <a href="https://www.ruok.org.au/how-to-ask">good resources</a> out there regarding how to approach someone with the question of “Are you ok?”. And it goes without saying that supportive friends and family come foremost when it comes to building a support network for tackling mental health issues.</p><p>But it’s no good having all these people ask you if you’re okay and offering you help if you, yourself don’t know how to identify when you’re struggling. Also, it’s important to surround yourself with people who support you — but its just as important to know how to help yourself.</p><p>So In this post I’d like to share some personal techniques I use when I’m faced with anxious and depressive thoughts. I know that I still have a long way to go, but with the help of supportive friends, family and good psychologists I have developed some beliefs and elements of support that I lean on when I’m going through difficult times:</p><ol><li><strong>I remind myself that it is not going to last forever</strong>. When I have my episodes of anxiety, I find that it can feel like I’ve only ever felt that way. I also start wondering if I’m ever going to feel normal again. I start worrying about the future, and that causes me to spiral into an uncontrollable state of hopelessness. I have found that during these dark times, if I remind myself that this is a temporary state, and that it will pass — much like a bad flu — it helps me cope a lot better.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/1*mJUT79jmRaTX1SK_17r3UQ.png" /><figcaption>The viscous cycle of anxiety can make it feel like things will never get better. Illustration by <a href="https://www.instagram.com/steinbergdrawscartoons/?hl=en">@steinbergdrawscartoons</a>.</figcaption></figure><p>2. <strong>I remind myself that it’s not all bad.</strong> During my anxious moments, I can often get stuck in the process of thinking that all aspects of my life are terrible. I’m unfit, I look terrible, I don’t work hard enough, I am a failure, I can’t function as a normal human being. I also tend to discount the things that I have achieved. But it doesn’t have to be all or nothing. Just because I missed yoga one day and went out for ice cream with a friend that night, does not mean that I am a junk food addict with no self control. We can all be so harsh on ourselves for not living up to our own ridiculously high standards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/1*2zSZqXSJPHkM4N_Hh33Y0w.png" /><figcaption>I can get into a rut of thinking that everything in my life isn’t great. Illustration by<a href="https://www.instagram.com/steinbergdrawscartoons/?hl=en">@steinbergdrawscartoons</a>.</figcaption></figure><p>3. <strong>I try to identify if I’m catastrophising.</strong> Going back a few years, when someone really dear to me was diagnosed with cancer, I started seeing a psychologist. I remember saying to her that I was terrified of losing them. She asked me — “Well, that is a fair concern. But what if that does happen, is that going to be the end of your world?”. I remember being shocked at what she was suggesting. I remember thinking — <em>duh</em> — of course it is, that’s why I’m here! But when she explained what she was saying to me in more detail, it was such a revelation. If I lose her — it would be devastating, sad and excruciatingly painful. But it would not be a catastrophe. I would push through — I’d have to! Everyone does. And this simple truth was so grounding. You may get bankrupt, lose your job, get broken up with, get cheated on — whatever it is — it won’t be the end of the world. And that is comforting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*PlePmexc8RU_XpuiXntunA.png" /><figcaption>Definitely a catastrophe. Illustration by <a href="https://www.instagram.com/steinbergdrawscartoons/?hl=en">@steinbergdrawscartoons</a>.</figcaption></figure><p>4. <strong>I try to cut myself some slack.</strong> Sometimes anxiety and depression can get the best of us no matter how much we prepare and think that we can guard ourselves against it by doing all the “right” things. This is when I am often guilty of trying to mask my emotions — I tend to self medicate with an overconsumption of coffee, and I fill up my days with activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/569/1*kXc8Y7kh3qGTtIe6EG1zTg.png" /><figcaption>Drowning myself in coffee when I’m fatigued hasn’t worked out as well as I’d hoped. Illustration by <a href="https://www.instagram.com/steinbergdrawscartoons/?hl=en">@steinbergdrawscartoons</a></figcaption></figure><p>Needless to say, that hasn’t worked out well for me at all. It’s not very sustainable. So instead I’ve been trying a new approach. When I recognise that I’m having trouble coping, I tell myself it’s okay to take a mental health day, or to need to call a friend and ask for support, or to not be able to do as much work, or for needing to see a therapist, or needing medication. It can be hard to remember that it is okay to take time to recover, it is okay to ask for help, and it is okay to put yourself first during these times. It’s interesting how harsh we can be on ourselves during the times when we need to take care of ourselves the most. When everything else is an effort, it’s okay to read your favourite book, listen to your favourite music, eat your favourite food, and watch your favourite show. It’s okay to treat your inner child to these comforts when everything else in life is uncomfortable.</p><p>5. <strong>When I’m recovering, I try to give myself little things to look forward to</strong>. Sometimes, this can be a yoga class, or going climbing, or just making myself some chai and watching my favourite TV show. Sometimes it needs to be something bigger, like a trip to visit a friend, or family. But I try to make it a short term thing — rather than a life changing event (like moving to Paris) as otherwise I tend to get anxious about the logistics of making that happen. Little steps help.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/538/1*qU0EYcxWbXfeBeeguNx4xw.png" /><figcaption>Cool little illustration from <a href="https://www.instagram.com/bymariandrew/?hl=en">@bymariandrews</a>. It looks a little different for everyone, but the key message is the same.</figcaption></figure><p>6. <strong>Finally, I try to create a sustainable routine of taking care of myself so as to try and avoid burnout. </strong>When I feel like I’m coping much better, I try to practise yoga and meditation more regularly, climb more often, and try to eat a lot of good nourishing foods. I try to drink less alcohol, eat less sugar. I journal more regularly so I can stay in touch with my emotions. I try to get more sun by going for regular walks. Creating art helps, as does playing my guitar. When I’m working on something stressful I try to notice if I’m clenching my teeth, or fidgeting with my fingers, and I try to control these actions by focusing on my breath and trying as best as possible to be mindful about whatever I’m working on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*pQDMlvfV2jgyWvYqXdOh9A.png" /><figcaption>Illustration by <a href="http://hyperboleandahalf.blogspot.com/">Hyperbole and a half</a></figcaption></figure><p>These affirmations and routines form my foundation of internal support for when my anxious brain gets the better of me, and I hope that sharing this means that someone else facing similar issues can benefit from it.</p><p>I’d like to finish off by saying that there is no shame in admitting that you need help. If someone asks if you’re okay and you’re not — say that you’d like to book some time with them to talk through things — because no-one gives you an award for saying you’re okay when you’re actually struggling. Also, don’t ever feel like you need to wait for someone to ask you if you’re okay — you are not a liability. Admitting that I need support with mental health has been the first positive step towards a speedy recovery for me, and I’m grateful that I reached out when I did.</p><p>I am lucky that my workplace is one of the most supportive, open and genuinely caring environments that I have ever worked in. I never feel uncomfortable taking time to myself, going for a walk/break when I need it, or requesting flexible working arrangements. Where you work and how you feel at work can have such a massive impact on your personal life — and I am fortunate to have found a place that has a positive impact on my mental health in my day to day life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39a8b0525375" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting started with Functional Programming]]></title>
            <link>https://medium.com/@anweshachatterjee/getting-started-with-fp-609575254919?source=rss-1dac059d06dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/609575254919</guid>
            <category><![CDATA[functional]]></category>
            <category><![CDATA[functional-programming]]></category>
            <category><![CDATA[currying]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Anwesha Chatterjee]]></dc:creator>
            <pubDate>Thu, 12 Jul 2018 03:56:28 GMT</pubDate>
            <atom:updated>2018-07-12T06:17:54.851Z</atom:updated>
            <content:encoded><![CDATA[<h3>(for dummies like me)</h3><p>I was one week into my new role as a developer in REA Group when I saw a bit of code in our codebase that looked like this :</p><pre>const veryConfusingFunction = (someParameter) =&gt; (anotherParameter) =&gt; {<br>   // does some stuff and then returns<br>};‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍</pre><p>I was very confused. It looks like a function, but it accepts two lots of arguments, in two goes.</p><p>But … why?</p><p>So I did a bit of googling, and found out about “currying”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*it9EJUjHQU9fGLzSD0ip_A.png" /></figure><p>Upon mentioning my confusion regarding currying to a colleague, she showed me the <a href="https://mostly-adequate.gitbooks.io/mostly-adequate-guide/">Mostly Adequate Guide to Functional Programming Gitbook</a>.</p><p>And with that I took my first step into the wonderful and terrifying journey that is learning functional programming. So I thought I’d write a post about the first few bumps I faced on the way along my FP journey.</p><h3>Currying</h3><p>I understood how it worked, and it all looked really cool, but I still didn’t have an answer to my question …</p><blockquote><em>But … why?</em></blockquote><p>So let me explain what I found out about <em>why</em> you would even want to use currying. In order to do that, let’s take a look at this code snippet.</p><pre>const greet = (greeting, name) =&gt; `${greeting} ${name}!`;‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍</pre><p>The greet function takes in a greeting as the first argument and the name as the second argument, and when you invoke it with both these arguments, it greets the name with the provided greeting. Like so:</p><pre>greet(&quot;Hello&quot;, &quot;Anwesha&quot;);‍‍‍</pre><pre>// &quot;Hello Anwesha!&quot;‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍</pre><p>The curried version of this function and invocation would be:</p><pre>const greet = greeting =&gt; name =&gt; `${greeting} ${name}!`;<br>const greetWithHello = greet(&quot;Hello&quot;);<br>greetWithHello(&quot;Anwesha&quot;)‍‍‍‍‍‍‍‍;‍‍‍</pre><pre>// &quot;Hello Anwesha!&quot;‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍</pre><p>So here are some questions that popped into my head, and some of my thoughts on the answers.</p><h4><strong>How is currying different from the “normal” way?</strong></h4><p>The first version of the greet function accepts two arguments. This is known as a “dyadic” function. In this case, the arguments for greet <em>do</em> have a natural ordering. However, this may not always be the case based on what your function is doing. In the book <a href="https://www.amazon.com.au/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882">Clean Code</a>, Robert C. Martin gives the example of the function assertEquals(expected, actual) to demonstrate that it can be inconvenient to have to remember the order of the arguments in the function that doesn’t necessarily have a natural ordering. Currying helps to eliminate that inconvenience by only accepting one argument at a time, and thus isolating the logic better.</p><h4>Cool. But isn’t this just the same as partially applying a function?</h4><p>This one took me a while to wrap my head around. If you are unsure about what partial application of a function is, it is basically passing just a few of the arguments to a function, not all of them. It might also help to read the <a href="https://lodash.com/docs/4.17.10#partial">lodash partial function</a> docs.</p><p>While it is possible to achieve the same results with partial application of a function and currying, they are however not <em>exactly </em>the same things. A partial function may or may not have a predictable return type. As in, it may return a function with any <a href="https://en.wikipedia.org/wiki/Arity">arity</a> (fancy term for the number of arguments a function accepts), whereas a curried function always returns another function with an arity of 1.</p><p>Let’s look at another example to see what this means.</p><pre>const add = (num1, num2, num3) =&gt; num1 + num2 + num3;‍<br>const add1 = _.partial(add, 1);<br>add1(2);<br>// NaN<br>add1(2,3);<br>// 6‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍<br></pre><p>As you can see, when we partially apply an argument to our add function it returns a function with an arity of 2, and hence when we invoke our add1 function with only one argument, it returns NaN .</p><p>A curried version of this function would be:</p><pre>const add = (num1) =&gt; (num2) =&gt; (num3) =&gt; num1 + num2 + num3;<br>const add1 = add(1);<br>add1(2);<br>// (num3) =&gt; num1 + num2 + num3<br>add1(2)(3);<br>// 6‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍</pre><p>In this case, when you invoke add with only one argument, it returns another function with an arity of 1. So a curried function will always return a known type — which is a function of arity 1 — until all the arguments have been applied \o/</p><p>You can read more about currying Vs. partial applications in JavaScript in <a href="https://medium.com/javascript-scene/curry-or-partial-application-8150044c78b8">this article</a>.</p><h4>Okay, great. So where is this useful?</h4><p>Personally, I have found currying addresses a few different issues.</p><ol><li>It gives us a way to apply data to functions as they become available at different points of time and location. In the case of the greet function this would mean that with the curried version you could pass in the greeting when and where you knew what to greet someone with. For example, you may have separate modules in your project for greeting someone based on their language selection, and then a module on a higher level that had knowledge of the name to greet. Currying enables us to invoke the part of the the function that we know and care about, and leave the rest to be taken care of later by whoever cares about it. Another example, your application may have a certain behaviour in prod, but a slightly different behaviour in a dev environment. Instead of littering the codebase with logic about whether the app is running on dev or prod, the config can be supplied with this knowledge using currying. It would look something like this:</li></ol><pre>const doConfigDependentStuff =&gt; (isProduction) =&gt; (someOtherParams) =&gt; {<br> // does stuff based on where app is running<br>}‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍</pre><p>And you can partially apply the config, like so:</p><pre>const IS_PRODUCTION = process.env.NODE_ENV === ‘production’;<br>const doStuffInApp = doConfigDependentStuff(IS_PRODUCTION);‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍</pre><p>So now doStuffInApp can be invoked and passed around agnostic of whether the app is running in dev or prod.</p><p>2. Another one of the most common uses for currying is to make it easier to compose functions. Function composition is another separate concept that I will cover in the second half of this post.</p><p>3. Since curried functions return other functions, they essentially return a container. As mentioned in <a href="https://medium.com/javascript-scene/curry-or-partial-application-8150044c78b8">the currying article</a> referenced earlier</p><blockquote><em>By dealing with </em><strong><em>containers</em></strong><em> instead of the </em><strong><em>values inside of containers</em></strong><em>, you can create lots of generic </em><strong><em>functions that will work universally</em></strong><em> for anything that uses the </em><strong><em>container’s interface</em></strong></blockquote><p>This also brings me to the concept of Optionals, as it gives us a “container”-ised, encapsulated and cleaner way to error-check. But maybe I’ll leave that for a different post. You are welcome to check out <a href="http://rea.tech/introduction-to-option-and-either-types-in-js-part-1/">this post on Option and Either types</a>.</p><h3>Composition</h3><p>Function composition is the art of combining or chaining multiple functions into one. It takes the output of the rightmost function and pipes it into the input of the function to the left. You can read more about it in <a href="https://mostly-adequate.gitbooks.io/mostly-adequate-guide/ch05.html">the composition chapter in the mostly adequate gitbook</a>. Using the definition of compose in <a href="https://mostly-adequate.gitbooks.io/mostly-adequate-guide/appendix_a.html#compose">the appendix</a>, I shall attempt to demonstrate how compose works using the following example:</p><pre>const toUpper = (text) =&gt; text.toUpperCase(); </pre><pre>const addExclamation = (text) =&gt; text + &quot;!&quot;;</pre><pre>const makeUpperAndAddExclaim = compose(addExclamation, toUpper);</pre><pre>makeUpperAndAddExclaim(&quot;hello&quot;)</pre><pre>// &quot;HELLO!&quot; ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍</pre><p>So we have a function that capitalises text, and another one that adds an exclamation mark to it. All that compose does is it feeds the output of toUpper and then feeds it to addExclamation. So what does this have to do with currying? As is explained in <a href="https://stackoverflow.com/questions/36273977/are-currying-and-composition-the-same-concept-in-javascript">this stackoverflow post</a>:</p><blockquote><em>Generic function composition works with unary functions (functions that take one argument) and curried functions also only accept one argument (per application).</em></blockquote><p>As we covered earlier in the article, currying <em>always </em>returns a unary function (until all the arguments have been supplied). This is the reason you can use currying and composition together in harmony. You can look more into an example of that happening in <a href="https://medium.com/javascript-scene/master-the-javascript-interview-what-is-function-composition-20dfb109a1a0">this blog post about function composition</a>.</p><p>Another good thing about function composition is that it helps us keep code concise by reducing the need for temporary variables. It may not be completely evident from our simple upper-caser-exclaimer example, but it also helps us build big powerful functions from smaller simple functions. So it helps us make things more modular by helping us isolate and encapsulate logic into bite-size pieces</p><p>And that’s all. I am very new to the FP world, and this is probably one of the most technical blog posts I’ve attempted to write, so please feel free to correct me and leave feedback in the comments — I would highly appreciate it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=609575254919" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I got over my irrational fear of git]]></title>
            <link>https://codeburst.io/how-i-got-rid-of-my-irrational-fear-of-git-rebase-25a12095e45e?source=rss-1dac059d06dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/25a12095e45e</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[version-control]]></category>
            <category><![CDATA[beginners-guide]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[gitflow]]></category>
            <dc:creator><![CDATA[Anwesha Chatterjee]]></dc:creator>
            <pubDate>Sat, 14 Oct 2017 08:57:45 GMT</pubDate>
            <atom:updated>2017-12-10T17:07:10.579Z</atom:updated>
            <content:encoded><![CDATA[<h3>(Spoiler alert: It isn’t that scary!)</h3><p>When I first started using git, about 2 years ago, I was quite intimidated by it. As a graduate engineer just starting off, I didn’t entirely understand why we needed version control. But as I started coding as a part of a team that got bigger and bigger, the need for git became obvious to me. Git makes collaboration and backing up easy — and also provides a clear and easy way to store versions of projects. These are the main reasons why git has been indispensable in my life as a software developer. However, despite this, I always had this lingering fear of git — and it was because I didn’t <em>really </em>understand it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*0Xfaz0bvLpRksBv5." /></figure><p>Initially my plan was simple. Only use the things that I know. git clone. git pull. git commit. git add. git push. And if anything didn’t work out as planned, <a href="https://imgflip.com/s/meme/Scared-Cat.jpg">panic</a>. I got heavily dependent on the merge tools in PyCharm (PyCharm is awesome, btw), but that back fired. The abstractions provided by IDEs can be very neat, but I feel like they can get in the way of <em>really </em>understanding whats going on under the hood.</p><p>Recently, a few things got me to shake my bad git habits and really get into the nitty-gitty (see what I did there 😛) of git. Mainly, it was a change of workplace. In a previous workplace (maybe due to the large team size) I could get away with some bad practices. My commit messages didn’t make a lot of sense because I didn’t think they were <em>that </em>important.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/439/1*ifdKIW6eSNNPiZfT0PjCfw.png" /><figcaption>Somewhat like this. (<a href="https://imgs.xkcd.com/comics/git_commit.png">https://imgs.xkcd.com/comics/git_commit.png</a>)</figcaption></figure><p>My reliance on PyCharm for any form of merging, as well as working on a branch with atleast one other person meant that I had all these stray “merge commits” littered in my pull request. But recently I started working at a company where they’re a <em>lot </em>more strict about the quality of pull requests, right down to the wording of the commit messages. So I’d like to share with you my story of how I stopped being petrified of git rebase…</p><h4>Merging and rebasing</h4><p>In order to understand merging and rebasing, let’s look at a few scenarios.</p><ul><li><strong>Scenario 1</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OirI5IfNEJ_Ll_Pb." /><figcaption>Scenario 1: 1 unmerged commit in master</figcaption></figure><p>In this simple scenario, you had created a branch off the master branch in your project. The master branch had one commit at this point — commit “A”. Since then, there has been another commit added to master — commit “B”. Now, upon merging with master:</p><pre>git merge master</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/462/0*VFifAfdly-w1S52O." /><figcaption>The result of a merge in Scenario 1</figcaption></figure><p>The commit “B” is now a part of my-feature branch. Nice!</p><ul><li><strong>Scenario 2</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/418/0*XPgVpiIwtU4P97gb." /><figcaption>Scenario 2: a local and a remote commit</figcaption></figure><p>Moving along, you have created a commit in your local branch (commit “D”), and someone has pushed a new commit onto master as well (commit “C”).</p><p>Hmm… what to do. Let’s try merging…</p><pre>git merge master</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/0*WU7Fq3W3cOUCFy60." /><figcaption>Result of a merge in Scenario 2: A “merge commit” is created.</figcaption></figure><p>See the red commit “E” — that’s the “merge” commit that was created to get my-feature branch back on track with master. Note how the commit “E” has two “parents” (“C” and “D”), because it’s a result of merging the changes brought about the commits”C” and “D”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/0*XwWUz-1NxeqcImBy." /><figcaption>The “stitching pattern” look after another merge: 2 new remote commits and 1 new local commit</figcaption></figure><p>Now, if scenario 2 keeps happening, (as in, we <em>keep</em> merging master into our branch) this is what our workflow will start looking like. As you can see, this can become a bit messy. <em>Everytime </em>there is a new upstream commit, you end up with a merge commit.</p><ul><li><strong>Scenario 3: Enter git rebase…</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o3Kagjxwq1DWBklb." /><figcaption>Scenario 3: situation after rebasing — commit D is <strong>replaced </strong>by commit D*</figcaption></figure><p>In this scenario, when there is a new upstream commit, as well as a new local commit, we try rebasing instead.</p><pre>git rebase master</pre><p>This time, instead of creating a whole new commit (like commit “E”), our local commit “D” is now <strong>replaced </strong>by a new commit “D*” (The purple commit), that incorporates the local changes from the previous local commit “D” onto the parent commit “C” (the new upstream commit in master).</p><p>As you can see, rebase and merge essentially do the same thing — they just do it <em>differently. </em>Rebase leaves the git log much cleaner and easier to navigate. It also makes the history more linear, as opposed to the stitching pattern look in scenario 2 brought about by merging.</p><h4>Interactive rebase</h4><p>Rebasing can also be used to amend a commit that is <strong>not</strong> the previous commit. In this case, you would have to do an interactive rebase</p><pre>git rebase -i master</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/1*leuQA4U71Lr3yT8AlpyQdA.png" /><figcaption>Interactive rebase</figcaption></figure><p>You can also give rebase the commit hash you would like to rebase to. First, you would have to replace the “pick” next to the commit you want to amend with “edit”. Then, making the necessary changes, you would amend the commit, followed by completing the rebase</p><pre>git commit -a --amend<br>git rebase --continue</pre><p>If at any point, things go south, you have the option of aborting the rebase</p><pre>git rebase --abort</pre><p>If you’re still worried, you can also try out the rebase in a temporary branch first, to see how it goes. Interactive rebase can also be used to “squash” multiple commits into one commit. One word of warning about using git rebase though…</p><p><strong>Do NOT rebase public branches that others have created new commits on top of.</strong></p><p>If you would like to learn more about why this is so, or just in general about merging and rebasing, I highly recommend <a href="https://www.atlassian.com/git/tutorials/merging-vs-rebasing">the atlassian documentation</a> as well as <a href="http://eagain.net/articles/git-for-computer-scientists/">Git for Computer Scientists</a>.</p><h4>Some other tips and tricks I picked up along the way…</h4><ol><li>If you would like to pull from master while making sure your branch is rebased and not merged, you can do that using:</li></ol><pre>git pull --rebase</pre><p>Another scenario where I found this helpful was when I accidentally committed onto a branch I wasn’t supposed to commit to. The steps to get out of a situation like this would involve something like…</p><pre>git reset --soft &lt;commit-hash-to-reset-to&gt; <br>git stash <br>git pull --rebase<br>git checkout &lt;the-correct-branch&gt; <br>git stash pop<br>git commit -a</pre><p>So basically,</p><ul><li>Do a soft reset to the latest “good” commit hash</li><li>Stash the changes</li><li>Do a rebase-pull from your origin, so it <strong>doesn’t </strong>fetch your misguided commit</li><li>Checkout the correct branch</li><li>Unstash changes</li><li>Commit the changes</li><li>Live happily ever after 😍</li></ul><p>2. I have also sometimes gotten into a situation where I accidentally “lose” a commit after a rebase (It’s usually because I gave it the wrong commit hash). If this happens, rest assured — you <strong>can’t </strong>lose a commit. You can either git checkout or git cherry-pick the commit using its hash. How do you find the hash?</p><p>3. <a href="https://www.atlassian.com/git/tutorials/rewriting-history/git-reflog">Reflog</a>! Embrace git reflog as soon as you can. The more you read it, the easier it will get to pick out the commit and the corresponding commit hash that you need.</p><p>4. Also worth looking into what <a href="http://www.paulboxley.com/blog/2011/06/git-caret-and-tilde">tilde and caret mean in git</a> as this was something that took me a while as a noob.</p><p>And that’s it! That’s my git story so far. I’m certain that I have many git wars to fight yet, as my journey as a software engineer continues — but I look forward to coming out the other end reinforced with even more git knowledge, and hopefully a little less scared of the powers of git!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25a12095e45e" width="1" height="1" alt=""><hr><p><a href="https://codeburst.io/how-i-got-rid-of-my-irrational-fear-of-git-rebase-25a12095e45e">How I got over my irrational fear of git</a> was originally published in <a href="https://codeburst.io/">codeburst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NodeJS: Finding your way as a beginner]]></title>
            <link>https://medium.com/cloudboost/nodejs-finding-your-way-as-a-beginner-15643034c484?source=rss-1dac059d06dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/15643034c484</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[self-education]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[women-who-code]]></category>
            <category><![CDATA[node-for-begginners]]></category>
            <dc:creator><![CDATA[Anwesha Chatterjee]]></dc:creator>
            <pubDate>Wed, 23 Aug 2017 03:34:47 GMT</pubDate>
            <atom:updated>2017-08-24T12:19:06.901Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first started off trying to wrap my head around Node, and what the hell it does, I was a bit overwhelmed. With Node being <a href="https://insights.stackoverflow.com/survey/2017">one of the most popular technologies of today</a>, there isn’t a lack of resources out there for it. But the fact that I didn’t completely understand what it does and why it’s used meant that I didn’t know where to start my learning journey from. I eventually made my way through several resources (courses, github repositories, gists, websites…).</p><p>So I thought I’d make a (very subjective) list of tools and resources that helped me, and hence could help a complete beginner, to build the foundations for understanding NodeJS — and what the hell it does 🤔</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*boCOCYNBhf5AD34K01dO0Q.jpeg" /></figure><h4><a href="https://www.udemy.com/understand-nodejs">Learn and Understand NodeJS</a> on Udemy</h4><p>This <a href="https://www.udemy.com/understand-nodejs">course by Tony Alicea</a> is a great course for someone starting off with Node (and JavaScript).</p><p>Here are a few reasons why I liked the course:</p><ul><li>He dives deep into why you should even bother learning Node before he teaches you to write any code. I thought that this was a refreshing approach which helped me grasp the core logic and facts a lot better than any tutorials on NodeJS I had done (a.k.a blindly followed) in the past.</li><li>He defines every key concept needed to understand what Node does clearly and simply without the use of unnecessary jargon. I seriously don’t think I understood servers and clients completely until I watched the lecture on it in this course! It’s a good idea to keep a list of the “big words” he defines as you come across them, as he doesnt have the list documented in a written form in the course material.</li><li>He has a nice set of coding resources which someone can use to make the course as hands-on and interactive as desired, while still having access to the working and completed code.</li><li>He goes through how to use some essential tools for coding in JavaScript and using NodeJS: like using the debugger in VS Code and <a href="https://chrome.google.com/webstore/detail/postman/fhbjgbiflinjbdggehcddcbncdddomop?hl=en">the Chrome Postman extension</a>.</li><li>He explains how Node fits into the “MEAN stack” (and what MEAN stack is) by building a simple app that displays the main functionalities of Node and its role in the MEAN stack.</li></ul><p>While for a lot of more experienced developers, this course might seem too simplistic or slow paced, I couldn’t recommend this course highly enough for someone just starting off, who isn’t looking for something particularly exhaustive.</p><p>Some tips:</p><ul><li>It isn’t free, but you may catch it on special if you check the website regularly (I bought it for $19).</li><li>It contains a total 13 hours of lectures, but you can increase the speed of the video when you need. I found that running them at 1.25x most of the time worked, while I used 1.5x when going through concepts I was already semi-familiar with.</li></ul><h4><a href="http://nodeschool.io/">NodeSchool interactive tutorials</a></h4><p>The best way to dive straight into the coding side of things is to use the interactive workshops in <a href="http://nodeschool.io/">nodeschool.io</a>. These workshops are easily available if you have Node installed locally. Simply install it globally, for example:</p><pre>npm install -g learnyounode</pre><p>will install the “learnyounode” workshop. Then you can simply type learnyounodeto start the workshop (or type learnyounode help to see the help menu).</p><p>Be wary though — not all workshops on the website are well maintained. Personally, I would recommend trying out “learnyounode” as it covers the basic concepts in Node, such as: I/O, async I/O, modules, creating a HTTP server amongst others.</p><p>“stream-adventure” is also a good one to follow if you are interested in learning more about (and being less scared of) streams in Node. There are a couple of tasks that aren’t completely clearly explained, but a quick google search leads to some <a href="https://github.com/workshopper/stream-adventure/issues">issues on github</a> that have some clear explanations of the solutions (which, by the way, are available by typing stream-adventure solution).</p><h4><a href="https://github.com/node-girls">NodeGirls tutorials</a> on github</h4><p>If you are just looking for some light reading to understand what node actually is, a good place to start would be the NodeGirls <a href="https://github.com/node-girls/what-is-node">what-is-node</a> repository. It covers all the basic concepts of Node in a compact manner, and has references to a bunch of other great resources.</p><p>I would personally read this document after having written some basic code using NodeJS to better understand concepts like the event loop and callbacks.</p><h4><a href="https://github.com/maxogden/art-of-node">art-of-node </a>by maxogden</h4><p>If you are a beginner in NodeJS, but experienced in one or more scripting languages, art of node is a great comprehensive explanation of all things Node (streams, modules, npm, events, callbacks…) with excellent references to other resources.</p><h4><a href="https://www.youtube.com/watch?v=FqMIyTH9wSg">LearnCode.academy YouTube tutorial</a></h4><p>This one’s good if you are already aware of the core concepts in web development and are not looking for a particularly in-depth introduction to NodeJS. Or you just want to jump straight into it and get your hands dirty. <a href="https://www.youtube.com/watch?v=FqMIyTH9wSg">This YouTube video</a> is basically a crash course in NodeJS and ExpressJS — by the end of the 15 minutes or so, you will have created a basic web application. It assumes some fundamental knowledge (things like… what is a web server, what is a HTTP request) but he does run through using express-generatorand the architecture of the generated files, covers some basic concepts in express and Node (like routes, using `res.send()`, etc.), and demonstrates using the browsers network debug tool to monitor HTTP requests and responses.</p><p>I understand that sometimes learning is better in a collaborative environment. So finally, if you are looking to find an awesome community of supportive NodeJS and JavaScript users —</p><h4>Attend (or start) a <a href="http://nodegirls.com.au/">NodeGirls Australia</a> workshop!</h4><p>If you are based in Sydney, Melbourne, or Brisbane, follow us on <a href="http://facebook.com/NodeGirlsAustralia">Facebook</a> or out <a href="http://nodegirls.com.au/">website</a> to find out about upcoming events. NodeGirls Australia runs multiple events in a year, covering several different JavaScript-related topics. Women are given preference as attendees in our workshops, but anyone can be a mentor — irrespective of gender. Both attending <strong>and</strong> mentoring are awesome ways to learn more about NodeJS!</p><p>If you don’t see your city amongst the NodeGirls chapters, please consider starting a new chapter. You can read more about how I started the Brisbane chapter of NodeGirls Australia in <a href="https://medium.com/@anweshachatterjee/how-i-organised-a-coding-workshop-for-women-3170fac03dbe">this medium post</a> :-)</p><p>Hope this helps! Happy coding 🤓</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15643034c484" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cloudboost/nodejs-finding-your-way-as-a-beginner-15643034c484">NodeJS: Finding your way as a beginner</a> was originally published in <a href="https://medium.com/cloudboost">CloudBoost</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I organised a coding workshop for women]]></title>
            <link>https://medium.com/@anweshachatterjee/how-i-organised-a-coding-workshop-for-women-3170fac03dbe?source=rss-1dac059d06dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/3170fac03dbe</guid>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Anwesha Chatterjee]]></dc:creator>
            <pubDate>Wed, 16 Aug 2017 07:03:47 GMT</pubDate>
            <atom:updated>2017-08-16T08:20:16.838Z</atom:updated>
            <content:encoded><![CDATA[<h3>…and didn’t completely suck at it</h3><p>I had always enjoyed attending women’s workshops such as <a href="http://railsgirls.com/brisbane.html">Rails Girls</a> and <a href="https://djangogirls.org/brisbane/">Django girls</a>, and was a regular at <a href="https://www.meetup.com/en-AU/Women-Who-Code-Brisbane/">Women Who Code (WWC) Brisbane’s monthly meetup</a>. I had just started learning JavaScript for my job as a graduate software engineer, and I wanted to find a similar community of women to learn JavaScript with.</p><p>I was ecstatic when I stumbled upon <a href="http://nodegirls.com.au/">NodeGirls Australia</a> — an organisation that holds free women’s JavaScript workshops. However, my excitement was short-lived as I scrolled through the “events” page, only to realise that there was no NodeGirls in Brisbane. I was heart-broken when the founder Tanya wrote back to me explaining how she was stretched too thin to conduct workshops in Brisbane, alongside managing the existing chapters in Melbourne and Sydney. I was prepared to seek other ways to start learning more about JavaScript and NodeJS, but some things changed my mind.</p><p>I found the <a href="https://insights.stackoverflow.com/survey/2016#technology-most-popular-technologies">2016 Stack Overflow statistics</a>:</p><blockquote>More people use JavaScript than use any other programming language. PHP appears to be falling out of favor as Node and Angular emerge.</blockquote><p>But a stark contrast to the soaring stats for JavaScript in software was that of <a href="https://business.linkedin.com/talent-solutions/blog/2014/03/women-in-engineering-the-sobering-stats">the number of women employed in the field</a>. It couldn’t be that women just <em>happened</em> to be less interested in software or coding. I had always loved coding, starting from my very first “hello world” program. However, I preferred learning in a female-friendly environment. It felt like a secure learning space. I felt less conscious of my shortcomings as a coder than I did in a male-dominated environment. I wondered how many other women felt this way — how many women didn’t enter the field because the environment didn’t seem welcoming for a woman starting off?</p><p>I decided I wanted to do something about it. This, along with my desire to learn more about NodeJS drove me to take on the role of lead organiser for the Brisbane chapter of NodeGirls Australia, and I’d like to share a few of the many things that I learnt along the way, and that helped me bring this event together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V5C_KDMN0GJCGXXlHQgsCw.jpeg" /><figcaption>Group photo time!</figcaption></figure><h4>Be a mentor</h4><p>As Tim Minchin says in his graduation speech —</p><blockquote>Even if you’re not a teacher, be a teacher.</blockquote><p>Especially if you think you don’t have much to offer — be a teacher. Mentor kids to learn how to code using <a href="https://scratch.mit.edu/">scratch</a>, or volunteer as a mentor at coding workshops near you. Tutor a kid who’s interested in coding. Teaching kids is great because it forces you to understand things in a way that you can explain them simply, which is the key to understanding things well.</p><p>Being a mentor, especially when you don’t see yourself as one, is an incredibly efficient way to learn about yourself. It’s the fastest and most efficient way to realise how much you know that you don’t give yourself credit for. I’ve definitely found that I don’t realise how well I understand something until someone asks me to explain it to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/927/1*ZpUZmtVcbGdD5G_Zs-tx_Q.jpeg" /><figcaption>Tim and Ian mentoring at the NodeGirls workshop</figcaption></figure><p>I also feel like I am obligated to understand a topic better when someone else is relying on me to explain it to them. It sounds funny, but it works — the pressure of having to explain what NodeJS is, and why it is used, in front of 40 odd people, made me learn things a lot more thoroughly and in-depth. But it’s also important to know where to draw the line, which leads us to the fact that …</p><h4>You don’t have to know everything.</h4><p>It sounds cliche. But its a difficult one to remember when you’re surrounded by people who just seem to know it all. This notion that we need to know everything holds us back from the actual doing of things. The secret is not to know everything, but to know<em> how </em>to know<em> </em>everything. In the age of Stack Overflow answering your questions before you even knew you had them, and thousands of free or reasonably priced courses on everything and anything that you’re interested in, there is no lack of learning resources. Start with something, anything — and when you are stuck, there’s doctor Google to the rescue. Whatever questions or problems you have, seek comfort in knowing that you are most definitely not the first person to ask them on the internet.</p><p>If I had waited until I knew everything about NodeJS to announce the first Brisbane event, I don’t think I would’ve announced it yet!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*VcOCurfdfcduuuheNtYhDA.jpeg" /><figcaption>Here’s me, talking about NodeJS, despite not knowing everything about it ;)</figcaption></figure><p>Chances are that your journey to whatever your goal is won’t be “perfect”, you’ll discover several gaps you’ll have to fill as you progress. But this isn’t a bad thing, which brings us to the next point…</p><h4>Dont be so afraid of failure</h4><p>Reshma Saujani, the founder of Girls Who Code has a <a href="https://ed.ted.com/featured/16DCJILa">brilliant Ted talk </a>where she speaks about how we teach little girls to be perfect, and little boys to be brave.</p><blockquote>Most girls are taught to avoid risk and failure. They’re taught to smile pretty, play it safe, get all A’s.</blockquote><blockquote>Boys, on the other hand, are taught to play rough, swing high, crawl to the top of the monkey bars and then just jump off headfirst.</blockquote><p>With software being the fast paced ever-changing industry that it is, no wonder women don’t attempt to enter it when they have been trained by society to be “overly cautious” and “aspire for perfection”.</p><p>This was an especially difficult one for me — I often worried about the event not being perfect, or being called out on being an impostor. After all, I didn’t know a thing about NodeJS 4 months before the event! I had to repeatedly remind myself, that this was all an experience, and that the worst case scenario is that I put together an event that brings together a lot of like minded people… and that isn’t a bad worst case to have at all :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/475/1*UwxhRKNNU6PyPh8qV2UYfQ.jpeg" /><figcaption>Worst case scenario — there’s a lot of delicious food!</figcaption></figure><p>This is why we didn’t mention the coding level in the workshop description — As soon as you mention the word “intermediate”, people start doubting whether this is the right event for them. My aim was to show women, that even though they might not view themselves as a person with intermediate skills, they won’t really know if they are unless they try it out.</p><h4>Get comfortable with making noise</h4><p>This one was a tough one for me to begin with, especially because I would define myself as an introvert. Personality tests have always classified me as an introvert. So it wasn’t exactly shocking to me when I discovered that getting people to notice this event wasn’t one of my strong suits — and it definitely wasn’t the easiest thing on my to-do list. I treated my ability to socialise like a muscle — I believed that as long as I keep exercising it, I’ll get better at it. I signed up as mentor at Coderdojo Brisbane, I attended as many coding meetups as possible, I attended hackathons. I basically forced myself to be social. I discovered the power of <a href="http://twitter.com/NodeGirlsBri">twitter</a>. Luckily I already had a couple of lovely friends, who from day 1 were 100% committed in co-organising NodeGirls with me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*f6Z28G6lCpkyoU8ZfORhlg.jpeg" /><figcaption>Laura Armagan and me — the power team!</figcaption></figure><p>Laura is our star designer who is incredibly proactive in managing all the digital media for the workshop. Armagan has an amazing ability to explain even the hardest things so beautifully and simply. She is also one of the most social and kind people that I know. She put together a very successful fundraising potluck for NodeGirls at Red Hat, which ended up paying for a big part of the event.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/597/1*AAgbV-BC-h55KXEgZ5Pmyw.jpeg" /><figcaption>A delicious and creative cake contribution at the potluck</figcaption></figure><p>Together we formed a strong team, with each of us having our own specialised responsibilities. But socialising in the various events is how I found the network of people who ended up being the support I needed to make this event happen.</p><p>And finally…</p><h4>You can’t please everyone</h4><p>This is coming from a glass-half-empty kind of person — I’m the kind of person who would fixate on a handful of negative responses amongst all the positive ones in a survey. I learnt through organising this event that there are a large number of people with a diverse set of skills who will attend such workshops. To try to cater to each and every single need is an impractical goal. So while I would 100% recommend you to seek feedback for the event, I would also say that you shouldn’t get disheartened by every negative feedback you receive.</p><p>It’s important to reflect on all the feedback, and exchange your takes on them with your team, and then classify the improvement advice as feasible or unfeasible based on your goals. And it’s equally important to celebrate the positive feedback as well :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3170fac03dbe" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>