<?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 Jeremie Shaker on Medium]]></title>
        <description><![CDATA[Stories by Jeremie Shaker on Medium]]></description>
        <link>https://medium.com/@jeremieshaker?source=rss-fed5526ba358------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Bw_7Sn9tfgTtZAy7.</url>
            <title>Stories by Jeremie Shaker on Medium</title>
            <link>https://medium.com/@jeremieshaker?source=rss-fed5526ba358------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 07:33:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jeremieshaker/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[Golang Ticker Best Practices — Using tickers in a multi-threaded program without losing your mind…]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">My experience writing Golang has taught me that it&#x2019;s easy to write production code, but not as easy to write test code. There are many&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@jeremieshaker/golang-ticker-best-practices-using-tickers-in-a-multi-threaded-program-without-losing-your-mind-dfc307c6de62?source=rss-fed5526ba358------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@jeremieshaker/golang-ticker-best-practices-using-tickers-in-a-multi-threaded-program-without-losing-your-mind-dfc307c6de62?source=rss-fed5526ba358------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfc307c6de62</guid>
            <dc:creator><![CDATA[Jeremie Shaker]]></dc:creator>
            <pubDate>Sun, 12 Jul 2020 13:57:38 GMT</pubDate>
            <atom:updated>2020-07-14T16:44:25.822Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Front-end vs. Back-end: Which one should you pick?]]></title>
            <link>https://medium.com/@jeremieshaker/front-end-vs-back-end-which-one-should-you-pick-e53f92feb087?source=rss-fed5526ba358------2</link>
            <guid isPermaLink="false">https://medium.com/p/e53f92feb087</guid>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[backend]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Jeremie Shaker]]></dc:creator>
            <pubDate>Wed, 28 Aug 2019 21:10:10 GMT</pubDate>
            <atom:updated>2020-07-18T19:36:06.828Z</atom:updated>
            <content:encoded><![CDATA[<p>To give you full context, I was primarily a front-end developer for the past 3 years. I’ve made the transition to back-end and wanted to share my experience, hoping that’ll help you make a decision if you were ever indecisive about this choice.</p><h4>Front-end development: The good parts</h4><p>People love to hate on JavaScript, sometimes reasonably sometimes unreasonably, but with the release of TypeScript, the front-end universe benefited a lot. I think it’s a fun language to work with, and it’s very productive. Other than the syntax, there’s the benefit of no compilation being required, which makes development that much faster.</p><p>Additionally, the tooling around JavaScript is all contained within NPM, so setting up a project is a breeze. Clone, npm install, done. Overall theme here: productivity.</p><h4>Back-end development: The good parts</h4><p>Because performance is typically important when doing back-end dev, you end up writing less code. This might sound like a disadvantage, but I think spending time writing clean elegant code for a single feature is more satisfying than writing a dozen of components. Concerns about size and time complexity are actually important here, so you get to use what you’ve studied in school and actually apply computer science concepts.</p><h4>Front-end development: The bad parts</h4><p>The fast moving nature of front-end is without a doubt the worst part about it. I’m not only talking about the fast-growing ecosystem that is NPM, but also the nature of UI development. Unlike back-end development, you can’t write specifications ahead of time and hope that everything works out. You’re building a user experience and therefore the requirements are constantly changing. You end up writing a lot more code a lot more quickly to do A/B testing and adapt the UI, so it’s definitely a deal of quantity over quality. There isn’t really any benefits to applying the CS concepts such as time/space complexity because the code runs on the client’s machine anyways, therefore no concept of scale.</p><p>I was also going to bring up E2E testing in front-end, but I think that can have a post of its own. I’ve worked on 4 different front-end teams, and no one seems to have the perfect solution for that. You’ll always have flaky tests, and usually writing those tests is extremely boring. Also unit tests feel useless most of the time.</p><h4>Back-end development: The bad parts</h4><p>This might sound obvious, but things move slower in back-end. Not only in terms of compilation time, but also in terms of infrastructure. There’s usually more pieces to the puzzle; one part is written in C/C++, the other’s written in C#/Java, and who knows maybe you also have a Node.js server. This means that configuration is more of a hassle.</p><p>The other negative is that seeing the results of your work are less visible. Unlike UI development, you can’t really see what you’ve worked on…until it’s connected to some UI somewhere. I don’t think this is a big deal personally, but if you’re someone who values creating great user experiences, then back-end might not be for you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e53f92feb087" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Front End Developers: They’re not “real” engineers]]></title>
            <link>https://medium.com/@jeremieshaker/front-end-developers-theyre-not-real-engineers-a961efe6e2a3?source=rss-fed5526ba358------2</link>
            <guid isPermaLink="false">https://medium.com/p/a961efe6e2a3</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Jeremie Shaker]]></dc:creator>
            <pubDate>Sun, 23 Dec 2018 22:03:02 GMT</pubDate>
            <atom:updated>2020-01-19T04:50:13.622Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*HPGzysLVdFgdfV356RpKRA.jpeg" /></figure><h4>The increasing demand</h4><p>Front end developer job openings seem to be at an all-time high. Every company needs some front end developer to develop their newest and greatest product with cutting edge web technologies such as React, Angular or Vue. Yet, looking back on my bachelor’s degree, there was a discrepancy. Web development undergrad courses teach us how to use SOAP and XML, when the industry standard is REST and JSON. We were taught how to build pages in JSP, paired with jQuery code; no mention of any modern library. That isn’t representative of how modern web applications are built today and indirectly causes a decrease in interest for front end development.</p><p>The new university graduates don’t fill these openings for front end developers, which creates this gap that needs to be filled. Now we’re seeing an emergence of “Bootcamp” type courses. They teach you everything you need to know to get up to speed with modern web technologies. These often consist of learning an SPA Framework (React/Angular/Vue), Node + Express.js and some MongoDB for data persistence. After a mere 3–6 months, you’ve mastered the art of Front End Development, and are now ready to build real world applications.</p><p>This gave birth to a new breed of developers; one who’s knowledge of software development doesn’t extend to statically typed languages and usually is limited to Javascript. Why bother to learn anything else? You can technically call yourself a Fullstack developer since you can do Node.js on the server. Besides, writing Java is slower than writing Node.js by virtue of being a dynamic language.</p><h4>My experience with front end development</h4><p>I find myself in a weird position. I studied software engineering, I learned about software lifecycle, object oriented programming, data structures, algorithms, testing, operating systems. I personally enjoy building web applications; I started learning Angular.js outside of class on my own time because I liked the idea of building a product; it felt “concrete”. The more I learned about it, the more I appreciated the enjoyable UX that some of my favorite websites delivered. I would look up to the teams of developers behind web apps like Soundcloud and GSuite products overall (I’m a big fan of Material Design).</p><p>Being passionate about front end development, I pursued jobs in that industry. When I look at the background of my colleagues, I notice that my profile didn’t really match theirs. My colleagues typically fall into one of two categories; the Backend/Generalist developer who ended up on a team that does some front end OR the JavaScript developer. The generalist developer typically did a bit of everything; write a new service, hook it up to the front end, maybe some database operations and they seem to enjoy the overall variety of the workload. The JavaScript developer typically limits himself to doing strictly front end tasks, and he’s actually quite good at completing tasks. The quality of his code is definitely not on par, but from the manager’s perspective, he gets shit done, he makes the backlog shrink. And then there’s me. I put in the work into breaking down my code into short modular functions, carefully naming functions and variables in such a way that the code is easy to read with little to no documentation. I write tests, and deliver the whole thing in a timely manner, but in the end the task gets marked as completed, just as the JavaScript developer’s code did. The result is the same.</p><p>This is where I started realizing that front end development is not software engineering. It is pure development, there’s no engineering there. The reality of building a front end application is that things change a lot all the time. And I’m not even talking about the change in frameworks. I’m talking about a website; they get constant visual updates, additional features and such. They’re the most unstable piece of software in the whole stack. This means that things need to move fast.</p><p><strong>You know what’s fast?</strong> Writing all your piece of logic in a massive Javascript function and manually testing it. Of course, I’m exaggerating. But what I’m getting at is that, sometimes putting in the effort to make your code modular, maintainable and re-usable is actually a waste of time. Because this piece of code is doomed to be replaced in the near future, iterating faster is actually better in this case.</p><p>This all ties in to the concept of technical debt. In developing backend applications, accumulating technical debt can and will bite you in the ass if not monitored appropriately, and adding more debt represents a risky tradeoff.</p><p>The same doesn’t necessarily apply to front end development. Scalability is less of an issue in front end as most of the “hot paths” are the framework level code. The pace of the evolving web also makes it such that a rewrite will be needed anyways.</p><h4>My verdict</h4><p>I recently came to the conclusion that Front End Development wasn’t for me. It’s strange because when I did it on my own, I actually really enjoyed it. I could spend as much time architecting my code since I didn’t have deliverables, and I really started seeing the craftsmanship that is programming. Having worked on front end teams for the past two years l, I’ve realized that the craftsmanship isn’t present in front end development. I think only Front End architects get the satisfaction of doing engineering work, whereas everyone else is just slaving away at new feature requests from your PM.</p><p>This is my opinion. Keep in mind I’ve only worked in the industry for two years, so I don’t have much data to base myself off of. Disagree? I’d love to hear about your thoughts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a961efe6e2a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>