<?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 Craig Pearce on Medium]]></title>
        <description><![CDATA[Stories by Craig Pearce on Medium]]></description>
        <link>https://medium.com/@ScouseHobbit?source=rss-8ed206729798------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RlXvxQsKTC5yNvlpASmjnQ.jpeg</url>
            <title>Stories by Craig Pearce on Medium</title>
            <link>https://medium.com/@ScouseHobbit?source=rss-8ed206729798------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 16:48:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ScouseHobbit/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[Fuchsia OS: is now the time for a 21st Century Operating System?]]></title>
            <link>https://medium.com/@ScouseHobbit/fuchsia-os-is-now-the-time-for-a-21st-century-operating-system-d6aac02f349c?source=rss-8ed206729798------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6aac02f349c</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[fuchsia-os]]></category>
            <category><![CDATA[operating-systems]]></category>
            <dc:creator><![CDATA[Craig Pearce]]></dc:creator>
            <pubDate>Fri, 18 Jun 2021 08:09:23 GMT</pubDate>
            <atom:updated>2021-06-18T08:09:23.945Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UWXeuRcOaJguD-Zj" /><figcaption>Photo by <a href="https://unsplash.com/@charlesdeluvio?utm_source=medium&amp;utm_medium=referral">Charles Deluvio</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>After its first appearance online back in 2016, Google recently released their first product to use its new operating system called Fuchsia OS, without any major announcement from the company. With Operating Systems being one of the most complicated and expensive pieces of software both to build and to maintain. Why has google decided now is the time for a new operating system, what is their endgame, and what wider implications could it have on the technology industry? Those are the questions I plan to try and answer in this article.</p><p>So lets start with what the Fuchsia is Fuchsia OS? Currently, Google has two main operating systems available to its users, Android and Chrome OS. The difference with Fuchsia is that it does not use Linux. Which is huge, the backbone of the internet and the majority of the technology we all use today will use Linux as the underlying Operating System, with companies in a lot of cases building their own “flavors” on top of it. Even a lot of those who don’t use Linux use the same underlying principles Linux is built on, known as Unix.</p><p>So the next natural question, why move away from Linux? To answer this question, it is probably best to have a very brief history lesson. So, Linux, first released in the early 1990s, is a free open source Operating System. The principles of it however are heavily tied up in something known as Unix, which is even older. The inception of Unix was in the late 1960s. You don’t need to be familiar with either technology to see the common problem here. The Technology Industry is an ever-changing and unpredictable ecosystem, the landscape can change significantly in a very short space of time. Just think about what computers and mobile phones looked like at the start of the millennium. Crucially, both Linux and Unix alike were ideas conceived long before the World Wide Web became the massive societal backbone it is now. Just think how difficult the last year full of lockdowns would have been without the internet. Both in keeping us entertained and keeping the economy afloat. The coupling of very old principles and software with something which changes frequently is what I believe is the problem Google is trying to resolve.</p><p>As well as trying to resolve this problem, it could also allow for them to copy a very lucrative model formed by their biggest competitor. Apple over the years have managed to build their own “walled garden”. The idea of a walled garden is you buy one Apple product, you really love the experience, so when you need to expand or replace your current tech, you naturally buy an Apple product. Now you have two products which work brilliantly together, so it both encourages you to buy more products from them, as well as discourages you from ever leaving. All the while Apple is laughing all the way to the bank. This system works brilliantly, but also will cause a lot of pain for Apple. With the many different Operating Systems they have built over the years, any cool features or functionality they want to introduce, they need to consider not only how to implement on the initial device, but also how the functionality ties in with the wider ecosystem and how to implement it into each OS accordingly. This has a heavy cost both in resources and in time. Apple can afford to take their time in a lot of cases as they have loyal customers and fans alike, there aren&#39;t really any true alternatives to that experience on the market as it takes years of planning and implementation. But with Apple mainly being a hardware focused company, what if a competitor appears, offering the same seamless integration at the fraction of the price, since the competitors model is based on personalized advertising and not on hardware.</p><p>A new Operating System from the ground up suddenly makes sense. Every smart device in your home, all running on one OS. It means all of your devices can synchronize seamlessly which is a massive plus for the user. Imagine all of the data you access on your smartphone being available on any device you own which can access the internet. Better yet, it will be a familiar layout on all these devices so you only ever need to learn how to use it once. Lets say you might decide you want to install an app, so it installs it on the device you request it on, but as part of this system it also installs on every other device you are logged into automatically. At the moment, the “Internet of Things” future we were all sold on is still in its infancy, the connections between applications, devices and companies is very messy and prone to bugs, incompatibility and misalignment. This idea of a unified Operating System could be the start of a seamless, painless experience for all those with devices on this software.</p><p>It is also a massive selling point for developers. You build one common code base and you are then able to deploy it to any of the devices running Fuchsia OS, therefore, the potential reach of your application is huge, but the cost of building and maintaining the application is low. Google even have a toolkit available already called Flutter, which allows for you to build your common code base in their own programming language, then it builds the appropriate packages for your code to deploy to both iOS and Android. This would be the next evolutionary step for that, and I can imagine Fuchsia OS will only work exclusively for apps wrote in Googles own programming language.</p><p>For Google, it means only having to worry about maintaining one Operating System for all of their products, which means its easier to innovate, easier to keep secure and easier to provide a great stable experience for all of its users. The more devices Google is able to sell to you, the more data points it is able to collect to make its advertising models even more lucrative. It doesn’t even need to be a “Walled Garden” in Googles case, they can license it to as many companies as they want. Since they are primarily a software company. It doesn&#39;t matter who makes the hardware, so long as its Googles software that ships on it.</p><p>The idea of one common OS for all of your smart devices is extremely appealing. The best way to visualize what it could look like, is if you open a website on your smartphone, then open the same website on a computer or TV. This dynamic scaling modern websites do, regardless of the device being used, can be thought of as a very lightweight version of the potential future possibilities we could have with a unified OS.</p><p>As the fight between Google and Apple continues. It will be interesting to see how both companies strive to innovate. Until a competitor emerges, both sides are crucial in driving technology forward, and it will be interesting to see what conversations we are having around this subject in another five or ten years time.</p><p>Thanks for reading, any feedback or discussion is always welcome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6aac02f349c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Confidence is the most valuable skill]]></title>
            <link>https://medium.com/@ScouseHobbit/why-confidence-is-the-most-valuable-skill-f4e1ed8298e0?source=rss-8ed206729798------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4e1ed8298e0</guid>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Craig Pearce]]></dc:creator>
            <pubDate>Fri, 01 May 2020 15:10:25 GMT</pubDate>
            <atom:updated>2020-05-01T15:10:25.957Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lBo3RBncFofs5pfE" /><figcaption>Photo by <a href="https://unsplash.com/@mbrunacr?utm_source=medium&amp;utm_medium=referral">Miguel Bruna</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>So, this topic is a strange one for me. As someone who grew up extremely shy, and in many regards is still very shy, talking about confidence is not something that comes naturally to me. The reason I wanted to write about it is because how much of a massive impact a bit of confidence can really have.</p><p>Important to note, I&#39;m not implying I&#39;m a confident know it all who thinks the world isn’t on his level. It doesn’t mean blind arrogance but measured, realistic confidence. In this case it is specifically related to my career and the work I do. It enables me to do my job effectively(most of the time hopefully) and provides the foundation of self assurance required. Self assurance is a necessity to fight back any doubt that creeps in, if that doubt builds up, you suddenly have imposter syndrome on your hands. As someone who had spells feeling like that earlier in my career, it is not a nice place to be.</p><p>I wrote this in the hopes of helping those who are/were in similar positions. This article is going to explore what exactly confidence is, what it means to me, how it helps me in my career and how confidence is built and what it should be built on.</p><p>Firstly, it is important to stress the difference between confidence and arrogance. Being confident is about having a realistic image of yourself, knowing your own ability and applying it. Arrogance is when this image of yourself is inflated and illogical. It is irrational and is not reflective of true skills and abilities, disregarding the facts and basing opinions and views on the idea that you always know better than others. Furthermore, it’s important to distinguish between the two, because confident people are often labelled as arrogant. But there is nothing wrong with confidence as long as it is a realistic interpretation of yourself — someone who knows their strengths, but also their flaws. Knowing the importance of the skills and views of those around you is crucial, as well as being able to accept that you are not always right. That is what I am referring to in this article.</p><p>As mentioned, confidence is something which should be based on measurable factors. An example is experience. Experiences, both good and bad, are valuable foundations to build upon. If you are tackling a problem, and have encountered similar issues 100s of times before and overcame them, you should be fairly satisfied that you can conquer the challenge again. Likewise, if you find yourself stuck with a reoccurring issue, that has caused you plenty of grief, you know solving that particular aspect is not one of your strengths. Therefore, you should use this to inform your judgement.</p><p>Confidence doesn’t mean you are outstanding at everything, or should think you are outstanding at everything. It’s about having a strong sense of identity and knowing your traits, both good and bad. The more experience you gain, the stronger your confidence should be, as you learn more about who exactly you are. The feedback you obtain from peers should also assist you in constructing confidence. They help to provide another perspective on your skills and attributes (again, both good and bad), and what they value you for is something you should take pride and confidence from.</p><p>As a programmer, confidence is simply a necessity for a number of reasons. With programming being a facet of problem solving, having the confidence to persevere is crucial. Coding (and problem solving) is iterating on multiple failed attempts, for one reason or another. If you didn’t have the confidence that you will eventually reach a solution, then you would forever be stuck in the initial phase. Obviously, there are some times where you have to make the difficult decision of stopping, leaving an issue unsolved. The situation leaves a bitter taste in the mouth, but ultimately provides the valuable knowledge required to improve your understanding of yourself, further increasing your odds of success for the next time you stumble across the problem.</p><p>When you reach your solution, it will also provide you with assurance that your implementation is correct and solves the problem you set out to fix adequately. If you are forever perplexed, second guessing your work, you would never be able to move on. Productivity would be non-existent. Again, this doesn’t mean your solution will always be right, because no one is “all knowing”, and solutions can always be optimised. We always learn and mature both in our careers and personally. It’s about being comfortable with not being perfect, and thriving for improvement on each iteration. A convenient example is these articles. I know my writing leaves a lot to be desired, but feeling insecure and nervous about publishing it doesn’t help anybody — I just need to be realistic with myself and strive for improvement each time I write. Which is better for both me and for those who read it.</p><p>It doesn’t just help with the technical side of the job. Additionally, it helps with the general day to day aspects of the job. For instance, meetings, when individuals look to you to solve a task or provide some insight. Giving a confident, definitive answer helps assure those around you, as well as improve their understanding of your capabilities. It doesn’t mean say yes to everything, because not everything is possible/feasible. Colleagues need to know if something isn’t realistic, so they can plan accordingly and put the necessary contingencies in place, should they be required. Clearly, this isn’t always possible, there will be times where you simply don’t know either way. In addition, it gives you the courage to voice your opinion when required. If you believe in your own thinking on a matter, you are much more comfortable and likely to share it. Therefore, it is much easier to persuade others to have faith in you.</p><p>An additional facet it helps me with is coaching those around me. If you told me five years ago that I would be coaching others in the role and helping them develop, I would ask what you’ve been drinking and where can I obtain some, but here we are. Realistically, I couldn’t sit there providing knowledge or opinions on a matter if I didn’t feel I was comfortable or assured on the topic. It’s really important that before you start coaching, mentoring or managing others, that you are comfortable and confident yourself. When you are in this position, it is inevitable that you will be asked a multitude of questions. Therefore, it’s important that you are in a position where you feel relaxed enough to provide a valuable answer. Again, no one is expected to know everything, but providing accurate and definitive answers is important in these situations (even if the answer is no).</p><p>In summary, confidence is like respect, it has to be earned. Thanks for reading, as someone who has always struggled with confidence, I felt it was an important topic to discuss. All feedback is welcome, and hopefully you have gained something, even if it’s the opinion that I am terrible at this! Thank you for your time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4e1ed8298e0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first three years in a tech role: The key lessons I've learnt]]></title>
            <link>https://medium.com/@ScouseHobbit/my-first-three-years-in-a-tech-role-the-key-lessons-ive-learnt-8407881ae110?source=rss-8ed206729798------2</link>
            <guid isPermaLink="false">https://medium.com/p/8407881ae110</guid>
            <dc:creator><![CDATA[Craig Pearce]]></dc:creator>
            <pubDate>Mon, 14 Oct 2019 15:55:43 GMT</pubDate>
            <atom:updated>2019-10-14T15:55:43.220Z</atom:updated>
            <content:encoded><![CDATA[<p>During the last few months studying at University, I realised I seriously needed to consider what sort of career I wanted to forge myself with my Computing Degree. The problem is, what careers are available and suitable for such a degree?</p><p>All I have ever seen myself realistically doing was leaving University, getting a job at a Company as a Software Developer and see out my working days coding away in my own little world. It wasn’t a particularly realistic vision, but it was the only vision I had at the time.</p><p>Reflecting on where I am now, I could never have predicted it three years ago when I was still in my student days. So, how did I get here and more importantly, what have I learnt?</p><p>This is hopefully what I am going to answer in this article. Here are the five key points I would advise anyone new to the industry in order to make their development as smooth and fast as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DV7HX-3MKIpNuY1C" /><figcaption>Photo by <a href="https://unsplash.com/@thomasschweighofer_?utm_source=medium&amp;utm_medium=referral">Thomas Schweighofer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><ul><li><strong>Think bigger</strong>: If I was to summarise this in an analogy, lets talk about Lord of the Rings, because why not. In the series, the Hobbits are quite happy, gratified individuals. All they know is the Shire and that’s all they need to know. They are not concerned with the wider realm as it is all they need to know and enjoy in their self contained part of the world. However, once they leave the Shire, they see what it’s like beyond the borders, thus they have a better grasp and understanding of the world. When they return home, they are better people for it. They have realised their potential, their strengths and seeing the bigger picture has helped them grow as individuals and also as a team. When starting out in a programming/technical role, we naturally have tunnel vision and focus on fixing the sole problem we are given. That being a bug fix, a new method that needs writing etc. It is extremely easy to just stay focused on the sole problem, it is comfortable. When you solve it you still get an enormous amount of gratification. So why would your mind want to expand? I struggled to push myself out of this comfort zone for a long time. Being able to see the larger project in its entirety, to base your solution on the wider system rather than one self contained little aspect. I find it the most valuable skill I have learnt during my career. Then to go one step further to assess the overall process. Understanding what are the bottlenecks, what are the teams challenges etc. Solving the problem of the process makes the day to day tasks much easier. It is also extremely valuable, it is the key to maximising productivity and your problem solving abilities. I find problem solving to be a natural skill which like any physical tool, it can be sharpened, refined and upgraded. Seeing the bigger picture has vastly improved my own problem solving abilities. Creating more optimal solutions(nothing is ever perfect), solving the harder challenges, finding flaws in your initial ideas, iterating and of course, refactoring your previous work. All of these help your natural problem solving ability, all of these are influenced by the scale of your vision and how you view the project. Therefore trying to see the bigger picture, is probably the most valuable advice i could have given myself three years ago.</li><li><strong>Mentoring helps both individuals learn</strong>: Mentoring/Coaching has given me a fresh perspective in my work and has assisted both me and the person I am mentoring. There will be problems you’ve never experienced/have forgotten about during your career that are reiterated from it. Getting this fresh view helps to push you towards seeing the project on a wider scale which as mentioned above, is extremely important. Mentoring helps both people get involved, learn and grow. Being a mentor helped me to expand my thinking to see from different angles. Mentoring is not a one way street, it is an open conversation where both parties express ideas and opinions with one another. The job of the mentor is to help to hone the learners understanding so they can grow and mature. It is not to dictate or force someone into a way of thinking. You are just the shepherd guiding them in their development. Be it through teaching, advising or general discussions. I am extremely grateful to have been given the opportunity to mentor. I would recommend anyone with the opportunity to grasp it with both hands. It has helped me to gain an incredible amount, and I only hope my mentee has learnt as much as I have from it.</li><li><strong>Trust your gut instinct:</strong> When starting out, I tended to not trust my ideas and was prone to doubting them. I felt the dreaded “Impostor Syndrome” that is often mentioned, but it is something that is never really discussed. From early on in my University days , I&#39;ve always been confident in my technical ability. I know I have the ability, but there has always been that fear of failing, of my peers not seeing me as good enough. Of not being able to apply my abilities in the real world. Again, this is self inflicted (at least I hope!) and is something we all have to overcome. As I mentioned, I believe that problem solving is a natural skill, this is what gives me the confidence that I can do my job well, as i know I have this skill. From personal experience, I believe that our initial gut reaction ideas where we conceive our resolutions are always right. However, I believe these ideas need to be refined and optimised through planning which is something I am going to elaborate on in the next section. Fundamentally, my belief is you need to trust that you make the right decisions on the initial inspection. That your ideas should not be second guessed, scrutinised or questioned. When starting out, it is very easy to question our own ideas and thoughts, as we believe experience would result in a different outcome, when in fact experience provides us with more polished versions of our initial idea. Therefore I encourage you to always go with your gut.</li><li><strong>The first solution isn&#39;t always the best:</strong> It is our natural instinct to see a problem - fix a problem. When I started my career, I felt a pressure to perform and deliver solutions as fast as possible. Even if that actual pressure wasn’t actually there, and it was self-inflicted. The optimal solution and also the hardest to make, is to be given the problem. Then scheme how to best solve this problem before tackling it. Ten minutes of planning can avoid many issues down the line. As i previously mentioned, I believe we always come to the high level solution. But early on with our lack of experience, these concepts require more forethought to correctly reach the optimal solution. Being able to draw out a well thought out plan is a talent in itself. The more planning you carry out as well as the more experience you gain, the easier it is to resolve these problems. A well thought out design can help minimise the risk of bugs, as well as refactoring time. In summary, when you come across an issue, fight your instincts and outline your design first. This will save you time in the long run, both in terms of the quality of your work, and the time it takes to plan over time.</li><li><strong>Be open to career changes and additional responsibility:</strong> When I applied to join the tech academy at my current company, I applied thinking I would be a Software Developer. You give me something to code and that&#39;s it — I would be in my own little coding world. Three Years on and I&#39;m a Test Engineer. I lead the test automation front in my team, own all of these tests we run as well as mentor those less experienced with the automation in my team. It’s impossible to know what you are going to do in your career at the start. It is easy to be apprehensive and nervous. Ignoring my fears and concerns and diving into opportunities head first has worked wonders. It has helped me mature, grow and to learn.Your career goal has to evolve as you do, so always be open to new possibilities. Life is what you make of it so always take the leap of faith!</li></ul><p>I hope you have found this information useful as this is something I&#39;ve always considered writing about but never really had the confidence to. If it has been helpful, Great! If not well I at least hope you enjoyed the ride. <br>Thanks for taking the time to read my ramblings, any feedback is most welcome and I hope you enjoyed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8407881ae110" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>