<?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 Harold Serrano on Medium]]></title>
        <description><![CDATA[Stories by Harold Serrano on Medium]]></description>
        <link>https://medium.com/@haroldserrano?source=rss-97ff40404202------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3TBFLtfil9fJyryujFW0YQ@2x.jpeg</url>
            <title>Stories by Harold Serrano on Medium</title>
            <link>https://medium.com/@haroldserrano?source=rss-97ff40404202------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 05:38:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@haroldserrano/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[The art of Game Engine Development]]></title>
            <link>https://medium.com/@haroldserrano/the-art-of-game-engine-development-709703b87ec2?source=rss-97ff40404202------2</link>
            <guid isPermaLink="false">https://medium.com/p/709703b87ec2</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[game-engine]]></category>
            <dc:creator><![CDATA[Harold Serrano]]></dc:creator>
            <pubDate>Mon, 24 Dec 2018 14:45:25 GMT</pubDate>
            <atom:updated>2018-12-24T14:45:25.824Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve written several articles explaining how a game engine works. However, I feel that I left out an important concept.</p><p>Over the years, my view on Game Engine development has evolved. It has changed from “<em>This is how you develop a game engine</em>” to “<em>There is no one way to develop a game engine.</em>”</p><p>When I started, I spent hundreds and hundreds of hours pouring over technical books; learning, deciphering code snippets and trying to implement the same ideas I learned on my game engine.</p><p>There is nothing wrong with the approach mentioned above. But over the years, I realized that Game Engine development is not only science, but it is also an ART.</p><p>There was a point in the development of the engine when I stopped treating the implementations provided in technical books as “Gospel.” Instead, I would make an effort to truly understand the “concept” and then go on and implement it my way.</p><p>When I did this, I started to fall in love with Game Engine Development. That was the moment that I felt that I was genuinely doing Engineering.</p><p>To develop a game engine, focus on understanding the primary role of each component, but implement the internals of each component, not as mentioned in a book, but as YOU think is the best way.</p><p>In other words, let your creativity flow through your game engine. Game Engine Development is science mixed with “technical” art.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=709703b87ec2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Psychological trick to help you develop a Game Engine]]></title>
            <link>https://medium.com/@haroldserrano/a-psychological-trick-to-help-you-develop-a-game-engine-17fd6c0de9d8?source=rss-97ff40404202------2</link>
            <guid isPermaLink="false">https://medium.com/p/17fd6c0de9d8</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[game-engine]]></category>
            <dc:creator><![CDATA[Harold Serrano]]></dc:creator>
            <pubDate>Mon, 24 Dec 2018 14:40:04 GMT</pubDate>
            <atom:updated>2018-12-24T14:40:04.045Z</atom:updated>
            <content:encoded><![CDATA[<p>Is going to be almost six years since I decided to develop a game engine. When I started, I knew that it was a crazy idea, and many people thought it too. But looking back, the craziness was not related to the technical complexity, but in the psychological battle that I had to fight with myself.</p><p>Throughout the development of the game engine, the desires of giving up was a constant thought. There was a period that I wanted to give up every single day. The constant whisper of “Just Give Up” was always present. And I did give up. I quit for about four months. It was just too much to bear.</p><p>But I came back to it. After my sabbatical, I started wondering “What would it feel, if I didn’t give up,” and “How would the engine look like in a year from now.” The excitement of working on the engine again was slowly growing. But there was something that had an impact on my psychology.</p><p>Since the beginning of the development, I documented the progress of the engine through images and videos. One night, I started watching these videos. I watched all the small progress I’ve made and the slow evolution of the engine. Seeing with my eyes how far I’ve come, had a psychological impact on me. It gave me the energy to continue with my crazy decision to develop a game engine.</p><p>Here is a video of the evolution of the Untold Engine, from its inception five years ago to today.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F304604290%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F304604290&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F743865214_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/dd25deebc9067996513029403f18821b/href">https://medium.com/media/dd25deebc9067996513029403f18821b/href</a></iframe><p>Documenting my work have been a tremendous psychological tool. It has helped me keep going, and I hope it will continue doing so.</p><p>If you are embarking on a complex project, document your work through images and videos to remind YOU how far you’ve come when you are about to give up.</p><p>Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17fd6c0de9d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Break things, learn and repeat]]></title>
            <link>https://medium.com/@haroldserrano/break-things-learn-and-repeat-702086ea661a?source=rss-97ff40404202------2</link>
            <guid isPermaLink="false">https://medium.com/p/702086ea661a</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[indiedev]]></category>
            <dc:creator><![CDATA[Harold Serrano]]></dc:creator>
            <pubDate>Wed, 07 Jun 2017 03:49:53 GMT</pubDate>
            <atom:updated>2017-06-07T03:49:53.203Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally published on </em><a href="https://www.haroldserrano.com/blog/break-things-learn-and-repeat"><em>haroldserrano.com</em></a><em> on Sept 28 ,2016</em></p><p>When I was growing up in Ecuador, my mom gave me a soccer ball as a gift. Being Latino, a soccer ball was the best gift ever. Along with the soccer ball, she also gave me a box of old, dirty, used Legos. I realized I wasn’t going to make it as a soccer player. So I decided to spend my days building cars, boats and airplanes out of legos. Legos kept me entertained. They allowed me to be creative and somehow sparked my love for making things.</p><p>When we moved to the US, I asked my mom to buy me a Nintendo. She refused and instead bought me an electronic kit that she found at Radio Shack back in the 1990s. I think you may remember them.</p><figure><img alt="Electronic kit of the 1990s" src="https://cdn-images-1.medium.com/proxy/1*BRhWFZz6d4PrQnLl8zOktQ.jpeg" /><figcaption>Electronic kit of the 1990s</figcaption></figure><p>I distinctly remember her tossing the kit onto my bed and saying: “Instead of playing games, learn to make one.” The kit came with a manual and instructions for several projects. Some of the projects were how to make a simple radio, timer, etc. Just like Legos, they kept me entertained and my desire to make things grew more and more.</p><p>Unfortunately, when I went to college, the burning desire to make things flame out. I don’t know what happened, but the engineering lectures and labs somehow killed my love to create. College burnt me out to the point that I didn’t care anymore. I just wanted it to be over.</p><p>A couple of years passed by until my desires to create came back. I ended up buying a game development book. The curiosity to know how games are developed kept me reading and coding till late at night. Interestingly, I had barely played video games during my youth, but I have always been fascinated with computer graphics effects.</p><p>I became so interested in game development that my desires to learn more, led me to experiment more, which led me to break things, which led me to learn even more. The constant experimentation fueled my love for engineering all over again. And I realized that college didn’t kill my passion for engineering. What killed it was the lack of time required to learn through experimentation. College was too rushed; midterms today, twenty-page paper due tomorrow, etc.</p><p>It was then when I realized that the beauty of engineering lies within the “Aha” moments that are born during discovery and experimentation. It is from that particular toy you got, the one you took apart and glued back together; that lit your desire to create, to make.</p><p>If you have lost the desire to create, I hope you find it soon. If you are a new developer, experiment and challenge the status-quo. Ask yourself “What would happen if ….?” and don’t be afraid to break things. Because you don’t become an engineer, a developer, a maker, by just solving equations or following a tutorial. To become one, you need to break things, learn and repeat.</p><p><em>Originally published on </em><a href="https://www.haroldserrano.com/blog/break-things-learn-and-repeat"><em>haroldserrano.com</em></a><em> on Sept 28 ,2016</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=702086ea661a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Become a documentarian of your work]]></title>
            <link>https://medium.com/@haroldserrano/become-a-documentarian-of-your-work-691c383b964b?source=rss-97ff40404202------2</link>
            <guid isPermaLink="false">https://medium.com/p/691c383b964b</guid>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[Harold Serrano]]></dc:creator>
            <pubDate>Wed, 07 Jun 2017 02:06:21 GMT</pubDate>
            <atom:updated>2017-06-07T02:06:21.454Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally published on </em><a href="https://www.haroldserrano.com/blog/the-power-of-your-game-dev-story"><em>haroldserrano.com</em></a><em> on June 6 ,2017</em></p><p>I enjoy reading rags to riches stories. They are powerful, inspirational and they resonate with our emotions. Humble beginnings connect us. They are a reminder that no matter who you are, or how broke you are, you do have a chance to succeed.</p><figure><img alt="Game Engine Beginnings. Circa 2013: Implementing the rendering engine." src="https://cdn-images-1.medium.com/proxy/1*_pOGljP1vBMLcqtBOtUIFw.gif" /><figcaption>Game Engine Beginnings. Circa 2013: Implementing the rendering engine.</figcaption></figure><p>Now and then, I search on Wikipedia the stories of successful companies. I look for any photos that were taken before they made it big. I enjoy reading their “About” page and get a glimpse of how it all started.</p><p>Success is not glamorous as the media sells it. In fact, It is a lot of time working in the dark. I know this fact first hand.</p><figure><img alt="Game Engine Beginnings. Circa 2013: Improving the rendering engine" src="https://cdn-images-1.medium.com/proxy/1*pSLrJYv9BCCuxKENhy6d5A.gif" /><figcaption>Game Engine Beginnings. Circa 2013: Improving the rendering engine</figcaption></figure><p>I worked over 15,000 hours in developing a 3D game engine. I would wake up at 5 am and work on the engine from 5am-7am before heading to work. I worked on it during my lunch break. And then again after work. And during the weekends, I would work on it for about 16 hours. I wanted to develop a 3D game engine so bad, that it became my life for about three years and a half.</p><figure><img alt="Game Engine Beginnings. March 2014: Improved the engine to render textures." src="https://cdn-images-1.medium.com/proxy/1*h3oYj7Qm7tR24esW0aKlig.gif" /><figcaption>Game Engine Beginnings. March 2014: Improved the engine to render textures.</figcaption></figure><p>Throughout this time, the thought of failure kept disturbing my peace. I kept thinking, what if I fail and have nothing to show? What if this is just a waste of time?</p><figure><img alt="Game Engine Beginnings. April 2015: Improved the shadows in the engine" src="https://cdn-images-1.medium.com/proxy/1*wgGTDgKNYkK2qnwUysdDhA.gif" /><figcaption>Game Engine Beginnings. April 2015: Improved the shadows in the engine</figcaption></figure><p>However, I found a way to combat it. I was inspired by <a href="http://austinkleon.com/show-your-work/">Austin Kleon</a> to document the humble beginnings of my game engine. At first, I was against this idea. In my mind, nobody would want to see the progress of my game engine. But Austin made me realize that it is the process, not the end product, that makes our work exciting and inspiring.</p><figure><img alt="Game Engine Beginnings. July 2016: Collision Detection System implemented." src="https://cdn-images-1.medium.com/proxy/1*IFoZTt5A0zzykbu9cK4CJw.gif" /><figcaption>Game Engine Beginnings. July 2016: Collision Detection System implemented.</figcaption></figure><p>I want to let you know that you are not alone in your struggles. It is OK if your game is not glamorous yet. It is OK if your indie game studio is your room. That is OK if your game only sold ten copies. And there is something powerful about your struggles.</p><figure><img alt="Game Engine Beginnings. Sept 2016: Improved animation and shadows effects." src="https://cdn-images-1.medium.com/proxy/1*XUkG-AxZjMpIlrmgp7Gq5g.gif" /><figcaption>Game Engine Beginnings. Sept 2016: Improved animation and shadows effects.</figcaption></figure><p>The finish line of success does not inspire people. It is the road you took to achieve it. It is your suffering, the pain, the obstacles that make your story interesting. It is what gives others strengths to go beyond they thought possible. It is your underdog story that connects us as human beings and inspires us.</p><figure><img alt="Game Engine Beginnings. Aug 2016: Game engine first demo." src="https://cdn-images-1.medium.com/proxy/1*qeT4Jgdb9uFrKdeM3NoM0w.gif" /><figcaption>Game Engine Beginnings. Aug 2016: Game engine first demo.</figcaption></figure><p>So document your humble beginnings. Share photos and videos of your work in progress. Take screenshots of your game. Share pictures of your indie studio; even if it is your room. Write about your struggles and how you overcame them.</p><figure><img alt="Game Engine Beginnings. Dec 2016: Added particle system to the engine." src="https://cdn-images-1.medium.com/proxy/1*bUYfq_Ew0-Xyaih_DXR5Yw.gif" /><figcaption>Game Engine Beginnings. Dec 2016: Added particle system to the engine.</figcaption></figure><p>Don’t worry if your game characters look like crap. Don’t worry if your game mechanics suck. Don’t worry if there are plenty of bugs. It is all OK. As indie game developers, we can all relate and do understand that it is a work in progress.</p><figure><img alt="Game Engine Beginnings. Dec 2016: Tested the engine collision detection capabilities." src="https://cdn-images-1.medium.com/proxy/1*7BrpE5kv_I5aJMM8Di63_A.gif" /><figcaption>Game Engine Beginnings. Dec 2016: Tested the engine collision detection capabilities.</figcaption></figure><p>A final product is not interesting. It is not inspiring. What is, is your story.</p><p>So what is your story?</p><p><em>Originally published on </em><a href="https://www.haroldserrano.com/blog/the-power-of-your-game-dev-story"><em>haroldserrano.com</em></a><em> on June 6 ,2017</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=691c383b964b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why is a non-gamer developing a game engine?]]></title>
            <link>https://medium.com/@haroldserrano/why-is-a-non-gamer-developing-a-game-engine-f77821ce22b1?source=rss-97ff40404202------2</link>
            <guid isPermaLink="false">https://medium.com/p/f77821ce22b1</guid>
            <category><![CDATA[gamedev]]></category>
            <category><![CDATA[indiedev]]></category>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[Harold Serrano]]></dc:creator>
            <pubDate>Thu, 01 Jun 2017 05:42:06 GMT</pubDate>
            <atom:updated>2017-06-01T05:42:06.129Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally published on </em><a href="https://medium.com/www.haroldserrano.com"><em>haroldserrano.com</em></a><em> on Sept 21 ,2016</em></p><p>I don’t play video games. I don’t even own a game console. I have played Atari games less than five times. And for what I can remember, I only played Mario Bros less than ten times. Yet I’m working in developing a game engine.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F179755900&amp;url=https%3A%2F%2Fvimeo.com%2F179755900&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F587752169_640.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="692" height="540" frameborder="0" scrolling="no"><a href="https://medium.com/media/ecde19db3ab406eafb39048f178b285a/href">https://medium.com/media/ecde19db3ab406eafb39048f178b285a/href</a></iframe><p>I know what you are thinking. “How in the world could you be developing a game engine if You don’t even play video games?”. Trust me. I ask myself this question often.</p><p>Many times I feel like an impostor. Like attending a party, I never was invited to. But before I get kicked out of the party, let me explain myself.</p><p>I’m good at math. I love programming. I love computer graphics, and I love challenging problems. I have never been a gamer. I could care less for gameplay, game story, etc. What gets my curiosity are the graphical effects in a game. For example, have you ever wondered how shadows are produced? Or how characters collide with each other? Have you ever wondered how the engineers take full control of pixels on a screen and simulate realistic physical effects?</p><p>Those were the questions I asked myself whenever I played a video game. And the answers to these questions got me interested in computer graphics.</p><p>I taught myself OpenGL. I spent hundreds and hundreds of hours trying to understand computer graphics. Eventually, I became good at it. However, that hunger to be the master of pixels on a screen was not satisfied. I wanted to do more with computer graphics. I wanted to do something beyond my intellectual abilities. Something that I knew I was not qualified to do. Something that I knew with 99% certainty that I was going to fail.</p><p>Why did I decide to develop a game engine? I don’t know. It just happened. I woke up and without knowing what a game engine is or does, I decided to develop one. I jumped into developing something I didn’t understand.</p><p>I read a lot and understood nothing. Programmed a lot and threw everything I coded into the trash. My first couple of attempts were complete failures. But with every failure, I was more intrigued. I couldn’t throw the towel. And 3 1/2 years later, <a href="http://www.haroldserrano.com/blog/showcasing-the-first-game-engine-demo">I finally was able to get it right</a>.</p><p>In the end, I have felt in love with game engine development. No, I still don’t play games. I leave the gameplay and the game story for gamers. I’m more interested in creating a tool that helps game developers create games faster and easier. I’m more interested in coding 1000 lines of code so that developers can enable collisions in a game with one line of code.</p><p>So why is a non-gamer developing a game engine? Because you need someone like me, a geek who loves mathematics, programming and computer graphics, to develop tools game developers need to create games you enjoy.</p><p><strong><em>About Me</em></strong></p><p><em>Harold Serrano writes at haroldserrano.com on game engine development. For the best articles on programming, computer graphics and game development </em><a href="https://www.haroldserrano.com/subscription"><em>sign up for my newsletter</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f77821ce22b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On this Mac, I developed a Game Engine]]></title>
            <link>https://medium.com/@haroldserrano/on-this-mac-i-developed-a-game-engine-b5c369c6229f?source=rss-97ff40404202------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5c369c6229f</guid>
            <category><![CDATA[indiedev]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[gamedev]]></category>
            <dc:creator><![CDATA[Harold Serrano]]></dc:creator>
            <pubDate>Mon, 29 May 2017 20:56:52 GMT</pubDate>
            <atom:updated>2017-05-29T20:56:52.699Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally published on </em><a href="https://www.haroldserrano.com/blog/on-this-mac-i-developed-a-game-engine"><em>haroldserrano.com</em></a><em> on Nov 10,2016</em></p><p>Two weeks ago, my Mac stopped working. I took it to the Apple store so they can diagnose the problem and unfortunately, the hard drive was no longer usable.</p><p>I lost all of my data and ended up buying a new Mac. Yes, I could have bought a new hard drive, but I’ve had this Mac for over six years, and it was time to get a new one.</p><figure><img alt="My Mac with a blinking question mark after a reboot" src="https://cdn-images-1.medium.com/proxy/1*Cx9GGgDBywiZvZodgS23Og.jpeg" /><figcaption>My Mac with a blinking question mark after a reboot</figcaption></figure><p>When the Apple technicians told me that my Mac was no longer usable, I got sad. Not because I lost my data, but because I’ve had built a relationship with my laptop.</p><p>No, I am not weird. Let me explain.</p><p>Developing a Game Engine is hard. It takes a lot of dedication, persistence, and motivation. It took me over three years to develop a game engine. I had worked on it before heading to work, during lunch, after work and during the weekends. I can say that I worked over 15,330 hours on it.</p><p>Game Engine Development is not that hard technically-wise. It is hard psychologically-wise. You can spend three or four months of work only to implement a simple feature. You can spend two to three months trying to implement an algorithm and fail. I spent almost a whole year trying to get the Collision Detection System to work.</p><p>To be honest, I wanted to give up every single day of development. I was mentally tired. The enthusiasm that I had when I started development was gone. There was no desire in my heart to finish the game engine. I was spiritually tired.</p><p>And throughout all this time, my Mac was with me. It witness all the hours I put on it. It witnesses me dancing when I successfully implemented the first beta version of the engine:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F126003626&amp;url=https%3A%2F%2Fvimeo.com%2F126003626&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F516299034_640.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="768" height="598" frameborder="0" scrolling="no"><a href="https://medium.com/media/a86712982a518cad84f001094641c38e/href">https://medium.com/media/a86712982a518cad84f001094641c38e/href</a></iframe><p>It heard me swear in Spanish when the engine would crash. It saw me stared at it for hours pondering the idea of giving up. And it saw me when I screamed and jumped when I implemented the basic framework of the engine (Beta version v0.0.2):</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F176011048&amp;url=https%3A%2F%2Fvimeo.com%2F176011048&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F583209918_640.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="694" height="540" frameborder="0" scrolling="no"><a href="https://medium.com/media/e04ab63e8971feb59f8ded3803d83179/href">https://medium.com/media/e04ab63e8971feb59f8ded3803d83179/href</a></iframe><p>It saw the game engine first demo:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F179755900&amp;url=https%3A%2F%2Fvimeo.com%2F179755900&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F587752169_640.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="692" height="540" frameborder="0" scrolling="no"><a href="https://medium.com/media/ecde19db3ab406eafb39048f178b285a/href">https://medium.com/media/ecde19db3ab406eafb39048f178b285a/href</a></iframe><p>The night before it died, I was preparing a demo to showcase version v0.0.3 of the engine. It was going to showcase the final piece of the engine framework. But my Mac never saw this demo working:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F189583933&amp;url=https%3A%2F%2Fvimeo.com%2F189583933&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F599954183_640.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="664" height="394" frameborder="0" scrolling="no"><a href="https://medium.com/media/735924ba82c6889c752c662b19c69524/href">https://medium.com/media/735924ba82c6889c752c662b19c69524/href</a></iframe><p>The next morning when I tried to turn on the computer, a folder with a blinking question mark showed up on my screen. I tried rebooting the computer, but it was useless.</p><p>I got sad when I realized my Mac was no longer usable. It may sound weird; I agree with you. But I am not sad because it no longer works. I am sad because, through this Mac, I learned to persist.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*Lmi7MmQadWR0Kuqu0Nvkbw.jpeg" /></figure><p>Thanks for reading.</p><p><em>Originally published on </em><a href="https://www.haroldserrano.com/blog/on-this-mac-i-developed-a-game-engine"><em>haroldserrano.com</em></a><em> on Nov 10,2016</em></p><p><strong><em>About Me</em></strong></p><p><em>Harold Serrano writes at </em><a href="http://www.haroldserrano.com/"><em>haroldserrano.com</em></a><em> on game engine development. For the best articles on programming, computer graphics and game development </em><a href="https://www.haroldserrano.com/subscription"><em>sign up for my newsletter</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5c369c6229f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Showcasing the game engine first demo]]></title>
            <link>https://medium.com/@haroldserrano/showcasing-the-game-engine-first-demo-4ec54613e81b?source=rss-97ff40404202------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ec54613e81b</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Harold Serrano]]></dc:creator>
            <pubDate>Mon, 22 Aug 2016 14:51:55 GMT</pubDate>
            <atom:updated>2016-08-22T14:51:55.880Z</atom:updated>
            <content:encoded><![CDATA[<p>About a month ago I finished implementing the core framework for the game engine. My goal for this month was to create a small demo which would showcase what the engine can do and most importantly, to find code bugs in the engine. I have to admit; I found more bugs than I would have liked. However, I was able to fix 90% of them.</p><p>While creating the demo, I took inspiration from these images:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/1*FcJ3edvp0x0xDiAiaIl8Qw.png" /><figcaption><a href="http://cgi.tutsplus.com/tutorials/secrets-to-creating-low-poly-illustrations-in-blender--cg-31770">Image Credit</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yaQ7WjUvLFIxdIIeV4UEAg.png" /><figcaption><a href="http://www.manuelgraphics.com/">Image Credit</a></figcaption></figure><p>I decided to create similar 3D models using Blender. I combined the scenery from each image and imported them in the engine as shown in the video below.</p><p>The demo is very simple. It starts off with the rocket bouncing up and down colliding with the ground. The camera is set to follow this bouncing movement. As I press the button, the rocket starts flying upwards until it collides with several asteroids. After each collision, the rocket &amp; asteroid respond by moving in opposite directions. After several collisions, gravity takes over the rocket and forces it to come down to the ground. The rocket bounces several times with the ground as it collides.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F179755900&amp;url=https%3A%2F%2Fvimeo.com%2F179755900&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F587752169_640.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="692" height="540" frameborder="0" scrolling="no"><a href="https://medium.com/media/ecde19db3ab406eafb39048f178b285a/href">https://medium.com/media/ecde19db3ab406eafb39048f178b285a/href</a></iframe><h3><strong>More details about the engine</strong></h3><p>The purpose of this first demo was to showcase the physics engine, especially the Collision Detection System, Shadows, Individual material Rendering, Camera movement and Digital Asset Loader.</p><h4>Digital Asset Loader</h4><p>The engine can read 3D models created in Blender. To do so, I wrote a Python script which exports all the attributes of a 3D model to a file. The engine parses the data in this file and loads the attribute data into the GPU of the iOS device. As of now, the python script outputs the data to the terminal as is shown below.</p><h4>Individual Material Rendering</h4><p>I am not an artist, and I can’t design beautiful hand-painted textures. Moreover, I wanted to create a game engine that would render multiple materials colors and not need to attach a texture to a model (if I don’t want to). So I made sure that the engine can render multiple materials per 3D models. For example, the engine renders the mountain with all three different materials (green, dark purple and white).</p><h4>Shadows</h4><p>Having Shadows in the engine was a must. It took me a while to get it right, especially since I was forced to modify the camera and light space matrices (I had them backward in the beginning.) Shadowing is done using the Shadow Mapping technique.</p><h4>Collision Detection System</h4><p>By far, the most complicated part of a game engine. Developing a collision detection system takes a lot of time and a lot of redos. During this demo, I ended up modifying the Convex-Hull algorithm needed for collision detection. As you can see from the video, the engine can detect collision between any convex objects and it computes the correct collision response.</p><h4>What’s next?</h4><p>I’m going to develop more demos with the sole purpose to find more code bugs. This is going to be my focus until the end of the year. I hope that by the end of December I have decent beta version.</p><p>Learn more about me at <a href="http://www.haroldserrano.com/">haroldserrano.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ec54613e81b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I finally finished the basic framework of my Game Engine]]></title>
            <link>https://medium.com/@haroldserrano/i-finally-finished-the-basic-framework-of-my-game-engine-766e83cd50ba?source=rss-97ff40404202------2</link>
            <guid isPermaLink="false">https://medium.com/p/766e83cd50ba</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Harold Serrano]]></dc:creator>
            <pubDate>Sun, 24 Jul 2016 19:07:59 GMT</pubDate>
            <atom:updated>2016-07-25T03:56:18.872Z</atom:updated>
            <content:encoded><![CDATA[<p>On July 21, 2016, around 2:00 am, I did it!!! I finally finished the basic framework of my game engine. It took <strong>three years</strong>, about <strong>1,095 days</strong>, approximately <strong>15,330 hours</strong> of work. It demanded that I wake up earlier than most people (5:00 am), so I could squeeze in about two hours of coding before heading to work. It asked that I spent my lunch hours coding at Coffee Bean instead of enjoying lunch with colleagues. Instead of relaxing after a long day of work, it forced me to code until the late hours of the night (approx. 7:00 pm-1:00 am). And it made me say goodbye to my weekends. Weekends that I spent coding in my room or at Starbucks instead of enjoying life.</p><p>But I did it!!! And I’m damn proud of myself.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F126003626&amp;url=https%3A%2F%2Fvimeo.com%2F126003626&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F516299034_640.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="768" height="598" frameborder="0" scrolling="no"><a href="https://medium.com/media/a86712982a518cad84f001094641c38e/href">https://medium.com/media/a86712982a518cad84f001094641c38e/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F176011048&amp;url=https%3A%2F%2Fvimeo.com%2F176011048&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F583209918_640.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="694" height="540" frameborder="0" scrolling="no"><a href="https://medium.com/media/e04ab63e8971feb59f8ded3803d83179/href">https://medium.com/media/e04ab63e8971feb59f8ded3803d83179/href</a></iframe><p>And NO! I am not proud because it proved that I am an amazing engineer. That ego left my soul a long time ago. I am proud because <strong>I DID NOT GIVE UP</strong>. I am proud because I persevered every day. I am proud because I was able to control my mind and tell it to SHUT UP when it was telling me to throw the towel.</p><p>I started this project back in June 2013 because I wanted to do something beyond my intellectual capabilities. Instead, I discovered that my failures in life were related to never having practiced Not-Giving-Up.</p><p>Most of us are good at giving up because that is all that we have practiced. We start the year with the resolution to lose weight, but when it becomes tough, we give up. We start hopeful with a new business venture, but when things are going sour, we give up. We start motivated to learn a new skill, but when it is taking longer than planned, we give up. All that we have practiced, all that we know is HOW TO GIVE UP. And there are no gurus, no self-help books, no quotes that can teach you how NOT to give up but yourself.</p><p>This project improved my math, coding and engineering skills tenfold. However, I could care less. Because all the knowledge, imagination and talent is worth nothing if you have the habit of giving up. This project instilled in me the habit of NOT giving up, and that is what I’m most proud of.</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fcdn.knightlab.com%2Flibs%2Ftimeline3%2Flatest%2Fembed%2Findex.html%3Fsource%3D187JkBNke-7zeMPdivSDCsoE7o6KjibTPZDdQ-mJ6Km4%26font%3DDefault%26lang%3Den%26start_at_end%3Dtrue%26timenav_position%3Dtop%26initial_zoom%3D2%26height%3D650&amp;src=https%3A%2F%2Fcdn.knightlab.com%2Flibs%2Ftimeline3%2Flatest%2Fembed%2Findex.html%3Fsource%3D187JkBNke-7zeMPdivSDCsoE7o6KjibTPZDdQ-mJ6Km4%26font%3DDefault%26lang%3Den%26start_at_end%3Dtrue%26timenav_position%3Dtop%26initial_zoom%3D2%26height%3D650&amp;type=text%2Fhtml&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;schema=knightlab" width="700" height="650" frameborder="0" scrolling="no"><a href="https://medium.com/media/c789181c0e852bfb7fb80a6c37be67ac/href">https://medium.com/media/c789181c0e852bfb7fb80a6c37be67ac/href</a></iframe><p><strong>So what is next?</strong><br>I will do several demos to showcase the features of the engine. I will keep working on the engine and hopefully will have a beta version ready by the end of the year.</p><p><strong>Almost forgot</strong><br>To all of those individuals that throughout my life told me that I was not good enough, smart enough or capable enough, you were right! I am not good enough. I am great enough!</p><p><strong>About the author:</strong></p><p>My name is Harold Serrano. I enjoy teaching what I learn during the week. Check out my website at <a href="http://www.haroldserrano.com/">www.haroldserrano.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=766e83cd50ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Make it a habit to code every day]]></title>
            <link>https://medium.com/@haroldserrano/why-you-should-code-daily-c227d481386?source=rss-97ff40404202------2</link>
            <guid isPermaLink="false">https://medium.com/p/c227d481386</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Harold Serrano]]></dc:creator>
            <pubDate>Wed, 01 Jun 2016 03:16:41 GMT</pubDate>
            <atom:updated>2016-06-01T03:32:13.253Z</atom:updated>
            <content:encoded><![CDATA[<p>You may be an indie developer with a full-time job whose only chance to code is during lunch, after work or on weekends. Even though you may have limited time to focus on coding, you should strive to code daily.</p><h4>Don’t code a lot. But do code often</h4><p>Writers and coders share similar struggles. For a writer to become a master at his craft, it is recommended to write 1,000 words daily.</p><p>For coders, it is absurd to follow the same recipe. Instead of focusing on how many lines of code you will write daily, focus on coding small tasks daily.</p><p>For example, strive to code just one function or method per day. During the weekends aim to code one feature of the game, but keep it realistic.</p><p>The point is to <strong>Not to code a lot, But to code often</strong>. Focus on building a coding habit first.</p><h4>Have a To-Do list</h4><p>A tip to keep you going is to have a To-Do list. Every morning, list your coding task for the day. The task should be small and doable within an hour or less. When you have completed your coding assignment, check off the task. Believe it or not, checking off the task tricks your mind into thinking that it was productive; even if the work accomplished was small.</p><p>The goal is not to code only one day of the week for 5 hours but to code 1 hour every day of the week. Habits are made by showing up every day.</p><p>This article was initially published in <a href="http://www.haroldserrano.com/">haroldserrano.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c227d481386" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why your knowledge is only worth 50%]]></title>
            <link>https://medium.com/@haroldserrano/why-your-knowledge-is-only-worth-50-bd166aa6f157?source=rss-97ff40404202------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd166aa6f157</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Harold Serrano]]></dc:creator>
            <pubDate>Tue, 31 May 2016 15:06:58 GMT</pubDate>
            <atom:updated>2016-05-31T15:06:58.160Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why your coding knowledge is only worth 50%</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*52h5OED2uCiJAxippZM5KA.jpeg" /><figcaption>Photo Credit: <a href="https://unsplash.com/@tirzavandijk">https://unsplash.com/@tirzavandijk</a></figcaption></figure><p>Yes, that is right. In this global economy, a diploma no longer sets you apart. Professionals in the US no longer compete with local experts but with international experts whose cost of living is lower than ours.</p><p>Don’t believe me?</p><p>Do a search on freelancer sites such as Upwork and you will see bids that can barely get you through a couple of days in the US. These international experts can outbid us anytime. They will gladly develop an application for $300 or less. The global economy has changed, and you must accept it.</p><p>The truth is this: Stating what you know is no longer enough. To compete, you must show what you know.</p><p>Let me explain what I mean,</p><h4>Show your work in progress</h4><p>I’m sure you have a side project. It may not be ready for showtime, but that should not stop you from sharing your struggles. When you share your Work-in-Progress, it puts you in a position as an expert. You may have the answer to a problem a company or a developer is currently struggling with. Who knows, they may ask for your help.</p><h4>Teach</h4><p>Setup a blog, focus on a topic and start teaching. Do it through posts, videos, etc. Teach us about Design Patterns, Data Structures, C++ or new programming languages like Swift. If you can, answer questions on Quora.</p><p>There is no better way to demonstrate what you know than by teaching it. It provides concrete proof to employers that you are an expert. It sets you apart from other candidates.</p><h4>Think like an artist</h4><p>What do all artist have in common? They all have a portfolio; they show their work. Call me nuts, but I think coders are artists. We make 0’s and 1’s do very impressive things. Set up a portfolio of your work. Collaborate to open source projects on Github or showcase your expertise on CodePen.</p><p>A diploma no longer sets you apart. What you know is only worth 50%, the other 50% is self-promotion.</p><p>So, go ahead, show us your code.</p><p>This article was originally published in <a href="http://www.haroldserrano.com/">haroldserrano.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd166aa6f157" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>