<?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 Rajko Winkler on Medium]]></title>
        <description><![CDATA[Stories by Rajko Winkler on Medium]]></description>
        <link>https://medium.com/@rajko.winkler?source=rss-daef0f02b321------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2kASIZ2SVjEUXm4rg58iDg.jpeg</url>
            <title>Stories by Rajko Winkler on Medium</title>
            <link>https://medium.com/@rajko.winkler?source=rss-daef0f02b321------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:10:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rajko.winkler/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[Why, the bilingual is actually working!]]></title>
            <link>https://medium.com/@rajko.winkler/why-the-bilingual-is-actually-working-b0c40545a1f9?source=rss-daef0f02b321------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0c40545a1f9</guid>
            <category><![CDATA[parenthood]]></category>
            <category><![CDATA[english-learning]]></category>
            <category><![CDATA[english-language]]></category>
            <category><![CDATA[language]]></category>
            <category><![CDATA[bilingual]]></category>
            <dc:creator><![CDATA[Rajko Winkler]]></dc:creator>
            <pubDate>Wed, 01 May 2019 19:39:09 GMT</pubDate>
            <atom:updated>2023-01-17T08:37:01.428Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DAqsL4vjXSNPt7JOBdNLbQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/OdF1YWzW_vA?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Sven Brandsma</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I’m a German father living in Germany raising our child in English. Despite some doubts, in the beginning, I’m amazed by the joy and the positive results we’ve seen with this very personal experiment.</p><p>This post is a follow-up to <a href="https://medium.com/@rajko.winkler/heres-what-i-learned-from-18-months-into-bilingual-parenting-9e19067abdc8">my first post on bilingual parenting</a> from February last year. In it, I describe our motivation and experiences during the first 18 months of raising our son in English.</p><p>Now, more than a year later it remains one exciting experiment. We‘re even more dedicated today considering the development we saw within the last 14 months. So I felt it was time to share some of our experiences on pushbacks, positive feedback, and exciting new progress.</p><p>I concluded my last post with sound advice to boldly step forward on your commitment. You easily end up being surrounded by skepticism originating from other parents, colleagues, or even friends. In any way, you’ll need to find a good way of dealing with it, if it does bother you.</p><p>So I followed my own advice: I stepped forward. I published links to my blog post via social media. It didn’t take long for the first discouraging comment to arrive. Surprisingly, it was from a former colleague. I had anticipated him as a peer, someone with similar views and common interests and values.</p><p>To sum up the negative points, here’s a list of what was put in question:</p><ol><li>Sufficiency of own language level</li><li>„Overloading our children“</li><li>Kids can easily pick up languages when they’re older</li></ol><p>Immediately this gave me a hard time. Why? Especially the first point had been among my doubts when considering this <em>project</em>. On the other two I’m much more confident, so let’s try to take them apart one by one.</p><h4>1. Language level</h4><p>For over two years I’ve been speaking English to my son only. (Almost) Every English word he’s to learn, the responsibility is on me. That includes every wrong interpretation or false pronunciation. Let alone the grammar which will become more important over time.</p><p>The obvious cure to that is to expose him to more English-speaking people, be it in playgroups or other occasions. Also, every one of our friends is welcome to speak English with him, we have a few that actually enjoy this. Nevertheless, we will look out for more opportunities.</p><blockquote>I’m learning along the way and I’m also fine with looking up words from time to time.</blockquote><p>On the other hand, I’ve been thinking about various ways of improving my own language level. I have not taken any particular action so far, though. For now not being confident about the spoken word all the time is okay with me. I’m learning along the way and I’m also fine with looking up words from time to time.</p><p>So the conclusion: My language level is sufficient for now. Improvement will happen naturally. If you’re not a native speaker or you might have not been exposed to the language you grew up with for a while, it can make perfect sense to actively work on improving your language skills.</p><h4>2. Overloading our children</h4><p>This specific point is about the assumption of over-straining our children by exposing them to an additional language. The general opinion is to keep it easy on them, and let them learn, and discover what they like in a playful manner.</p><blockquote>A two-year-old does not even realize it’s handling two languages.</blockquote><p>The fear of overloading a child seems to be one of the most common misunderstandings in bilingual parenting. A two-year-old does not even realize he’s handling two languages. It’s our personal assumption to have gone through language education in school.</p><p>Another common concern that oftentimes comes along is the delay in starting to speak. If people believe in over-strain then this must be the metric to measure it by. Science has proven this wrong for a long, and from what’s our very personal experience there’s no delay at all.</p><p>Will our child have preferences for words in one or the other language? Of course. And will he mix up words from both languages in a sentence at times? Definitely! He’s exposed to a different language in a very subtle way, so that doesn’t happen by surprise. But he‘s everything but lost.</p><h4>3. It‘s too early to learn</h4><p>A topic that is closely related to the previous one. The assumption is there’s plenty of time for children to pick up languages. So when is that? In school? I vividly remember my English and French classes. In most cases, this will not get you anywhere beyond a basic understanding of the language, let alone enough practice in speaking and writing.</p><blockquote>All that matters is to expose yourself to that other language in your day-to-day life.</blockquote><p>Usually, a language needs to become part of one’s life to reach a certain level. Some lucky ones take part in a school exchange program or study abroad after school. All that matters is to expose yourself to that other language in your day-to-day life.</p><p>Offering that early exposure to a language will also help in other fields. Not only will these children be more capable to learn a third (or fourth) language. A recent experiment among first and second graders in Bavaria shows measurable improvements in e.g. math classes held in English.</p><h4>So, anything positive here?</h4><p>Be assured there’s plenty of curiosity and encouragement from friends and family. At times this can keep you floating. To my surprise, I learned that many people admire the idea. They can easily comprehend the beneficial outcomes of this little “project”. I’ve picked some of these floaters to share with you. Some of them might make you smile a bit, too.</p><p>The other day our son’s caretakers in kindergarten confessed they had tested him. They used English to discuss secret topics like desserts at lunchtime in front of the children. They were astonished realizing that he was picking up almost everything. Time to change tactics, if you ask me. 😀</p><p>A couple of weeks ago I was getting him ready for bed, singing the first lines of <em>Feeling Good</em>. He looked at me almost angrily just to tell me (in German) “No, Papa, birds are not flying high, they are in trees”. This has not been something that I expected him to catch up on. And it increases confidence in how well he has embraced the language.</p><blockquote>Usually it’s me talking to him in English and accepting him answering in German.</blockquote><p>Talking, however, and that has been the norm so far, is preferably done in German. It might be due to the high degree of exposure to German in kindergarten and around our family and friends. He’s never forced to use <em>other words</em>. Usually, it’s me talking to him in English and accepting his answer in German.</p><h4>So what’s next</h4><p>The before mentioned fact makes us think of incentives to change this. I could tell him that I don’t understand, but that would feel unauthentic because I do. For now, I want to challenge him every once in a while and then increase it gradually. I get him to say certain sentences, for instance when picking him up from kindergarten I ask him to say “We’re going home” in a cheerful manner.</p><blockquote>Something else I’ve been thinking about lately was introduced to me by one of our neighbors. How long do we plan to pursue this project?</blockquote><p>Something else I’ve been thinking about lately was introduced to me by one of our neighbors. How long do we plan to pursue this project? Will there be a natural barrier we’ll hit, e.g. when he’s in school? Will he at some point tell me to stop that weird behavior immediately?</p><p>Those two points will have to sink in for a bit. The former is something I’m addressing already. Thus I would like to get in touch with others to discuss this. The latter, considering he’s not even three, I’m assuming to have some time left until it does require any action.</p><p>Exchange is always helpful. Comments are very much appreciated. If you want to get in touch here or reach out to me on <a href="https://www.twitter.com/rwi">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0c40545a1f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobile development at reBuy: Moving (back) to Native]]></title>
            <link>https://medium.com/@rajko.winkler/mobile-development-at-rebuy-moving-back-to-native-7f66bed9b882?source=rss-daef0f02b321------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f66bed9b882</guid>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[kotlin]]></category>
            <dc:creator><![CDATA[Rajko Winkler]]></dc:creator>
            <pubDate>Tue, 31 Jul 2018 14:44:56 GMT</pubDate>
            <atom:updated>2023-01-17T08:41:56.075Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fFg2a1n-2FYmrgkG" /></figure><p>Sometimes it takes guts to make decisions, this is equally true for the tech world as for any other field in life. And sometimes it takes even more guts to revoke those decisions and move on.</p><h3>“Write once, run everywhere”</h3><p>In late 2014 we as the mobile team at <a href="https://www.rebuy.de/">reBuy</a> were utterly impressed by Xamarin’s unique promise: Build native UIs for Android, iOS, and Windows Phone based on one single, shared C# codebase.</p><p>“Write once, run everywhere” seemed like the perfect fit for our rather small mobile team back then. Xamarin Forms supported a common set of UI controls and layouts to then map those to the corresponding native UI controls at run time.</p><p>Besides the predefined set of controls, developers could also extend the UI with custom layouts by providing additional custom render classes for the targeted platforms. The promise also included interoperability towards native libraries through bindings.</p><p>Considering that we had previously come from minimal native implementations in Java and Objective C partly embedding web views, this seemed like an incredible opportunity: Design and develop one app and literally roll it out at once to our Android and iOS users.</p><h3>Start Fresh</h3><p>The mission of reBuy is to increase the overall life cycle of products by selling and buying used goods. Providing a usable and appealing app is essential to bind customers in a long term.</p><p>So we gave it a shot: The team started off by implementing the purchasing branch of reBuy. Customers can sell used media products and consumer electronics at a fixed price and receive their money once their items arrived at the reBuy warehouse. Development included the usage of the user’s camera to easily scan products by their bar codes along with the regular product search and checkout process.</p><p>It took another year until we managed to release the selling part of the reBuy app, by that time the number of developers had doubled, totaling four. In July 2016 the team released a feature-complete Xamarin Forms app to our users.</p><p>Technically we delivered a solid app. However, basically, all design decisions had been taken top-down, an approach that implies design confidence based on personal opinions and experiences, but lacks measurement of impact on the users overall.</p><h3>Step up</h3><p>A/B testing provided us with a tool to gain immediate feedback from our users. In very small experiments we could tell if a certain feature went in the right direction. It felt like we were moving fast.</p><p>It was that time, however, when we started to run into limitations within Xamarin Forms. Design approaches became more tedious to fulfill, and bindings to third-party libs we desperately wanted to use, didn’t exist. Creating some of them turned out to be cumbersome and error-prone.</p><p>At this point however you usually don’t make a move yet, the app had literally just been released. Instead, you work your way around it, which means investing some extra time in tweaks and fixes. And that might be bearable for the moment.</p><h3>Turning point</h3><p>The performance turned out to be another major disturbing point to the user experience of our app, though. This had been especially true for the Android app. The underlying Mono layer became a massive bottleneck, resulting in unacceptable startup times beyond 15 seconds.</p><p>So while Xamarin Forms’ abstraction level had been extremely convenient during development and maintenance, the outcome more and more turned into an unpleasant solution for our customers.</p><h3>Into the wild</h3><p>This is when you <em>do</em> know it’s time to make a move. But now that we saw what’s wrong, where do you start? Well, we locked ourselves up in a remote location for a few days and began testing possible alternatives, at first for our troublesome Android app with its mentioned burdens. In small teams, we created two minimal prototypes of the reBuy app that gave us just enough load and data to compare them in startup times and still were doable within the given time frame.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/0*at0o8EqqIqJjhamE" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/0*A8HgzszfRWJTxPnt" /><figcaption>Code camp in the wilderness of Brandenburg</figcaption></figure><h3>Going half-native?</h3><p>Technically speaking we had Xamarin Native vs Android Native in this battle. Xamarin Native for Android simply provides a C# abstraction layer to the complete Android stack. So the obvious hope was to make use of a large amount of code reuse and still benefit from native UI components.</p><p>Expectations towards Android Native were naturally driven by the idea to get the most out of the richness of the Android ecosystem. To be able to follow the latest design approaches and get to use a wide variety of available components and tooling. The obvious downside was the assumed learning curve to embrace Android development.</p><p>In retrospect, the adoption of Xamarin never provided the needed comfort to easily navigate through obstacles. From small things like a terrible “official” forum as a promoted source of support to quite often breaking changes in layouts in the broader picture, we never fully gained the confidence of either a helpful backing or a critical mass user base.</p><blockquote>We had to leave our comfort zone, though, to deliver something more appealing to our customers.</blockquote><p>It was a tough debate on opportunities, risks, and also about leaving our comfort zone. We discussed, compared, and timed. While Xamarin Native outperformed Xamarin Forms as expected we had to accept that we still were not able to make use of third-party components natively. And user adoption seemed even lower than Forms, so not much help in sight either.</p><p>In the end, it was a clear decision to commit ourselves to the idea of “moving back” to native. The expected benefits were just too overwhelming. We had to leave our comfort zone, though, to deliver something more appealing to our customers.</p><h3>The green field</h3><p>So here we were: A developer&#39;s dream, the green field. About a week after we took the decision Google happened to announce broad support for a JVM language other than Java — Kotlin. Effectively they said it was to become a first-class development language for the Android environment. Support and samples were meant to cover Kotlin from now on also.</p><p>So since we were starting fresh anyway, we tried out Kotlin by converting some of our prototype Java code to it. We quickly dug deep into it, grasped its concepts, and were astounded by its capabilities.</p><p>Toward the start of development, we looked at what other teams were doing to adapt to the new language. Often other companies would start including Kotlin by writing unit tests for their existing Java code base first to ease the shift. Well, that wasn’t us exactly…</p><h3>Kotlin — All in</h3><p>Instead, we took our next bold decision: we as the dev team committed to 100% Kotlin right from the start. On one hand, this felt right, why start with Java? On the other hand, a new language bears risks, as its adoption was low at that point and there were fears that we might miss out on mature of an existing ecosystem again. In the end, this was one of the reasons to move away from Xamarin in the first place.</p><p>The milestones for the fully redesigned app were already planned and they did not allow additional time to be wasted, because let’s face it: if we put our team on a complete redesign, we effectively stop delivering anything new to our customers until the new app had been released.</p><blockquote>The team concluded we could always fall back to Java for certain classes in case we got stuck. To this day this has not happened once.</blockquote><p>But hey, Kotlin is a JVM language, and the interoperability capabilities between Kotlin and Java were convincing. The team concluded we could always fall back to Java for certain classes in case we got stuck. To this day this has not happened once.</p><p>Kotlin itself was an easy play, the language has similarities to C#, which we had used with Xamarin. In addition to that, we again went for the Reactive Programming model which comes as RxJava in the Android world. Its usage allowed us to apply some of the concepts we had already used intensively.</p><h3>Hands-on</h3><p>The main target was a minimal release by mid-December. This left the team with around six months to complete this ambiguous goal. Work got structured in four milestones, the first two targeting the selling side, followed by one for the purchasing side, finalized by one running QA test rounds with an external testing company, and finishing up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8AytMno4zmhbfZpF" /></figure><p>Team’s additions chart from GitHub, created some impact around the milestones in August and September</p><p>Despite the language being friendly, we had to invest a lot in understanding the platform itself. The team had different experience levels regarding technical topics like application life cycle, view handling, and UI creation. So naturally, it took some weeks to really get us going.</p><p>After having settled with some of the more important technical decisions, and already making use of new designs that our design team had prepared for us, we were up and moving at the end of July.</p><p>In retrospect, we roughly made every milestone on time. We held various internal presentations and started internal tests to gather early feedback. Constantly we were driving on that slightly uncomfortable edge, knowing we are moving fast.</p><h3>Getting there</h3><p>The closer we got to December 15th, the more the team got excited. After going through an evaluation with an external QA company and plenty of hours of bug fixes and last improvements we managed to release to the targeted audience of 1% at the exact date. This meant around 2000 of our users were able to download the new app version.</p><p>From experience, the learning starts once an app is released. There are so many things that you can test even with such a low number of customers. We found some serious troubles in the way we handled our fragments that required quite some effort at the beginning of this year to get this straight.</p><p>The team did an awesome job of catching up on the issues that arose. We managed to improve the app, even adding more features and getting A/B testing in place. From sprint to sprint, we carefully released to an increased number of our users.</p><h3>Break-even</h3><p>One of the most desperately awaited moments at that time was the break-even in mid-April: Distribution of the new app to 50% of our users. For the first time in over 10 months of development, we were able to directly compare old vs new apps and see how well they would perform. Would users accept the new app? Did we manage to provide something meaningful to our users?</p><blockquote>No more rolling back, no back up, we are live!</blockquote><p>To keep it short: The numbers we saw were quite promising! The conversion rate on our selling side was up by more than 4 %. Green, the purchasing side, was even beyond expectations by seeing a 19.5 % increase in conversion rate and a 12.75 % uplift in average order value.</p><p>Here and there we still had some smaller flaws, but the numbers proved us right. By the end of April, we finally rolled out to 100% of our customers. No more rolling back, no backup, we are live!</p><p>In the past months, we were able to keep those numbers on the right track and in addition had two months with an all-time high in created revenue with our Android App. The new app not only outperformed the old one economically, but startup time also went down by 3x. Also by not carrying around the Xamarin overload anymore, our app size went down by 5x and is now below 10 MB.</p><h3>It won’t stop here</h3><p>Not taking too much of a rest we went on to release our app to our French customers by the end of May this year. This effort will be extended in Q3 and beyond. On top, we will see more A/B testing to continuously provide more value to our customers.</p><p>You as the reader might recall that we completely stepped out of development to create our new Android app in June 2017. Well, this was also true for our iOS app. So from the beginning of 2018, we also started investing heavily in its re-development. A tremendous team effort with some help from third parties led to its projected completion at the beginning of Q3. This feels pretty exciting and the past year has truly been an incredible learning time for the complete team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f66bed9b882" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Here’s what I learned from 18 months into bilingual parenting]]></title>
            <link>https://medium.com/@rajko.winkler/heres-what-i-learned-from-18-months-into-bilingual-parenting-9e19067abdc8?source=rss-daef0f02b321------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e19067abdc8</guid>
            <category><![CDATA[children]]></category>
            <category><![CDATA[language]]></category>
            <category><![CDATA[bilingualism]]></category>
            <category><![CDATA[bilingual]]></category>
            <category><![CDATA[parenting]]></category>
            <dc:creator><![CDATA[Rajko Winkler]]></dc:creator>
            <pubDate>Wed, 07 Feb 2018 20:45:39 GMT</pubDate>
            <atom:updated>2023-01-17T08:33:15.390Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TZrDHXA-nJnT1bKJL__J3A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/dSUfc_Qr0Fc?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Milada Vigerova</a> on <a href="https://unsplash.com/search/photos/parenting?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I’m a German father living in Germany raising our child in English. So far I’ve followed this path for the first 18 months of his life and I’m more convinced than ever that this is the right thing (for us) to do. Read on to find out why.</p><p>The idea to raise our child bilingually came up a couple of months before birth. I had just returned from a job interview which was held in English without prior notice but it went smoothly nevertheless.</p><p>I think what helped me was a decent level of both writing and speaking English. As a student, I was fortunate enough to take part in an exchange program, so I got to spend my 11th grade abroad. Throughout my entire academic and work career, this was highly beneficial, sometimes even enabling opportunities only because of this advantage.</p><p>So while I felt good about that part, another big doubt arouses: I’m lacking a natural and cultural background, and English is not my mother tongue. Hence the question, with this drawback, am I capable of fulfilling something that significant for our child? How big of a blocker is it?</p><p>Turns out: It’s not in our way, but some doubts remain, I’ll come back to this topic. On the other hand, so many sources indicated that this is not a must. Instead, they suggest it’s the steadiness and the long-term commitment that is much more important.</p><p>Great, so we are convinced, let’s go for it, what can go wrong? It started off slowly. First I only had to prevent switching back and forth between the languages. Also, part of the process was to accept not knowing all the necessary vocabulary right away. From time to time I compensated for this gap by looking up some words or asking friends. Overall, in the beginning, it’s your voice that is important, the rest can be learned over time, that’s for sure.</p><p>However, I didn’t go out telling everybody right away. The grandparents knew beforehand, some were skeptical. Everybody else was about to find out gradually.</p><p>In retrospect, this proved to be hard. In certain situations (for example let’s take the waiting room at your child’s doctor&#39;s) this can make you feel uncomfortable because it might seem odd to speak to your child in a foreign language and, in the next moment, to walk up to the counter and speak in fluent German. While it shouldn’t bother one much, trust me it did bother me.</p><p>The question is why? Maybe it’s because in Germany as in many other western non-English speaking countries, there’s an ongoing controversy about cultural values. With borders vanishing people fear losing some of their “identity”. It’s taken for granted that the language spoken usually is one of the strongest ties to one’s culture and therefore should be protected. That’s why some Germans strongly oppose new trends like English-only bars in hipster Berlin-Mitte.</p><p>So how can I circumvent possibly unpleasant feedback: I learned the best approach is to boldly step forward and just expose others to the situation proactively. Make them find out without hesitation. Stand that moment of skepticism and you’ll most likely find yourself in a small chat right after that if people are interested. And even if not, sometimes you can and should simply ignore what others might have to say.</p><p>The most important thing is: You need to take the initiative, don’t let the fear of intimidating situations hold you back. You are the one that has this idea implanted while others might not (yet) foresee the potential future benefits of those efforts taken.</p><p>In the meantime how did we adjust? We continue following the path of me speaking English, and my wife speaking German with him. In addition, we sing and read books to him. The “Gruffalo” which he already very much reacts to, is read to him in both languages. Also, we ordered some of the rather annoying talking toys in both languages.</p><p>To enhance the exposure to the language a little more, we ask every native English speaker among our relatives and friends to speak English to him. In addition, his Kindergarten group happens to have a total of four other language backgrounds, so multiple languages are part of their culture. It is to be said though that this was by coincidence, we didn’t go out looking for a multi-language place.</p><p>As a result, he’s already understanding very well. We can ask him about himself (“Where is your nose, your ears?”) or about things we see around us (“Where is the clock, the lamp?”). We intentionally ask things in both languages, and he happily points at each and everything. I can even ask him to put away the LEGO bricks. Sure some of that is anticipation or is working because of repetition. But that’s what learning is about and the second language is everything but in his way.</p><p>He’s in the process of starting to speak, he has the five things he can name and point to, and it’s quickly picking up. We are eager to see what the next steps will be and we are fascinated with what we already see him do.</p><p>So far the effort needed has been moderate, it is a different mindset, though. But if you have ever tried to learn another language as an adult, you know how much effort it takes to “switch”, to translate, and to find the appropriate words. Think about it, with him being a child he doesn’t even realize he’s “speaking” two languages.</p><p><strong><em>Part of stepping forward boldly can also be to share thoughts, exchange ideas, and hear other stories. So the first step has been taken. I’d love to hear from others about their experiences in raising a bilingual child. So feel free to comment, ask or discuss.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e19067abdc8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>