<?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 Francisco González Preciado on Medium]]></title>
        <description><![CDATA[Stories by Francisco González Preciado on Medium]]></description>
        <link>https://medium.com/@francisco.gonzalez_51776?source=rss-c0dbaec2530e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*P49LtxgvVJNqsyHx2q55QA.jpeg</url>
            <title>Stories by Francisco González Preciado on Medium</title>
            <link>https://medium.com/@francisco.gonzalez_51776?source=rss-c0dbaec2530e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:15:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@francisco.gonzalez_51776/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[Weekly Blog 6]]></title>
            <link>https://medium.com/@francisco.gonzalez_51776/weekly-blog-6-20a6684c7a71?source=rss-c0dbaec2530e------2</link>
            <guid isPermaLink="false">https://medium.com/p/20a6684c7a71</guid>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[intern]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Francisco González Preciado]]></dc:creator>
            <pubDate>Sun, 15 Dec 2024 05:38:42 GMT</pubDate>
            <atom:updated>2024-12-15T05:39:09.204Z</atom:updated>
            <content:encoded><![CDATA[<h4>Spark Week 8</h4><p>On our eighth week… These were some eye-opener seven days, all regarding the certfications had we chose. I think I didn’t mention it in the last blog but we also had our EOY (end of year) party ✨; it was during Friday the 6th and it was actually pretty fun to go. The second week of my courses (GCP — Associate Cloud Engineer) was sort of intriguing and even insightful in some senses. Our world, and everything about it that makes it work, is just huge, complex, intertwined, and even contrived at times 🌎.</p><p>These were some rather heavy seven days; a lot of doubts arise by hearing the experiences of my fellow Sparks ⚡️. My main concern was time (a concept that will reappear during the first lightning talk), it is astounding to see how fast everyone else is; I’ll extend this idea. Thanks to various comments and the check-ins/outs calls I could see that some of my peers were really dashing through all their courses 🏃‍♂️‍➡️. Kudos to them, sincerely, but being honest I felt like I wasn’t making enough effort to learn about my topic or to advance through my certification; imposter syndrome just hides, never leaves 🎭. Truth is that I was making progress but comparison is truly happiness’ killer.</p><p>The EOY party was just two Fridays ago, it was fun and a well deserved distraction time 🙂‍↕️. There’s really nothing technical to add regarding the event; plenty to eat, plenty to drink, and a lot of new faces. Well, maybe that would be technical enough for this entry; there’s a lot of people that work at my city’s office that I’ve never seen before 😯. This kind of celebrations are great taking into account the reality of our workplace; there’s hardly 20% of the workforce at office at any given time 😝. It was actually great to see them in a non-programmatic environment.</p><p>The cloud is really one of a kind, a marvel in its own right; still, the reality of it all always comes right back to me. The only way that you are able to read this, considering that it was written from an unknown specific place (to you…), just proves the unbelievable amount of parts that are at play at any given situation regarding the internet ⚙️. It is an immense wild corner of our technological advances to date and it’s not even a hundred years old. The cloud, in my case the GCP, just covers a specialized portion 🛜 of what needs need (no pun intended) to be covered in our current time. Thanks to my mentor I was able to consider a larger scope of what I was previously contemplating; thinking outside the box if you will 🔎.</p><p>Sometimes in order to understand or even begin to comprehend the moving parts of a composite subject such as the cloud you need to take a step back. As with any other subject or discipline, in order to see the bigger picture you might need to stop and reconsider the steps taken up to that very moment. Even the most novel and complex things that you can think of in this very moment are constructed over previous discoveries 🔙. That’s the beauty of it, the charm that I’m still trying to digest in relation to the whole structure that makes the cloud “run”. So, in order to learn the new stuff we must consider reconstructing what we already know about alternative matters; here’s for week 9 🤠!</p><figure><img alt="Sean Connery giving thumbs up approving the message above. Ready for week 9." src="https://cdn-images-1.medium.com/max/1024/1*VxX_h1l3uFK5dLKgt2YmRg.jpeg" /><figcaption>Sean Connery giving thumbs up approving the message above. Ready for week 9.</figcaption></figure><p>-Francisco G. P. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20a6684c7a71" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weekly Blog 5]]></title>
            <link>https://medium.com/@francisco.gonzalez_51776/weekly-blog-5-07b9d0dc5982?source=rss-c0dbaec2530e------2</link>
            <guid isPermaLink="false">https://medium.com/p/07b9d0dc5982</guid>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[intern]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Francisco González Preciado]]></dc:creator>
            <pubDate>Mon, 09 Dec 2024 00:14:28 GMT</pubDate>
            <atom:updated>2024-12-09T00:14:28.492Z</atom:updated>
            <content:encoded><![CDATA[<h4>Spark Week 7</h4><p>On our seventh week… The certifications period just started and it will involve the next six weeks of the Spark program. I decided to take a GCP (Google Cloud Platform) certification regarding the cloud; Associate Cloud Engineer ☁️. As it was expected the topics to cover and every new detail revolving is as interesting as it holds a new level of complexity; the plot just thickens. The most fun part (till now) of studying all the material for this certification is to actually test all the techniques learned this past six weeks 🔄.</p><p>When the certifications were mentioned during the first days of the Spark program I was somewhat intrigued as to what was the whole scoped involved in the selection. The possible paths to take, the best decision to make, and everything that would lie ahead was running to me 🔀. My two main options were about artificial intelligence and cloud; I had to ask for some advice 🧐. After having some conversations with friends and considering a whole lot of opinions and arguments I went for the cloud . I felt it as the right choice for me, in simple terms, it aligns best with what I want to do 🚀.</p><p>The Associate Cloud Engineer certification was the right choice for me consideration two outstanding points. The first one being that the arguemnts that I heard regarding this type of certification sounded logical to me. The second one was that I was drawn into it, for the past week I really couldn’t put my finger on why 🤔. For some reason my interest in the second option, which was A.I., had been washing off through the last few weeks 🫥. It may have nothing to do with the certification itself, but with some specific uses that’ve been given to the technology during the past few months~years 🙄.</p><p>The first topics about the cloud certification have been everything but known, and also, better said, boring. The foundations of what the cloud’s capabilities are just continue growing; at this point there isn’t a clear picture of the complete reach of the GCP ↗️. Up to this point I’ve managed to get to know the bottom layer of everything needed to know to navigate through Google’s cloud 🗺️. The virtual machines (which are basically virtual servers) have become the main focus of the first courses; how to create, navigate and manage them. It never ceases to amaze me the complexity and redundancy that is needed for these digital spaces to exist; physical locations 📍.</p><p>This is once again a different week and with it new challenges were made obvious, although now I’m coming to them with a little more edge. Is not that I’m assuming that the next topics will be easier or that I’m getting significantly better at my presentations; the approach will indeed be distinct. At the same time, assuming that with a change of direction the results have to be better would also be a big mistake from me, it’s all about improving and trying to find the techniques that work with ourselves. So, this week’s main goal is to learn how to learn how to learn how to…; I’ll be trying to reduce the trial and error iterations with time 🕰️. Let’s improve the improving and be grateful for the errors; here’s for week 8 🤠!</p><figure><img alt="Joaquin Phoenix giving thumbs up approving the message above. Ready for week 8." src="https://cdn-images-1.medium.com/max/1024/1*ohwGRRSStSOEGeZ-_p7Y_w.jpeg" /><figcaption>Joaquin Phoenix giving thumbs up approving the message above. Ready for week 8.</figcaption></figure><p>-Francisco G. P. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=07b9d0dc5982" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weekly Blog 4]]></title>
            <link>https://medium.com/@francisco.gonzalez_51776/weekly-blog-4-9e44413d1768?source=rss-c0dbaec2530e------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e44413d1768</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[intern]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Francisco González Preciado]]></dc:creator>
            <pubDate>Mon, 02 Dec 2024 01:52:29 GMT</pubDate>
            <atom:updated>2024-12-02T01:52:29.255Z</atom:updated>
            <content:encoded><![CDATA[<h4>Spark Week 6</h4><p>On our sixth week… The Breakable Toy I was finally presented (Buildable Bug 0.5) through some extra given time. The amount of details to prepare between the program and presentation were surprisingly not very few 📝. The demo’s presentation was a great way to bring to light other necessary abilities that at first thought might seem unrelated to the main purpose; not the case. One step at a time seems to be right way for now, or in other words, let&#39;s first focus on the ladder’s first step and then look upwards onto the next 🪜.</p><p>This last Thursday was the day me and other Spark members presented our demos 👨‍🏫. Some hours before the actual presentation my peers (Abraham and Ramón) and I rehearsed what we were going to say in front of each other. It might seem like just another “necessary” part of the process but it really helped to know how you feel about your methods in front of other people 🗣️. This type of practices is not only about yourself, it is actually a tremendously useful tool to give advice and comments to others. I know that thanks to those extra 2~3 days at the end we were able to improve our project and, definitely, our presentations ⌛️.</p><p>Now, the new, unlooked for, requirement we had to deal with was to actually do, prepare and establish everything surrounding the demo’s presentation. All of these also resulted in a great way to catch a glimpse of what organizing a true demo presentation could look like 🤞. Getting to chose the day in order to the most amount of people to be available is one thing, actually finishing your slides is a whole other topic. I have always loved the process of making presentations, I tend to think about how you have to process the total amount of information and return specific points or key concepts that can lead you to the whole picture 💭. To spice things up a little bit more, all of these is in english, like, you could already tell by now… 🤭</p><p>The language, preparation, and control over the material were the main points that were now in need to be covered. As I said, I really enjoy bringing all the parts of a presentation together and seeing all these several connections be made 🧩. The act of presenting, in itself, had only a tiny bit of rust over it, the hard part relies always in the start; like getting to start an old car’s engine in a cold morning. Once the fuzz of the first few tries fades away you can actually start to polish all those rough edges regarding pronunciation, rhythm, and rolling the r’s 🥴. Good thing is that the majority of what we’ve been doing is already in english so we’ve been having plenty of practice from the start 🤓.</p><p>This was an awesome week, not an easy one, but also not a boring one. It was more of a walk in a park… while the park was on fire and where I felt I was on fire as well 🔥. To keep on the jokes and the same unstoppable spirit I have to say that this has been the toughest week (til now). The best part of getting to repeat stuff is that you can also get to do the great things one more time; more to learn and more appreciation for the people surrounding me. With a better attitude and more humility upfront I’ll receive the new challenges ahead; here’s for week 7 🤠!</p><figure><img alt="Chuck Norris giving thumbs up approving the message above. Ready for week 7." src="https://cdn-images-1.medium.com/max/1024/1*FtVNKbnp1qVUh2Tcj7sgLQ.jpeg" /><figcaption>Chuck Norris giving thumbs up approving the message above. Ready for week 7.</figcaption></figure><p>-Francisco G. P. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e44413d1768" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weekly Blog 3]]></title>
            <link>https://medium.com/@francisco.gonzalez_51776/weekly-blog-3-927650cd3325?source=rss-c0dbaec2530e------2</link>
            <guid isPermaLink="false">https://medium.com/p/927650cd3325</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[intern]]></category>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Francisco González Preciado]]></dc:creator>
            <pubDate>Mon, 25 Nov 2024 01:20:31 GMT</pubDate>
            <atom:updated>2024-12-15T05:40:56.148Z</atom:updated>
            <content:encoded><![CDATA[<h4>Spark Week 5</h4><p>On our fifth week… The Breakable Toy I continued or how I tenderly call it: Buildable Bug 0.5. I struggled a lot with this project’s technologies, it isn’t easy to write those words, but along came the teachings 🤔. It’s clear that I need to re-structure my game, take a step back and analyze what I’ve been doing and also what’s not be getting done. So, in Plato’s spirit, I can also say that all I know is that I know nothing 🙂‍↔️.</p><p>This was the last week to develop the to-do list project. Although I got to touch all the distinct elements of the program, traces of my soon-to-be-acquired skills are easily visible 😅. I’m surprised even that I got to do what I got to do! Having said that… the bugs… I am in so much need of a great insect repellent 🪲 or more advanced technical knowledge and skills. The silver-lining here is that now I have a better idea of which parts I enjoyed the most and where I am to develop better techniques 🆙.</p><p>The way in which I approach the problems might become my main point of focus. Despite of not understanding each individual segment of an issue it’s important to acknowledge its parts properly 🧐. As it is popularly said, knowing a problem is half a solution, after that complexity might make its appearance, but it will be in a more known fashion. An almost forsaken step of the problem-solving conundrums is that one must rest if one wishes to make it to the end 🛌. This isn’t only about the physical aspect, but also about the mental and emotional portions that must absorb everything that’s new 🧠.</p><p>In the future I need to understand the parts in front of me in a more concise manner. Counterintuitively 🔀, taking a slower approach could be useful for me, I tend to try and rush into things. That just tends to produce a quicker burnout and a sense of helplessness that the only thing that achieves is to paralyze; that’s not the way. At the same time, the never-ending imposter syndrome 🎭 shows up at the worst of times, one just needs to listen and keep going. My little bug-fest will become something to look back and remember with tenderness ☺️.</p><p>This has been the toughest week (till now), although that phrase has become a recurrent statement if I’m being honest. I could never say that this was boring, not at all, it has been, in the very least, riveting 🫨. It has been daunting at times, like entering a dark room and with each new step I take it remains dark but grows in size. At this point it’s all about how one chooses to see it; “There’s too much to learn! ” can be either an encouraging chant or a cry for help. Perhaps, in my journey, humility will become the first great step of every new week and curiosity the following one to begin a new path; here’s for week 6 🤠!</p><figure><img alt="Tom Hardy giving thumbs up approving the message above. Ready for week 6." src="https://cdn-images-1.medium.com/max/1024/1*DyO_aEZ5RRiw44SyiN-4qw.jpeg" /><figcaption>Tom Hardy giving thumbs up approving the message above. Ready for week 6.</figcaption></figure><p>-Francisco G. P. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=927650cd3325" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weekly Blog 2]]></title>
            <link>https://medium.com/@francisco.gonzalez_51776/weekly-blog-2-6499f6defe2e?source=rss-c0dbaec2530e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6499f6defe2e</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[intern]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Francisco González Preciado]]></dc:creator>
            <pubDate>Sun, 17 Nov 2024 19:52:43 GMT</pubDate>
            <atom:updated>2024-12-15T05:40:31.095Z</atom:updated>
            <content:encoded><![CDATA[<h4>Spark Week 4</h4><p>On our fourth week… We were presented with the first individual project; Breakable Toy I; sounds amazing 🙂‍↕️. Through the email’s first reading the task ahead was honestly daunting to me or overwhelming to say the least. I had to think of something to do and how to effectively approach the situation in front of me. Lots of thoughts and ideas came to me 🙃, some more pleasant than others.</p><p>I was “simply” supposed to deal with a rather easy project, a to-do list 📝. I believe that the requirements and parts of the problem where common for those who have been presented with similar scenarios. This wasn’t the case for me, it was indeed the first time that I had to deal with with easily more than 80% of what was before me 😅. Front-end section was the most easily digestively part, not so new concepts, Back-end, requirements, and its technology was a whole other story. This was definitely going to be a whole new experience 😮‍💨.</p><p>During the first day the whole project was easily becoming a pile of different types of stress 🧐. There were also specific moments of excitement and curiosity given the opportunity of trying something so new, at least for me 🤓. This last part can pretty much sum up the whole experience during this first week. It has been a true rollercoaster of emotions, expectations, and realities. It’s so intriguing and scary at the same time that’s almost impossible to not come back to it 🤯.</p><p>The most repeated advice that I received this first week was to divide the issue. “Divide and Conquer” 🗡️ as plenty algorithms tend to work, and then take a look at each individual piece remaining, to this I must add my own twist… I have barely known, let alone apply, many of the technologies to use, so in my specific position it was more of a “Divide, Conquer,… and Breathe” (constantly) 😆. I analyzed the options, calculated the time needed for the possible chocies available, and then made my decisions. It’s always encouraging to know that people have my back and that I‘m surrounded by family and friend that want to see me succeed 🫂.</p><p>It’s easily been one of the more thought demanding weeks I can remember in the last year. Key factor to mention about these types of topics is that most of the time it’s about it; time ⏳. I won’t try and call this experience a walk through a park, not at all, but what I’m focusing on is in the background of everything that I’m going through. Things will get harder and so I will get better, it’s about improving and, most importantly, getting to know what I don’t know. I have questioned myself about how all of these was a good decision and even if I should carry on and all I can say now is that despite my doubts, learning curves, and imposter syndrome I’m still writing my weekly blog; here’s for week 5 🤠!</p><figure><img alt="Arnold Schwarzenegger giving thumbs up approving the message above. Ready for week 5." src="https://cdn-images-1.medium.com/max/1024/1*C5dg6pa7l-FHnGGgZDnzdA.jpeg" /><figcaption>Arnold Schwarzenegger giving thumbs up approving the message above. Ready for week 5.</figcaption></figure><p>-Francisco G. P. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6499f6defe2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weekly Blog 1]]></title>
            <link>https://medium.com/@francisco.gonzalez_51776/weekly-blog-1-1c1dc6ccf1ae?source=rss-c0dbaec2530e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c1dc6ccf1ae</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[intern]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[blog]]></category>
            <dc:creator><![CDATA[Francisco González Preciado]]></dc:creator>
            <pubDate>Mon, 11 Nov 2024 04:58:08 GMT</pubDate>
            <atom:updated>2024-12-15T05:39:52.318Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Spark Week 3</strong></h4><p>On our third week… We had to face our first coding challenges in teams and individual form and it was pretty educational 😅. At the same time we had the opportunity to meet more people in the organization, as well as lots and lots of new information. Finally, to wrap all things up, we finally had our mentors assigned; that’s what I consider is my week’s highlight 🤓. All in all, there were many new things, problems, experiences, and people, and it was awesome!</p><p>The problems and coding made me realize of one of the best parts of Spark which is the people around us, either working with us or not 👨‍💻. It’s always great to meet new people, although it’s even better when you get to meet great people. With each day that passes there are less communication barriers between us and a real sense of confidence is growing, enabling to ask, doubt, respond, and chat freely. I’ve learned (the hard way and several times 🙃) that it tends to be burdensome to reach for help, but it’s even worse than you can imagine not doing so 🙂‍↕️. That could easily be one of this week’s teachings.</p><p>The act of meeting new people can be as intentional as it can be random, both of them add to the whole experience ☝️. Through the different courses and calls we chatted with people we already knew and also several others that we didn’t. It has been amazing to see how everybody involved in Encora adds a little bit of their own essence into the Spark’s mix ⚡️. It’s at this point, when you interact with them that you get an actual glimpse of what lies ahead and what’s there to improve. There’s always something to make better, boost or correct, all of these becomes a richer experience when you with which people to surround with 🤝.</p><p>In of the week’s calls we got a little time to get to know all the mentors that are going to be involved with batch 2024F, we introduce ourselves and got to know a little bit of each other. This last Thursday our mentors were assigned and since that moment on we were able to make contact with them. After some technical and time inconveniences 😅 we got into a call and started talking about our experience in tech, programming, personal interests, and the road ahead. She had a really engaging talk and really showed interest in knowing what my current path is and where I would like to go from now on 🤔. Her experience and she willing to listen to my questions and doubts was reassuring and I’m confident that this will be of great help for both of us 🤟.</p><p>It’s been an important week and something that has resonated with me is that is best to solve a problem through its smallest component, then augment complexity; whatever this type of issue is. I have to catch on and learn how to learn in a more efficient way, also, a little bit more of acknowledgement hasn’t harmed anybody 🙂‍↕️. I’m grateful for the new people I’ve known along the way at, barely, the third week of Spark, even more excited for those I’ve yet to meet. Considering my background there have been some confusing details to overcome by now, but nothing that some patience, reading, and asking can’t resolve. So, all things considered, this was yet another interesting week that serve as a guide for the journey before me and the skills I need to work on; here’s for week 4 🤠!</p><figure><img alt="Ryan Gosling giving thumbs up approving the message above. Ready for week 4." src="https://cdn-images-1.medium.com/max/1024/1*yFUGJfdU6qmQAhPmdkQs2w.jpeg" /><figcaption>Ryan Gosling giving thumbs up approving the message above. Ready for week 4.</figcaption></figure><p>-Francisco G. P. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c1dc6ccf1ae" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>