<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Christopher J Almeida-Symons</title>
    <description>The latest articles on DEV Community by Christopher J Almeida-Symons (@chrisjsymons).</description>
    <link>https://dev.to/chrisjsymons</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F96843%2F988f4660-4ae4-4f03-962c-6e06df0cb5ca.png</url>
      <title>DEV Community: Christopher J Almeida-Symons</title>
      <link>https://dev.to/chrisjsymons</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/chrisjsymons"/>
    <language>en</language>
    <item>
      <title>When does a system become a legacy system?</title>
      <dc:creator>Christopher J Almeida-Symons</dc:creator>
      <pubDate>Fri, 13 Sep 2019 06:46:44 +0000</pubDate>
      <link>https://dev.to/chrisjsymons/when-does-a-system-become-a-legacy-system-4c52</link>
      <guid>https://dev.to/chrisjsymons/when-does-a-system-become-a-legacy-system-4c52</guid>
      <description>&lt;p&gt;Currently, I am working on a modernisation project in which the team are creating new applications, as well as updating old applications (some are older than me😄) with new modern technologies, such as Angular, NodeJS etc.&lt;/p&gt;

&lt;p&gt;We realised that some of the new technologies we are using are already out of date, for example, we are using Node 6.9.1 (current LTS version is 10.16.3). Along with other packages being behind their most recent version the question came up of &lt;strong&gt;"When does our application become a legacy application?"&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;So I thought I would put this question out into the community to get your thoughts.&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>systems</category>
      <category>upgrades</category>
      <category>legacy</category>
    </item>
    <item>
      <title>Is getting a Computer Science degree worth the time?</title>
      <dc:creator>Christopher J Almeida-Symons</dc:creator>
      <pubDate>Thu, 07 Mar 2019 10:03:18 +0000</pubDate>
      <link>https://dev.to/chrisjsymons/is-getting-a-computer-science-degree-worth-the-time-3nc5</link>
      <guid>https://dev.to/chrisjsymons/is-getting-a-computer-science-degree-worth-the-time-3nc5</guid>
      <description>&lt;p&gt;You will see many different arguments on whether developers are required to have Computer Science (CS) degrees. People saying "YES" you must have a Computer Science degree, while others say it is the experience that matters most. Well, they are both right.&lt;/p&gt;

&lt;p&gt;When I first started coding, in the days of using tables for layouts, I was learning by looking at online tutorials. Without these, I would have never created my first hand-coded website. These were a valuable source to me, and have still remained a valuable source of learning.&lt;/p&gt;

&lt;p&gt;Making the step into becoming a developer full-time, I realised there is so much more I needed to learn. I had to improve my foundation so I could build upon that. This is where my CS degree came in. I could not afford to go to university full time so decided on studying part-time.&lt;/p&gt;

&lt;p&gt;Studying part-time, I believe, gave me a greater benefit as not only was I working towards the degree, I was getting valuable work experience. Being around people at work that has vast amounts of knowledge was allowing me to ask questions about what I was learning in my degree, and get real-world answers.&lt;/p&gt;

&lt;p&gt;The CS degree gave me a greater foundation that I feel I was getting from doing tutorials online. Sure, I learnt languages which I probably will never use again, but, the logic around those languages and the paradigms they conform too are important aspects of coding. Being exposed to these languages helped me focus on which ones I enjoyed working with and the direction I would like my career to take. When I first started, my main goal was creating websites and I was a little bit more design focused. As I've gone through my degree I have changed to be more focused on software and providing the user with the service they require. Before people step in and say "a good system needs both good UI and UX", I know, I have just changed my focus from UI to UX.&lt;/p&gt;

&lt;p&gt;Since finishing my degree I have continued my learning using online courses, but without the knowledge gained from my CS degree, I feel I would struggle to understand some of the concepts as easily as I do now.&lt;/p&gt;

&lt;p&gt;All in all, I believe it is good to have a CS degree but I do not take away the real world experience I have gained. With so many more online resources new developers can gain the same knowledge as someone with a CS degree. One issue of learning this way, unfortunately, is when you start applying for jobs, as many companies require a degree. One of my previous companies hired me without a degree and when I came to hire new developers I was told they must have a degree. Due to this, I believe they missed out on hiring some great developers because they did not have a degree.&lt;/p&gt;

&lt;p&gt;If you enjoy coding, and learning, this will never stop you finding a job within this industry and not having a degree will never stop you. If you have the time and resources to attend universtiy, whether fulltime or part-time, I certainly recommend it.&lt;/p&gt;

</description>
      <category>computerscience</category>
      <category>coding</category>
      <category>beginning</category>
      <category>university</category>
    </item>
  </channel>
</rss>
