<?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[Axilis - Medium]]></title>
        <description><![CDATA[Thoughts from Axilis - Medium]]></description>
        <link>https://medium.com/axilis?source=rss----1976fa49668c---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Axilis - Medium</title>
            <link>https://medium.com/axilis?source=rss----1976fa49668c---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:18:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/axilis" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Pitali ste kako je prošla Axilis JavaScript škola…]]></title>
            <link>https://medium.com/axilis/https-blog-axilis-com-pitali-ste-kako-je-prosla-axilis-javascript-skola-e1f151df3813?source=rss----1976fa49668c---4</link>
            <guid isPermaLink="false">https://medium.com/p/e1f151df3813</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[schools]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[free]]></category>
            <dc:creator><![CDATA[Danijela Kobescak]]></dc:creator>
            <pubDate>Fri, 23 Jun 2017 07:26:01 GMT</pubDate>
            <atom:updated>2017-06-23T07:26:00.828Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nXukqG5MdYQYsYs4mxLtiA.png" /></figure><p>Emocije i dojmovi su se slegli, a mi smo sretni što smo imali priliku upoznati brojne ambiciozne studente s iznimnim talentima i ponosni jer smo dali najbolje od sebe kako bi ostvarili obećano.</p><p>Ove se godine na Axilis JavaScript School prijavilo više od <strong>350 studenata</strong> sa svih mogućih fakulteta što nas je posebno razveselilo jer je to pravi pokazatelj koliko je programiranje važno u današnje vrijeme, ali i da su mladi svjesni toga. Nakon 2 selekcijska kruga, odabrali smo <strong>15 polaznika</strong> koji su se družili s našim mentorima <strong>5 subota zaredom</strong>. Osim stare, uigrane ekipe predavača: <a href="https://medium.com/u/837cfb881423">Vedran Maršić</a>, <a href="https://medium.com/u/eeb5e1084b97">Matko Raguz</a> i <a href="https://medium.com/u/ed458f1f0609">Petar Kovačević</a>, ovogodišnjoj postavi pridružio se i prošlogodišnji student <a href="https://medium.com/u/5d066097ecc9">Sergej Jakovljev</a>. O Sergeju i njegovim junačkim djelima pišu se priče, <a href="http://www.netokracija.com/sergej-jakovljev-axilis-javascript-midnighty-137907">održavaju intervjui</a> i organiziraju photo sessioni, a on je i dalje ostao skroman, ali vrstan mladi developer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xxB1vvlQc4TDmLSe6A2Drw.jpeg" /></figure><p>Osim Sergeja koji je bio veliki motivator AJSS studentima, ključna motivacija bio je program radionica prilagođen predznanju polaznika. Obrađeni su <strong>JavaScript</strong>, <strong>Node </strong>i <strong>React </strong>te odradili brojni praktični zadaci kako bi pripremili AJSS 15-orku na završni projekt koji su sami trebali napraviti. Taj projekt bio je potvrda: <strong>predavačima </strong>da su uspješno prenijeli znanje i <strong>studentima </strong>da su zaista naučili, kao i da to znanje mogu implementirati u praksi.</p><h4>Samo pusta predavanja ili nešto više?</h4><p>Uz završni projekt, polaznici su svaki tjedan dobivali zadaću koju su pregledavali i komentirali na predavanju kako bi što kvalitetnije obradili sadržaj. Predavačima, koji su ujedno bili i <strong>mentori dostupni 24/7</strong>, bilo je važno izgraditi prijateljski odnos u kojem će svi moći pitati i komentirati što god im nije jasno ili gdje smatraju da bi mogli naići na problem. Vjerujem da je taj prijateljski odnos u obrazovnom sustavu, kao i brzina prilagodbe novim potrebama tržišta krucijalna.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0EpsS95Ev-Op3N2E6_a_EQ.jpeg" /></figure><p>Iako navedeni programski jezici još uvijek nisu zauzeli svoje mjesto u kurikulumima hrvatskih fakulteta, poznavanje istih postalo je uvjet za dobivanje posla u struci. Iz tog razloga jako cijenimo studente koji žele raditi na svom znanju i koji su upoznati s potrebama tržišta, posebno brzim izmjenama novih trendova u programiranju. Da to nije samo floskula u Axilisu, može potvrditi 5-ero polaznika Axilis JavaScript škole kojima je ponuđen posao.</p><p>Osim učenja tijekom tih 5 radnih subota i nesprestane komunikacije na <a href="https://medium.com/u/26d90a99f605">Slack</a>u, bilo je puno zabave i smijeha na predavanjima kad bi nekom od predavača zapeo demo, kao i za vrijeme ručka kad smo se osjećali kao da smo vani s društvom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QyQWgl4_jwu5kEjiwxl31A.jpeg" /></figure><h4>Malo statistike još nikog nije ubilo</h4><p>Međusobna povezanost i prijateljski pristup odlično su prihvaćeni od strane polaznika. Na pitanje: “Što te posebno oduševilo na AJSS radionicama?” u anketi koju smo proveli nakon AJSS, najviše ljudi odgovorilo je upravo to — <strong>prijateljski pristup</strong>. Samo neki od odgovora su:</p><blockquote>Atmosfera, te prijateljski i vrlo profesionalni i stručni odnos svih djelatnika Axilisa.</blockquote><blockquote>Pristupačnost cijele Axilis ekipe te spremnost na pomoć u svakom trenutku, što za vrijeme, što izvan trajanja radionica.</blockquote><blockquote>Totalna opuštenost tijekom predavanja. Sudjelovanje svih koji su prisutni u prostoriji u nastavi posvaljanjem pitanja bez i malo zadrške i osuđivanja.</blockquote><blockquote>Jako smo srdačno primljeni i voditelji i svi drugi iz Axilisa koji su bili s nama na radionicama su bili jako dragi prema nama i nastojali da nam bude što ugodnije.</blockquote><h4>Suza u oku, knedla u grlu</h4><p>Pitali smo ih i što će od stečenog znanja i vještina moći primijeniti na novim projektima. <strong>Više od 70% ekipe odgovorilo je — sve.</strong> Dok smo čitali odgovore ankete, već smo na ovom pitanju bili razgaljeni.</p><p>To potvrđuje i sljedeće pitanje — “Axilis JavaScript School bila bi kvalitetnija kada bi…”, odnosno odgovori: trajala dulje (1) i se ne bi prekinula (2). I mi bi da je moglo trajati dulje…</p><h4>Red, rad i disciplina</h4><p>Ovogodišnja Axilis JavaScript škola okupila je tim mladih developera koji su svojom voljom i disciplinom ranosubotnjeg ustajanja, kao i aktivnom interaktivnošću i spremnošću na rad dokazali da su spremni za nove poslovne avanture. Zasluženo su dobili svoje <a href="https://blog.axilis.com/kako-obi%C4%8Dnu-prijavu-zamijeniti-personaliziranom-c4d0ada2f371">personalizirane nagrade</a> :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YFBFzJZNKrXncfD63Nlk8A.jpeg" /></figure><p>Još jednom — <strong>hvala </strong>svim studentima koji su proveli s nama 5 tjedana, svima koji ove godine nisu dobili priliku sudjelovati jer smo bili ograničeni s brojem mjesta i svima koji su sudjelovali u realizaciji Axilis JavaScript School.</p><p>Hvala na čitanju! ❤!</p><p>Who is <strong>Axilis</strong>? We are an agile team of <strong>exceptional engineers</strong> and <strong>designers</strong>, who like to help businesses of all sizes <strong>design &amp; build impactful software products</strong>. Check us out on <a href="https://www.facebook.com/axiliscom/">Facebook</a>, <a href="https://twitter.com/axiliscom">Twitter</a>, <a href="https://www.instagram.com/axiliscom/">Instagram </a>and <a href="https://www.linkedin.com/company/axilis">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1f151df3813" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axilis/https-blog-axilis-com-pitali-ste-kako-je-prosla-axilis-javascript-skola-e1f151df3813">Pitali ste kako je prošla Axilis JavaScript škola…</a> was originally published in <a href="https://medium.com/axilis">Axilis</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kako običnu prijavu zamijeniti personaliziranom]]></title>
            <link>https://medium.com/axilis/kako-obi%C4%8Dnu-prijavu-zamijeniti-personaliziranom-c4d0ada2f371?source=rss----1976fa49668c---4</link>
            <guid isPermaLink="false">https://medium.com/p/c4d0ada2f371</guid>
            <category><![CDATA[schools]]></category>
            <category><![CDATA[free]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[students]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Danijela Kobescak]]></dc:creator>
            <pubDate>Fri, 16 Jun 2017 11:51:07 GMT</pubDate>
            <atom:updated>2017-06-19T07:24:38.157Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QY0EVyE6HzveXYJEzqGLcg.png" /></figure><p>Puno smo <a href="https://blog.axilis.com/axilis-javascript-school-2-0-22e5739e61b0">najavljivali</a> i <a href="https://blog.axilis.com/the-1st-axilis-javascript-school-workshop-is-done-808667471cc4">pisali</a> o Axilis JavaScript školi prije nekoliko mjeseci, ali nismo spomenuli kako je došlo do prijavnog procesa i koji je bio njegov tajni sastojak. Nakon što smo odradili sve u vezi AJSS, možemo reći da smo posebno zadovoljni kako je sve prošlo. A započelo je silnom željom za nečim drugačijim i to ne samo od prve AJSS, već i od svih mogućih dosadnih prijava na koje smo naišli.</p><p>Da se prvi mačići u vodu bacaju, potvrđuje i naš prošlogodišnji sustav prijave na AJSS kad smo otišli malo predaleko sa simplifikacijom aplikacije. Zato smo ove godine odlučili biti nešto mudriji i pokušali pronaći najproduktivniji način za izvući ono najbolje od prijavljenih. Nakon brojnih poslijeposlovnih beerstormanja u kuhinji, shvatili smo da je tajni sastojak dati mogućnost i potrebne alate kako bi svaki kandidat dobio jednaku šansu pokazati svoj karakter. Ideja vodilja bila je personalizirati samu prijavu.</p><h4><strong>Napravi svoj avatar</strong></h4><p>Drugim riječima — opiši se sam kako najbolje znaš i dok se opisuješ gledaj u što ti se pretvara avatar. AJSS tim napravio je intuitivnu i kreativnu aplikaciju dizajniranu kako bi se maksimalno reducirali napetost i stres prilikom prijavljivanja. Svaki kandidat dobio je na raspolaganje 25 bodova koje je mogao rasporediti kroz set karakteristika kako bi se najbolje opisao i oduševio stručni žiri.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/797/1*F0YPpK5Y5XL4X_gySXFJ3Q.gif" /></figure><p>Uvođenjem dimenzije osobnog, nismo samo saznali nešto više o kandidatima, nego ih i zabavili. Dosta nam je više aplikacija koje ispunjavamo cijelu vječnost, postajemo frustrirani, skoro zaboravimo za što se prijavljujemo pa krenemo upisivati štogod nam prvo padne na pamet samo da je čim prije završimo. I ono najvažnije — željeli smo pronaći ne isključivo mlade talente, već ljude od krvi i mesa sa snažnim, jedinstvenim karakterima.</p><h4>Easter Eggs</h4><p>Da malo zapaprimo situaciju i ispipamo kako će kandidati reagirati na neoubičajenosti (s kakvima se susrećemo gotovo svaki dan sa zahtjevima klijenata) AJSS tim ubacio je u prijavu i nekoliko easter eggova. Neki od njih probudili su kod manjeg broja prijavljenih inženjerski instinkt i učinili nas ponosnima. Na primjer, ekipa koja je odabrala JavaScript, Web development i HTML dobila je poruku s tragom za sljedeći korak gdje su mogli crackat aplikaciju i dobiti dodatnih 25 bodova za avatar. Ne treba ni napominjati da su ti ustrajni hakeri željni avanture ostvarili prednost. Tko bi odolio ovakvom profilu kandidata?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*23vqfK-iND-g0guy9lciag.png" /></figure><p>Neki od njih bili su fokusirani na humor, jer što je muškarac bez dobrog smisla za humor. Stand up komičari koji su za svoj avatar odabrali 10/10 za humor (a bilo je i takvih), dobili su zahtjev da to i dokažu. Iako smo vas uhvatili nespremne, svaka čast! Pošteno smo se nasmijali.</p><h4><strong>Personalizirane nagrade</strong></h4><p>Kad smo već krenuli s personaliziranim avatarima još kod prijave, htjeli smo 15-oricu veličanstvenih, koji su uspješno odradili Axilis JavaScript School, nagraditi s unikatnim nagradama. Umjesto staromodnih papirnatih diploma, pripremili smo im nagrade s avatarom kojeg su sami napravili. Sreća na dodjeli nagrada bila je obostrana.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Iv837CKNk6236v311HNaFA.jpeg" /></figure><p>Uskoro detaljnije o ovogodišnjoj Axilis JavaScript školi — u pisanom i <strong>video </strong>formatu.</p><p>Hvala na čitanju! ❤!</p><p>Who is <strong>Axilis</strong>? We are an agile team of <strong>exceptional engineers</strong> and <strong>designers</strong>, who like to help businesses of all sizes <strong>design &amp; build impactful software products</strong>. Check us out on <a href="https://www.facebook.com/axiliscom/">Facebook</a>, <a href="https://twitter.com/axiliscom">Twitter</a>, <a href="https://www.instagram.com/axiliscom/">Instagram </a>and <a href="https://www.linkedin.com/company/axilis">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4d0ada2f371" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axilis/kako-obi%C4%8Dnu-prijavu-zamijeniti-personaliziranom-c4d0ada2f371">Kako običnu prijavu zamijeniti personaliziranom</a> was originally published in <a href="https://medium.com/axilis">Axilis</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 1st Axilis JavaScript School workshop is done!]]></title>
            <link>https://medium.com/axilis/the-1st-axilis-javascript-school-workshop-is-done-808667471cc4?source=rss----1976fa49668c---4</link>
            <guid isPermaLink="false">https://medium.com/p/808667471cc4</guid>
            <category><![CDATA[workshop]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[axilis-javascript-school]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Danijela Kobescak]]></dc:creator>
            <pubDate>Wed, 15 Mar 2017 11:56:09 GMT</pubDate>
            <atom:updated>2017-03-15T11:56:08.792Z</atom:updated>
            <content:encoded><![CDATA[<h4>1 lecturer, 2 mentors, 10 pizzas and 16 attendees to conquer the JavaScript</h4><p>After 2 weeks of analyzing more than 350 candidates that applied for Axilis JavaScript School and interviewing the selected 30, we finally chose our magnificent sixteen and invited them to Axilis’ office this Saturday. To be totally honest with you, we were a bit afraid that it will be too early to start the first workshop at 9 am, buuut all of them showed up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7k9tzzmemwwTQXfhg-86sg.jpeg" /></figure><p>First, we got to know each other with a cup of hot coffee and some sweets, and then we started the lecture with lots of jokes, regular and developer ones. We tried to take a break, but nothing worked… until the pizza came in the house.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QyQWgl4_jwu5kEjiwxl31A.jpeg" /></figure><p>The lecturer of the last Saturday’s workshop was <a href="https://medium.com/u/837cfb881423">Vedran Maršić</a> who is a senior developer experienced in wide variety of projects. Vedran enjoys teaching, coding being his personal favorite.</p><p>“With the Axilis JavaScript School workshops I combined my two loves: coding and teaching, and that’s why I do it with pleasure and passion. Young people who are just getting into coding careers and have a lot of questions are pretty interesting. Also, I’m very glad that they are so ambitious and ready to ‘spend’ their free time on some more learning”, said Vedran.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xQGY7r2PY8yPPblIZ1x63w.jpeg" /></figure><p>Basics of JavaScript are conquered.</p><p>Can’t wait for the 2nd AJSS workshop next Saturday.</p><p>If you are interested in more details about the 1st Axilis JavaScript School workshop, material is available on <a href="https://github.com/axilis/jsschool-2017">GitHub</a>!</p><p>Don’t forget to fill our ❤ and check new AJSS materials next 4 Saturdays!</p><p>Who is <strong>Axilis</strong>? We are an agile team of <strong>exceptional engineers</strong> and <strong>designers</strong>, who like to help businesses of all sizes <strong>design &amp; build impactful software products</strong>. Check us out on <a href="https://www.facebook.com/axiliscom/">Facebook</a>, <a href="https://twitter.com/axiliscom">Twitter</a>, <a href="https://www.instagram.com/axiliscom/">Instagram </a>and <a href="https://www.linkedin.com/company/axilis">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=808667471cc4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axilis/the-1st-axilis-javascript-school-workshop-is-done-808667471cc4">The 1st Axilis JavaScript School workshop is done!</a> was originally published in <a href="https://medium.com/axilis">Axilis</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Axilis JavaScript School 2.0]]></title>
            <link>https://medium.com/axilis/axilis-javascript-school-2-0-22e5739e61b0?source=rss----1976fa49668c---4</link>
            <guid isPermaLink="false">https://medium.com/p/22e5739e61b0</guid>
            <category><![CDATA[axilis-javascript-school]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[schools]]></category>
            <dc:creator><![CDATA[Danijela Kobescak]]></dc:creator>
            <pubDate>Thu, 16 Feb 2017 11:21:59 GMT</pubDate>
            <atom:updated>2017-02-16T11:39:31.315Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Applications are open — ready, steady, apply!</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p1YIcSYbwirGfB_dllEZag.jpeg" /></figure><p>Almost 1 year after our first Axilis JavaScript School, we are proud to present the second one with the same motivation — extracurricular education. This year’s JS School will be organized in our new office and will contain 5 free workshops, held on Saturdays from 9am to 1pm. The first workshop will start on March 11th. JS School requires basic knowledge of programming, not necessarily in JavaScript.</p><p><strong>Our motivation and Croatian situation (read it out loud)</strong></p><p>One of the biggest problems in the educational system is the lack of practical competence. Nowadays, students have a great theoretical background, but are lost in the sea of the available technologies not recognized in university curriculums. In some fields it’s not a big deal, however, in software development, it is. As most of our projects require developers to be up to date with latest technologies, we are constantly investing in educating people internally, which is also a part of the reason we decided to open our door to the community last year.</p><p>As a development company, we always need to be on our toes, we adopt new technologies early, quickly making us competent to transfer knowledge to other people. We decided to take action and jump on the education train to fill in the gap.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EJRRkIsfBYeEXfFaJXltnw.jpeg" /></figure><p><strong>What will you get?</strong></p><p>As JavaScript is not covered in Croatian universities’ courses, you would be getting valuable knowledge: both theory and practice, all for free <a href="https://blog.axilis.com/axilis-new-croatian-headquarters-unveiled-57c0c6fb6776#.96ig0olrq">in a new office</a> with mentors who will lead and assist you on your projects, but also answer many questions that you haven’t even thought of yet.</p><p>Lecturers of the workshops will be our engineers who are quite active writing blog posts, speaking at the conferences, work full-time job and have some cool hobbies. For 5 Saturdays, they will be your mentors who can’t wait to share their valuable knowledge with you.</p><p>The greatest emphasis of our workshops will be on applied knowledge. We combine theory with practical assignments and code reviews. By the time Axilis’ JavaScript School ends, you will have acquired the skills necessary to develop your own application. Stand out, and you might even get a job at Axilis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UScPAHKkVlht8DEGl_unvg.jpeg" /></figure><p><strong>What last year’s attendees have got?</strong></p><p>Didn’t I just mention that if you stood out, you might get a job? Yeah, I did and I was serious. Last year, 2 out of 15 attendees were special, passionate and pretty ambitious about JavaScript which is why we offered them a job. They said yes and we worked happily ever since.</p><p>If you’re curious and want to know how the first Axilis JavaScript School went down, read more in <a href="https://blog.axilis.com/filling-the-education-gap-how-we-organized-our-first-javascript-school-ec82eb78175f#.4rofto7g6">our blog post</a> and check all school materials that are available on <a href="https://github.com/axilis/jsschool-2016">GitHub</a>.</p><p>And if you are interested in more details about this year’s workshops, check <a href="http://jsschool.axilis.com/">our website</a> and apply.</p><p>Don’t forget to fill our <strong>❤ </strong>and that you can apply for the Axilis JavaScript School until the 2nd of March!</p><p>Who is <strong>Axilis</strong>? We are an agile team of <strong>exceptional engineers</strong> and <strong>designers</strong>, who like to help businesses of all sizes <strong>design &amp; build impactful software products</strong>. Check us out on <a href="https://www.facebook.com/axiliscom/">Facebook</a>, <a href="https://twitter.com/axiliscom">Twitter</a>, <a href="https://www.instagram.com/axiliscom/">Instagram </a>and <a href="https://www.linkedin.com/company/axilis">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22e5739e61b0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axilis/axilis-javascript-school-2-0-22e5739e61b0">Axilis JavaScript School 2.0</a> was originally published in <a href="https://medium.com/axilis">Axilis</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Axilis’ New Croatian Headquarters Unveiled]]></title>
            <link>https://medium.com/axilis/axilis-new-croatian-headquarters-unveiled-57c0c6fb6776?source=rss----1976fa49668c---4</link>
            <guid isPermaLink="false">https://medium.com/p/57c0c6fb6776</guid>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[office]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Danijela Kobescak]]></dc:creator>
            <pubDate>Wed, 01 Feb 2017 09:19:52 GMT</pubDate>
            <atom:updated>2017-02-16T11:41:22.481Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Place for Collaboration, Creativity and Community</h4><p>A few months ago we <a href="https://blog.axilis.com/oops-we-did-it-again-40d956f22bfc#.wkrymq4d6">shared a photo</a> of the raw space that we’ve chosen to become Axilis’ future Croatian headquarters. Guess what? The build out is done!</p><p>We’re proud to present you our new home in Radnička cesta in Zagreb.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qq8b4DrM1CMwpPkYlQAcHQ.jpeg" /></figure><p>After gutting the entire space (and creating a huge mess in the process), it was hard to imagine that it could ever become an inviting environment.</p><p>But six months later, we’re all moved into our new 325 square meter (3,500 square foot), industrial-design-inspired digs. To say we feel at home, would be an understatement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AxdYRIH0O4trJlsdCZXtgg.jpeg" /></figure><p>We wanted to create a fluid and functional interior that promotes creativity and teamwork. Additionally, we wanted the space to reflect Axilis’ friendly, relaxed culture. Finally, we needed a lot of light in order to keep our plants alive (us techies are not known for our green thumbs).</p><p>Based on these goals we decide to adopt an open concept. We did so though fully aware of the potential downsides — a lack of privacy and excessive noise.</p><p>To mitigate these concerns we broke the space up into smaller work areas, made liberal use of “white space,” and added a lot of soundproofing.</p><p>The conference room is an elegant glass box smack dab in the center of the office.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uGMswKb4J-guXStczpz07w.jpeg" /></figure><p>There are 2 phone rooms that are ideal for quiet, solo work or for conference calls with our American colleagues and clients. Usually phone rooms are very small, and can only fit one person at a time. We opted for larger rooms that can accommodate multiple team members, whether they are on a call or otherwise collaborating.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QvcLAdmB1tpbNVvZmrR0rg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dHPaYtwZ2yJwrjKn90sEKw.jpeg" /></figure><p>The kitchen is the communal heart of our office. Here, we love to eat, make espresso and catch up with one another. Also every Thursday, it’s the site of our “ChCh” — the internal meetups that have become an integral part of Axilis culture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1TjsbcpP2ucEtURXb-_2cw.jpeg" /></figure><p>The living room is what you’d expect: a mellow area with lots of comfortable seating.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SyRMTcFh2hnnAsj3fckAig.jpeg" /></figure><p>Next to the living room is a black wall, featuring a giant drawing by our designers. Once we get bored with this drawing, they will “delete” it and draw a new one, they said. It will be fun, they said.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hcluLbToZd4LBnY8i9YTWw.jpeg" /></figure><p>This office is a good combination of the comfort of home and professional business atmosphere. If you agree, fill our empty <strong>❤</strong></p><p>Who is <strong>Axilis</strong>? We are an agile team of <strong>exceptional engineers</strong> and <strong>designers</strong>, who like to help businesses of all sizes <strong>design &amp; build impactful software products</strong>. Check us out on <a href="https://www.facebook.com/axiliscom/">Facebook</a>, <a href="https://twitter.com/axiliscom">Twitter</a>, <a href="https://www.instagram.com/axiliscom/">Instagram </a>and <a href="https://www.linkedin.com/company/axilis">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57c0c6fb6776" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axilis/axilis-new-croatian-headquarters-unveiled-57c0c6fb6776">Axilis’ New Croatian Headquarters Unveiled</a> was originally published in <a href="https://medium.com/axilis">Axilis</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Axilis makes Deloitte’s list of fastest growing technology companies]]></title>
            <link>https://medium.com/axilis/axilis-makes-deloittes-list-of-fastest-growing-technology-companies-2f01873e35ba?source=rss----1976fa49668c---4</link>
            <guid isPermaLink="false">https://medium.com/p/2f01873e35ba</guid>
            <category><![CDATA[deloitte]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Bruno Kovacic]]></dc:creator>
            <pubDate>Wed, 26 Oct 2016 08:49:11 GMT</pubDate>
            <atom:updated>2016-10-26T09:58:03.162Z</atom:updated>
            <content:encoded><![CDATA[<h4>#22 in Central Europe and #3 in Croatia</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5BdTj22NaBQHIchgJ8hH6w.png" /></figure><p>U.S. professional services giant<a href="http://www.deloitte.com/"> Deloitte</a> has named Axilis to its <a href="http://www2.deloitte.com/global/en/pages/about-deloitte/articles/technology-fast-50-ce.html">17th annual list of the fastest growing technology companies in Central Europe</a>.</p><p>Axilis’ ranking was based on our revenue growth of <strong>613%</strong> between 2012 and 2015.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KeOQAQ_EKNiG8gnskB7B2A.png" /><figcaption>Croatian firms on Deloitte Technology Fast 50 list</figcaption></figure><p>Read more at <a href="http://www2.deloitte.com/global/en/pages/about-deloitte/articles/technology-fast-50-ce.html">Deloitte</a>, <a href="http://www.index.hr/vijesti/clanak/ovih-sest-hrvatskih-tvrtki-razvaljuje-po-rastu-u-europi/928016.aspx">Index.hr</a> and <a href="http://www.netokracija.com/deloitte-technology-ce-fast-50-2016-126075">Netokracija.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f01873e35ba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axilis/axilis-makes-deloittes-list-of-fastest-growing-technology-companies-2f01873e35ba">Axilis makes Deloitte’s list of fastest growing technology companies</a> was originally published in <a href="https://medium.com/axilis">Axilis</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Things you should know before using Lambda]]></title>
            <link>https://medium.com/axilis/5-things-you-should-know-before-using-lambda-bf4cf1c9d917?source=rss----1976fa49668c---4</link>
            <guid isPermaLink="false">https://medium.com/p/bf4cf1c9d917</guid>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Sergej Jakovljev]]></dc:creator>
            <pubDate>Mon, 17 Oct 2016 13:56:03 GMT</pubDate>
            <atom:updated>2016-10-17T13:56:03.392Z</atom:updated>
            <content:encoded><![CDATA[<p>Like any relatively new tool, there are a lot of small things about AWS Lambda that you don’t figure out before really diving into it. Below I outline 5 areas where you can expect challenges, and ways to address them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1dt-1XZSt0zJ7Qwues6GVw.png" /></figure><h3>1. Code structure</h3><p>Unlike traditional, monolithic applications where setup is typically straightforward, seemingly simple things on Lambda may require some workarounds.</p><h4>Environment variables</h4><p>Lambda doesn’t support typical environment variables, but there are some alternatives:</p><ul><li><strong>Stage variables — </strong>Although <a href="https://aws.amazon.com/blogs/compute/using-api-gateway-stage-variables-to-manage-lambda-functions/">stage variables</a> only work for functions that are called through API Gateway, they are an easy way to set specific variables for each development stage.</li><li><strong>Build phase injection — </strong>You can store environment variables in a build service. When the build succeeds, it will insert the appropriate variables and deploy the code.</li><li><strong>Configuration service — </strong>A centralized service can store all settings. Then using one of the previous methods to configure access to the service, a function can retrieve needed information. This approach brings the additional benefit of having all of your configuration in one place.</li></ul><p>In practice, you’ll probably end up using some combination of the options above. A significant advantage of microservices is that you don’t need to make such decisions for everything upfront — you can implement each microservice however makes the most sense.</p><h4>Functions end up simple, integration becomes hard</h4><p>Since services end up being simple functions, it’s easy to unit test them. However, that also means that conventional, manual local testing of the whole stack is significantly harder as it requires configuration of all of the interdependent services.</p><p>In <a href="http://martinfowler.com/articles/microservice-testing/">Testing Microservice Architecture</a>, Martin Fowler provides valuable insights into the different approaches. I recommend reading it.</p><h4>Initial configuration overhead</h4><p>While each service has a smaller set of dependencies compared to a monolithic architecture, much more effort is required in aggregate to configure all of the services.</p><p>Because each microservice is an isolated unit, each will require its own separate initial setup including repository permissions, code integration, linter, test runner, monitoring tools, etc. Furthermore, current deployment tools are still missing some settings (such as VPC-s when using <a href="https://claudiajs.com/">Claudiajs</a>), and so you’ll need to manually configure certain things.So, in the beginning, it may seem as there is not much progress.</p><p>After you finish all of the configuration, however, the benefits will soon become evident: build times will be much shorter since each service has its own set of dependencies. Service separation also makes it easier for multiple people to work on different parts of the project at the same time.</p><h3>2. Using Amazon RDS with Lambda</h3><p>RDS needs to reside inside the same VPC (Virtual Private Cloud) as the Lambda functions to be used with it.</p><p>If the Lambda functions only need to access RDS, the default VPC setup will suffice since input to and output from Lambda will be piped through API Router.</p><p>However, if the Lambda functions need to access both Amazon RDS and other web services such as remote APIs, further VPC configuration will be required. It will be necessary to <a href="https://gist.github.com/reggi/dc5f2620b7b4f515e68e46255ac042a7">add NAT gateway and setup routes</a> to enable entities inside VPC to access the Internet.</p><p>While the effort required to run a “Hello World” function is small, integrating VPC and Lambda may take some time, and has considerable <a href="http://docs.aws.amazon.com/lambda/latest/dg/vpc.html">implications</a>:</p><ul><li>Automatic scaling of the number of instances becomes limited by VPC subnet address space within Lambda function resides. The default VPC contains subnets with about 250 addresses remaining. While that may seem like a lot, it is shared among all instances of all services connected to a given subnet.</li><li>Additional setup is required to achieve redundancy by configuring functions and VPC in multiple availability zones.</li><li>Lambda functions that run within a VPC require additional start-up time in order to connect the ENI (Elastic Network Interface) to the instance.</li></ul><h3>3. Lambda limits and pricing</h3><p>Some of Lambda’s <a href="http://docs.aws.amazon.com/lambda/latest/dg/limits.html">limits</a> may not be immediately apparent.</p><p>When compressed into an archive, the code for each service cannot exceed 50MB (250MB uncompressed). While this may seem like a lot, if you’re not careful in your use of Node packages, it is quite possible to exceed it. Additionally, there is a 75GB limit within the entire region, which includes all versions of all of the Lambda functions. Since deploying a new version doesn’t automatically delete the old ones — unless you delete them manually — they will remain and take up space.</p><p>There is also a limit of 100 concurrent executions per account per region that can be increased by making a request to AWS in the support center.</p><h4>Pricing</h4><p>Although Lambda may be inexpensive — and, in many cases, is — there are a number of additional costs when using it.</p><p>For example, using VPC to enable database and internet access for a given service, requires at least one NAT Gateway plus the associated data transfer costs. All services which initiate external data transfers (e.g. external API) are charged at the EC2 data transfer rate. There will likely be some database and S3 hosting expenses as well.</p><p>So when estimating the total cost of using Lambda, make sure you include all of the needed AWS services in the calculation.</p><h4>Lambda functions become frozen</h4><p>A common problem with service-oriented architectures is that queries that could be done on a single database using joins end up having to access multiple services.</p><p>One of applications more complex queries that could be done entirely in the database, when split into multiple services ended up taking an order of magnitude longer. Also joining has to be done manually since each service should be able to change data store at any time without other services even noticing. So there certainly are some tradeoffs to data separation.</p><p>Amazon automatically scales the number of instances to ensure optimal performance and cost. That also means <strong>lack of steady flow of requests will cause a function to have zero instances running</strong>. Causing next request to incur some spin up time. Even though one second may not sound as much, services that depend on others have a cascading effect.</p><p>Additionally, our tests showed that when using VPC, ENI attachment time is in the range of a few seconds. All of that combined caused the aforementioned user-facing request to take 14s when cold started. When normally, while all services are running it takes just few hundred milliseconds to execute.</p><p>Although there is no option to enforce that functions don’t freeze, it should be possible to avoid freezing by calling the function every few minutes, thereby ensuring there is an active instance. <a href="http://docs.aws.amazon.com/lambda/latest/dg/with-scheduled-events.html">CloudWatch Scheduled Events</a> are a simple way to achieve this.</p><p>Here is a great article with <a href="https://www.linkedin.com/pulse/aws-lambda-container-lifetime-config-refresh-frederik-willaert">more details about container lifetime</a>.</p><h3>4. Deployment tools</h3><p>Most popular tools include <a href="https://serverless.com/">Serverless</a> and <a href="http://apex.run/">Apex</a> which mainly attempt to simplify deployment.</p><p>There are also language-specific ones such as <a href="http://claudiajs.com/">Claudiajs</a> which is focused only on Node but offers some framework-like features. One worth mentioning is <a href="https://claudiajs.com/claudia-api-builder.html">claudia-api-builder</a> which automatically generates API Gateway routes for each service and enables you to write application similar to how you would using Express in a regular Node.js stack. There is a similar Python-based tool by AWS Labs — <a href="https://github.com/awslabs/chalice">chalice</a>.</p><p>Although all of those tools can help kickstart implementation of web services, there is still much work left to be done manually, especially in more complex scenarios.</p><h4>Instance configuration requires redeployment</h4><p>While configuring VPC we had an issue where despite everything seeming to be fine, instances still couldn’t access the database. It turned out that the Lambda configuration changes requires a redeployment in order to take effect.</p><h3>5. Challenges of Continuous Integration</h3><p>With microservices, the only viable way to continuously deliver new versions of the application is by using automated tools to deploy services. However, there are some gotchas when using Lambda with CI tools.</p><h4>Building on EC2</h4><p>Most automated deployment tools bundle Node projects by installing dependencies locally, archiving them and uploading them to Lambda. That works for most packages, but some (like image resizing libraries or some parsers) have native implementations that are compiled while the package is being installed. So packages built on the development machine produce binaries that are incompatible with Lambda’s Amazon Linux.</p><p>To overcome the problem, you should always build packages on an EC2 instance running the same version of Amazon Linux as Lambda.</p><blockquote>If you compile your own binaries, ensure that they’re either statically linked or built for the matching version of Amazon Linux. The current version of Amazon Linux in use within AWS Lambda can always be found on the Supported Versions page of the Lambda docs. — <a href="https://aws.amazon.com/blogs/compute/running-executables-in-aws-lambda/">https://aws.amazon.com/blogs/compute/running-executables-in-aws-lambda/</a></blockquote><h4>Automatic migrations</h4><p>Since the database is only available within the VPC, the easiest way to run automatic migrations upon deployment is to have the CI server located inside the VPC as well.</p><h4>How we ended up doing it?</h4><p>Although CircleCI is Axilis’ preferred CI tool, we weren’t able to use it with AWS Lambda due to the aforementioned issues.</p><p>One solution to both problems is to use an EC2 instance running a self-hosted version of a CI tool. We finally settled on Jenkins.</p><h3>So… should I use Lambda?</h3><p>Yes! Just make sure it fits the problem you are trying to solve.</p><p>There are challenges you will need to face, but each platform of course has its own. Overall, Lambda and serverless infrastructure in general, offer a lot of advantages that will pay off if you need to build a large, scalable system.</p><p><em>We do our best to share our knowledge with you. If you found this post helpful, please hit that little heart.</em></p><p><a href="http://www.axilis.com/"><strong><em>Axilis</em></strong></a><em> is a premium software design and development company with offices in New York and Croatia.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf4cf1c9d917" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axilis/5-things-you-should-know-before-using-lambda-bf4cf1c9d917">5 Things you should know before using Lambda</a> was originally published in <a href="https://medium.com/axilis">Axilis</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Filling the education gap — how we organized our first JavaScript school]]></title>
            <link>https://medium.com/axilis/filling-the-education-gap-how-we-organized-our-first-javascript-school-ec82eb78175f?source=rss----1976fa49668c---4</link>
            <guid isPermaLink="false">https://medium.com/p/ec82eb78175f</guid>
            <category><![CDATA[agencylife]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Petar Kovačević]]></dc:creator>
            <pubDate>Tue, 28 Jun 2016 12:41:40 GMT</pubDate>
            <atom:updated>2016-06-28T12:41:40.091Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*5dgEU0rPUmxsjUFLn6uPDw.jpeg" /></figure><p>Last week we ended our little JavaScript adventure, five free workshops which we conveniently hid under the name — Axilis JavaScript School. It was a great experience for us and for a few minutes, we’re going to describe what made us undertake such journey and dedicate our employees’ Saturdays for this cause, what were the challenges we fought and how satisfied we were with the overall result.</p><h4>Post Graduation Reality</h4><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*z2RcrRJQFMpZmGgmZk-y5A.jpeg" /></figure><p>One of the problems we face, as a development agency in Croatia, is that we get a lot of fresh graduates with strong theoretical backgrounds but often lacking real-life practical knowledge. Our experience has shown that graduates with strong theoretical background end up as a pretty good molding material — they are problem solvers, they adapt quickly to new environments and they learn new technologies pretty quick. But there has to be a better balance between practice and theory, because today a great amount of work falls on our backs. Companies are required to invest time, resources and people into the molding process. That could take months or even years and is an investment that most companies can’t afford.</p><p>Universities in Croatia are recognizing this issue. There are more and more optional classes that are giving students practical experience, but unfortunately, they can often lag behind the reality in terms of latest technologies.</p><p>On the other side, as a development company, we always need to be on our toes, we early adopt new technologies and that makes us early competent to transfer knowledge to other people. We decided to take action and jump on the education train to fill in the gap. We decided to open our first Axilis school.</p><h4>What’s Cookin Doc?</h4><p>Majority of the work done today in Axilis is related to JavaScript. Be it backend applications on Node or mobile apps with React Native and Cordova, we have guys here that really know their business. It was no brainer, our first school had to be about JavaScript. We also anticipated more people would be interested in learning JavaScript than anything else since it’s everywhere today and the business opportunities are pretty rich. And did I mentioned it’s not covered in our universities?</p><p>But there were some other floating questions. How many people are we capable of handling? What format should we deliver the lectures in? How many lectures should we do? What should be the time frame in which the lectures will take place? We started tackling questions one by one.</p><p>First major issue was the time frame. School was open for people of all profiles but we expected most of our applicants to be students still doing their homework and exams. We didn’t want to overlap with their activities. The other thing we didn’t want to overlap with were some similar initiatives by our local friends. We found a nice, untouched stretch of five weeks, just before final exams and summer break, leaving enough room for students to tackle their other activities after the JavaScript school.</p><p>We were counting on five weeks, Saturday morning sessions were a safe bet which meant we had only five lectures to spare. Some of our speakers were already raging — you expect me to teach them Node in just one session?! Of course it was impossible to cover everything there is about Node in just a couple of hours, a certain amount of individual work was expected of our attendees. Everybody had to understand that our job was to kick start them, show them the basics and give them an opportunity to grow further with our assistance and mentoring.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*C8FAPffyjPou_XsOU7MAIQ.jpeg" /><figcaption>(Photo: Wikipedia)</figcaption></figure><p>The other thing we had to settle was the number of attendees we would be able to accept during the lectures. This was directly tied to the question of lecture delivery format. We knew that the best way to learn was through hands on labs. We wanted the attendees to be involved and active, so we didn’t want the groups to be too big. We also had a limited number of staff available for every lecture, we needed to make sure the number of staff and attendees is sufficient for every attendee to get the right level of support during the assignments.</p><p>We kept our expectations low regarding the applicants number, because we had no clue about how this will catch on in the community. We decided to go with a magic number of 15 attendees which has, spoiler alert, proven to be a great choice.</p><h4>The Magnificent Fifteen</h4><p>So, everything was settled, we agreed on five lectures, we had the dates, five experts that will cover the topics. There was no going back. We pushed the registration page online and then we got a nice surprise — in just a few days, we got more than 200 applications. It was a nice confirmation that our school was heading on a right track, a lot of people recognized the gap we were trying to fill.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*IU-yf1MZSwd1wrNX2R_Rvw.jpeg" /></figure><p>After the initial excitement came a cold realization — we will have to say no to a lot of quality individuals. Our registration form was relatively simple, the exception being a small motivational letter we expected to see from our applicants. It wasn’t such a good idea since many candidates didn’t find the field important, but it ended up being our only mean of filtering people. Definitely, in the future we will probably go with some kind of problem solving assignment.</p><p>In the end, we’ve read every single motivational letter and finally decided on 15 great attendees. Profiles varied, most of them were software engineering or computer science students, but we even had civil and mechanical engineers in the group.</p><h4>Schedule</h4><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*vQAhx3oU-FsBeTlm2hs_9A.jpeg" /></figure><p>Now a few words about the organization of the workshops. As I already said, we had five different speakers, each expert in the topics they were assigned to speak about. Some of them didn’t have any experience with public speaking, but a friendly atmosphere in the room helped the speakers and attendees to really be themselves. Good thing we decided for a smaller group.</p><p>In the first workshop we had a slow start with JavaScript language basics. We knew that almost nobody in the room could say they perfectly understand JavaScript and all of its flaws (or dare I say it, features) so the lecture was convenient for the first timers, but also the JavaScript veterans.</p><p>After the torture with vanilla JavaScript, second workshop introduced the much friendlier ES2015 standard. Attendees managed to see how they can use this new JavaScript today, even without the full browser support. Additionally, they got a sneak peak of the concepts they’ll be using in Node and React applications.</p><p>Third workshop was dedicated to building server applications with Node and Express, and the fourth one rounded it off with building web clients with React. We decided to leave the fifth workshop as a let’s-see-what-we-learned lecture. Attendees were split into teams and they had to build a final project using the knowledge they gathered during the workshops. Of course, we were always there for them, mentoring and assisting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bbWJ___izXm6EjGlKExsbA.jpeg" /><figcaption>Axilis JavaScript School</figcaption></figure><p>Finally, just by looking at the applications number, it’s obvious a large interest exists for these kinds of initiatives. We got good feedback from our attendees, we’ve met some quality individuals and are more than satisfied with the experience got from organizing the JavaScript school. We definitely plan on organizing similar events in the future especially since there are plenty of interesting topics we could cover. Regarding the JavaScript school, there is no reason not to see it again next year (or who knows, even sooner).</p><p>If you want to see what we did, all school materials are available on <a href="https://github.com/axilis/jsschool-2016">GitHub</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec82eb78175f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axilis/filling-the-education-gap-how-we-organized-our-first-javascript-school-ec82eb78175f">Filling the education gap — how we organized our first JavaScript school</a> was originally published in <a href="https://medium.com/axilis">Axilis</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Oops, we did it again!]]></title>
            <link>https://medium.com/axilis/oops-we-did-it-again-40d956f22bfc?source=rss----1976fa49668c---4</link>
            <guid isPermaLink="false">https://medium.com/p/40d956f22bfc</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agencylife]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Bruno Kovacic]]></dc:creator>
            <pubDate>Mon, 27 Jun 2016 13:12:24 GMT</pubDate>
            <atom:updated>2016-06-27T13:16:19.464Z</atom:updated>
            <content:encoded><![CDATA[<p>For the 3rd time in 5 years, team Axilis has outgrown our Croatia office!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ENe6W0FbeyxdDrM-1TF4mw.jpeg" /></figure><p>This summer we will be moving across town into the heart of Zagreb’s business district.</p><p>We’ve gutted the 325 square meter (3,500 square foot) interior, and our architects and designers have planned a gorgeous new space.</p><p>At Axilis, we believe in the power of the right environment to increase team productivity, creativity and happiness.</p><p>We look forward to hosting you soon at our new Croatian home!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40d956f22bfc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axilis/oops-we-did-it-again-40d956f22bfc">Oops, we did it again!</a> was originally published in <a href="https://medium.com/axilis">Axilis</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Context switching tax — when to talk and when to write]]></title>
            <link>https://medium.com/axilis/context-switching-tax-when-to-talk-and-to-write-766079839a91?source=rss----1976fa49668c---4</link>
            <guid isPermaLink="false">https://medium.com/p/766079839a91</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Bruno Kovacic]]></dc:creator>
            <pubDate>Thu, 09 Jun 2016 18:52:52 GMT</pubDate>
            <atom:updated>2016-06-09T18:50:04.146Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ARUvwTre5iAESZYF-UW_tg.png" /></figure><p>Peter: “Can you help me with blahblahblah?”<br>Mary: “Sure.”<br>Peter: “Hm, never mind. In fact, I just figured it out.”</p><p>…and there goes half an hour of Mary’s productivity.</p><p>Even though it only takes a couple of seconds, interrupting someone takes way more of person’s time. It’s easy to lose focus and it takes time to get it back.</p><p>In Axilis, we prefer written communication. Primarily because reading IM/mail can be avoided when you don’t want to be disturbed and secondly, the person contacting you will think more about what she needs.</p><p>Writing stuff down takes time and it can serve as a <a href="https://en.wikipedia.org/wiki/Rubber_duck_debugging">rubber duck</a> to resolve your issues even before you press “send”. When writing stuff down, you need to think more about your problem than when you just want to say it. You wouldn’t write a sentence like “You know, I was just thinking about… in fact, I just realized — not about that in particular, but… “. When you talk, sentences like that one are common. They are essentially noise which requires the listener to concentrate in order to extract the real message.</p><p>Avoid doing that. When you need something, write it down — it won’t distract your teammate, it will make sure you think through the issue and think about how to present it in a concise and understandable way.</p><p>We’re humans and we forget stuff. If you do have a longer verbal discussion, you should want to prepare the points of discussion beforehand and write down a discussion summary afterwards. Why talking and writing the same stuff down afterwards if you could have written it immediately?</p><p>I am not saying we shouldn’t talk to people, but in a workplace, written communication is more efficient in a lot of cases. And when discussions do happen, they should be meaningful, structured and their conclusions documented.</p><p>Original post: <a href="http://www.axilis.com/2016/01/04/context-switching-tax/">http://www.axilis.com/2016/01/04/context-switching-tax/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=766079839a91" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axilis/context-switching-tax-when-to-talk-and-to-write-766079839a91">Context switching tax — when to talk and when to write</a> was originally published in <a href="https://medium.com/axilis">Axilis</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>