<?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 Yoran Brondsema on Medium]]></title>
        <description><![CDATA[Stories by Yoran Brondsema on Medium]]></description>
        <link>https://medium.com/@yoran.brondsema?source=rss-5b2680c46357------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zUpGka_8uXxMhpwBViUXXg.jpeg</url>
            <title>Stories by Yoran Brondsema on Medium</title>
            <link>https://medium.com/@yoran.brondsema?source=rss-5b2680c46357------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:41:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yoran.brondsema/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[Ember.js roadmap]]></title>
            <link>https://medium.com/@yoran.brondsema/ember-js-roadmap-fa5f5d02ce30?source=rss-5b2680c46357------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa5f5d02ce30</guid>
            <category><![CDATA[emberjs]]></category>
            <dc:creator><![CDATA[Yoran Brondsema]]></dc:creator>
            <pubDate>Sun, 16 Jun 2019 15:01:53 GMT</pubDate>
            <atom:updated>2019-06-16T15:01:53.352Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ember.js roadmap in 2019</h3><p>The Ember.js team has made a call for blog posts from the community with proposals for things the framework should focus on in 2019. This is my contribution.</p><h3>Context</h3><p>I’m writing this as the sole developer in a team of 3 that works on <a href="https://www.sutori.com/">Sutori</a>. I built and maintain the entire codebase of the application, which is an Ember.js SPA backed by a Ruby on Rails API. Some stats about the application at the time of writing:</p><ul><li>1,081,826 users: we passed the 1 million mark a couple of months ago <a href="https://www.sutori.com/item/what-is-your-first-thought-when-seeing-this-photo">during our company retreat in Greece</a>!</li><li>456,000 visits during the month of May</li><li>649 Ember.js components</li><li>49 Ember Data models</li></ul><p>I’m giving these stats to give the context for the things that are important to me in Ember.js.</p><h3>Productivity</h3><p>Remaining productive is the most important thing for me. To me, that means <strong>being able to create business value with minimal effort</strong>. I want to be able to ship new features and fix bugs without having to spend time on non-essentials.</p><p>I think that Ember.js is already doing great on this front. The fact that I can maintain Sutori all by myself is a testament to it. These are provided by:</p><ul><li>great support for testing</li><li>embracing standards like JSON-API</li><li>the extensive addon ecosystem</li></ul><p>In 2019, I would like the framework to maintain their attention on maximizing developer productivity.</p><p>Ember Octane brings a lot of improvements to the framework. Some, like element modifiers (my favorite), are truly new tools in the developer’s toolbox that have the potential of increasing productivity. I’ve started a library of element modifiers that I find myself constantly reusing throughout the application. I can already see that it’s going to save me time.</p><p>Other changes, such as angle-brackets notation, or other have less obvious value to me. To avoid spending too much time on e.g. migrating to angle-brackets notation for templates, <strong>codemods should do most of the work</strong>. Again, I think that Ember.js is already doing great on that front.</p><p>Every new release brings its new deprecations. <strong>Having a sort of codemod for deprecations, for instance as part of </strong><a href="https://github.com/mixonic/ember-cli-deprecation-workflow"><strong>ember-cli-deprecation-workflow</strong></a><strong>, would be great.</strong> Because right now, addressing deprecations is a fully manual process. I’m aware that this is challenging technically but any improvement over a full manual process would be welcome.</p><h3>Mobile</h3><p>I think that the mobile story in Ember.js is not good. To me, two things are problematic: <strong>performance</strong> and the absence of <strong>“Ember.js Native”, the Ember.js counterpart of React Native</strong>.</p><h4>Progressive Web Apps are not a thing yet</h4><p>As excited as I was about Progressive Web Apps, I don’t think that they’re living up to their expectations. The user experience of mobile web apps is far from being on par with native apps. The process of adding web apps to your Home screen as “installation” is not being adopted by the masses. None of my non-tech friends install web apps that way. To them, apps can still only be found and installed through the App Store or Play Store.</p><p>Until PWAs really become a thing, native apps still have to be written when the majority of your users is on mobile. React has React Native, a framework that is maintained by the React core team and <a href="https://facebook.github.io/react-native/showcase">that seems to be working very well</a>. Having an Ember.js Native framework, which is also blessed and supported by the Ember.js core team, would be great.</p><h4>Performance</h4><p>I remember being very excited after watching <a href="https://www.youtube.com/watch?v=JTzvYJBxwyI&amp;t=7228s">Tom Dale’s talk at the January 2017 Ember.js NYC meetup</a>, where he explained that the framework was going to focus on performance in 2017. Some of the things he talked about have arrived: FastBoot is a real thing (although I’ve never used it myself) and the Glimmer 2 renderer works really well. However, over 2 years after the talk, optimizations like code splitting and tree-shaking are still not possible in Ember.js. The dynamic import of <a href="https://github.com/ef4/ember-auto-import">ember-auto-import</a> works well for external libraries (although it requires manual setup), but as far as I know, there’s no solution for the framework itself or Ember.js addons.</p><p>I hope that the framework will focus on reducing code size over the next few months. Performance is a real bottleneck on mobile, and I think that is slowing down the adoption of Ember.js</p><h3>2020, the year of Ember.js?</h3><p><strong>To me, Ember.js is the only framework with a vision</strong>.</p><p>I do not consider React and Vue to be frameworks, but they’re libraries. Having just the view layer won’t get you far because when developing any application, you will soon need a router, a data layer, a deployment solution,… Ember.js supplies all the APIs needed to build a full application, that’s why it’s a framework.</p><p>As I was researching what front-end framework to choose for a next project, I listened to a lot of podcasts on the topic. I heard the founders of both Next.js (React framework) and Nuxt.js (Vue framework) speak about their project, and I couldn’t recognize a long-term vision for what they are creating. When Tom and Yehuda started Ember.js years ago, they set out to create the best framework to build ambitious web applications.<strong> </strong>That vision still holds today and it’s turned into reality by an impressive team of highly-skilled developers.</p><p><strong>That’s why it saddens me that Ember.js is so unpopular.</strong></p><p>It frustrates me that it maybe won’t be the best idea to pick Ember.js for a next project. I’m scared that the Ember.js ecosystem is going to shrink. Development will slow down, the offering of addons will reduce, etc…</p><p><strong>What can we do to make Ember.js popular in 2020? </strong>I’m sure that the Ember team has many ideas to further market the framework and reach more developers. And I hope that the framework will put marketing high on the list of priorities.</p><h3>Conclusion</h3><p>To conclude, I’m still very happy that we chose Ember.js over 5 years ago to build Sutori. It’s made it possible for me to maintain the technical side of the application all by myself. I hope that they keep their focus on developer productivity.</p><p>However, I wish that Ember’s story on mobile was more compelling. More importantly, I fear that its lack of popularity is putting the community into a downward spiral it may never get out of. Proper marketing will be a crucial task for the next few months to guarantee the survival of the framework.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa5f5d02ce30" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Personal Finance 101 for Developers: How to Hack Your Financial Well-Being]]></title>
            <link>https://medium.com/hackernoon/personal-finance-101-for-developers-how-to-hack-your-financial-well-being-3c86001dc651?source=rss-5b2680c46357------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c86001dc651</guid>
            <category><![CDATA[investing]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[personal-finance]]></category>
            <category><![CDATA[retirement]]></category>
            <category><![CDATA[money-management]]></category>
            <dc:creator><![CDATA[Yoran Brondsema]]></dc:creator>
            <pubDate>Thu, 16 May 2019 19:01:01 GMT</pubDate>
            <atom:updated>2019-05-16T19:01:01.087Z</atom:updated>
            <content:encoded><![CDATA[<p>As a freelance web developer, it recently dawned on me that I had never given any thought to my pension. After all, at thirty years old, retirement is still a couple of decades away. But I know that being a freelancer comes with the responsibility of having to take care of my own pension, and I don’t want to end up as a retiree without any income. So I set out on a quest to improve my financial well-being and be better prepared for the future.</p><p>In this article, I share the most important principles that I’ve successfully applied to my own financial life.</p><h3>The importance of financial planning</h3><p>Money is as important in our lives as food and having a place to sleep. We use it every day and we can’t live without it. Yet, most of us have never learned how to manage it well. When I look back at my own education, I realized that I was never taught how to manage my money, how to fill in my taxes, etc… These are very important life skills and it astonishes me our school systems do not teach them.</p><p>We’ve all heard stories of people who ended up in a precarious financial situation, often caused by an unexpected event: they lost their job, they’ve been diagnosed with an unexpected illness, had a costly repair to their house… To use Nassim Nicholas Taleb’s words, such events are “<a href="https://www.goodreads.com/book/show/242472.The_Black_Swan">black swans</a>”: they come as a surprise and have a major effect. You might think that your life will be safe of black swans, but that is the whole point: they always come unexpectedly and can happen to anyone.</p><p>So the goal of planning your personal finance is simple: <strong>to avoid ending up in financial trouble, and to improve the financial situation of your future self</strong>. It all starts with acquiring the right knowledge, and fortunately for us, there are only a couple of basic principles that underlie it all!</p><h3>Spend less than you make</h3><blockquote>“The ultimate secret to personal finance is quite simple: spend less than you make.” — Andy Rachleff</blockquote><p><strong>Spending less than you earn is the most important principle.</strong> It’s common sense! Still, you’d be surprised at the number of people who live beyond their means. It’s fine to go in debt under some circumstances, for instance when buying a house. But otherwise, you should only spend the money that you actually possess.</p><p>As developers, we are fortunate that we generally make a good living compared to people in other industries. After all, we have skill sets that are currently in high demand. Unless you have a lavish lifestyle or have unusually high costs, you should be able to live within your means.</p><h3>Measure then optimize your spending</h3><blockquote>“To measure is to know.” — Lord Kelvin</blockquote><p>Optimizing your spending is a bit like software optimization. Similarly like how you shouldn’t randomly improve the performance of parts of your code without knowing where the actual bottlenecks are, you need to actually understand your spending habits before you can make good changes.</p><p><strong>Tracking all of my spending</strong> for about 3 months helped me substantially in getting the bigger picture of my financial situation. When you know what you spend your money on every month, you have the data necessary to <strong>reduce your spending</strong>. Figure out what expenditures really are important to you and try to reduce spending money on things that don’t add much to your life. Maybe you will find out that you spend a lot on eating out, so start by cutting down on your outings to restaurants. On the other hand, if you’re a food lover, you might want to keep spending money on restaurants because those times are vital to your happiness.</p><p>It’s important to decide on those trade-offs for yourself. <strong>You’re the only person who knows what things contribute to your happiness.</strong></p><h3>Invest your savings in index funds</h3><p>Once you’ve optimized your spending, you’re left with all that excess money every month. What do you do with it?</p><p>Most people would put it into a savings account. However, <strong>savings accounts are far from optimal when you’re saving for the long term</strong>. In both the US and the EU, interest rates have been extremely low for the past decade. As I’m writing this in May 2019, the interest rate set by the European Central Bank is exactly 0.0%. This causes the returns on a savings account to be very low. Much lower than inflation, in fact, which means that <strong>you’re losing buying power every year that your money is in a savings account</strong>.</p><p>History has shown that you can achieve drastically higher returns by investing your savings. However, the smart investor does not try to beat the market by investing in individual stocks. Indeed, as amateur investors we can never compete against expert Wall Street analysts who spend their entire day analyzing companies. You might make a couple of good investments here and there, but over the long run it’ll be very difficult and time-consuming to sustain high returns.</p><p>Instead, we invest in <strong>index funds</strong>. An index is like a bag of stocks. When you invest in an index fund, you own a little bit of each company in the index. The most famous index is the S&amp;P 500, which consists of the 500 largest American companies. The MSCI World index is another well-known one. It contains stocks of over 1,600 companies from the developed markets (US, Europe, Australia, Japan,…). So instead of investing in a handful of stocks, you invest in the entire stock market. This approach of investing is called <strong>passive investing</strong>, because you don’t have to spend time managing your portfolio of investments. You just invest in the index fund and let it be.</p><p>Let’s benchmark <strong>the return of a passive investing strategy against a savings account</strong>. Imagine Lucas and Emma, who are both about to retire at 65 years old. They started working at the same age, 40 years ago when they were 25. For all these years, they’ve consistently been saving $100 every month. There’s one difference: Lucas didn’t know anything about investing so he put all of his hard earned savings into a savings account with a steady annual return of 1%. On the other hand, Emma was fortunate enough to have learned about passive investing when she was a student. Because of that, she has been putting her monthly savings into an index fund tracking the MSCI World index.</p><p>Let’s see how the size of their savings has evolved during their lifetime.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cBrAJHiGIRqadltx5OmUyg.png" /><figcaption>Investing in an index fund quickly outgrows a savings account.</figcaption></figure><p>By age 65, both Lucas and Emma will have put aside the same amount of €48,000. With the steady 1% interest that he gets from his savings account, Lucas will have grown this to €58,989. In the meantime, Emma’s savings have grown to a staggering<strong> €335,185</strong>! This is over 5 times more than what Lucas has, and all she had to do was deposit her savings into an index fund rather than into her savings account.</p><p>Looking at the evolution of Emma’s savings, you see that it has swings up and down. These are unavoidable as financially markets inevitably go up and down. For instance, during the 2008 financial crisis, the stock market lost half its value, and so did the index. But when you spread out your investment over 30 or 40 years, you have the time to recuperate any major losses. <strong>This makes passive investing ideal for saving for your retirement</strong>.</p><p>Finally, you don’t have to just take my word for it. Warren Buffett himself, the most successful investor of the past decades, <a href="http://fortune.com/2019/02/26/warren-buffett-investment-strategy/">says that index funds are the best investments for most people</a>.</p><h3>Conclusion</h3><blockquote>“Do not save what is left after spending, but spend what is left after saving.” — Warren Buffett</blockquote><p>As developers, we are fortunate to generally be well-paid compared to the general population. However, this doesn’t mean that we can live a financially irresponsible life. The two principles outlined in this article are the foundation for your financial well-being:</p><ol><li>Reduce your expenses by only spending money on things that contribute to your happiness.</li><li>Invest your savings in index funds rather than leaving them in a savings account.</li></ol><p>There’s a lot more to learn on the topic, especially on investing. But let this be a start. How do you manage your finances and better prepare for the future? Leave your comments below.</p><p><em>Yoran is the CTO and co-founder of </em><a href="https://enzo.fund/?utm_source=hackernoon&amp;utm_medium=blog-post&amp;utm_campaign=personal-finance-101"><em>Enzo</em></a><em>, where he improves the financial well-being of millennials through passive investing. The finance world is filled with jargon, complicated financial “solutions”, horrible stock photos of old men in suits and clunky apps. In contrast, Enzo brings simplicity and transparency, and requires no financial knowledge to start investing.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c86001dc651" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/personal-finance-101-for-developers-how-to-hack-your-financial-well-being-3c86001dc651">Personal Finance 101 for Developers: How to Hack Your Financial Well-Being</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Debug your Rails application using real production data with Amazon RDS]]></title>
            <link>https://medium.com/@yoran.brondsema/debug-your-rails-with-real-production-data-with-amazon-rds-6eefc35971b1?source=rss-5b2680c46357------2</link>
            <guid isPermaLink="false">https://medium.com/p/6eefc35971b1</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[heroku]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[rds]]></category>
            <dc:creator><![CDATA[Yoran Brondsema]]></dc:creator>
            <pubDate>Tue, 20 Sep 2016 04:45:58 GMT</pubDate>
            <atom:updated>2016-09-20T04:50:55.888Z</atom:updated>
            <content:encoded><![CDATA[<p>There are certain bugs where you need the actual production data to be able to reproduce and therefore fix them. When you&#39;ve just launched your application, you can do this simply by downloading the entire database and importing it locally. However, as your application (hopefully) becomes successful and the size of the database grows, this quickly does not become feasible anymore. In this post I will explain how we solved this problem by maintaining a backup of the production database on a cheap Amazon RDS instance and accessing it through a special <em>debug</em> environment in Rails.</p><h3>Amazon RDS</h3><p>RDS is Amazon&#39;s relational database service. They offer several types of instances as can be seen on the <a href="https://aws.amazon.com/rds/pricing/">pricing</a> page, differentiated by performance characteristics. As we&#39;re only going to use the database as a debugging environment, performance is not important so the smallest type (db.t2.micro) will do.</p><p>It&#39;s straightforward to set up a PostgreSQL instance simply by <a href="https://console.aws.amazon.com/rds/home">going to the RDS console</a> and following the steps there. The only parameter that is important now is the allocated storage as it contributes to the price. Therefore, make sure to pick a value that represents the actual size of your database and don&#39;t over-allocate (see the <a href="https://aws.amazon.com/rds/faqs/">FAQ</a> on more information of how the monthly price is calculated).</p><h3>Setting up the Rails environment</h3><p>Now that your RDS instance is ready, we&#39;re going to try to access it through a new Rails environment <em>debug</em>. The goal is to be able to connect to the RDS instance simply by starting the Rails server with:</p><pre>RAILS_ENV=debug rails s</pre><p>Start by creating the environment in <em>config/environments/debug.rb</em>. The easiest is to simply have it inherit from the <em>development</em> environment:</p><pre># Based on development defaults <br>require Rails.root.join(“config/environments/development”)</pre><p>The next step is to configure <em>config/database.yml</em> for the new environment.</p><pre>debug:<br>  adapter: postgresql<br>  encoding: unicode<br>  database: &lt;%= ENV[‘DEBUG_DB_DATABASE’] %&gt;<br>  username: &lt;%= ENV[‘DEBUG_DB_USERNAME’] %&gt;<br>  password: &lt;%= ENV[‘DEBUG_DB_PASSWORD’] %&gt;<br>  host: &lt;%= ENV[‘DEBUG_DB_HOST’] %&gt;<br>  port: &lt;%= ENV[‘DEBUG_DB_PORT’] %&gt;<br>  sslmode: verify-full<br>  sslrootcert: config/ca/rds-combined-ca-bundle.pem</pre><p>The two things to explain here are <em>sslmode</em> and <em>sslrootcert. </em>As we are going to transfer real production data between your computer and AWS, which may contain sensitive data, we want to make sure that we do so over SSL. As explained on the <a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.SSL">RDS documentation</a>, you need to download the public key stored at <a href="https://s3.amazonaws.com/rds-downloads/rds-combined-ca-bundle.pem">https://s3.amazonaws.com/rds-downloads/rds-combined-ca-bundle.pem</a> and save it in your project, in this case in <em>config/ca/rds-combined-ca-bundle.pem</em>.</p><h3>Transferring a backup of the database to RDS</h3><p>Finally, we need to populate the debug database. At <a href="https://www.hstry.co/">HSTRY</a>, we already store a nightly backup on AWS S3 using the <a href="https://github.com/kjohnston/pgbackups-archive">pgbackups-archive</a> gem. We therefore wrote a job that we run nightly to restore the latest backup from S3 to the database on RDS. It does three things:</p><ol><li>Determine the latest backup.</li><li>Download the latest backup to a temporary file.</li><li>Import the backup into the RDS database using <em>pg_restore.</em></li></ol><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/eb2794152dd6640fe4528496446acd49/href">https://medium.com/media/eb2794152dd6640fe4528496446acd49/href</a></iframe><h3>Conclusion</h3><p>That&#39;s it! By simply starting the Rails server with <em>RAILS_ENV=debug</em>, we can switch to an environment where we have access to real production data. We found the two main benefits to be:</p><ul><li><strong>bug fixing: </strong>It greatly improved our capacity for quickly solving bugs that our users were experiencing as there’s only so much you can do with seed data.</li><li><strong>performance:</strong> An additional benefit is that it also allows us to identify and fix n+1 queries on real production data. We use New Relic to detect especially long requests and then reproduce and fix them locally.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6eefc35971b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>