<?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 Caleb Andersen on Medium]]></title>
        <description><![CDATA[Stories by Caleb Andersen on Medium]]></description>
        <link>https://medium.com/@CalebAndersen_64831?source=rss-d92fbb9ede8c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*iNnAUcgWaDHFoTraXFmpew.jpeg</url>
            <title>Stories by Caleb Andersen on Medium</title>
            <link>https://medium.com/@CalebAndersen_64831?source=rss-d92fbb9ede8c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:38:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@CalebAndersen_64831/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[October 2020 — End of the Month Update]]></title>
            <link>https://medium.com/nativshark/october-2020-end-of-the-month-update-d5ffd12f3b62?source=rss-d92fbb9ede8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5ffd12f3b62</guid>
            <category><![CDATA[nativshark]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[updates]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[japanese]]></category>
            <dc:creator><![CDATA[Caleb Andersen]]></dc:creator>
            <pubDate>Tue, 03 Nov 2020 13:08:23 GMT</pubDate>
            <atom:updated>2020-11-03T13:08:23.435Z</atom:updated>
            <content:encoded><![CDATA[<h3>October 2020 — End of the Month Update</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eKUqvsE4FA9APTSBhydJjA.jpeg" /></figure><p>Hi everyone,</p><p>I feel like I say this every month but... Another month down! Can you believe it?</p><p>It’s November now.</p><p>Anyhow, let’s take a look at October.</p><p>Change is in the air. October has been an eventful month for NativShark. Our focus has been: “Simplification.”</p><p><strong>What that looks like:</strong></p><ul><li>Consolidate our operations to just Fukuoka and Bellevue.</li><li>Simplify pricing plans.</li><li>Massively speed up the platform’s performance.</li><li>Simplify development process.</li><li>Simplify the student flashcard experience.</li><li>Establish new content creation flows to work in the interim before our new content management platform is ready.</li><li>Kicked off our livestreaming and other media efforts to continue to strengthen our community.</li><li>Focus on building the company in a financially sustainable manner. NativShark’s gotta make it in the long term if we’re going to make the biggest impact we can.</li></ul><h4>Community / Media:</h4><p>We have a livestream now! And we’re active on Instagram and YouTube. Come check us out.</p><p>Here’s our <a href="http://nativshark.tv/">Twitch</a> where we stream most days of the week:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.twitch.tv%2F%3Fchannel%3Dnativsharktv%26muted%3Dtrue%26parent%3Dcdn.embedly.com&amp;display_name=Twitch.tv&amp;url=https%3A%2F%2Fwww.twitch.tv%2Fnativsharktv&amp;image=https%3A%2F%2Fstatic-cdn.jtvnw.net%2Fjtv_user_pictures%2Fb1188494-be9e-4212-b525-a1a2a00c43f3-profile_image-300x300.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=twitch" width="620" height="351" frameborder="0" scrolling="no"><a href="https://medium.com/media/099a13e4deb35f3565b3fb5662137bd3/href">https://medium.com/media/099a13e4deb35f3565b3fb5662137bd3/href</a></iframe><p>Our <a href="https://www.youtube.com/channel/UCSN6MYC4fYAZGvt2sBzBfDg">YouTube</a> and our most recent video we put up:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FhMJv8PCeT0E%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DhMJv8PCeT0E&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FhMJv8PCeT0E%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/cf3982734721b7113388de5e7b35d04e/href">https://medium.com/media/cf3982734721b7113388de5e7b35d04e/href</a></iframe><p>And finally our <a href="https://www.instagram.com/nativshark/">Instagram</a> where we make daily posts involving factoids about Japan, our word of the day, and yojijukugo. Here’s a peek at the first slide of a recent post:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*cLb7OyCOcMd-z1qCpCOwpw.jpeg" /><figcaption><a href="https://www.instagram.com/p/CHEnHUFnJ1s/">Click here to read the full post!</a></figcaption></figure><p>We’ve also been doing a lot in our community on Discord lately. We have events that are streamed with student participation weekly, there’s been so much good vibes and Japanese practiced by everyone. Really proud of some of our new students, they’re doing so well! You should check out our streams to see ^^ We’ll also get highlights up on YouTube soon.</p><p>Additionally, we’ve updated the discord server a lot. The roles are now sorted by streak! <a href="https://www.nativshark.com/tools/community">You can link your NativShark and Discord account.</a> That way no matter what you’re studying with NativShark, you can show up how boss your streak is. (or if you’re like me uhh, how you’ve accidently missed a day here and there. Streak saver when??).</p><p>Anyway, come join, it’s a great place to connect with fellow students: <a href="https://discord.gg/nativshark">https://discord.gg/nativshark</a></p><h4>Content Production:</h4><p>It’s been about 6 weeks since we last posted Phase Two content.</p><p>The main reason for this is that the content production workflows used to build Phase One were not sustainable long-term with how much content we are working towards producing. More on that in a bit.</p><p>So, rather than slowly put out content and further delay sustainable content production, we’ve put it on hold and spent October reviewing the processes and figuring out what they should be in the future. Now we’re looking at what we can do in the interim before a new content management platform is built.</p><p>We have come up with combinations of various technologies and workflows that we’re going to be testing in November and onward. As such, we hope to resume consistent content releases soon — faster than any single student could hope to keep up.</p><h4><strong>Company Direction:</strong></h4><p>NativShark is going multilingual next year.</p><p>Actually, we’re <em>going beyond languages entirely</em> and will begin offering the same highly comprehensive educational experience in other non-language fields.</p><p>It’s too early to announce which subjects we’ll be working on offering first, but I wanted to let you all know that <strong>this is something we’re working towards</strong>. There are a <em>ton</em> of moving parts and work to be done for NativShark to go multilingual and beyond, so we are still quite a ways out, but the initial framework is being put in place. Since it’s confirmed that we’re headed in this direction, I thought you all should know.</p><p>Though we can’t share which non-language topic we’ll be working on first yet, <em>the first languages we’ll be offering have been decided</em>.</p><p><strong>We’ll be bringing:</strong></p><p>English<br>Korean<br>Spanish</p><p>To the NativShark platform.</p><p>We’ll be building them as language <em>pairs </em>as well. This means that each language will learnable from each other language. So Japanese, English, Korean, and Spanish language pairs represent 12 language directions.</p><p>Here’s a screenshot from our business plan docs:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*--TqkWyzXierG_wEEx7rsw.png" /></figure><p>We’re setting up our new content production methods so that, in addition to helping us publish Japanese content more regularly, we’ll be able to easily transfer to whatever other languages we might want to teach. So that’s how this will be doable. I’m really, really looking forward to it.</p><p>The other big effort we’d like to see out of 2021 is getting native mobile app support for our platform.</p><p>Once we have app support and teach several languages, NativShark will be truly unstoppable. If you’re just as excited about this future as I am, thank you! I appreciate your energy.</p><p>The more we’re able to spread awareness of NativShark and the larger our subscriber base grows, the more we will be able to bring all of these plans into reality. It’s a long game process for sure, but the more everyone shares and talks about NativShark, the more exposure it generates. It really does make a difference. Additionally, if you’re interested in our mission and you’re an investor or have expertise you’d like to share with us, please do reach out! contact@nativshark.com</p><h3>Significant improvements in the most recent update:</h3><p><strong>Speed —</strong></p><p>We changed the way the site is rendered, and it now performs <em>significantly</em> better than before.</p><p><strong>Flashcards &amp; learning new material —</strong></p><p>We updated the flashcard answer buttons to simplify the mental load on responses to help students more efficiently and effectively get through flashcard sessions. They’re now simple emoji.</p><p>The response to this from students has been really amazing :) Many people are reporting much faster flashcard sessions!</p><p>We also updated the new card information view, <em>but it isn’t complete yet.</em> It’s only a partial implementation and more work has yet to be done there. We’re monitoring feedback and student usage data closely to get all of your input as we finish up the version of this new implementation that we’re working on.</p><p>That said, what we’re turning it into is the first time you see new material that will show up in flashcards, it isn’t like a flashcard. It’s a special tool for learning new material, which then feeds your flashcard system.</p><p>As such, the first time you view new information, one should not be thinking about it as a flashcard going forward. Rather, it’s just “first time exposure,” as if someone had spoken it to you in a real conversation, on a TV show, or something you read in a book, where it just happens that you’re thrown into and immersed in the real word with something you didn’t know before. Then when you see it next — in your flashcards, that’s when you start rating how you feel about your familiarity with it using the new flashcard options.</p><p>So the two systems play into each other in order to create a more streamlined process.</p><p>Flashcards are not and should not be thought of as a tool to learn new information. If flashcards are being used to learn new information, they’re being used wrong. Likewise, if there is too much information on a flashcard, they’re being used wrong.</p><p>As such, our first iteration of flashcards had some of these issues, and we’ve now taken the first strides towards fixing and improving the experience immensely.</p><p>At some point I’ll get into a full discussion on the topic of flashcards, either in an article or on our <a href="http://nativshark.tv/">stream</a>. There’s much to talk about here and a lot to get excited for with where NativShark is headed!</p><p><strong>Pace slider —</strong></p><p>We removed the 1 year pace option. It was always an experiment, and from the data we could tell it wasn’t working well for the platform.</p><p>NativShark is supposed to simplify the learning experience and set the learner up for the highest chance of success in their target goals. The one year pace was counterproductive to this effort.</p><p>For those who have extra study time after going through their Today’s Studies, we’re working on getting more review tools and Extra Credit stuff together. For example, we should have the ability for you to manually add in / self report your immersion time soon.</p><p>Additionally, with the removal of the 1 year pace option, we will be adding in a 3 year pace option. Long term, being able to set a more precise variable time between 2 and 8 years is certainly on the table. For now, it will still need to be set in year-long increments.</p><p><strong>Pricing —</strong></p><p>We updated our pricing plans. We got rid of the different tiers and simplified things to just have one product that you’re subscribing to. You can now pay monthly, annually, or once with lifetime.</p><p>Our initial pricing plans, aside from being really confusing to students, were also not sustainable for the company to maintain.</p><p>With this change, we’ve been seeing strong initial responses and good feedback from new students on how it is a nicer and more simple experience.</p><p>With more exposure, NativShark should hopefully be on its way to being profitable.</p><p>If you’re interested in this business side of NativShark, Niko and I are starting a podcast on our twitch on Wednesday mornings, JST. More info on that soon.</p><p>That pretty much covers the highlights from the last month~</p><p>Looking forward to the next month. Lots coming up, excited to share. November will be a good month.</p><p>Thanks as always. Stay safe!</p><p>~ Caleb</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5ffd12f3b62" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nativshark/october-2020-end-of-the-month-update-d5ffd12f3b62">October 2020 — End of the Month Update</a> was originally published in <a href="https://medium.com/nativshark">NativShark</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[September 2020 — End of the Month Update]]></title>
            <link>https://medium.com/nativshark/september-2020-end-of-the-month-update-bca00c865d3b?source=rss-d92fbb9ede8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/bca00c865d3b</guid>
            <category><![CDATA[updates]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[japanese]]></category>
            <category><![CDATA[nativshark]]></category>
            <dc:creator><![CDATA[Caleb Andersen]]></dc:creator>
            <pubDate>Wed, 30 Sep 2020 07:27:48 GMT</pubDate>
            <atom:updated>2020-09-30T07:40:10.378Z</atom:updated>
            <content:encoded><![CDATA[<h3>September 2020 — End of the Month Update</h3><p>Hi everyone 👋</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*os31gUNXzKX0msqvaUPXfw.jpeg" /></figure><p>We’re at the end of September. Yet another month down! And now the seasons are beginning to change :)</p><p>September has been a busy month for NativShark. Lots of work happening. Let’s get into it✨</p><h3>What we’ve been up to</h3><h4>Development</h4><p>Lots of content fixes ^_^ As well as a couple of tricky bugs early on in the month. For the second half of September, the development team has been working on a total re-work of our theming system in order to massively improve site speed and performance.</p><p>That update is set to come out very soon. Be sure to keep an eye on our <a href="https://twitter.com/nativshark_">twitter</a> and <a href="https://discord.gg/nativshark">discord community</a> for updates. Our testers have been saying things like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*KMPKH5SewIXG4nrTxpSyWQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/927/1*CE5Qz89a6Y9HlkY4q-evuA.png" /></figure><p>So that’s a feels good :) NativShark will now be buttery smooth, just as it should be.</p><p>In addition to the performance improvements, there are some other highly requested QoL changes (e.g. Premium students can now adjust their minimum Shadow Loops looping defaults to below 3). Take a read of the patch notes for full details on the update.</p><h4>Students</h4><p>We’ve seen many students maintain their perfect streaks for 6 weeks straight, quite exciting.</p><p>And over 3 million student events have transpired on the site with nearly 3 years total study time! Keep up the good work everyone, you’re nailin’ it.</p><p>Additionally, we’ve received even more fantastic feedback on our feedback site. It’s lead to some great conversations in the community and on the forums regarding how students are enjoying the platform and in what ways we can make it better.</p><p>Our feedback site: <a href="https://feedback.nativshark.com/">https://feedback.nativshark.com/</a></p><p>We had our first students hit their 30 day streaks and join the “Torch Club” this month:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/892/1*HkLT-75xp6TrT7FOJQP9HA.png" /></figure><p>That was really exciting!</p><h4>Content</h4><p>We released the first 7 Units of Phase Two this month, with more set to release next month.</p><p>Additionally, we began firing up the extra content production &amp; community engagement engines. We started a couple new series on our Instagram:</p><ul><li><a href="https://www.instagram.com/p/CFF8E8FH5mw/?utm_source=ig_web_copy_link">引っ込んだ - to withdraw - is our Word of the Day!⁠ ⁠ What situations might you find this phrase useful?⁠ ⁠ .⁠ .⁠ .⁠ ⁠ #nativshark #learnjapanese #japanese #wotd #wordoftheday #studyjapanese #japaneselanguage #studyjapanese #japan #explorejapan #traveljapan</a></li><li><a href="https://www.instagram.com/p/CFV1wntn141/?utm_source=ig_web_copy_link">一心同体 - two hearts beating as one.⁠ ⁠ Yomigana: いっしんどうたい⁠ ⁠ .⁠ .⁠ .⁠ ⁠ #nativshark #learnjapanese #japaneselanguage #studyjapanese #japanese #japan #idioms #traveljapan #learnkanji #kanji #kanjiaday</a></li><li><a href="https://www.instagram.com/p/CFVk1L_nDpM/?utm_source=ig_web_copy_link">Where did Kanji come from? You might be surprised at the answer!⁠ ⁠ .⁠ .⁠ .⁠ ⁠ #nativshark #japan #japanfacts #kanji #kanjiaday #history #japanhistory #traveljapan #explorejapan #travel #travelfacts #learnjapanese #japaneselanguage #studyjapanese #japanese</a></li></ul><p>We started some chill hangout streams on our Twitch channel, NativSharkTV: <br><a href="https://www.twitch.tv/nativsharktv">https://www.twitch.tv/nativsharktv</a></p><p>Made a lo-fi beats mix:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F9MS2Dv_xa_4%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D9MS2Dv_xa_4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F9MS2Dv_xa_4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/199325a11188fb0f27b1b0182fc0768c/href">https://medium.com/media/199325a11188fb0f27b1b0182fc0768c/href</a></iframe><p>And Chengaiz started a Study Vlog to document his learning progress:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FqTTzHoUY9B0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DqTTzHoUY9B0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FqTTzHoUY9B0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a62d14873a78bac3bf40e67af9a455e1/href">https://medium.com/media/a62d14873a78bac3bf40e67af9a455e1/href</a></iframe><p>Lastly, we put out a press release:</p><p><a href="https://medium.com/nativshark/nativshark-language-learning-made-simple-1973679ceeb0">NativShark: Language learning made simple.</a></p><h4>Management</h4><p>Hoping that the world opens up ever so slightly so that some of our long-lost team members can re-enter Japan… Will just try to remain optimistic that things will improve in that regard :)</p><p>In the mean time, we’ve gotten pretty good at being a globally dispersed remote team haha. I talked a bit about that on stream the other day, chat was asking about it — good conversation.</p><p>Additionally, as an ever-evolving product and company, we’ve been closely analyzing the usage of the pace slider and have determined that we need to remove the ability to turn it off. We’ve removed the 1 year pace as well.</p><p>There is a full post coming on this pretty soon, as it deserves one of its own… but in short, it ended up not working well for students, and sort of broke NativShark. We put those options in from the start as a test, and we learned a lot. Very exciting that we’re able to adapt to data and feedback and tune the platform in response!</p><p>Having come from teaching in other ways and through 3rd party platforms... Having our own software platform really is a dream :D</p><p>Another thing we’ve been monitoring closely is our pricing as we’re on the ever-important startup quest of hitting profitability💪</p><p>We’ve received such a fantastic overall response to the product that, now as a management team, we’re settling in and thinking long and hard about how to optimize things such that we can continue to grow our subscriber base. Both through better awareness and outreach around NativShark, and in making the pricing be rewarding while making sense.</p><p>Much like with learning a language, there’s always ways to improve!</p><h3>What’s coming up</h3><p>This past month, after reviewing all the usage data and tons of student feedback, we’ve managed to come up with the direction we’re taking the platform over the next 6 months and let me just say — I’m SO excited about where we’re going.</p><p>The DesignOps team got together and had an Architecture Sprint where we essentially built the “blueprints” of what we’re internally calling “NativShark 2.0,” as it is that much of an improvement. I can’t give away too much yet but… Just saying it’s amazing. In the coming monthly updates we’ll be sharing more and more about where things are headed.</p><p>For the time being, with NativShark 1.0 we’ll continue putting out QoL updates and making things better for students while we lay the foundations of NativShark 2.0.</p><p>Our main development focus as part of this will be on a massive improvement to our Content Management Platform (CMP). It needs to be re-worked so that the content team can properly publish Units at a faster pace. On the current CMP... well, essentially, it “works” and that’s all there is to say about it. That needs to change before Phase Two content and beyond can come out quickly.</p><p>Additionally, we need to get the CMP updates in so that we can introduce the new review tools and such that we’ve been designing. These new review tools should drastically improve the “I finished my Units for today but I want to study more” experience, along with generally helping new content stick in the mind easier. More about this as we get closer to their release…</p><p><strong>In short:</strong></p><ul><li>Continued QoL updates on the platform</li><li>More phase two Units</li><li>Dev team to focus hard on new content management platform (CMP) to unlock the future.</li><li>More community content, events, videos, etc.</li></ul><p>Thanks for reading this month’s update and I’m really looking forward to what October has in store.</p><p>Keep up the good work on your studies~</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bca00c865d3b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nativshark/september-2020-end-of-the-month-update-bca00c865d3b">September 2020 — End of the Month Update</a> was originally published in <a href="https://medium.com/nativshark">NativShark</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[August 2020 — End of the month update]]></title>
            <link>https://medium.com/nativshark/august-2020-end-of-the-month-update-b1799b8c3249?source=rss-d92fbb9ede8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1799b8c3249</guid>
            <category><![CDATA[launch]]></category>
            <category><![CDATA[language-learning]]></category>
            <category><![CDATA[japanese]]></category>
            <category><![CDATA[nativshark]]></category>
            <category><![CDATA[edtech]]></category>
            <dc:creator><![CDATA[Caleb Andersen]]></dc:creator>
            <pubDate>Thu, 03 Sep 2020 03:15:42 GMT</pubDate>
            <atom:updated>2020-09-03T06:29:24.593Z</atom:updated>
            <content:encoded><![CDATA[<h3>August 2020 — End of the month update</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T1iTtaIJaLv1zAY5ThdZiw.jpeg" /><figcaption>We named the context menu on the bottom right of the site “Context-Kun” and Chie drew him a profile picture 😂</figcaption></figure><p>1 year.</p><p>That’s how long it took us to go from designs in Figma to a platform students could use.</p><p>That’s also the amount of time students have spent studying Japanese with NativShark in the first 20 days of the platform being live.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/365/1*xI9WGRTXrE2G9fK_sV9uCw.png" /></figure><p>Take a look here for most updated stats: <a href="https://www.nativshark.com/roadmap">https://www.nativshark.com/roadmap</a></p><p>We did it.</p><p>Anyway, hi everyone 👋</p><p>August has just ended, I’m writing this on September 2nd. It was a great (possibly the best yet?) and very busy month for NativShark.</p><p>We started the month with a clear goal: Launch the product.</p><p>The full team went into overdrive and really pulled together. Our project management became something of legends. I think some may have had their doubts if you had seen where we were at on August 1st, but I believed in our team and knew we’d pull through.</p><p>I’m honestly blown away with what we’ve accomplished with such a small team. Every team member has grown in their abilities so much in the past couple months, and as a company we’ve learned a lot.</p><p>It’s a good feeling to see things actually come together after months of pushing and uncertainty.</p><p>But now we’re near 10,000 students and we have more than 1 year of student study time on the platform in such a short time! Amazing.</p><p>That said, this is only the beginning. After a short rest for the team, we got right into improving the performance on the site and planning our roadmap.</p><p>We’ve been receiving feedback and feature requests on our feedback site: <a href="https://feedback.nativshark.com/">https://feedback.nativshark.com/</a> which has been an excellent resource to help direct our planning. Hearing your direct comments on the experience of learning with NativShark is and will continue to be key in building the best language education platform possible.</p><p>We also put out some videos in August, one of which was a quick Q&amp;A video with questions from around the first week of launch, take a look:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F9Rp-DQNABFY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D9Rp-DQNABFY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F9Rp-DQNABFY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/dad88d1814359ac2d4b1afb6ae7e6915/href">https://medium.com/media/dad88d1814359ac2d4b1afb6ae7e6915/href</a></iframe><p>Now that it’s out, students are learning, and feedback is rolling, it’s time to perfect and scale. Speaking of which…</p><h3>Where we’re at now</h3><p>The core experience is online. People are learning Japanese.</p><p>That said, currently there are some issues and missing features that we’re addressing.</p><p>The biggest one currently is that kanji learning is not introduced well.</p><p>We’ve been looking at this very closely and have worked out a better introduction and a near-full redesign to the learning experience. We’ll be testing prototypes with the testing group soon.</p><p>Perhaps we could have an entire blog post on the new method once it’s ready… Let me know if you’d be interested.</p><p>Another issue we’ve identified is with the first 30 or so Units. Unless you’re completely 100% new to the language, or you have a ton of interest in travelling to Japan soon, we feel the choice to introduce nearly only travel lessons was misguided. While a lot of those lessons are amazing, having so many at once can be tiring.</p><p>We’re improving this as well.</p><p>The last issue I want to draw attention to is the lack of a level / placement test. This is largely because only Phase One is out, and we want to be careful with how we implement such a feature. It is done notoriously poorly in the learning community and we want our Level Check Mode to be meaningful.</p><p>That said, we’ve definitely always wanted to do it so I can say: “Level Check Mode” is coming eventually 👍</p><p>There’s a couple more minor things we’re adjusting like the in-Unit flow of Today’s Studies and how / where the “My Journey” circles can show up to let you know what part of the Unit you’re in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*adaNs8krNEO3gQLvAc3Fwg.png" /><figcaption>We want to be able to see these lovely progress circles from more places!</figcaption></figure><p>All I can say is I’m <em>so</em> glad to have it released so we can get real data from thousands of students. I want to say a massive thank you to everyone who has contributed to our feedback forums and in the discord community.</p><p>I think one of the best things about NativShark, and why I’m so thankful to be a part of it, is how much growth potential there is in the platform and how committed we are to constantly improving the platform over time. There’s no reason it should just sit and be static. It’s well past time for Language Education as Live Service. Thrilled to be the ones doing it ✨</p><h3>Where we’re headed</h3><p>So that’s where we’ve been and where we’re at. Time for a bit of a look at what’s down the line.</p><p>In the next week or so, we have some more performance optimizations coming out and minor improvements.</p><p>Then, we’ll be focusing on our Content Management Platform again so the content team can be much more efficient, even while they’re still such a small team. And because our engineering team is so small, it’ll take the whole team’s focus.</p><p>But, this time will give us the focus we need to clean up some of our architecture choices that were made to get the launch out 😅</p><p>The content team will be publishing some Phase Two content, and then working on their improvements to Phase One before going back to publishing loads of Phase Two content as they complete it.</p><p>During all that, we’ll have had time to finish designing and testing our nicely sized update to the Student Experience, bringing the solutions to what I mentioned in the previous section.</p><p>At this point, we’re far enough down the timeline that it’s hard to say exactly what will be next, but a native mobile app and prepping for going multi-lingual are high on the list.</p><p>As always, one step at a time.</p><p>See you in the next one 🌊</p><p>~ Caleb</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1799b8c3249" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nativshark/august-2020-end-of-the-month-update-b1799b8c3249">August 2020 — End of the month update</a> was originally published in <a href="https://medium.com/nativshark">NativShark</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NativShark 1.0 — We’re live.]]></title>
            <link>https://medium.com/nativshark/nativshark-1-0-were-live-f1fcd869030a?source=rss-d92fbb9ede8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1fcd869030a</guid>
            <category><![CDATA[education-technology]]></category>
            <category><![CDATA[japanese]]></category>
            <category><![CDATA[language-learning]]></category>
            <category><![CDATA[nativshark]]></category>
            <category><![CDATA[launch]]></category>
            <dc:creator><![CDATA[Caleb Andersen]]></dc:creator>
            <pubDate>Fri, 14 Aug 2020 06:53:52 GMT</pubDate>
            <atom:updated>2020-08-14T06:53:52.710Z</atom:updated>
            <content:encoded><![CDATA[<h3>NativShark 1.0 — We’re live.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*JJTvqRdqKfQZzUuGuuzGAA.gif" /><figcaption>It’s happening.</figcaption></figure><p>We’ve launched the core NativShark experience. It’s been a long time coming and an <em>insane</em> level of work, but the team pulled together and we made it happen.</p><p>We put together some videos, we’ll have a couple more on the way in the next month as well.</p><p>Here’s how NativShark helps you learn Japanese:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FDXGDHiQ4gVM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDXGDHiQ4gVM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDXGDHiQ4gVM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/df6626435c57857c8ef50c043e1caf4a/href">https://medium.com/media/df6626435c57857c8ef50c043e1caf4a/href</a></iframe><p>Here’s a video of Niko and me talking a bit about why we founded NativShark.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FNScNmp4GJ7g%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DNScNmp4GJ7g&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FNScNmp4GJ7g%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/335ac374c95899644033daf4fb6b0010/href">https://medium.com/media/335ac374c95899644033daf4fb6b0010/href</a></iframe><h4><strong>Our development of the student platform and what we’re working on is now viewable by users of NativShark</strong></h4><p>If you want to see what we’re working on, you can check out our feedback site here: <a href="https://feedback.nativshark.com/">https://feedback.nativshark.com/</a></p><p>Our roadmap here: <a href="https://www.nativshark.com/roadmap">https://www.nativshark.com/roadmap</a></p><p><strong>We welcome your participation.</strong></p><p>All feature requests can be sent here: <a href="https://feedback.nativshark.com/feature-requests">https://feedback.nativshark.com/feature-requests</a></p><p>All lesson and content requests here: <a href="https://feedback.nativshark.com/lesson-requests">https://feedback.nativshark.com/lesson-requests</a></p><p>All errors, issues, bugs and unexpected / strange behavior goes here: <a href="https://feedback.nativshark.com/bug-reporting">https://feedback.nativshark.com/bug-reporting</a></p><p><strong>Check out the change log for the Day 1 patch: </strong><a href="https://feedback.nativshark.com/changelog/nativshark-day-one-patch">https://feedback.nativshark.com/changelog/nativshark-day-one-patch</a></p><p>I’ll do a monthly update later as usual at the end of August where I’ll go more in depth about how things have gone.</p><p>For now, sign up and hit “Study Now” <br><a href="https://www.nativshark.com/">https://www.nativshark.com/</a></p><p>~ Caleb</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1fcd869030a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nativshark/nativshark-1-0-were-live-f1fcd869030a">NativShark 1.0 — We’re live.</a> was originally published in <a href="https://medium.com/nativshark">NativShark</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[July 2020 — End of Month Update]]></title>
            <link>https://medium.com/nativshark/july-2020-end-of-month-update-4771f352d3c7?source=rss-d92fbb9ede8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4771f352d3c7</guid>
            <category><![CDATA[learn-japanese]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[nativshark]]></category>
            <category><![CDATA[monthly-update]]></category>
            <dc:creator><![CDATA[Caleb Andersen]]></dc:creator>
            <pubDate>Sat, 01 Aug 2020 00:19:06 GMT</pubDate>
            <atom:updated>2020-08-01T00:19:06.696Z</atom:updated>
            <content:encoded><![CDATA[<h3>July 2020 — End of Month Update</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y-Ur4b25osa1MZ2JmTLbLQ.jpeg" /><figcaption>Artwork for “The Process” section of Using NativShark</figcaption></figure><p>Hi everyone 👋</p><p>Fortunately, July has been another strong month.</p><p>We expanded the community tester group and opened the platform to them to get in there and break as much as possible so as to provide a much smoother experience for the public launch.</p><p>We nearly made a full July launch, but it looks like we’ll have things ready for the public come mid to late August.</p><p>So let’s get into it a bit.</p><h3>Progress Report</h3><p><em>A look at what’s been going on during the month of July in Management, Content, Community and Development at NativShark.</em></p><h4>Management</h4><p>This month we’ve brought in Canny, which is a reporting and feedback forum for us to use in our development. It allows students to post feature requests, lesson requests, and bug reports easily.</p><p>We’ve integrated it with our internal systems as well. So when we’re working on something you’ve suggested or reported, you’ll be notified of the progress made in development on that feature or lesson.</p><p>Additionally, we’ve begun using it for our own internal feature and lesson planning. For example, if you take a look at “lesson requests” now, there’s a good many of them and we’re updating their status as they move along the publishing timeline.</p><p>We implemented Canny just before we brought on the community testers and I must say, it’s worked quite well. We’re very happy to have it and it’s made the reports received from testing <em>much</em> easier to work with and track, especially because it links to our internal backlogs so easily. When we update the status of the task internally, it is automatically reflected in the Canny post status.</p><p>It’s really nice to have what’s being worked on out there. If you’d like to, you can take a look at it here: <a href="https://feedback.nativshark.com/">https://feedback.nativshark.com/</a></p><p>We’ve three public boards:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tB6WpH7G8jRo28gmHfjcVQ.png" /></figure><p>Our discord community has an integration set up as well that posts the feature request and lesson request reports directly to the feedback channel. After public launch, we’ll be handling our changelogs through Canny as well.</p><p>We really are working to build a platform that people will love, use and learn from. I believe that requires direct feedback from those paying to use the platform and being responsive to said feedback as much as is reasonable.</p><p>The response and helpfulness of the testing community already has shown this to be true. Thank you to all who are a part of that group!</p><p>Just yesterday, Niko and I filmed a video with the media team where they interviewed us about why we’ve made NativShark, our plans for it, and how it fits into language learning.</p><p>It was pretty fun to make and I’m looking forward to when Chengaiz has the edit of the video done. We uhh... Ended up talking for nearly an hour :P He’d ask us one question and we’d have a 20 minute answer. I suppose we just have a lot to say. I imagine he’ll have fun editing it.</p><p>If it goes well and if the community would like it, we’re open to starting a series of videos about NativShark, Japanese and language learning.</p><p>Due to COVID, we did it all remote as well. Chengaiz acted as a remote director and interviewer, and so as to avoid as much contact with anyone as we could, we filmed it out of our studio apartment.</p><p>Here’s some photos —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pU0HRhng6en2jsXR4W2sDg.png" /><figcaption>Chengaiz and Chie directing over Discord.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zexhbaItV58m0Ev2pgrQKw.jpeg" /><figcaption>Niko and me, deeply focused.</figcaption></figure><p>Good times.</p><h4>Content</h4><p>The content team has accomplished all their “what’s left” tasks as per the <a href="https://medium.com/nativshark/june-2020-end-of-month-update-6ef0edd396fb">June monthly letter</a>, which is great news.</p><p>All Phase One core content is in.</p><p>They finished this past week, and have since been working on helping make things more clear based on tester feedback while also writing “Lesson Cards,” which are short pieces of info that show up during a Unit to help explain and give context to certain aspects of learning.</p><p>Additionally, they’re working on Using NativShark articles, which help explain parts of the NativShark platform, whether that be about our Tools, Process, Logistics of learning, or the team itself.</p><p>With the time that’s left from now until launch in August, they intend to work on potentially a couple of Extra Credit lessons for Phase One, and perhaps more importantly, the first few units of Phase Two. Niko has said he’d like to have 5–10 units of Phase Two ready just after launch.</p><p>We’re working to get a consistent publishing schedule in place for Phase Two units. Such that if one were to start Phase One at launch at the standard pace, they would never be ahead of the content team as far as new content goes.</p><p>Really exciting stuff this month from the Content team, and I know they can’t wait for all of you to get in and start using it. They’re craving feedback, I can tell 😃</p><h4>Community</h4><p>We’ve made a couple changes to the layout and organization of the Discord server.</p><p>We intend to have your Discord account be able to be linked with your NativShark account. This will give NativShark subscribers access to special channels, as well as the ability to easily share things like your stats and streaks in the future.</p><p>We’d also like to bring in the ability to use chat commands in Discord to bring up lesson summaries and things like that to make it easier to share and discuss your learning journey with fellow students.</p><p>So certainly stay tuned as we improve that Discord integration with NativShark.</p><h4>Development &amp; Design</h4><p>As I’ve mentioned above, we grew the tester community to around 20 members this month and have had them in the platform and using it for just over a week.</p><p>As expected, initially there were some pretty intense bugs with the system. Once spotted by multiple people, though, we could reproduce them locally and get them fixed.</p><p>Over time, the initial bumps were smoothed out and things are coming along well now. At first, Jacob was coding like crazy and fixing things up while the rest of the dev team was still working on final touches to a couple crucial UX features. Things like a guided tour that shows when first viewing something new that we’ve nicknamed “Overlay-chan” in the company.</p><p>After about a week and a half of testing with the community, we’ve put a pause on it so the dev team can catch up. About a week before public launch, we’ll have them back in again to help us with final checks.</p><p>What remains development-wise is working through the bug report backlog, enhancing site performance, and finalizing some more robust devOps solutions.</p><p>Before I end off this section, I’d like to share some pictures of one of the experience improvements made by having the testers with us.</p><p>Here’s a screenshot of what the Today’s Studies unit progression system looked like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JbgwsdooPlkKIjlaa01Igw.png" /><figcaption>Early prototype design of the “Today’s Studies” flow that made it into production.</figcaption></figure><p>Above you’ll see something that really doesn’t make a lot of sense. If you’re totally confused, don’t worry, I am too and I designed it.</p><p>Honestly, I find it humorous that this design made it all the way into the testing stage of the site, but! It’s a great example of how getting feedback from users can immensely help the design process.</p><p>Naturally, they were confused when they hit this. It’s unclear what’s going on.</p><p>What it’s supposed to be showing is that you’ve completed everything in the unit for the day. But there’s so many colors, and the completion states throughout the day don’t make sense.</p><p>After reading the feedback reported in Canny and talking with some testers in discord, I worked out a new design which is a lot more clear:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5UK5xqZPDrVOixaTY-qQ-g.png" /><figcaption>What “Unit 23” looks like before you’ve started it the day it’s assigned.</figcaption></figure><p>Above you can see that today, you’ll be studying Unit 23. You haven’t started it yet, so you’ve got 36 review cards to complete to “Maintain” your study progress and get your study streak badge for the day.</p><p>1 kana set to learn, 1 lesson, 12 new cards and 1 dialogue in order to make “Progress” for the day towards improving your abilities and continuing through your learning journey.</p><p>If you were to click on each of these circles, they’d give you a preview of what’s coming up.</p><p>Clicking “Study Now” would start you off straight away with your reviews.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aZRyD35fgq1pTZcCXXfx5w.png" /><figcaption>Unit in progress view.</figcaption></figure><p>In the view above, we’ve made progress and have 3 of 12 new cards, and 1 dialogue remaining.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VnPvCIkel8DFj8b8jbJwCQ.png" /><figcaption>Unit 23 completed and you’re finished with Today’s Studies!</figcaption></figure><p>In the view above, you’ve completed all your core activities for today. All your circles have filled up green, and you’ve gotten your “Progress” badge for the day. Nice!</p><p>Looking at the original and then the re-work, I think, “how did I let that original design live for so long?!” but alas, at least it was caught.</p><p>In some ways, I’m glad the testing group got to interact with the really bad design. Because by hearing their feedback, I was able to much more quickly work out an improvement.</p><p>Needless to say, I’m really looking forward to everyone being in the platform soon.</p><h3>In summary / tl;dr</h3><h3>What’s done:</h3><ul><li>Final checks on content✅<br><em>Ordering the units in the phase and proofreading everything.<br>All 725 Phase One kanji added to the platform, all 1,035 Phase One vocabulary cards added to the platform, 165 Phase One dialogues entered into the platform</em></li><li>Finalized the student-facing experience✅<br><em>Front end of system flashcards, front end of the Study Now experience, attach frontend of progression system and pace slider to the working backend code, updated student dashboard, improvements to the payments system, stability improvements, content update to shadow loops.</em></li><li>Finished server / backend code of main student experience systems ✅<br><em>System flashcards, dialogues, study now experience, progression system / pace slider, student account settings, using NativShark articles, lessons renderable.</em></li><li>Launched to testers and gathered initial feedback✅<br><em>Fixed initial issues discovered with the flashcard scheduler, made design and UX improvements.</em></li></ul><h3>What’s left:</h3><ul><li>Last few student experience implementations ⏳<br><em>Implementing re-design to the Today’s Studies section and the My Lesson Plan section of the student dashboard.</em></li><li>DevOps ⏳<br><em>Testing our deployment flow.</em></li><li>Final tests! ⏳<br><em>Bring in the community testers again, make sure billing is working, free trials, refunds, upgrading, downgrading, etc.</em></li><li>Launch NativShark 1.0 in mid to later August 🚀🚀🚀</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/128/1*TVZB5Dvr_B53GHeJezvnCQ.gif" /></figure><p>In some ways, it feels like we’ve been here before… But by far, we’re the closest we’ve ever been.</p><p>The fact that real students have been in the system and able to use it, and that most of the issues now revolve around styling and display, centering around iOS and Safari (forever the developers bane)… It bodes well for us.</p><p>We’ve really opened up our development process and feedback channels as well. We’re doing things right this time around and, as they say, third time’s the charm 🌟</p><p>See you on the inside soon! Looking forward to another great month and for all of you to join us.</p><p>Stay safe out there friends,</p><p>~ Caleb</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4771f352d3c7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nativshark/july-2020-end-of-month-update-4771f352d3c7">July 2020 — End of Month Update</a> was originally published in <a href="https://medium.com/nativshark">NativShark</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[June 2020 — End of Month Update]]></title>
            <link>https://medium.com/nativshark/june-2020-end-of-month-update-6ef0edd396fb?source=rss-d92fbb9ede8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ef0edd396fb</guid>
            <category><![CDATA[nativshark]]></category>
            <category><![CDATA[japanese-language]]></category>
            <category><![CDATA[updates]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Caleb Andersen]]></dc:creator>
            <pubDate>Wed, 01 Jul 2020 02:43:32 GMT</pubDate>
            <atom:updated>2020-07-01T02:43:32.797Z</atom:updated>
            <content:encoded><![CDATA[<h3>June 2020 — End of Month Update</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*olsHgbkyOqvgb8L46g5JTw.jpeg" /></figure><p>Hi everyone 🍉</p><p>Summer is setting in, the heat is rising and the rainy season has started in Japan.</p><p>I’m really looking forward to it, I think the rainy season and the summer heat might be one of my favorite seasons here haha. It has such a 懐かしい feeling to it for me.</p><p>Continuing the theme from last month, NativShark has had an even better month. The momentum has carried through and I’m anticipating a great July as well.</p><p>Let’s get into some specifics about the improvements from the different parts of NativShark…</p><h3>Progress report</h3><p><em>A look at what’s been going on during the month of June in Management, Content and Development at NativShark.</em></p><h4>Management</h4><p>As per last month’s update, we’ve been working on bringing standardized project management methods into our flows at NativShark as part of our continued growth as a company.</p><p>Somewhere between 6 and 10 team members and this kind of thing becomes incredibly necessary, especially when the product being built is as incredibly massive as NativShark.</p><p>It takes a lot of work to refine such a product down to the set of core launchable functionalities, though in the first week of June we’ve done just that and began properly implementing an Agile project management system loosely following the SCRUM principles.</p><p>We started with bringing Agile methods to the engineering team, then the management team, then content team, and now we’re working out how to implement agile in the media and art teams.</p><p>Building a system of project management that works inside a company is different and unique for every company; there are no copy-paste solutions. Though, naturally, we’re still growing and improving our efforts weekly (as one should in an agile organization) and we’ve made a lot of progress in systematizing NativShark.</p><p>With agile comes learning to separate what to do when and learning to prioritize. We’ve been figuring out the question, “what does ‘Agile at NativShark’ look and function like?”</p><p>Exciting times.</p><p>With that, we now have a much clearer view of what it will actually take to release the core experience. We’re looking at July or August as being launch ready.</p><p>Lastly, something major Niko and I have done this past month is build out a mindmap of the entire organization of NativShark in order to get it out of our heads and out into the world for team members to see. Here’s a screenshot of what that looks like zoomed out enough to almost show the whole structure:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/907/1*s05pQOCYVbSvtAXthAPz4A.png" /><figcaption>Mindmap of NativShark the Company. Every part of operations, future plans, the content management platform, the student platform, our philosophies, and our language education process is defined here.</figcaption></figure><p>With that, we refined our mission, vision, and guiding principles, and I’d like to share them with you.</p><p><strong>The NativShark Vision</strong></p><p><em>A more understanding, connected and multilingual future.</em></p><p><strong>The NativShark Mission</strong></p><p><em>Make learning simple.</em></p><p><strong>NativShark’s Guiding Principle</strong></p><p><em>The power of education is for everyone.</em></p><h4>Content</h4><p>The content team has been editing all the Phase One content during June, getting it primed and ready.</p><p>Additionally, we’ve been working on creative ways to teach concepts in lessons with the tools available to us as part of the core experience launch. In the future we’ll be able to add even more neat elements to teach different concepts even better.</p><p>We’ve been doing things such as standardizing the use of elements and highlights. So no matter the lesson, you can bring up the highlight legend and get a refresh on what they represent in regards to helping you create a framework in your mind for understanding Japanese.</p><p>Here’s an example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*naCuIF-FA3S6836fdI7UNA.png" /><figcaption>Snippet of a Phase One lesson.</figcaption></figure><p>Now I want to take a quick look at, “what actually <em>is</em> the ‘core experience’?”</p><p>The core experience of NativShark is being able to set your study goal completion pace with the pace slider, log in everyday, hit the “Study Now” button and have all of the core studies needed delivered to you in an i+1 fashion.</p><p>In an oversimplified way, to do this, we’ve built out the system to have a Path that has Phases in it, Phases that have Units in them and Units that have Studyables in them.</p><p>A <em>Path </em>is the language you’re learning, so in this initial case, English to Japanese.</p><p>A <em>Phase </em>is a group of <em>Units </em>arranged linearly that build your language ability up to a certain level.</p><p>A <em>Unit </em>is a group of <em>Studyables. </em>On the standard pace, you’ll complete one<em> Unit </em>per day.</p><p><em>Studyables </em>are lessons, flashcards, dialogues, or assigned activities (such as learning kana, conjugation quizzes, comprehension quizzes, production quizzes etc).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a7VUrp7UeSAYRm5tc2uVvQ.png" /><figcaption>The core experience / NativShark education process in mindmap form.</figcaption></figure><p>What we’re launching with is the full core experience, with content through Phase One. At the standard pace, Phase One takes around 5 months to complete.</p><p>For those familiar with NihongoShark, NativShark Phase One is nearly 100% different. The kanji are taught differently, the vocabulary are new and taught in a different order, and the lessons are new or significantly reworked. In some sense, NativShark Phase One is what NihongoShark Phase One and Two used to be.</p><p>One of the more significant impactful differences between NHS and NativShark is the addition of Dialogues, which are what actually drive the content creation of a Phase.</p><h4>Development</h4><p>One of the main things, besides the health challenges we faced in February and March and the lack of scalable project management systems that has continually blocked us from releasing student content, has been the content management platform.</p><p>In order for NativShark to be NativShark, there had to be a robust content admin site built to power the lessons and the platform. While we of course couldn’t get all the features of the system in, we’ve finally finished it to the point that content can be made and delivered.</p><p>Now we’re on to finishing up the student experience side of things.</p><p>That said, I’d like to show you a look at some of the stuff we’ve built in the past month.</p><p>We’ve just finished the Dialogue Editor:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fff96r2XMZh8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dff96r2XMZh8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fff96r2XMZh8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/133a44aa8ed531697559e54658eaef39/href">https://medium.com/media/133a44aa8ed531697559e54658eaef39/href</a></iframe><p>In the lesson editor, we’ve built interactive sentence elements that play audio, show formality level of the sentence, and hover-able literal breakdowns that highlight the corresponding Japanese:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/889/1*KNe5_sFhq6mpUUKWF5pFYg.gif" /></figure><p>And we have kanji cards with animated stroke order:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BVz80sGC-it7Q0CTr_Fm-A.gif" /></figure><p>This stuff is really exciting to use and see finally coming together.</p><p>Bringing agile methods into the engineering team has worked miracles for focus and productivity by providing transparency and bringing the team together to work as one unit. Our teams are now Fullstack dynamic teams, rather than building each part of the stack separately.</p><h4>Community</h4><p>We’ve broken the #日本語で channel into two channels, #formal-日本語で and #casual-日本語で. This is so that community members and students can get practice and corrections in both types of speech, as native speakers often stop by these channels and provide corrections for students in #日本語で-chat-corrections. Additionally, Phase One teaches a lot of casual Japanese and we wanted to provide students with a place to practice the language they’re learning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/285/1*7tQm2FMwHNOXRQeXA_-2gA.png" /></figure><h3>In summary / tl;dr</h3><h4>What’s done:</h4><ul><li>Redesigned and built logged out pages ✅<br><em>Landing page, pricing page, community page, process page, faq page.</em></li><li>Finished Content Management Platform to lesson-publishable state ✅<br><em>Lesson editor, dialogue editor, vocabulary entry editor, sentence editor, kanji entry editor, path planner, phase planner, unit planner (including system flashcard builder), audio for every sentence recorded and addable, browse page for content writers to search all in progress and published content.</em></li><li>Finished server / backend code of main student experience systems ✅<br><em>System flashcards, dialogues, study now experience, progression system / pace slider, student account settings, using NativShark articles, lessons renderable.</em></li><li>All 166 Phase One lessons added to the platform ✅</li></ul><h4>What’s left:</h4><ul><li>Final checks on content ⌛️<br><em>Ordering the units in the phase and proofreading everything.<br>All 755 Phase One kanji added to the platform, all 1066 Phase One vocabulary cards added to the platform, 165 Phase One dialogues entered into the platform</em></li><li>Finalizing the student-facing experience ⌛️<br><em>Front end of system flashcards, front end of the Study Now experience, attach frontend of progression system and pace slider to the working backend code, updated student dashboard, improvements to the payments system, stability improvements, content update to shadow loops.</em></li><li>Final checks and community testing ⌛️<br><em>Bug fixes and stability changes in response to initial feedback.</em></li><li>Launch 🚀</li></ul><p>Thanks for reading, and thanks for being part of our community. With all that is going on in the world, I hope you’re doing well. We’re really looking forward to being able to bring the joy of learning to you all very soon.</p><p>Best,</p><p>Caleb</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ef0edd396fb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nativshark/june-2020-end-of-month-update-6ef0edd396fb">June 2020 — End of Month Update</a> was originally published in <a href="https://medium.com/nativshark">NativShark</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[April 2020 — End of month update]]></title>
            <link>https://medium.com/nativshark/april-2020-end-of-month-update-81259649ffba?source=rss-d92fbb9ede8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/81259649ffba</guid>
            <category><![CDATA[japanese-language]]></category>
            <category><![CDATA[phase-one]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[content]]></category>
            <dc:creator><![CDATA[Caleb Andersen]]></dc:creator>
            <pubDate>Sat, 25 Apr 2020 03:22:37 GMT</pubDate>
            <atom:updated>2020-04-25T03:22:37.690Z</atom:updated>
            <content:encoded><![CDATA[<h3>April 2020 — End of month update</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wtyjNEkZEG7iZ2RTKmUFhw.jpeg" /></figure><p>Hey everyone, Caleb here.</p><p>First, let’s just rip the band-aid right off: <strong>We’re not going to release Phase One of NativShark at the end of April as we had promised before.</strong></p><p>That said, we have just put out a general stability update that takes advantage of much of the work we have done this past month. Those who have had issues with resetting passwords, creating accounts, or subscribing should no longer have these issues.</p><p>I’m not going to set another public deadline. We’ve removed the public timeline element on the roadmap page and are deeply thinking how to make a better one that is accurate and represents NativShark better. I know that what we need to do right now is just deliver the Phase One experience so that’s what we will do.</p><p>This is a very hard message for me to send to everyone but I know it’s the right call. What we have now isn’t working well enough to release and we want what we do launch to be quality. I can assure you that we are focused, and that it is coming soon.</p><p>Perhaps the message I sent to the rest of our team earlier this week sums it up best:</p><p><em>We’ve been through a lot and we’ve learned a lot this past month.</em></p><p><em>We learned that we were really bad at estimating how long things would take us to do. But from this process I think we’ve gotten better at estimating time to completion, and we’ve learned a lot about better ways to work as a team and operate our development and deployment strategies so that they suit the complexity of our system and its rapid growth. <br> <br> Also, I’ve noticed everyone working extra hard the last two weeks and both Niko and I really appreciate that a lot. It’s been amazing to see, and I’m really glad we’ve all put so much into this and are doing something that we believe in, enjoy, and want to see through. Not only are we building an awesome product for the world, we’re also building a really special team. You’re all becoming NativShark experts. <br> <br> With that said, when you’re working on something you love, it can be easy to accidentally push too hard. It can begin to feel like there’s no end in site and then the thing you loved can become a point of pain. We don’t want to see that happen and I fear we’re on the verge of team-wide burnout. So we’re gonna nip that right in the bud. I personally don’t like to push the team on overdrive for more than 2 weeks at a time and we’ve definitely hit the point. So to say the obvious that we all know, despite how much we’d like to, we cannot launch this week on April 25th. That’s just reality. We’ve got more work in front of us and we can’t keep pushing at this rate. So we need to reframe our deadlines and deliver a polished Phase One experience, which includes the admin panel working as we need it to for Phase One publishing.</em></p><p><em>While we do still need to keep working hard here until the Phase One experience is out, we need to lighten up a little bit. We need to return to better sleep schedules and work schedules.</em></p><p>Learning Japanese is a long term commitment. So is building a comprehensive platform for learning Japanese.</p><p>This isn’t something we started because it was easy. We started it because we know what it’s like to be a student and we all have a passion for learning.</p><p>Just like setting out to learn a language, we knew there would be bumps along the way. Still, it sucks when you actually hit one of those bumps. Like we have just now.</p><p>Like good students, however, we won’t let some setbacks break our will to succeed. We will find the parts of our estimates that were unrealistic, adjust them a bit, and keep pushing forward.</p><p>Reading this, you may be curious as to why, exactly, we’ve now pushed back the Phase One release again. This is going to be a long post. We want to give you as much context into what’s going on behind the scenes as we can and what it’s like to bring a project of this scale into life. We’re so close. Anyway. Taking a look at how some of our team members have spent the last few weeks should provide some insight…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8x6R4e3M0ofdTLm0J-GZEg.jpeg" /><figcaption>The image Chie drew specially for the team to help keep our spirits high</figcaption></figure><h3>Niko, President</h3><p>In the first part of April, I finished writing the base content for the Phase One lessons. This meant preparing a 450+ page document with over 140,000 words teaching Japanese while also throttling the amount of new information students are exposed to (i.e. limiting sentences to 1 new word max; teaching kanji before vocab show up using them; not using any grammar until it has been introduced; etc.).</p><p>This would have been easier if we allowed ourselves to “cheat” and just make students study extra vocab flashcards when we wanted to use specific vocab in an upcoming lesson, dialogue, etc. Instead, we very rarely go over 7 new vocabulary cards / 5 new kanji cards per unit in the first 100 or so lessons, and 8 new vocabulary cards / 5 (very rarely, 6) new kanji cards after lesson 100 or so.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*v45UpYqtCnLjuK4YO3cYSw.png" /><figcaption>Official stats from the Phase One lesson word document. Now to transfer all of this into our content management system and add all the formatting…</figcaption></figure><h3>+1 tracking</h3><p>For the majority of April, I’ve spent most of my waking hours staring at our many spreadsheets.</p><p>Since our admin panel is not fully set up yet, I have to track the +1 iteration manually. This means that I need to record:</p><ul><li>The unit in which each word appears for the first time. This includes each iteration of a word. If we have 美味しい, we also need to know that we have already used the same word without kanji, おいしい, because it is commonly written both ways.</li><li>When kanji have been introduced, and that vocab flashcards only show up after all of the kanji in them have been introduced. (There are a very small number of exceptions here. This one is tricky because the vocab flashcards also frequently double as the onyomi or kunyomi example of a kanji that shows up in a kanji flashcard. So, our spreadsheet also needs to know that (1) we have or have not taught a word in Phase One containing that reading of a particular kanji, and (2) we haven’t accidentally assigned more than one word as the onyomi or kunyomi example for the flashcard of a particular kanji. This is further complicated by the fact that a single word can be the reading example for multiple kanji. For example, 前髪 (bangs) could be the kunyomi example for both 前 (before) and 髪 (hair).</li><li>Duplicate sentences. In order to keep example dialogues in our lessons natural-sounding, and to teach all of the things we want to teach in what we think is the most effective way, we occasionally need to use the same exact sentence in multiple places in a phase. We need to watch out for when this happens so that students don’t get assigned the same flashcards all over again.</li><li>Which content slotted for Phase One remains to be introduced. In the past six months, we have had 4 or so dictionaries/reference books manually entered into spreadsheets so that we could be sure we weren’t missing any useful language. Rei pored over these lists, then ranked each of these entries by phase. So, for Phase One, for example, we determined that there were 16 onomatopoeic words we wanted to teach, along with 6 四字熟語 (4-kanji compound words) and 32 phrasal idioms. I had to make sure that all of these were taught in Phase One without breaking the +1 iteration, meaning I couldn’t use kanji or things like individual parts of an idiom (e.g. 赤 [red], the prefix 真-, and 嘘 [lie] and all three of those kanji are taught before the idiom 真っ赤な嘘 [complete lie; outright lie] is taught).</li></ul><h3>More adventures in Spreadsheet Land</h3><p>Managing all of this in Google Sheets means using LOTS of formulas, separate cross-referenced sheets within a single workbook, and all kinds of conditional formatting rules.</p><p>This led to other problems, though:</p><ul><li>You can only have 5 million cells in a Google Sheets workbook. I was repeatedly breaking this limit, which meant deciding when and where to move data to a separate workbook that could not be cross-referenced in formulas.</li><li>When you have millions of formulas being calculated over and over again, Google Sheets puts too much of a load on a person’s CPU, even if they have a pretty fantastic setup. So, I was playing a dancing game of disabling/removing various formulas and conditional formatting, then reapplying them and editing stuff in pieces or when other team members were sleeping or not using the workbook.</li><li>A program like Excel might have been another solution, but I can work a lot faster in Sheets (though for years I only used Excel). Also, most days we had 5–8 people looking at the workbook simultaneously, with about 4 of us actively editing cells. We’ve found Google Sheets to be more reliable and generate fewer conflicts than Microsoft products for this level of simultaneous work.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a9-DaJdP0ll9l3D_9X0IGQ.png" /><figcaption>Screenshot from our master document. These are some of the dialogues at the end of Phase One. Once you’ve gone through the whole of Phase One you’ll have been exposed to and studied all of the Japanese you see here, before seeing it used in a real-life dialogue example.</figcaption></figure><h3>Japanese audio checks/editing</h3><p>In the latter part of the month, I’ve been checking and editing thousands of audio files.</p><p>In the past, we’ve hired one female and one male voice artist to record each sentence for a particular set of learning materials. We want NativShark to be better, though. Accordingly, even though we already had 2 recordings for a significant number of sentences in Phase One, we hired an additional 8 voice actors to record every sentence. This way students can get exposed to different people’s voices and pronunciation, which naturally vary from person to person (especially because we have them record at natural speed and not in a “textbook” or slowed/dumbed-down voice.</p><p>Long story short, I find myself needing to check, organize, and properly label around 25,000 sentence recordings. In this one week, I’ve gotten through just under 10,000 of them. This includes not only listening to each sentence but also making sure that the title of the sentence is the Japanese being read and the filename matches up with the unique slug in our system so that we can match it to that sentence and have it show up in NativShark. Which means, again, I’m spending a lot of time in spreadsheets. But even more time staring at the titles showing up in my audio player and making sure they match the words being said, to say nothing of cutting out errors the voice actors make, silencing background noise in places, deleting improperly recorded audio, and so on.</p><p>I sound like I’m complaining, but I actually love this part of the job because I’m fascinated with the way Japanese sounds, and I get lots of ideas for tools and lessons that we need to teach in the future. The work would be a complete indulgence if I didn’t have to do it <em>quickly</em>.</p><p>Once all that audio stuff is done, native speakers and I will need to sift through it and choose which male and female voice we want showing up for each individual sentence. So, 25,000 sentences, Round 2!</p><h3>NativShark usage guides and whatnot</h3><p>I also wrote several of these posts/articles this month as well, and there are several more in the works. I almost forgot to mention this job because I can write a few rough drafts of these a day, which feels like light speed compared the monstrous tasks described above.</p><p>All in all, I’m repeatedly surprised at just how huge of an undertaking the building of NativShark is. I can’t help but get a little bit excited every time that happens, though.</p><p><em>You can’t take a monstrous thing like an entire language and make it simple for people to learn without putting in a monstrous amount of effort.</em></p><p>I get so thrilled thinking about how new students of Japanese will now learn the language so much faster than I was able to. It’s a great feeling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Ma0RzafQKbuXGS_nAFKFA.png" /><figcaption>Screenshot of the way dialogues appear in your “Study Now” track, at the end of each unit. The dialogues use incredibly natural Japanese, casual when it should be, formal when it should be.</figcaption></figure><h3>Ty, Editor</h3><p>One thing I’ve learned: doing things right takes a very long time. And it’s harder than it looks to estimate that time. I also know that I don’t want to sacrifice quality so we can get something out faster.</p><p>At the start of the month, I was full-focus on finishing up my last edit run through the kanji. Doing so took several days, at the pace of about 400 kanji elements and mnemonics checked a day.</p><p>And that was going fast so I could keep up pace with the speed of everything else happening.</p><p>Thing is though, the faster you go when you edit, the more you miss. So I had to tell myself to slow down so I could read everything and actually catch typos / weird phrasings.</p><p>Editing is a very precise job, and I’ve been learning that more and more every day. All I can do is keep thinking about ways to be efficient, and keep practicing my own writing so I can deliver even better content through NativShark.</p><p>Another precise job is doing quality translations, especially when you know students are going to be using these to learn. It’s a whole new level of “I have to make sure this is perfect,” and the content team and I want to make sure that <em>every single translation </em>is high quality.</p><p>So there’s always discussions going on among the content team about things like “does this translation capture the nuance of the Japanese? Do we need to add a note to this, and if we do, did we do a good enough job with the translation to begin with?”</p><p>These discussion can take a while once we add up all the sentences and dialogues that are going into Phase One.</p><p>We have similar discussions on the lesson in general, too:</p><p>Does this explanation do a good enough job of explaining this concept? Is it precise enough to explain it well and not too long-winded as to bore readers? Is the lesson as a whole fun to read or is it slow and boring to get through? Do the example sentences properly show off good ways to use this grammar / main point? Is everything easy to digest? Do we stay on topic or are we side-tracking every other paragraph? Etc. etc.</p><p>I’m also, at the time of writing this, editing through lessons now that the admin site for that is up and running (after a long fight to get that thing working, which Jacob will explain shortly). There are bugs which I take time to report in detail to the devs, and suggestions on how we can improve the editor to better workflow when going through it. They’re really good at getting stuff fixed and implemented, so thank you devs!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y32Zo96xUiVWp7ZFbwVSNQ.png" /><figcaption><em>What the admin side editor looks like in action. It allows us to write out lessons with our formatting happening in real time.</em></figcaption></figure><p>All things considered, I can get through usually up to 10 lessons per workday if I only focus on editing for that day. (There are 166 lessons to go through.)</p><p>Though I’ve slowed this down a bit due to needing to focus on content, I also spend the start of my mornings checking the discord and answering questions where I can. Our community is great so I basically never have to worry about stepping into a situation as a mod, and can just do so as a fellow community member. So I’m grateful to all the community members and mods there who allow me to do that. Thank you.</p><p>In addition to that, I’ve been writing use guides / explanations for NativShark and thoroughly testing the site while doing so. So while doing that, I was trying my best to break the site as much as I could. And oh boy did I. I’m sure the devs love me for it, too.</p><h3>Rough list of things done in April (this is just the main points):</h3><ul><li>At the start of April I was finishing editing through everything I wrote for the kanji. So I went through almost <strong>400 kanji elements and mnemonics a day</strong>, spending the entire day on it until it was done. Didn’t even stop to check discord.</li><li>Checked and discussed all <strong>165 Dialogue translations</strong> with the content team</li><li>Translating takes longer than one might initially think. It’s not just understanding the sentence and throwing it into English. There is a lot of discussion on how exactly to word our English translations to convey as much of the nuance the Japanese has as possible, and <strong>there is a LOT of back and forth over so many of the sentences</strong>. We’re making these translations as absolutely accurate as we can so they can be the best they can be.</li><li>Reading/modding all of Discord (almost) every time I start the day.</li><li>The search for more native materials that I can get onto the list continues. Got some suggestions from community members too, so thanks!</li><li>Wrote/outlined “Using NativShark” articles with Niko which will be coming with Phase One. While doing so I also took the time to….</li><li>…do some in-depth testing of our tools throughout the site. I caught and reported many bugs that we’ll be fixing up, along with QoL changes. It also led to discussions on design updates that we can do to make the experience smoother, easier to use, and overall better.</li><li>Discussed our study streaks in relation to new art that Chie drew for them with Caleb. The numbers are pretty different from the first time we showed them off, but we think the new numbers will feel better when studying.</li><li>Lots of discussion with the content team about kanji flashcard design and function. And I mean lots.</li><li>Community updates and ideas for down the road with Chengaiz. We’ve put a slight pause on them so we can both focus on the mountain of tasks left for Phase One though.</li><li>Edited over all of our kanji readings for Phase One so make sure you blame me if something slipped by.</li><li>When the editor was released, we found some bugs that slowed our devs down because they were vital to fix.</li><li>At the time of writing this, my life is editing and I love it.</li><li>Also finding bugs, another enjoyable pastime of mine.</li><li>Also constantly thinking of QoL and design suggestions for both sides of the system.</li></ul><h3>A personal look at this month in general:</h3><p>I still have a lot of learning to do in a lot of areas. I have a way to go yet in regards to learning and using Japanese, and I mean it when I say it too, I’m not just being humble. That’s part of the reason I’m so excited to NativShark to be out. It teaches natural language so there’s not a disconnect between Japanese used by actual people and what I’ll be studying.</p><p>My writing is something I’m working on, too. For example, I spent a good while writing up a “Using NativShark” article and asked Niko to give it a look, and he gave me great feedback… which I used to rewrite the whole thing. I feel a lot better about what I produced with Niko’s feedback on this particular article, but wish I got it right the first time.</p><p>But I don’t let those things discourage me. As Niko told me in that PDF almost 5 years ago, I just need to show up and keep trying. Even if it doesn’t go fantastic every day, I’ve still gotten further than someone who didn’t show up at all. Just keep swimming.</p><p>I’ve carried that advice with me ever since I read it, and believe it applies to our work at NativShark too.</p><p>While we sadly can’t release Phase One quite yet, we’re closer than we have ever been, and progress is made every day. I’m honored to be on a team with as much dedication, drive, and ability to find solutions as this one. We won’t stop swimming.</p><h3>Jacob, CTO</h3><p>This last month seemed like both the longest month and the shortest month I’ve ever experienced. On top of that, the COVID-19 situation makes every day feel like it takes 10 years to pass.</p><p>Looking at the past month in the team activity log, it’s apparent that I’ve actually been able to accomplish quite a bit. Most of what was done does not affect the students, nor will they see it, but some things (such as the Dictionary service) will likely make its way into their hands in the future for things like custom flashcards.</p><p>Before writing about issues faced in the codebase, I want to talk about general development issues that were faced.</p><h3>The Commanded library</h3><p>Commanded is an Elixir library for event sourcing that comes with some auxiliary libraries to make implementing this system easier. While event sourcing is a great concept, it’s only a great concept when the following hold true:</p><ol><li>It works without any issues</li><li>All developers need to understand the errors that occur and be able to fix them, otherwise their development environment is broken</li></ol><p>For #1 above, we started to notice various bug reports coming in from the community that didn’t make sense to us. Things such as being unable to change passwords, save various parts of their profile, the billing information not updating correctly, etc. etc. When looking at our logs, we saw that these events were being dispatched in the system successfully, so what was going wrong? As it turns out, a few of our projectors were stuck. Projectors have the job of processing events and updating the database based on those events. What this means is that when a projector is stuck, the database never gets updated.</p><p>For #2, we would run into issues where developers would encounter an error on their end which was the result of events failing to process correctly on the server. Due to the nature of event sourcing, when they would restart their development environment, it would try to replay those events, crashing their environment. Due to the distributed nature of our team, this meant that developers were often unable to proceed with their work until myself or Manuel were awake and able to fix the server. This led to lost time and frustration.</p><p>In the end, we removed all event sourcing from our system. I have looked into how to better use events in the future and how we can decouple our services while maintaining stability. Although none of these new approaches have been tested or implemented yet, the system is being written in a way where it’ll be relatively easy to decouple in the future.</p><h3>The lack of a staging server</h3><p>The title here is a bit misleading, it’s not that we <em>didn’t</em> have a staging server, it’s moreso that the entire development team was too busy trying to write code to hit a deadline that we didn’t have time to change our deployment process to continue having a staging server. In addition to this, there wasn’t a single team member who had enough time to be able to test the new things being finished because everyone was scrambling to complete a mountain of work in time for the deadline.</p><p>Once it was reported that the admin site was functional enough for lessons to be created, we decided to deploy it. We ran into countless errors when deploying the site because of some core architectural changes that were made to the codebase, which I’ll discuss now.</p><h3>Separate projects sharing components</h3><p>Our frontend is written in React. React is marketed as a JavaScript library for building user interfaces, which is pretty succinct. In summary, it allows you to break down a large, complex experience into small components that can be composed together to make something special. When we thought about the admin site, it didn’t make sense to bundle it together with the student-facing site for a couple of reasons:</p><ol><li>There will likely be different security requirements for the admin site such as wanting to deploy it behind a firewall, restricting access points, randomizing the access URL, etc., etc.</li><li>There will often be times where changes are pushed that affect the admin site that do not affect the student site and vice-versa. We want to avoid increasing the payload size of either of these sites unnecessarily as well as avoid re-deploying one when only the other has changed</li></ol><p>After deciding that we needed to separate these sites into two separate entities, we decided that we needed to restructure the project in a way that allowed common components to be shared across both sites. We shouldn’t have to re-code a button on the admin site if it already exists on the student site, for example. This led us down the path of using something called Lerna to manage our frontend applications. I won’t go into what Lerna is, but you can think of it as a system that understands what each sub-project needs and intelligently shares the components between the two.</p><h3>Lerna is amazing!… While developing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l6C7QRZvLbllxPoVCswA9Q.png" /><figcaption>A goofy example of building a component with the help of Lerna packages :)</figcaption></figure><p>With Lerna in place, our frontend developers were once again up and running, and now were able to create components that were shared across both sites. This was great and resulted in improved productivity generally across that group. Everything was great until we wanted to deploy the site, where a few things went wrong:</p><ol><li>The way Lerna manages your code is different to how anything assumes your code is managed</li><li>All of our deployment pipelines and hosting that we chose had no idea how to handle a Lerna project</li></ol><p>This meant that we needed to redo our entire deployment pipeline while under the pressure of looming deadlines. Normally this would be pretty bad, but it was amplified by the fact that our entire content team was basically unable to do their job now because they needed the admin site to continue doing their job. This led to myself and Ben putting in roughly 36–38 hours over the span of two days to get this system back in place. This was probably one of the most frustrating things I’ve experienced as a developer.</p><p>If you haven’t had to work on a deployment pipeline, it’s frustrating because it takes <em>forever</em>. In general, the steps go like this:</p><ol><li>Make a tweak to the CI/CD (continuous integration/continuous deployment) script</li><li>Push the new code into source control</li><li>Wait 10–15 minutes for it to build and try to run your code</li><li>Get errors and attempt to fix them locally</li><li>Go back to step 1 and repeat ad-infinitum until you have a working system</li></ol><p>In the end, we got the new pipeline setup and discovered a couple of other issues with our staging server that we were able to resolve. While that time wasn’t enjoyable, it ended up resulting in a staging server that is more performant than the current production server. This means that we’ll also be changing where our production site is deployed which comes with a ton of other issues (looking at you NihongoShark.com redirects).</p><p>Time to evaluate the various services that encountered issues last month and how they were fixed.</p><h3>The dictionary service</h3><p>As one might expect, this service (along with the SRS service) are probably the two most complicated systems that we have at this point. The progression service will likely also land in this group once it’s finished, though not enough progress has been made on that yet to be able to say for sure. I’m going to break down some of the problems that were encountered by this service.</p><h3>Problem #1 — Mecab has no idea what it received</h3><p>This was one of the first problems that we encountered, specifically when Jannis tried to break a sentence down to where every individual kana/kanji was its own word. When Mecab received things such as ー or ゃ, it was unable to do anything with it and was returning back a blank results set.</p><p>This edge case was unaccounted for and thus resulted in the server erroring out. As mentioned earlier, this meant that our developers were stuck because their development environments were crashing. The fix for this was rather quick, but it meant that I had to refactor how the service worked and write more tests to ensure that this error wouldn’t happen again. I coordinated with Jannis, who was the primary frontend developer using this service to figure out how best to approach situations like this, and we came up with a solution that basically meant that our system would create new words out of nothingness. This works quite well and leads to general stability in the system overall.</p><h3>Problem #2 — Special characters and numbers</h3><p>This was an interesting problem that is a combination of something that was fixed this month and something that was fixed last month. To break this down even more, we’ll first look at numbers.</p><h3>Numbers and Furigana</h3><p>After searching high and low, I could not find an easy algorithm, solution, or library to import that would automatically generate furigana for an arbitrarily-large number in Japanese. What this means is that NativShark now has a custom-built library that will automatically generate furigana for an arbitrarily-large number in Japanese.</p><p>What’s curious about Japanese is how the numbers are logically grouped differently than they are in English. To talk about this, we’ll look at a couple of examples:</p><ul><li><strong>English: </strong>1,000 — <strong>Japanese: </strong>千</li><li>So far nothing too horrendous, this is a pretty logical mapping, until we go to 10,000…</li><li><strong>English:</strong> 10,000 — <strong>Japanese: </strong>１万</li><li>Yeah, I know. If anyone is unfamiliar with Japanese they probably would have assumed something like 十千, which isn’t a thing.</li></ul><p>The above is a really small example, but it gets quite confusing when you get into higher numbers, such as 938,535,235,831 (which is, by the way: きゅうせんさんびゃくはちじゅうごおくさんぜんごひゃくにじゅうさんまんごせんはっぴゃくさんじゅういち). Not only was this slightly brain-melting to figure out by hand, coding it was even worse.</p><p>Needless to say, we now have a system that is tested and works. Moving onto symbols…</p><h3>Symbols and what is (I)?</h3><p>In our earlier lessons in our platform, we often will include things such as “(I)”, or “(their)” to bring attention to the fact that these common words in English are dropped in Japanese. Mecab takes this and splits it up into the following (only after adding the neologd dictionary):</p><ul><li>(</li><li>I</li><li>)</li></ul><p>It’s probably obvious why this isn’t helpful. We don’t want ( as a word in our dictionary, that’s not helping anyone. This was a relatively quick fix wherein the system is able to logically understand that although Mecab gave us back 3 words, we know that we are only asking for a single word so it knows to combine them. The only thing that was left to do was to structure the “reading” of this so that the frontend was able to correctly display it in an intelligent way.</p><p>The above issues weren’t too bad, but they were unforeseen things that came up during actual use.</p><h3>SRS, flashcards, and new friends</h3><p>It’s hard to express how complex this system is. While it’s possible that others will suggest easier ways to handle this (and there are easier ways to handle this), those ways are also generally less flexible than what we have. Timezones are hard, allowing users to specifically state when they want their “study day” to reset and have that respect their timezone is hard, and having the system understand and respect all of these configurations is even harder.</p><h3>Complexities with old friends</h3><p>While the SRS and Flashcard services were happy with their only friend, User Flashcards, they were also complicated. The SQL queries were pretty intense and required writing custom database functions to simplify the code in other places. These functions had to account for the database server timezone, the user’s timezone, the fact that we store everything in the database in the UTC timezone, converting between timezones for any arbitrary date AND time, and other things.</p><p>This led to a friendship like most others — a tight circle that <em>could</em> let other friends in, but not without conflicts within the group. It wasn’t until the Flashcard service made a new friend, Kanji Flashcards, that the group’s complexities were tested, broken, and resolved.</p><h3>Kanji flashcards want to join the group</h3><p>Kanji Flashcards started integrating themselves into the system easily enough. The only big changes that needed to be made was updating the GraphQL API for the flashcard queries and mutations to understand that a flashcard could now either be a UserFlashcard or a KanjiFlashcard. This took roughly half of a day of coding to do along with updating all of the server tests and ensuring the entire test suite still passed. The good news was that this worked! The test suite passed, the server was happy, and the Flashcards service welcomed in Kanji Flashcards with open arms. The problems started when the Flashcards service wanted to introduce its new friend to the SRS service.</p><p>If you’ve done much with databases, you know that it can be complex to join tables across null values, compare null values, try not to miss any rows because of null values, etc. etc. I’ll be the first to say that I am not a SQL expert, nor am I a database expert, and I fully expect to dive deep into the workings of SQL, joins, and handling null values gracefully as soon as time permits. With that stated, it’s probably obvious that there were a lot of problems that were encountered.</p><p>Without diving too much into this, basically getting the SRS system to work with kanji flashcards took another day and exposed frustrations with our system. Ecto (the Elixir library that we use to talk to the database) was throwing random errors that experts couldn’t figure out. Postgrex (the underlying service that Ecto uses to directly talk to the database) wasn’t happy. And our test cases and environments were complex and time-consuming to debug.</p><p>The result in the end was to side-step everything and use SQL directly to solve my problem. The only issue is that this has to touch roughly 5 separate queries across the system required during various actions (give me all of my archived flashcards, give me my unarchived flashcards, give me my next set of flashcards for a given deck, give me how many flashcards I have learned today from a given deck, among some others that I can’t remember right now). While the entire test suite has passed, I am still not sure if it works 100%, but user testing will find all of the edge cases, resulting in new tests and a stronger test suite.</p><h3>General technology concerns and discoveries</h3><p>During the development to this point, as the system has grown in complexity, it’s become obvious that there are some shortcomings to our selected technology stack. Ecto has some issues, Commanded had issues under load (and has since been removed from the project), various domains need to talk to various other domains and are currently dependent on each other, most cloud services do not support Elixir as a first-class citizen, etc. It has also become obvious that we need to start employing design and architectural patterns to give us flexibility and adaptability moving forward.</p><h3>Elixir and alternatives</h3><p>One positive thing with our current architecture is that, without much more work, we can slowly split our system up to explore alternatives if we want. We do not need to rewrite the entire system at once because we have a clean separation in Elixir which allows us to proxy a single layer out to some other service. I am exploring alternatives while discussing them with Caleb and the development team and am keeping the following things in mind:</p><ol><li>The server must remain in a functional language</li><li>Once you start developing in a functional style, it becomes hard to go back to any other method. The code is too clean, too reusable, and way easier to test.</li><li>The chosen technology must be able to handle the complexity of the project</li><li>Everything looks golden on the surface and do not show their ugly side until you hit a project with a complexity such as ours</li><li>The current server developers must be able to quickly adapt to the language, and new developers should be able to be trained</li><li>The current server developers are Manuel and myself, and whatever we choose to do we both will need to maintain documentation to help get new developers up to speed</li><li>IF we change, we must upgrade and not downgrade</li><li>Currently this means that the system needs to have a rich ecosystem, should probably have a strong type system, and should not sacrifice performance</li></ol><p>With those in mind, the current forerunner is Scala.</p><h3>Patterns and architecture are important</h3><p>When working on smaller projects, it’s easy to overlook design patterns and general architecture guidelines. Usually things like that are overkill. Our project is now the most complex thing I have ever worked on and is only growing in complexity every day. This means that it is now time to look for patterns, refactor the code to make those patterns easier to replicate, and stay informed.</p><p>When pulling Commanded out of the project, I discovered a pattern that I thought gave us good flexibility and allowed us to easily separate the concerns of our business logic with the restrictions of the database. This started with the Kanji domain and made that code some of the cleanest in the system. There’s still some issues with it that should be refactored (the error-handling portion of every function looks the same now with some <em>slight</em> differences, this can be cleaned up).</p><p>I really want to talk with Manuel and, together, find books about patterns and architectures that fit our server and our system. Ideally the frontend engineers would do the same on their half of the system so that all of our code is not only easy to understand, but also easy to contribute to and flexible to pivot when necessary to solve any problem that comes up.</p><h3>One last reflection, personally</h3><p>It’s crazy to go from where I was to the CTO of this company with 4 other developers working alongside me to try and change the world of language education. Our project is insane, our goal is insane, and our potential is limitless. I have no doubt that we will create what we set out to do, and I can’t see a future where this doesn’t succeed. Our content is too good, our system is too good, and our passion is far more than what I’ve seen from any other team that I’ve been a part of. It’s on us to make sure that our execution matches everything else. Everything we make must be with the best-possible user experience in mind. Everything must feel good, every interaction must be flawless, every reasonable device must work. That is our only job.</p><p>With this dump of thoughts and analysis, I am signing off for the day, eager to jump back into the project and keep pushing forward towards our bright future.</p><h3>In short…</h3><p>…we’re hard at work.</p><p>And every decision we make is with you, our user and student, at the front of our minds.</p><p>Thank you for joining us on this journey and thanks for reading.</p><p>Talk to you again soon.</p><p>~ Caleb</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81259649ffba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nativshark/april-2020-end-of-month-update-81259649ffba">April 2020 — End of month update</a> was originally published in <a href="https://medium.com/nativshark">NativShark</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>