<?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 Alex Vernacchia on Medium]]></title>
        <description><![CDATA[Stories by Alex Vernacchia on Medium]]></description>
        <link>https://medium.com/@vernacchia?source=rss-2b1589ad1e73------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*9ByIAF-QQCNjiafT.jpeg</url>
            <title>Stories by Alex Vernacchia on Medium</title>
            <link>https://medium.com/@vernacchia?source=rss-2b1589ad1e73------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:55:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vernacchia/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[Inheriting an Open Source Project]]></title>
            <link>https://medium.com/salesforce-engineering/inheriting-an-open-source-project-6a479d3e962e?source=rss-2b1589ad1e73------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a479d3e962e</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Alex Vernacchia]]></dc:creator>
            <pubDate>Tue, 17 May 2016 18:01:18 GMT</pubDate>
            <atom:updated>2017-01-20T17:35:12.098Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*U-xzn_S4XcTcQZR2FX4hdw.jpeg" /></figure><p>During my time at Salesforce, I’ve come to love open source software (OSS).</p><p>I previously maintained <a href="http://getfuelux.com/">Fuel UX</a> and actively maintain the Salesforce Marketing Cloud’s Node.js SDKs (<a href="https://github.com/salesforce-marketingcloud/FuelSDK-Node-Auth">Authentication</a>, <a href="https://github.com/salesforce-marketingcloud/FuelSDK-Node-REST">REST</a>, <a href="https://github.com/salesforce-marketingcloud/FuelSDK-Node-SOAP">SOAP</a>).</p><p><em>(From this point on I will be referring to these individual SDKs as “modules.”)</em></p><p>Before becoming maintainer for some of these projects, I had used them a lot. For some, I had even built them myself. I felt confident in what I was doing.</p><p>Unfortunately, I was not so familiar with the SOAP module. I’d only helped out here and there, and to be perfectly honest, I knew almost nothing about it. But, it had been modelled after the other two modules I built (Auth and REST from above), so there’s that.</p><p>Everything was going well until a few months ago. Someone submitted a pull request (PR), as they needed a feature implemented. (Good on them for the PR — often I would be asked to make code changes, but it is much more pro-active for the individual to improve the code themselves.)</p><p>As I looked at the PR, I found myself wondering about the implications of this change. Will it affect backwards compatibility? Does it actually accomplish what is needed? Are there security concerns? The list goes on. I had no clue about any of these answers because I didn’t write that module.</p><p>If you find yourself in this situation, there are certain things that can help immediately. There are also things you can do to mitigate this situation in the future. Let’s explore a few.</p><h4>Read the Documentation</h4><p>Like I said, I knew very little about the SOAP module. For that matter, I also knew very little about the Marketing Cloud’s SOAP API.</p><p>But thankfully, compared to companies I had worked at previously, Salesforce had a good amount of documentation for the SOAP API, which proved really useful.</p><p>To be honest, when you have good documentation, implementing small features or bug fixing isn’t too hard, even if you don’t know the big picture.</p><h4>When in doubt, ask for help</h4><p>After realising I didn’t feel confident making these changes, I swallowed my pride and asked a co-worker for help.</p><p>Good thing too, as I would’ve missed a small change that could’ve had a huge impact. Basically, I almost released a major change according to <a href="http://semver.org/">semver</a>, but in a minor release. Not the best!</p><p>There’s nothing wrong with asking for help. If you don’t understand something, ask. If you think you are implementing something incorrectly, ask. You’ll learn something new, if not get validation on what you were doing.</p><p>At this point, I ask so many questions, my co-workers are probably annoyed with me to be honest!</p><h4>Improve tests around existing functionality</h4><p>After this PR situation, I wanted to mitigate the chances of this happening in the future.</p><p>I started by analysing the current tests, which were along the lines of fake integration tests, and found holes and general things I wasn’t happy with. New unit tests were in order. A complete rewrite.</p><p><em>Side note: remember I said my modules were a template for this one? Well, so were the tests. Kind of my fault!</em></p><p>I started using <a href="https://en.wikipedia.org/wiki/Test-driven_development">TDD</a> at work a while ago and felt my code has become more concise and much more tidy. No accidental over-engineering. So, I tried it out on this project, with great success I think.</p><p>The whole process took a few days, but I finally got to <a href="https://github.com/salesforce-marketingcloud/FuelSDK-Node-SOAP/pull/92">around 100% coverage</a>. It’s one massive PR, but a needed one. And before you start saying “coverage doesn’t matter” … let me agree with you. What matters is that you test all the functional aspects. It just so happened that when I did that, I achieved a good amount of coverage.</p><p>I am now much more confident when implementing features/bug fixing. While my tests won’t catch everything, they are a great start!</p><p>During the test re-vamp, I actually found a few bugs, which were so easy to fix due to this work.</p><p>If you haven’t checked out TDD, I would highly recommend it. It takes a little while to get used to, but I feel it’s very worthwhile in the end. I’ve put a few links below (if you have a good one to add, just comment!).</p><ul><li><a href="http://blog.testdouble.com/posts/2014-01-25-the-failures-of-intro-to-tdd.html">The Failures of “Intro to TDD”</a> — the author actually likes TDD, but thinks it’s incorrectly introduced to people</li><li><a href="http://blog.testdouble.com/posts/2014-01-25-the-failures-of-intro-to-tdd.html">The Three Rules of TDD</a> — seem logical, but could be taken too far</li></ul><h4>Make the repo friendlier</h4><p>We’ve all heard that some maintainers are not the nicest and even discourage new contributors from ever starting.</p><p>That’s not what we want at Salesforce. The more contributors the better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*A1mUP-DIj15ykdu1E_YqOQ.gif" /><figcaption>If you understand this, I love you</figcaption></figure><p>In this vein, I’ve tried to make it as easy as possible to contribute using the issue tags on Github, writing better issues, and even including some pre-built tests for others to get passing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*uJUOKaZJAT87mvJL-JU2XA.png" /><figcaption>New issue tags</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*KA7ABaMJN0YwOqO_6lznag.png" /><figcaption>No way?!?! I wrote the test for you?</figcaption></figure><p>It’s certainly been a journey with this module, and one that is ongoing. But using these methods, I’ve been able to progress and improve a module I was unfamiliar with.</p><p>OSS is not always easy. Contributing and maintaining a project can be difficult and complicated, but it is a practical way to learn and develop your technical skills. Good luck!!</p><p><em>Originally published at </em><a href="https://medium.com/salesforce-open-source/inheriting-an-open-source-project-11259898d258"><em>medium.com</em></a><em> on May 17, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a479d3e962e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforce-engineering/inheriting-an-open-source-project-6a479d3e962e">Inheriting an Open Source Project</a> was originally published in <a href="https://medium.com/salesforce-engineering">Salesforce Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inheriting an Open Source Project]]></title>
            <link>https://medium.com/@vernacchia/inheriting-an-open-source-project-11259898d258?source=rss-2b1589ad1e73------2</link>
            <guid isPermaLink="false">https://medium.com/p/11259898d258</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Alex Vernacchia]]></dc:creator>
            <pubDate>Tue, 17 May 2016 18:01:18 GMT</pubDate>
            <atom:updated>2016-05-17T18:01:18.184Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U-xzn_S4XcTcQZR2FX4hdw.jpeg" /></figure><p>During my time at Salesforce, I’ve come to love open source software (OSS).</p><p>I previously maintained <a href="http://getfuelux.com/">Fuel UX</a> and actively maintain the Salesforce Marketing Cloud’s Node.js SDKs (<a href="https://github.com/salesforce-marketingcloud/FuelSDK-Node-Auth">Authentication</a>, <a href="https://github.com/salesforce-marketingcloud/FuelSDK-Node-REST">REST</a>, <a href="https://github.com/salesforce-marketingcloud/FuelSDK-Node-SOAP">SOAP</a>).</p><p><em>(From this point on I will be referring to these individual SDKs as “modules.”)</em></p><p>Before becoming maintainer for some of these projects, I had used them a lot. For some, I had even built them myself. I felt confident in what I was doing.</p><p>Unfortunately, I was not so familiar with the SOAP module. I’d only helped out here and there, and to be perfectly honest, I knew almost nothing about it. But, it had been modelled after the other two modules I built (Auth and REST from above), so there’s that.</p><p>Everything was going well until a few months ago. Someone submitted a pull request (PR), as they needed a feature implemented. (Good on them for the PR—often I would be asked to make code changes, but it is much more pro-active for the individual to improve the code themselves.)</p><p>As I looked at the PR, I found myself wondering about the implications of this change. Will it affect backwards compatibility? Does it actually accomplish what is needed? Are there security concerns? The list goes on. I had no clue about any of these answers because I didn’t write that module.</p><p>If you find yourself in this situation, there are certain things that can help immediately. There are also things you can do to mitigate this situation in the future. Let’s explore a few.</p><h4>Read the Documentation</h4><p>Like I said, I knew very little about the SOAP module. For that matter, I also knew very little about the Marketing Cloud’s SOAP API.</p><p>But thankfully, compared to companies I had worked at previously, Salesforce had a good amount of documentation for the SOAP API, which proved really useful.</p><p>To be honest, when you have good documentation, implementing small features or bug fixing isn’t too hard, even if you don’t know the big picture.</p><h4>When in doubt, ask for help</h4><p>After realising I didn’t feel confident making these changes, I swallowed my pride and asked a co-worker for help.</p><p>Good thing too, as I would’ve missed a small change that could’ve had a huge impact. Basically, I almost released a major change according to <a href="http://semver.org/">semver</a>, but in a minor release. Not the best!</p><p>There’s nothing wrong with asking for help. If you don’t understand something, ask. If you think you are implementing something incorrectly, ask. You’ll learn something new, if not get validation on what you were doing.</p><p>At this point, I ask so many questions, my co-workers are probably annoyed with me to be honest!</p><h4>Improve tests around existing functionality</h4><p>After this PR situation, I wanted to mitigate the chances of this happening in the future.</p><p>I started by analysing the current tests, which were along the lines of fake integration tests, and found holes and general things I wasn’t happy with. New unit tests were in order. A complete rewrite.</p><p><em>Side note: remember I said my modules were a template for this one? Well, so were the tests. Kind of my fault!</em></p><p>I started using <a href="https://en.wikipedia.org/wiki/Test-driven_development">TDD</a> at work a while ago and felt my code has become more concise and much more tidy. No accidental over-engineering. So, I tried it out on this project, with great success I think.</p><p>The whole process took a few days, but I finally got to <a href="https://github.com/salesforce-marketingcloud/FuelSDK-Node-SOAP/pull/92">around 100% coverage</a>. It’s one massive PR, but a needed one. And before you start saying “coverage doesn’t matter” … let me agree with you. What matters is that you test all the functional aspects. It just so happened that when I did that, I achieved a good amount of coverage.</p><p>I am now much more confident when implementing features/bug fixing. While my tests won’t catch everything, they are a great start!</p><p>During the test re-vamp, I actually found a few bugs, which were so easy to fix due to this work.</p><p>If you haven’t checked out TDD, I would highly recommend it. It takes a little while to get used to, but I feel it’s very worthwhile in the end. I’ve put a few links below (if you have a good one to add, just comment!).</p><ul><li><a href="http://blog.testdouble.com/posts/2014-01-25-the-failures-of-intro-to-tdd.html">The Failures of “Intro to TDD”</a> — the author actually likes TDD, but thinks it’s incorrectly introduced to people</li><li><a href="http://blog.testdouble.com/posts/2014-01-25-the-failures-of-intro-to-tdd.html">The Three Rules of TDD</a> — seem logical, but could be taken too far</li></ul><h4>Make the repo friendlier</h4><p>We’ve all heard that some maintainers are not the nicest and even discourage new contributors from ever starting.</p><p>That’s not what we want at Salesforce. The more contributors the better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/319/1*A1mUP-DIj15ykdu1E_YqOQ.gif" /><figcaption>If you understand this, I love you</figcaption></figure><p>In this vein, I’ve tried to make it as easy as possible to contribute using the issue tags on Github, writing better issues, and even including some pre-built tests for others to get passing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/993/1*uJUOKaZJAT87mvJL-JU2XA.png" /><figcaption>New issue tags</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*KA7ABaMJN0YwOqO_6lznag.png" /><figcaption>No way?!?! I wrote the test for you?</figcaption></figure><p>It’s certainly been a journey with this module, and one that is ongoing. But using these methods, I’ve been able to progress and improve a module I was unfamiliar with.</p><p>OSS is not always easy. Contributing and maintaining a project can be difficult and complicated, but it is a practical way to learn and develop your technical skills. Good luck!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11259898d258" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lowering Load Times Across Social.com]]></title>
            <link>https://medium.com/salesforce-engineering/lowering-load-times-across-social-com-d7704bfe835a?source=rss-2b1589ad1e73------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7704bfe835a</guid>
            <category><![CDATA[optimization]]></category>
            <category><![CDATA[scale]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Alex Vernacchia]]></dc:creator>
            <pubDate>Tue, 26 Jan 2016 17:41:05 GMT</pubDate>
            <atom:updated>2016-04-07T21:44:18.612Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*81lCuJT4mW9IUbfQxKVvwQ.jpeg" /></figure><p>While moving jobs can be thrilling, there are also bound to be a few “What the hell?” moments when you run into what appears to be suboptimal code where “creative” choices may have been made.</p><p>You may realize there was a method to the madness, but sometimes your reaction is warranted and there is room for improvement. In this case, front-end performance.</p><p>Having some time outside of my normal tickets, I decided to begin the optimization.</p><p>Our Campaign Builder (CB) is the main piece of software for the moment, allowing our customers to create and update advertising campaigns across different social networks. In the simplest sense, it uploads ads to social networks. It’s front-end heavy and needs to be performant.</p><h3>How did that get there?</h3><p>We began to analyze ourselves and found some obvious problems.</p><ol><li>Full-size images were rendered instead of thumbnails</li><li>The use of Angular’s templating engine was subpar</li><li>Too many files were loaded</li></ol><p>Some may say these are “huge” problems, but due to our production site’s use of caching, compilation, and other techniques, it wasn&#39;t a “huge” deal. It was more so a problem for us, the developers.</p><h4><strong>Proper Thumbnails</strong></h4><p>Hmmm, loading full-size images seems like one of the first things taught when learning about web development. Never load a huge image if you don’t have to.</p><p>Unfortunately, developers in general are often in a rush, which is all too common. Especially when you’re working for a start-up and looking to iterate super fast.</p><p>In order to combat our thumbnail problem we installed a resizing plug-in on our back-end and resorted to a few clever tricks on the front-end.</p><p>I&#39;ve compiled a small list of back-end image resizing plug-ins, but due to the greatness of open-source software (OSS) there are literally hundreds of solutions.</p><ul><li><a href="http://sharp.dimens.io/en/stable/">Sharp</a> (NodeJS)</li><li><a href="http://imageresizing.net/">ImageResizer</a> (.NET)</li><li><a href="https://github.com/thoughtbot/paperclip">Paperclip</a> (Ruby)</li><li><a href="http://www.imagemagick.org/script/index.php">ImageMagick</a> (Basically universal)</li></ul><p><em>Note: I would caution you if you choose a Node.js solution, as image manipulation can be pretty CPU intensive, blocking </em><a href="http://blog.carbonfive.com/2013/10/27/the-javascript-event-loop-explained/"><em>Node’s event loop</em></a><em>.</em></p><p>All said and done, image resizing was implemented across the entire site in a few sprints. As for the results, we were able to decrease the amount of image data transferred by ~70%.</p><h4>Angular on Par</h4><p>Our front-end is built using Angular. Angular allows for specific templates. Duh. When those templates get too large to put in your controller/directive file, you usually move them out, and then specify a template URL for Angular.</p><p>Without going into too much detail, here’s how Angular deals with “external” templates. First, an AJAX request is made to the designated URL. The result is then compiled and rendered in the browser. I know there’s a lot more to it, but that’s a whole different post.</p><p>Can you see the problem yet? If not, let me ask you, what happens when you’re developing a huge single page app? One that has a lot of nested templates? You get heaps of HTTP requests for templates, resulting in poorer performance and a slight delay a user usually reports as “it feels slow.”</p><p>To fix this, we looked for the simplest solution and found a grunt plug-in called <a href="https://github.com/karlgoldstein/grunt-html2js">html2js</a>. It does two things:</p><ol><li>Transforms templates from HTML to JavaScript</li><li>Creates files that load the transformed templates directly into Angular’s template cache</li></ol><p>This process is performed during our production build process (via grunt). One simple configuration object, with a regex to find our templates, and we were up and running. All our templates end with “.tpl.html” so the regex was super easy.</p><p>All that’s left to do is include these generated files on your page, and you should see the template requests cut to zero.</p><p><em>Note: We only do this for production as we have a load of templates. If your project is small enough where the compile time is negligible, I would recommend a gulp/grunt/broccoli process to handle this on template change.</em></p><p>Inlining templates also cut the user-reported “delay” to essentially zero. LOOK, we achieved a decrease in <a href="http://blog.teamtreehouse.com/perceived-performance">perceived load-time</a>!</p><h4>Too many files you say?</h4><p>Unfortunately, we loaded too many files across our site.</p><p>As mentioned prior, our CB provides the ability to create/update social media campaigns for three social networks. These builders are very independent and only rely on a small portion of shared components, but we were loading all files for each social media network.</p><p>For example, when a user built a Facebook campaign, Twitter’s and LinkedIn’s files would be loaded as well. In addition, we loaded legacy code as well, adding insult to injury. Doesn’t seem right, does it? We can do better!</p><p>To fix this we started at the very beginning. Where do these files get included? Is a template used? Is there a reason all these files need to be there?</p><p>It turns out the CB master template had been inherited from the legacy site. At the time, this was obviously the easiest, but not correct, path forward. You can’t fault anyone for that too much.</p><p>So we changed it, plain and simple. Now a slim master template is used and is inherited by each channel. The master template loads <strong>only </strong>the shared components while the channel templates load exactly what they need to run themselves and nothing else. Legacy code is no longer loaded in these areas either.</p><p>In addition, we removed old libraries that were no longer needed and implemented <a href="http://bower.io/">Bower</a> for front-end asset management. For those of you who haven’t used Bower, please check it out. It will save you heaps of time and hassle.</p><p>After implementation of these changes we observed our data transfer decrease by ~4MB and the number of requests by ~1000. Yes, we had way too many requests, but this change made our “dev” lives so much easier!</p><h4>The Future</h4><p>We’re continually working on improving this even further but it’s one hell of a start.</p><p>Even with these improvements there’s always more to do. What’s next on the list? We&#39;ve put a few thoughts below.</p><ul><li>Minifying JavaScript — Due to our adoption of Angular in it’s infancy and the use of Bundler, JavaScript is only concatenated. <em>This should still be done </em>e<em>ven if it is a </em><strong><em>non-issue </em></strong><em>in production.</em></li><li>Spriting images — This is done in some places, but could be implemented better across the site.</li></ul><p>If you have any thoughts relating to development practices we’d love to hear them.</p><p>We’re in the midst of changing how we think going from the start-up world to the enterprise world. One thing will remain the same. We’ll continue to remember there’s always room for improvement.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7704bfe835a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforce-engineering/lowering-load-times-across-social-com-d7704bfe835a">Lowering Load Times Across Social.com</a> was originally published in <a href="https://medium.com/salesforce-engineering">Salesforce Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A New Job: The Good Parts]]></title>
            <link>https://medium.com/@vernacchia/a-new-job-the-good-parts-17f8b143fb3f?source=rss-2b1589ad1e73------2</link>
            <guid isPermaLink="false">https://medium.com/p/17f8b143fb3f</guid>
            <dc:creator><![CDATA[Alex Vernacchia]]></dc:creator>
            <pubDate>Mon, 01 Dec 2014 19:38:13 GMT</pubDate>
            <atom:updated>2024-04-23T16:04:05.568Z</atom:updated>
            <content:encoded><![CDATA[<p>If you want to find out more about the bad parts of getting a new job, check out any other blog post about getting a new job [1].</p><p>About a month ago I started a new job; in a completely different industry. It’s very different even though I have many of the same responsiblities as my past job. You may be thinking, “it’s not a huge deal. Same thing different place.” I would reply, “you’re dead wrong.”</p><p>My situation may be a little different than most. I attribute this to the fact that I moved from Indianapolis, IN, USA to London, UK. I was also one of the first few to transfer between divisions. But, I will argue that, for the most part, starting a new job is the same almost anywhere you go.</p><p>You’ve left what you know. You knew all the processes; had the tribal knowledge; knew who the subject matter experts (SME) were; knew your co-workers. Now, you know none of these things (generally speaking).</p><p>This may seem like a horrible situation, but it’s time for you to be an optimist. You just got this great, new job! You have new domain knowlegde to learn! You will grow your knowlegdge base considerably with all the new tech/[insert topic here] you need to learn! You will meet new people!</p><p>You have a <strong>great, new job! </strong>You wouldn’t have taken this job if you didn’t want it. Whether it be because your old job sucked, you needed something different, or it was an amazing opportunity. It’s the beginning of another chapter in the story of your life. You better start writing it sooner than later.</p><p>You get to <strong>learn about a different domain. </strong>Take me as an example. I used to work in Email/Digital Marketing. I knew a lot about how marketers go about their daily business, how they used our solutions, who are competitors were, etc. Now, I work in Social Advertising. I’ll admit I know very little about it. I have to take a step back and learn. In the long run, doesn’t that make me much more valuable? Two is always better than one (generalizing of course).</p><p>You will get to <strong>network like no other. </strong>It’s not what you know, it’s who you know [2]. You made all these connections at your last job. You met the people that will, or did, give you recommendations. You now have the opporunity to expand your network even further. It’s always nice to have people that can vouche for your skills and/or you as a person.</p><p>Who doesn’t love <strong>learning new technology? </strong>This point relates to developers moreso, but if you’re not one, replace the word with a skill you need to learn. I really like something I saw in a recent blog article I read. The author said, “Our technological skills are depreciating assets. New tech is coming out virtually everyday, so what you know now will soon be deprecated.” This means you need to keep learning to stay ahead of the curve; to make sure you are still relevant in your field. A new job helps you do this more than you would know.</p><p>I think the hardest thing is <strong>meeting and getting to know your co-workers. </strong>Becoming part of the team can be rough, but it’s well worth it. Teams need synergy, and finding what you bring to the table is one of the hardest things. It happens with time. Don’t worry if you don’t find it right off the bat. It was/is hard for me; coming to a city halfway across the world and knowing very few people is not the easiest.</p><p>Remember, what happens in your life is up to you!</p><p>1 — Paraphrased from Douglas Crockford<br>2 — I tend not to like that phrase, and usually replace it with, “<em>It’s what you know and how you demonstrate this in front of the right people.”</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17f8b143fb3f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Open Source Projects and Version Control]]></title>
            <link>https://medium.com/@vernacchia/open-source-projects-and-version-control-50d8b5c45b61?source=rss-2b1589ad1e73------2</link>
            <guid isPermaLink="false">https://medium.com/p/50d8b5c45b61</guid>
            <dc:creator><![CDATA[Alex Vernacchia]]></dc:creator>
            <pubDate>Mon, 13 Oct 2014 18:07:29 GMT</pubDate>
            <atom:updated>2014-10-13T18:07:40.571Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m often disappointed with things that happen in open source projects. Most of these things relate to version control, and I’ve seen them in projects I maintain, projects I contribute to, and various other projects. I figured this was as good of time as any for me to write about it.</p><h4>Main Repo vs. Fork</h4><blockquote>Should contributors to your open source project use the main repo, or should they use a fork?</blockquote><p>I believe all contributors should use a fork of the main repo. Obviously, if they don’t have write access to the main repo they need a fork. Even if you have write access, you should still use a fork. I have two reasons for this.</p><p>First, there is less chance of things getting f&amp;%$ed up. There is always risk of overwriting code when pushing to a repo, and even more when pushing to the main repo. I’ve accidentally executed the code below while working on a project where “origin” was the main repo.</p><blockquote>git push origin -f</blockquote><p>Seems like a normal git command, right? Because I left out my branch name it didn’t do what I expected. It <strong>force</strong> <strong>pushed</strong> all my branches to that remote, no matter if I wanted to rewrite them or not. It even force pushed my master branch, which was not up to date. Whoops!</p><p>I was able to get my data back because Git is awesome, but what happens if you aren’t able to recover? You may have just lost a good amount of work. Why even take this risk?</p><p>Second, it keeps the main repo clean. Polluting the main repo with everyone’s branches makes it hard to see what’s going on. In most cases, I don’t care about other people’s branches until they submit a pull request. It shouldn’t take me more than a few minutes to find what I’m looking for. The more branches, the more time it takes.</p><h4>Are maintainers above the law?</h4><p>Most open source projects have contribution guidelines, which contributors follow in hopes of getting their code in the project. Should the maintainers have to follow these rules? Even the version control rules?</p><p><strong>YES and YES</strong>. Hopefully, the version control rules advocate the use of forks. Everyone makes mistakes, even maintainers (who have write access), and limiting work on the main repo reduces risk. Maintainers saying, “Using a fork is a lot of extra work. I’m a maintainer, I should be able to do what’s easiest for me” have it all wrong. There are 1–2 extra steps, which you only have to do once. Instead of pushing a branch to the main repo, you first click the “fork” button, update the remote’s url on your machine, push to your fork, and then submit your pull request. Further changes only require you to push to your fork and submit a pull request. How easy is that???</p><p>I’m not advocating never working on the master branch, just that there are certain times to do so. These would include releases and merges (done via command line).</p><h4>Version Control (VC) History and Merges</h4><p>If you’re like me, you like your project’s VC history to be clear and concise. I like when it’s easy to find when and where changes occurred, whether they be features or bugs.</p><p>There are a lot of things that make this hard to do. For example, I <strong>hate</strong> when someone uses an outrageous number of commits per fix/feature and/or when commits have nondescript messages.</p><p>How is anyone supposed to know what changes were introduced when looking at a vague commit message? How is anyone supposed to find where a change occurred if there are 44 commits for a one line change?</p><p>To fix these problems I do two things. First, I will squash my pull requests after they’re reviewed and passed (don’t mess with public history). If I’m the one merging the changes I will merge them, then rebase them into one commit with a descriptive commit message. The author still get’s the credit for the code addition, so it’s no biggie in my mind.</p><p>Second, I try to be descriptive when creating my branches and when writing my commit messages. An example of a branch may be “<em>feature-something-or-other</em>” or “<em>component-im-editing/what-im-updating</em>.” With subsequent commit messages I will start them with, “<em>component|feature/what I did</em>.”</p><p>I’ve committed all the crimes I talked about above, but over time I realized things could be done better. Don’t be the person resisting change because the end result is harder for you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50d8b5c45b61" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Career Advice From a 24-year-old]]></title>
            <link>https://medium.com/@vernacchia/career-advice-from-a-24-year-old-9ea03abcd048?source=rss-2b1589ad1e73------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ea03abcd048</guid>
            <dc:creator><![CDATA[Alex Vernacchia]]></dc:creator>
            <pubDate>Fri, 22 Aug 2014 18:44:43 GMT</pubDate>
            <atom:updated>2014-08-22T20:51:12.061Z</atom:updated>
            <content:encoded><![CDATA[<h2>A 24-year-old Giving Career Advice?</h2><h4>and maybe some life advice?</h4><p>Yes, I am a 24-year-old professional. To some this may mean I have no business giving advice. To others, this may be exactly what you’re looking for; possibly because you are at the same point in your life as I am. So let’s get down to brass tacks.</p><h3><strong>Ask for what you want</strong></h3><p>This is, by far, the most important advice I can give you. Whether it be our careers or our personal lives, we all want to progress. But, how are we going to progress if we’re afraid to ask for what we want?</p><p>Last year, I missed out on attending a pretty big conference. Since I did a lot of the conference demo work I assumed I would get to go, but I was wrong. After letting my manager know I was disappointed, they said that I could have gone, but they didn’t know I wanted to.</p><p>Since then, I have continually asked for what I want, and it has worked out great. I am currently in the process of transferring overseas at my current company, which is mostly due to the fact that I asked for the opportunity.</p><p>Some of you may be thinking, “Doesn’t this make me seem entitled?” I thought the same thing at first, but in most situations it doesn’t. Have you done the work that merits what you’re asking for? Do you think you deserve better? Are you content with what you have? Is this something you want and will it help you? These are just some of the questions I ask myself before moving forward with my request.</p><h3><strong>Get out of your comfort zone</strong></h3><blockquote>Coming out of your comfort zone is tough in the beginning, chaotic in the middle, and awesome in the end…because in the end, it shows you a whole new world!! Make an attempt..<br>- Manoj Arora, From the Rat Race to Financial Freedom</blockquote><p>Don’t be afraid to try new things! Simple as that.</p><p>Travel. Play sports (even if you’re not the best at them). Go on small adventures. Pick up a new hobby. The list could go on forever.</p><p>I recently went to my first <a href="http://thepeachmusicfestival.com/">music festival</a> and had no idea what to expect. I was a little nervous at the beginning, but after a few hours everything was amazing. I was elated just being there, and I ended up meeting a bunch of great people!</p><h3><strong>Do what you enjoy</strong></h3><blockquote>My philosophy is: It’s none of my business what people say of me and think of me. I am what I am and I do what I do. I expect nothing and accept everything. And it makes life so much easier.<br>- Anthony Hopkins</blockquote><p>I’m the only one who should care what I think about myself. Unfortunately I realized this too late, so during high school and college I put a lot of value in what others thought. Because of this I passed up things I enjoyed because I feared what other people would think. I still regret a lot of my decisions today.</p><p>Luckily, I finally found something I’m pretty good at and thoroughly enjoy. I was recently talking to one of my buddies about hypothetically winning the lottery. I said I wouldn’t change anything about my work life if that were ever to happen. He was a little baffled at that statement, which made me realize very few people can say that. Most of my friends hate their jobs and are still looking for the “right” fit. My days go by very quickly because I love my job. Their days continue to drag on.</p><h3><strong>Don’t accept the status quo</strong></h3><blockquote>One day everything will be well, that is our hope. Everything’s fine today, that is our illusion<br>- Voltaire</blockquote><p>Consistency is key. Change is bad. If it’s not broke, don’t fix it. It works good enough.</p><p>I’m sure we’ve all heard these phrases at one point or another. What’s the problem with them? They are boring. They stifle innovation. They are the past, not the present or the future.</p><p>Pushing boundaries is what I love to do; along with breaking stuff. Since I’m a software engineer I get to do both on a daily basis.</p><p>But, let’s keep it general for the time being.</p><p>Every company can be improve in some way. You may not see it until you’ve worked somewhere for an extended period of time, but when you do it will hit you like a ton of bricks. You’ll think to yourself, “Whoa! Why have we been doing it this way all this time?” Then, you’ll do one of two things; keep on doing what you’ve been doing or change to something new. You <strong>NEED</strong> to be doing the latter or you can just stay in the past.</p><p>This “improvement” concept applies to people as well. Everyone should be continually working to improve themselves. It doesn’t have to be huge changes all the time, little ones will do just fine!</p><h3>Any others?</h3><p>These are just some of the things that have helped me in both my work life and personal life. Please let me know if there are any others that work for you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ea03abcd048" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Old People and New Technology]]></title>
            <link>https://medium.com/@vernacchia/old-people-and-new-technology-6cc772956950?source=rss-2b1589ad1e73------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cc772956950</guid>
            <dc:creator><![CDATA[Alex Vernacchia]]></dc:creator>
            <pubDate>Sun, 11 Aug 2013 15:48:08 GMT</pubDate>
            <atom:updated>2013-08-11T15:54:35.357Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Be43sAp_nx62NsWK.png" /></figure><h4>It’s probably a little different than what you thought</h4><p>I am 23 years old, I just finished college, I have a job in the technology industry, and I work with older people everyday.</p><p>Every so often I seem to read an article about how my generation (Gen-Y) is the best at keeping up with new technology. They’re about how older people in the tech-scene can’t keep up with new technology; How they can’t adjust.</p><p>I would like to send a message to all the people who write these articles. It’s just not true.</p><p>How do I know anything about this since I’m a young professional? The workforce at <a href="http://www.exacttarget.com/">ExactTarget</a> (where I work) is roughly split 50/50; Between “young people,” under 30, and “old people.” On a daily basis I have the pleasure of interacting with a variety of people ranging in age. Sometimes I even get to help them!</p><p>We are on the bleeding-edge of technology at ExactTarget. Here, people constantly have to adjust to new technology and/or change their way of thinking (problem solving).</p><p>When I first started this job I thought I was going to be surrounded by people around my age. You know, because they are all up on that hip tech shit. Fortunately, I was wrong. Most people I work with daily are older than me, and let me tell you I am impressed by them everyday.</p><p>I was utterly surprised at how everyone, especially older programmers, keep up with technology. Many times when they were helping me with problems, they asked if I had used this? Or, if I had used that? Or, this will make everything so much better for you.</p><p>I recently asked one of my co-workers, who is approaching the early age of 60, “How do you stay up to date with all this technology?” The gist of his answer was, “I love doing it. Plain and simple. I could never imagine myself doing anything else. I love coming into work everyday, and I don’t want that to stop.”</p><p>None of those articles I’d read before even considered this point of view. I hope when I approach that age that I will feel the same way, not that I don’t feel that way right now!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cc772956950" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why go to college?]]></title>
            <link>https://medium.com/@vernacchia/why-go-to-college-d280478cc565?source=rss-2b1589ad1e73------2</link>
            <guid isPermaLink="false">https://medium.com/p/d280478cc565</guid>
            <dc:creator><![CDATA[Alex Vernacchia]]></dc:creator>
            <pubDate>Wed, 10 Apr 2013 20:22:45 GMT</pubDate>
            <atom:updated>2013-04-11T20:08:56.956Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*Td5duIiJ4W-dIlON.jpeg" /></figure><p>It feels like every day I see an article on some script kiddie’s blog that advocates not going to college for a technical degree. They tend to say something like, “I can learn this stuff myself,” or, “Why waste the money?” or, “This stuff is easy, I can stay in my Mom’s basement while doing it.” Well maybe not the last one, but you catch my drift.</p><p>I agree with the content of what they’re saying. You can learn technical subjects on your own. I learned most of what I know on my own. And why would you want to waste money? Damn, if I didn’t have my student loans, I could be a travelling or wasting it some other way.</p><p>But let’s be serious for a second. If you’re just out of college, have no loans, and are making bank, you’re going to be wasting it. I mean who wants to invest for the future when you could blow it now? Who listens to their parents anyway? Who are parents? I digress….</p><p>So onto the million dollar question: <strong>Why go to college to study in a tech-related field?</strong></p><p>First, you need the <strong>stress</strong>. Stress is a necessary evil. It pushes you to get things done, to deliver on what you promised. In college, you are under constant stress. (You don’t count if you’re one of those people who is good at everything and never needs to study.) You need to get this done for this class, that done for that class, oh and you forgot you have a paper due tomorrow that you haven’t even started.</p><p>This stressful atmosphere is extremely similar to today’s work environments (yes, even start-ups; especially start-ups). Your deadline is your release (usually, or some feature launch). Is this ticket complete? Does the new feature function correctly with your 5-person team’s work incorporated into it? As in college, if you don’t have it all done on time, “bad” things will happen.</p><p>When you go to college, this stress is a daily part of your life. So, when you get to your first real job, you’ll be accustomed to it. You’ll be able to make a smooth transition from college stress to work stress, and be able to deal with such situations appropriately.</p><p>Everyone reading this who didn’t go to college is probably saying, “I was stressed in everyday situations,” or, “Freelancing is hard and super-stressful.” To you I would say, “It doesn’t compare” (and yes, I have done both).</p><p>If you don’t complete something on time, be it a freelance gig or an assignment you made yourself do to learn something, the worst that can happen is that you might not get paid or you have to wait until tomorrow to tackle it. But if you’re in school, you’re like, “Shit…I cannot afford to stay here because I messed up. I just wasted $15,000 over the past 3 months. What was I thinking?” Can you judge which one is more stressful?</p><p>Second, go to college for the <strong>teamwork. </strong>In today’s tech work environment, unless you can do the entire project yourself or you’re a superhuman, you’re going to be working on a team. Most of the time this will be face-to-face, but if you’re working remotely, it’s going to be all over the phone and through e-mail.</p><p>If you’re a freelancer, chances are you’re going to be doing it all yourself. Or you’ll have one specific function and the other person will have another (I used to do all the programming and my buddy did all the design). If you’re working with the right people (let’s not even get started on working with the wrong people), communication within a small group is super easy. Or if you’re learning something by yourself, you’re probably going online and posting on stack overflow or chatting in forums. No real communication there.</p><p>This doesn’t mimic the real world. Depending on the size of a company you could be interacting with 20 or more people a day. I think my max was about 50, and that was when I was just a new hire.</p><p>Does college mimic this environment? I would say it’s the closest you can get. You take roughly 5 classes a semester. You’re given group projects for most of those classes. If you’re working in a 4-person group, you’re interacting with anywhere from 9-20 people over the course of these projects. And that’s just the people in your group; don’t forget the professor (a.k.a. your boss). And what about the other groups? If your group can’t figure something out, you need to ask others to point you in the right direction.</p><p>Third reason: <strong>networking. </strong>Pretty self-explanatory. If you’re willing to work hard and do exceptionally well, your professors will help you when it comes to getting a job by writing reference letters. And I’m pretty sure every decent professor knows people in your field that are hiring, as most of these profs already have real-world experience.</p><p>If you’re a freelancer, yes, your clients could be your references, and that could be enough. But what if you’re just learning stuff on your own? Are open-source contributions enough? Will making one website with the basic skills you learned get you the job you’ve always wanted?</p><p>Lastly, college makes you <strong>friends</strong>. I had fun in college because I got out of my comfort zone and met people. I couldn’t have done that if I had been behind a computer in my parents’ house teaching myself to program. The people I met at college helped me get my first internship, and my first job, and they are the people who are trying to pull me away from my current job.</p><p>I think college is a necessary evil. I have done it. I have learned languages on my own. I have freelanced. And now, I’m working at a job I enjoy going to every day.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d280478cc565" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>