<?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 Milan Stevanović on Medium]]></title>
        <description><![CDATA[Stories by Milan Stevanović on Medium]]></description>
        <link>https://medium.com/@milan.stevanovic?source=rss-ae051fa65f3f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6BQ8e9tiOKZfUyF3i8WNSg.jpeg</url>
            <title>Stories by Milan Stevanović on Medium</title>
            <link>https://medium.com/@milan.stevanovic?source=rss-ae051fa65f3f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 10:41:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@milan.stevanovic/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[Simplifying iOS UI Testing with Page Object Model]]></title>
            <link>https://medium.com/inside-bux/simplifying-ios-ui-testing-with-page-object-model-765a23e8ebd4?source=rss-ae051fa65f3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/765a23e8ebd4</guid>
            <category><![CDATA[ui-tests]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[page-object-model]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <dc:creator><![CDATA[Milan Stevanović]]></dc:creator>
            <pubDate>Fri, 28 Sep 2018 14:41:02 GMT</pubDate>
            <atom:updated>2018-09-28T14:58:16.410Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/782/1*vAziRzuxWw-Q_cnrQH-TZw.jpeg" /></figure><h3>Why bother to write tests?</h3><p>Let’s start with the basics, why do we even need to write tests?</p><p>Even though I’m a big proponent of writing tests, I do understand it’s sometimes the case that not enough time or resources can be dedicated to it, due to various reasons, most common being a lack of understanding from the powers that matter, or in other words a lacking company culture.</p><p>It’s usually us, developers, who have to convince our managers that we need to write tests.<br>On the other hand, there’s a substantial number of developers who simply don’t believe in writing tests, or they just don’t like writing them, for one reason or another.<br>If you are one of those developers or managers, I would ask you to carefully consider the following facts.</p><p>Hand washing in hospitals is a fairly recent practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/1*-3EFyptkKhK39qFg9UKdqA.jpeg" /></figure><p>It was only in 1847 that Hungarian doctor Ignaz Semmelweis proposed the idea of medical staff washing their hands in order to reduce mortality rates in hospitals.</p><p>His ideas conflicted with the established scientific and medical opinions of the time and his ideas and were outright rejected by the medical community of the time.<br>Because of rejection and ridicule he was exposed to, he suffered a nervous breakdown, and died in an asylum.<br>It took a long time for the medical community to start using hand washing as a mandatory practice.<br>Needless to say, since then, hand washing saved countless lives, and the mentioned doctor is a hero of the modern age.</p><h3>The killer bug</h3><p>I wish I could say that nobody had to die in order for us, software developers, to learn a similar lesson, about the importance of writing tests, but it already happened with the infamous “killer bug” in computer-controlled radiation therapy machine <a href="https://en.m.wikipedia.org/wiki/Therac-25"><strong>Therac-25</strong></a>, which caused it to malfunction and overdose at least 6 patients with massive (and in some cases even deadly) doses of radiation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*wknasUvRFpM5v02GC7X-yg.jpeg" /><figcaption>Therac-25</figcaption></figure><p>If Therac-25’s software was tested in a proper way, maybe this terrible series of tragedies could have been avoided.</p><h3>Testing iOS apps</h3><p>Situation regarding automated tests in software development community kind of looks like the late 19th century in the medical community, and this is particularly true in the iOS app development community.</p><p>Writing any kind of tests is usually an afterthought when it comes to iOS app development, especially in smaller teams. Some projects that actually have a fair amount of unit tests often totally omit UI tests.<br>As iOS developers, our job isn’t any different than that of other software developers, and we should stick to the same time-proven practices like other developers do, and thoroughly cover our code with tests.<br>Some of the tools available to us might be subpar (<strong><em>XCUITest</em></strong><em>, I’m looking at you!</em>), but that doesn’t mean we can’t build on top of them and solve the problem at hand, after all, that’s what we are being paid for.</p><h3>Testing at BUX</h3><p>When I started working at BUX, I was assigned to a team of seasoned iOS developers, who were getting ready to start building a challenging new iOS app.<br>The team has already set the quality bar very high with the <a href="https://getbux.com/"><strong>current BUX app</strong></a>, that’s been <a href="https://itunes.apple.com/app/id892809783"><strong>live on the App Store</strong></a> for several years now, and is incredibly stable, with hundreds of thousands of users and almost no crashes.<br>Needless to say, this stability is the product of rigorous testing procedures, that we are also applying and improving on, to the development process of the new app.</p><h3>New app, new challenges</h3><p>The new app that we are building is a next-gen stock trading app.<br>It’s designed from ground up with a mission of abstracting out the complexity of stock trading, bringing it to the people who might have never traded before, while keeping the user interface as intuitive as possible and adding a unique social component to it.</p><p>There’s a lot of overlapping realtime events such as stock quote updates, account balance updates, trade executions, social events and many others, that can happen in a split of a second and dynamically affect the user interface, sometimes multiple events at a time. Also, there’s a lot of custom flows that can be triggered from multiple points in the app.</p><h3>Our solution</h3><p>To reduce complexity, we have split our app into several modules/frameworks, one containing core business logic, one for making and sending http requests, another one for web socket event observation and so on.<br>Testing these frameworks was quite straightforward, by using unit tests, and they are 100% covered by unit tests.</p><p>The big question arose when it came down to testing the app itself.<br>Testing some parts of the app is quite straightforward, our logic control is decoupled from the views it supports, so we are able to easily cover most of that by using unit tests.</p><p>On the other side, testing all of the UI flows end-to-end is not so straightforward.<br>Testing them manually takes time, consumes manpower, and is error prone.<br>On the other side, automated UI testing using <strong>XCUITest</strong> isn’t the best developer experience ever.<br>There are some excellent iOS UI testing frameworks available out there, but we felt like most of them are not a good match for us, or are simply an overkill, so we decided to build our own simple and very minimal iOS UI testing framework.</p><p>What we are trying to do is to simulate the usage of the app in the way the user would use it, but in a controlled environment, by controlling all the data that the app receives. <br>In the case of unit tests this is quite simple to achieve through mocks and stubs, but in the case of UI tests it gets quite a bit more complicated because you don’t have the same level of access to the app’s code.<br>iOS App and its UI tests are essentially two separate processes and the only way for them to communicate is by passing some arguments at the start of the tests through XCUIApplication’s launchArguments variable.<br>There are some 3rd party solutions that enable passing data between the app and the UI test target even after they are already running, but we felt this was too hacky and error prone, so we built our framework around this constraint.</p><h3>Page Object Model</h3><p>Our solution is based on the Page Object Model (<a href="https://martinfowler.com/bliki/PageObject.html"><strong>great explanation by Martin Fowler here</strong></a>) pattern in combination with stubbed HTTP responses, mocked web socket events and a mechanism that allows us to have blocking, synchronous assertions.</p><p>We set the stubbed HTTP responses at the beginning of every test case, this is achieved through the use of the amazing <a href="https://github.com/AliSoftware/OHHTTPStubs"><strong>OHHTTPStubs framework</strong></a>. For the web socket event mocking, things weren’t as easy to do, so we had to create a small web server running inside the UI test target that the app connects to when UI tests start, and then we can emit the events directly from inside the UI test target accordingly to our needs. Blocking synchronous asserts are achieved through pre-existing XCUITest methods.<br>In this article I will only cover the component related to POM in details, and the other 3 components of our UI test system will be covered in a future article.</p><p>Every screen has its own page, and can also have sub-pages, eg. a screen with a table view will be a page of its own while containing as many sub-pages as the number of cells it contains, and every page will have some degree of interaction available to it (tap, swipe, detect if it’s on screen, etc.).</p><p>A Page is just a simple wrapper around a XCUIElement:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/44b98ad86429988fec9d6ab0caa20c51/href">https://medium.com/media/44b98ad86429988fec9d6ab0caa20c51/href</a></iframe><p>In turn, <strong>Page</strong> is wrapped inside the UIElementPage which provides access to particular UI elements:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1079f94cb3f2742dfa70fb9d7c2cdf10/href">https://medium.com/media/1079f94cb3f2742dfa70fb9d7c2cdf10/href</a></iframe><p>You can also see the examples of accessing different types of elements.</p><p>UIElement is a simple wrapper protocol around the accessibilityIdentifier:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/79923c33792316783ddfa9cf662f3839/href">https://medium.com/media/79923c33792316783ddfa9cf662f3839/href</a></iframe><p>In order for a view to be easily added to the accessibility hierarchy, we devised a simple protocol, UITestablePage:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/09211ac5aca49cf81dfb6460ba91d27f/href">https://medium.com/media/09211ac5aca49cf81dfb6460ba91d27f/href</a></iframe><p>UITestablePage also contains a method for making sequential types of views (eg. table cells) testable.</p><p>All our UI elements are organised as an enum UIElements with sub-enums for pages, cells, dialogs, alerts, etc.<br>Some examples of different types of pages that we have in our app:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f275db6e865be758a067cf02b94f57d8/href">https://medium.com/media/f275db6e865be758a067cf02b94f57d8/href</a></iframe><p>As you can see, a page usually has a root, which is basically the view of the view controller itself (or something else in case of a different page), and some other elements, such as buttons, tables, etc.<br>On the view controller’s side, utilisation of this looks like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/793dbaddf2dbd48920d83955da4b864d/href">https://medium.com/media/793dbaddf2dbd48920d83955da4b864d/href</a></iframe><p>First we set the adequate UIElements value for the UIElementType, then we write a helper method makeViewTestable that contains calls to methods of UITestablePage protocol that will register the elements of our view as elements of the page.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/59bcc2583bcb55bd154e668cbf7aee28/href">https://medium.com/media/59bcc2583bcb55bd154e668cbf7aee28/href</a></iframe><p>We are going to use the newly create page in SearchResultsTests:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9feee4a8d30b438d4d26c4677a56f5e0/href">https://medium.com/media/9feee4a8d30b438d4d26c4677a56f5e0/href</a></iframe><p>Here, you can see the usage of all the previously mentioned assert methods, and utilisation of the page itself. Basically this test replicates actions that a user can do on this screen, by doing a simple search, and clicking on a tag, and then asserting that the returned values are equal to expected values (that we set by our stubbing mechanism) and finally clears the text from the search bar and asserts that there are no results after that.<br> <br>It’s a simple yet illustrative example and it shows the whole principle behind our POM based UI testing system.<br>Pages and tests can be more or less complicated, depending on the use case, and the granularity required.<br>Because most of the app logic is covered by unit tests, we mostly limit our UI tests to “happy flows”, so that if we break them, our CI system will automatically notify us.</p><h3>Conclusion</h3><p>POM enables us to abstract out most of the complexity that XCUITest brings to the table. By implementing it in our UI tests, we are able to have a simple and maintainable system that’s easy to use and further extend for anything that we might require in future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=765a23e8ebd4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-bux/simplifying-ios-ui-testing-with-page-object-model-765a23e8ebd4">Simplifying iOS UI Testing with Page Object Model</a> was originally published in <a href="https://medium.com/inside-bux">Inside BUX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Living in the Netherlands]]></title>
            <link>https://medium.com/inside-bux/living-in-the-netherlands-d78f2ff8087e?source=rss-ae051fa65f3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d78f2ff8087e</guid>
            <category><![CDATA[expat]]></category>
            <category><![CDATA[relocation]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Milan Stevanović]]></dc:creator>
            <pubDate>Mon, 16 Apr 2018 12:11:22 GMT</pubDate>
            <atom:updated>2018-04-16T12:11:22.412Z</atom:updated>
            <content:encoded><![CDATA[<h4>From a perspective of a Software Developer hailing from Serbia</h4><p><strong><em>Disclaimer</em></strong><em>: Everything that you read in this is article is my personal subjective opinion and does not necessarily reflect attitudes of BUX or in that matter objective reality that might be wildly different.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TSIFfdV-LKqqiIPv_VLwCA.jpeg" /></figure><p>After working for a couple of years as an iOS Developer in my home country, Serbia, I decided that it was time for me to move on and try my luck somewhere else. To leave all of my friends, family, places I like, basically everything what was my life up to that point was not an easy decision to make. What brought me to this decision was the lack of opportunities for professional development in my home country.</p><p>As is the case with other “developing countries”, Serbia doesn’t have a strong and diversified economy. This directly reflects onto the Software Development industry, which I was a part of, in the way that most of the work available is second-hand contracting work for foreign companies, popularly known as <strong>outsourcing</strong>.</p><p>Working as an outsourced Software Developer certainly has its benefits, and may be a dream job for many, but after a couple of years of doing the same old pattern over and over again, I felt that I had enough. My biggest issue was that I never really felt like a part of the team, and I never owned the product I worked on. I was simply somebody&#39;s temporary hired worker with little or no right to have an opinion of my own. I just did what I was told, and then a time would come to move on to another project, where the same things would happen. All of this is coming from an experience of working in two different companies full time, and working for a couple of other companies as a freelancer, for international clients from almost every continent.</p><p>What I really wanted was to have my opinion appreciated and to contribute in a meaningful way to a product that will influence the lives of people with considerable impact, and would be something new, modern and cool. In short, I wanted to be in the middle of happenings in the global economy as an equal player, as much as it is possible.</p><p>I found all of that and more here, in the Netherlands, by <a href="https://www.getbux.com/join-our-team">working at BUX</a>, and I want to share my story with you, and hopefully help you to do the same.</p><h4>Why did I choose the Netherlands?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HH0lIAUoecAei7UFW3zPDQ.jpeg" /></figure><p>On my journey to accomplish the goals I mentioned, the first challenge I had was to pick a country. My (and maybe tomorrow yours) reasons for picking the Netherlands are:</p><ol><li><strong>Strong economy</strong> <strong>-</strong> Netherlands is a small country that has had a very strong economy for a very long time, and it’s only getting stronger. This directly reflects upon jobs available for Software Developers. Some of the hottest European startups and larger companies are headquartered here (BUX, Booking, Philips, ING and many others). Also, a lot of international companies have their European headquarters in Amsterdam (Uber, Tesla). There is no shortage of work, and there is a plenty of opportunities.</li><li><strong>It’s an (almost) English speaking country</strong> <strong>-</strong> you will be hard pressed to find somebody in the Netherlands who doesn’t speak at least a little bit of English. Especially in Amsterdam, everyone will address you in English, and you can do just about anything you want without having to know the Dutch language.</li><li><strong>Working culture</strong> <strong>-</strong> despite what many might think, working culture in the Netherlands is quite relaxed, and work/life balance is excellent. You will (almost) never work more that 8 hours per day, and many companies offer the opportunity of working as little as two or three days per week. Many of my colleagues (and in general a lot of people here) work only four days a week because they want to spend more times with their families. After five o’ clock, you don’t send emails, or call anyone regarding work, it’s simply not done here. There might be rare occasions when you might have to do some overtime, but for my first year here I’ve yet to see it happen to me.</li><li><strong>Way of life - </strong>simply said, it feels good to live here. There is a lot of other expats, from all over the world, so even if you don’t hit it off with the locals, you can easily find new friends. Everywhere you turn you can see a lot of different cultures mixed together. In the same street you can easily find Japanese, Indonesian, Lebanese, Serbian, Turkish and other restaurants, all next door to each other. There’s a tons of clubs and bars for going out to, a lot of cinemas, theatres, museums, and all kinds of cultural manifestations all the time. It’s not nearly like this in all the cities in the Netherlands, but Amsterdam and other big cities nearby are generally nice places to live. It’s Friday today, as I am writing this (during the working hours, using a <strong>“hackathon day” that we have at BUX every second week, that’s used for personal development</strong>), and I already went out in the evening three times this week, to a cinema, all night drinking session in a local bar, and a relaxed dinner in a ramen restaurant. All that while having a plenty of time to do my work, chores, exercise, and everything else you need to do from time to time. That’s possible because of the way how life works here, everything is relaxed, you can go anywhere in a short amount of time, and there is a plenty of choices, no matter what you like.</li><li><strong>Simple immigration</strong> <strong>-</strong> immigrating into the Netherlands for Software Developers is usually done through the <a href="https://ind.nl/en/work/Pages/Highly-skilled-migrant.aspx">“Skilled Migrant” programme</a>, that enables easier immigration procedure and a lot of benefits, such as lower taxes for first eight years here (to compensate for higher living expenses), easy exchange of your driver’s licence for a local one, and many others. Just for example, <a href="http://thetax.nl/">you can use this website to calculate a difference between a normally taxed salary and a “Skilled Migrant” salary</a>.</li><li><strong>Commuting to work and anywhere else is easy </strong>- being able to have a <strong>15 minute door to door commute</strong> is nothing to sneeze upon. In most cases, you should be able to afford to live less than 10 km away from your work, and with excellent biking infrastructure and mild (but often rainy) weather, that means that most people bike to work here. Since moving to Amsterdam, I have biked to work (and everywhere else) almost every day, saving a lot of time and money, and also shedding a good bit of fat. On the other side, if you don’t like biking, public transportation is also quite good, and the whole country is quite small and excellently connected (about two and a half hours to go across the whole country by train). <strong>You don’t need a car here</strong>.</li><li><strong>Close to home and just about anywhere else</strong> - international transportation is also very good, with Schiphol airport having direct flights to about anywhere on the planet. There are also a lot of cheap European flights daily from Eindhoven (I can often get a low-cost flight return ticket to Serbia for about €30, and that’s about 1.500 km). Rail connection to the rest of Europe is excellent, with cities such as Paris, Brussels, Berlin, London only a couple of hours away by train. On the other hand if you are more of a car person, Dutch highways are of excellent quality and cover every corner of the country, and connect to major European highways.</li></ol><h4>Immigration procedure</h4><p>A first step is obviously finding a job. After securing a job contract, your company starts a procedure to get your papers in order. Depending on the country you are coming from this can be more or less complicated. In my case, as someone coming from a non-EU country, the process consisted of a couple of steps, such as going to to embassy of the Netherlands, waiting for their approval, arriving here, registering, etc. In some other case it might be as simple as signing and opening a bank account here. Anyway, you shouldn’t worry too much, because all of this is handled by professionals who offload the brunt of immigration-related work from your back. All you have to do is follow the instructions given, which usually ends up in signing some papers, and providing a couple of papers such as your birth certificate and passport. Because the procedure is wildly different depending on country of origin, i won’t be going into more details. If you decide to <a href="https://www.getbux.com/join-our-team">apply for a job at BUX</a>, rest assured that everything will be done by our HR specialists in the most convenient way possible.</p><h4>Finding a place to live at</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U6KdnJdSNF1Hy12pfbTFkw.jpeg" /></figure><p>Due to the amount of expats arriving here all the time, the rental property market is inflated with prices, and finding a nice place to live at might present a challenge. Prices vary wildly depending on the location. A 80 square meter furnished apartment might vary from €1.000/month in a smaller city like Zaandam, to up to €2.000/month in Amsterdam. Also, a lot of apartments are not furnished, up to a point of having no floors or lightning. Expect to spend a lot of time looking for a nice apartment, and possibly furnishing one. Good thing with companies like BUX is that we can provide you with temporary accommodations until you find a nice place to call home. Also, buying a property is quite easy, because the initial costs are quite low (you pay only the tax and procedure costs, you don’t have to pay even a 1% of the property price), and interest rates are around (or under) 2%/year.</p><p>Some websites to checkout for home finding are:</p><ul><li><a href="https://www.funda.nl/">Funda</a></li><li><a href="https://www.pararius.com/english">Pararius</a></li><li><a href="https://rentfirst.nl/">RentFirst</a></li><li><a href="https://www.expatrentals.eu/">ExpatRentals</a></li></ul><p>There are also a plenty of Facebook groups, but you should be careful with these because there’s a lot of scammers around.</p><h4>Commuting</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yASSrnUlFm2Nzlvb9EBNDA.jpeg" /></figure><p>As mentioned above, you can go about your commute in a couple of different ways. Public transport is available in different forms such as subway, tram, bus and train. You can buy an <a href="https://www.ov-chipkaart.nl/">OV-chipkaart</a> that is valid on all forms of transport inside the country. It also offers daily/monthly passes, subscriptions and discounts. Going from South to North it would take you about two and a half hours to go through whole of Netherlands, at most. Living 80 km away from your work is doable here, although you don’t really need to do it, since as a Software Developer you can easily afford to live in less than 5 km from the city centre where your office might be located <a href="https://goo.gl/maps/aEdjD2DR5pL2">as is the case for me at BUX</a>. I bike everyday possible, and it takes me about 15 minutes door-to-door for about 4 km distance. Asides from being a short commute it’s also a very nice form of exercise. I never biked before, and I must admit that I was a bit sceptical about it, but since starting to do this kind of commute I wouldn’t switch back to using public transport or a car if I don’t need to. It’s simply not comparable. Everywhere you go there are separate bike paths, so it’s also quite safe, and there is place to park your bike just about everywhere you turn.</p><h4>Weather</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mxQDr5IZP6P8dzm84FGDXg.jpeg" /></figure><p>Most people will tell you that the weather here is bad. I think there is more than that to it. Climate is quite mild, it’s never too hot or too cold, but the humidity in the air is quite high also, which sometimes contributes to experiencing the weather more profoundly than it actually is. Also, it’s quite rainy, but the rain is never too strong, it’s mostly an easy drizzle, and it doesn’t really stop you from going outside.</p><h4>Cost of living</h4><p>As most other things in this article, this is quite subjective, so maybe consulting websites such as <a href="https://www.expatistan.com/cost-of-living/amsterdam">Expatisan</a> and <a href="https://www.numbeo.com/cost-of-living/in/Amsterdam">Numbeo</a> is your best option, but I would say that for a single living in Amsterdam your costs of living will be €1.500–€2.500/month, depending on your lifestyle choices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jmenAI1qD2BlU0_UhgBiDQ.jpeg" /></figure><p>All in all, I would warmly recommend Netherlands, and especially Amsterdam to anyone. It’s generally a nice and relaxed place to live in, with a lot to offer.</p><p><strong><em>Milan Stevanović</em></strong><em> is an </em><strong><em>iOS Developer</em></strong><em> at BUX. You can contact him through </em><a href="https://twitter.com/FathVader"><em>Twitter</em></a><em>, </em><a href="https://www.linkedin.com/in/milanstevanovi%C4%87/"><em>LinkedIn</em></a><em> and </em><a href="https://github.com/milanstevanovic"><em>GitHub</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d78f2ff8087e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-bux/living-in-the-netherlands-d78f2ff8087e">Living in the Netherlands</a> was originally published in <a href="https://medium.com/inside-bux">Inside BUX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>