<?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 Jorge Tapia on Medium]]></title>
        <description><![CDATA[Stories by Jorge Tapia on Medium]]></description>
        <link>https://medium.com/@profezy?source=rss-e871e0257b33------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Yh2rs1-mXmgk9xQy8xtGDg.jpeg</url>
            <title>Stories by Jorge Tapia on Medium</title>
            <link>https://medium.com/@profezy?source=rss-e871e0257b33------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:17:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@profezy/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[Tips for New Streamers]]></title>
            <link>https://medium.com/@profezy/tips-for-new-streamers-53a5b06ddb80?source=rss-e871e0257b33------2</link>
            <guid isPermaLink="false">https://medium.com/p/53a5b06ddb80</guid>
            <category><![CDATA[halo]]></category>
            <category><![CDATA[twitch]]></category>
            <category><![CDATA[streaming]]></category>
            <category><![CDATA[call-of-duty]]></category>
            <category><![CDATA[esport]]></category>
            <dc:creator><![CDATA[Jorge Tapia]]></dc:creator>
            <pubDate>Fri, 04 Jan 2019 23:29:28 GMT</pubDate>
            <atom:updated>2024-10-08T08:51:47.978Z</atom:updated>
            <content:encoded><![CDATA[<h3>Tips for New Twitch Streamers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mjm2hBKuKft3sjoVaIGvtg.png" /><figcaption>SWAT Nation: The most positive and friendly Halo community there is.</figcaption></figure><p>I began live streaming in March 2018, which marked a turning point in my Halo 5 SWAT career as I started seeing real improvement and climbed to the Diamond tier. One of my best friends and SWAT mentors, <a href="https://twitch.tv/NapTimez">NapTimez</a>, inspired me to start streaming. If you enjoy top-tier Halo gameplay, I highly recommend visiting his channel and dropping a follow.</p><p>In the past few months, I’ve grown my channel from nothing to a little bit over 10,000 followers as of writing this. I’ve put time, passion, dedication, resources, and professionalism into my streams to reach this point. I still feel I’m in the early stages, but getting here hasn’t been easy.</p><p>I want to share what I’ve learned from my experience, both what worked and what to avoid. While I’m still growing my channel, I’ve noticed new streamers making some common mistakes that hold them back. Here’s what I’ve learned to help you on your journey:</p><h3>ESTABLISH YOUR BRAND</h3><p>Creating a recognizable brand is crucial for building an audience. You want to be memorable and stand out. Here are the steps I took to establish my brand:</p><ul><li><strong>Create a logo</strong>: This becomes your face within the community.</li><li><strong>Develop a custom color palette</strong>: Use this for all your graphical assets.</li><li><strong>Design custom streaming overlays and screens</strong> based on your logo and color palette.</li><li><strong>Create aesthetically pleasing panels</strong> to catch viewers’ attention.</li><li><strong>Design custom social media profile pictures and banners</strong> and use them consistently across all accounts.</li><li><strong>Be consistent</strong>: Use the same handle across all your social and gaming platforms so people can easily recognize you.</li><li><strong>Promote yourself on social media</strong> without spamming. Follow guidelines on how to do this effectively — there’s no one-size-fits-all, so tailor it to your style.</li></ul><p>Most importantly, if you can, invest in a professional team or designer to handle this. It shows you take your stream seriously. Alternatively, you can start with free-to-use designs, but keep in mind that many people use them, so they might not have the same impact as something customized just for you.</p><h3>HAVE THE RIGHT EQUIPMENT</h3><p>If you’re serious about streaming, you need the right equipment to produce high-quality content. Streaming from your console is a great feature, but it won’t be enough to take you to the next level. Here’s what I recommend investing in:</p><ul><li>A <strong>stable, wired internet connection</strong></li><li>A <strong>good PC or laptop</strong></li><li>A <strong>capture card</strong> (if you’re a console streamer or dual-pc)</li><li>A <strong>high-quality microphone</strong></li><li>A <strong>high-quality webcam</strong></li></ul><p>Additional tools like a Stream Deck, green screen, audio mixers, or professional lighting can further enhance your stream, but the essentials listed above are a must if you want to succeed.</p><h3>BE CONSISTENT</h3><p>Consistency is the key to success in streaming. Even if you have few or no viewers at first, keep going. Set a schedule and stick to it — this helps build your audience. Success takes time, so be patient and stay committed.</p><h3>BE PATIENT</h3><p>Growing a channel takes time, and rushing for quick success won’t help. Many streamers focus on hitting Affiliate status but forget that’s just the beginning. Building an audience takes time, trust, and reputation. You can’t buy loyalty or respect with giveaways or prizes. You have to earn it through consistent streaming and engagement with your viewers.</p><p>Be mindful of how you approach charity streams. If you’re doing a charity stream, make sure it’s genuine and that you’re raising money for the right reasons, not for personal gain. Charity streams should be conducted when you already have an established audience that will help you raise funds.</p><h3>BE POSITIVE</h3><p>People are drawn to positivity. No one enjoys watching extremely toxic behavior, whether it’s yelling at teammates or using foul language. A positive attitude can make a huge difference in how people perceive you. Even when you’re frustrated, keep your composure. If you’re known for positivity, your audience will forgive occasional slip-ups, but always apologize and return to your usual self.</p><p>Some of my best streams have been ones where I’ve lost ranks in Halo but still had a great time interacting with my audience. Positive vibes are everything, and your viewers will feel that.</p><h3>LEARN TO SAY NO</h3><p>As you grow, you’ll encounter people asking for shout-outs, hosts, or raids. Learn to say no when it doesn’t feel right. Your stream is about building your community, and you should be selective about who you support.</p><p>I have a strict no self-promotion policy on my channel, but that’s up to you. Protect the space you’ve worked hard to build, and only promote those you believe deserve it.</p><h3>CHERISH YOUR AUDIENCE</h3><p>Your audience is your most valuable asset. Treat them with respect and get to know them. Recognize your regular viewers and interact with them. Set up games, giveaways, or raffles, and use features like VIP badges to show appreciation for your loyal followers. They’re the key to your success.</p><h3>HAVE FUN</h3><p>Most importantly, have fun! Watching a streamer who genuinely enjoys what they’re doing is contagious. I invite you to check out my channel on Twitch, where everyone is welcome, and I play with viewers regardless of rank. It’s all about having a good time and building a positive community.</p><p>If you want to see some of the most positive FPS streams on Twitch, check out my channel at <a href="https://twitch.tv/SynapseIX">twitch.tv/SynapseIX</a> and hit that follow button! I stream daily starting at 10 p.m. EST. Also, be sure to check out <a href="https://swatnation.net/">SWAT Nation</a>, the friendliest and most positive Halo community around. We host monthly tournaments and fun SWAT events on my channel. See you on the battlefield! Much love! The Partner push is real now!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53a5b06ddb80" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[iOS: Setting Up a Basic Voice Processing I/O Audio Unit in Swift]]></title>
            <link>https://medium.com/@profezy/ios-setting-up-a-basic-voice-processing-i-o-audio-unit-in-swift-253b09c7d1b8?source=rss-e871e0257b33------2</link>
            <guid isPermaLink="false">https://medium.com/p/253b09c7d1b8</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[audio-unit]]></category>
            <category><![CDATA[audiotoolbox]]></category>
            <dc:creator><![CDATA[Jorge Tapia]]></dc:creator>
            <pubDate>Tue, 04 Dec 2018 18:19:58 GMT</pubDate>
            <atom:updated>2018-12-04T18:38:04.634Z</atom:updated>
            <content:encoded><![CDATA[<h3>iOS: Setting Up a Basic Voice Processing I/O Audio Unit — Swift</h3><p>If you’re one of the unlucky folks that needs to work with Apple’s AudioToolbox and the AudioUnit API, let me try to make your life a little bit easier. Apple’s lack of documentation and working examples make development with these tools a literal <em>via crucis</em>. Through a lot of trial-and-error, I managed to figure out how to set up a Voice Processing I/O audio unit in Swift.</p><p>This code also works to setup any other audio unit, you just need to replace the values for component type, subtype, and all other parameters based on the constants described in their poor “documentation”, which is located <a href="https://developer.apple.com/library/archive/documentation/MusicAudio/Conceptual/AudioUnitHostingGuide_iOS/Introduction/Introduction.html#//apple_ref/doc/uid/TP40009492-CH1-SW1">here</a>.</p><p>With no further to say, here’s the code. In the sample, I also show how to set some of the unit’s properties like Automatic Gain Control and Bypass Voice Processing.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9ccaae3338497a055a1d11193d8fe3a5/href">https://medium.com/media/9ccaae3338497a055a1d11193d8fe3a5/href</a></iframe><p>Hope it helps you out in your quest with working with AudioToolbox and the AudioUnit API with Swift. Happy coding 👨🏻‍💻</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/1*FJiHdSW2EqwlZX3JoSA12g.png" /><figcaption>Image credit: Apple, Inc.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=253b09c7d1b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Experience Building a Live Streaming App with Wowza GoCoder SDK for iOS]]></title>
            <link>https://medium.com/@profezy/my-experience-building-a-live-streaming-app-with-wowza-gocoder-sdk-for-ios-bca50d3eaab5?source=rss-e871e0257b33------2</link>
            <guid isPermaLink="false">https://medium.com/p/bca50d3eaab5</guid>
            <category><![CDATA[streaming]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[gocoder]]></category>
            <category><![CDATA[swift]]></category>
            <dc:creator><![CDATA[Jorge Tapia]]></dc:creator>
            <pubDate>Fri, 30 Nov 2018 23:28:57 GMT</pubDate>
            <atom:updated>2019-11-17T20:02:56.219Z</atom:updated>
            <content:encoded><![CDATA[<p>Building a live streaming capable application is not an easy feat. There are many moving pieces that make up an app like this. Master knowledge of AVFoundation, AudioToolbox, VideoToolbox, and other tools is required if you want to build your own audio and video encoders/decoders. Many of these frameworks are complete black boxes, especially VideoToolbox.</p><p>There are some third-party options that make all the hard work for you, but they’re not everything they advertise. We’re going to take a look at the GoCoder SDK by Wowza Media Systems. Wowza is a major provider for live streaming solutions. I’d like to mention that I’m not affiliated, endorsed or sponsored by Wowza. This SDK is proprietary, and no access to its source code is provided.</p><p>When I faced the challenge of building the live streaming portion of an app for a client, I evaluated some options on how to tackle the problem. The first one was to build my own encoders, but the deadline wouldn’t allow me to complete the task on time. They also had all their server-side infrastructure powered by Wowza, one of the reasons we decided that it was appropriate to use their mobile SDK for the app as well.</p><h4>The Documentation</h4><p>GoCoder comes with a complete API reference and some sample applications that demonstrate some of the SDK’s capabilities. They also have an app in the App Store that you can configure with your streaming server parameters and go live in minutes. Initially, this was very good, but I quickly found out that the examples were almost “Hello World” type of applications, and that the API reference doesn’t provide anything else apart from listing classes, properties, and methods. I was on my own.</p><h4>Setting Up the SDK</h4><p>Setting up the SDK is straightforward: you just pass properties to a configuration object with settings for video, audio, and the streaming server instance you need to connect to. Then assign this to a shared instance of GoCoder’s main class, call the startStreaming method with a callback delegate object, and you’re golden.</p><h4>The Challenges</h4><p>Through the course of development, I found out that implementing GoCoder brought a set of unique challenges, that unfortunately, not even their developers took into account when writing the SDK.</p><p>Providing a solid mobile live streaming experience is not easy. There are many variables in play that need to be considered, and the following are the ones you have to pay special attention to:</p><ol><li>Performance and battery life</li><li>Connection stability</li><li>Interruptions</li><li>Wired and wireless headsets</li><li>Background execution</li><li>General error handling</li></ol><p>If you run Wowza’s examples or use their own app in the App Store, the live streaming experience works only if following the happy path: no interruptions during your broadcast, no connection loss or bandwidth variations, no external accessories connected.</p><p>All of these scenarios led us to discover that the SDK was far from been tested by a QA team that considered everything our team did. I take a moment to thank my QA team for all their hard work in helping me discover and work around many of the issues that the SDK team didn’t.</p><h4>About Performance</h4><p>The SDK is performant and conserves battery well, considering that audio and video encoding are intensive tasks for the hardware. One of the problems we faced regarding this is that when starting and stopping a broadcast, threading issues made the app crash, even their samples and their own app suffer from this. We were “lucky” enough to get that particular issue resolved after 8 months of submitting a ticket with additional issues, that yes, as of the writing of this story, are not yet fixed by Wowza. <strong>DO NOT </strong>use any version of GoCoder below 1.5.1.x, they fixed the threading issue there.</p><h4>Connection Stability</h4><p>Mobile live streaming is very susceptible to networking conditions and connection quality. GoCoder provides a rudimentary adaptive bitrate and frame rate system that tries to accommodate for variations in bandwidth. It doesn’t work as expected all the time.</p><p>If you start a broadcast using WiFi and switch to cellular, get ready to implement your first workaround: the SDK doesn’t transition well and an error is thrown. It’s up to you to use a reachability listener to validate that the error thrown is indeed caused by a connection loss or change, and restart the broadcast.</p><p>Some streaming architectures suffer from this, since they provide simultaneous broadcast functionality, and a broadcast with the same stream name cannot be restarted once it ends. Yes, I was the lucky winner on this one too. Our server-side streaming team had to put a substantial amount of extra work to accommodate functionality to “resume” a broadcast if it was ended within a few seconds timeframe. Make a mental note about this resuming feature, it will be mentioned a lot in the next sections.</p><h4>Interruptions</h4><p>Get ready to be surprised about this one: <strong>ANY</strong> audio session interruptions will <strong>KILL</strong> the broadcast audio and it will never recover. An alarm, reminder, Siri, <em>phone call</em>, and pretty much anything that would trigger an AVAudioSessionInterruption will make your audio completely go away. This isn’t handled internally by the SDK in any way. When I submitted a ticket with the issue, the answer was to stop the broadcast and restart it after the interruption ended.</p><p>Any developer with basic knowledge of AVFoundation knows that a began interruption notification has no guarantee that will also receive an ended one. We’ve been lucky so far and all interruptions we’ve tested have sent both.</p><p>Basically, you <strong>MUST</strong> implement an AVAudioSessionInterruptionNotification observer and start/stop the broadcast accordingly. Hopefully, your streaming architecture won’t suffer from having to implement “resuming” logic on the server-side.</p><p>A special case has to be considered among all interruptions: <em>phone calls</em>. These <strong>CANNOT</strong> be treated as a regular AVAudioSessionInterruption, so you <strong>MUST</strong> implement logic to stop/start a broadcast using a CXCallObserver object from CallKit. This means that your app cannot support iOS versions below 10.0.</p><h4>Wired and Wireless Headsets</h4><p>You’d think these would work out of the box right? Well… NO! Connecting and disconnecting wired/wireless headsets in any combination will <strong>KILL</strong> your audio. Once again, Wowza’s solution was to “stop and restart the broadcast.”</p><p>For this one, you’ll need to implement your own AVAudioSessionRouteChangeNotification observer and stop/start the broadcast accordingly.</p><p>It’s worth mentioning that if you don’t configure an audio session using the .videoChat mode, forget about using Bluetooth headsets, they simply <strong>DO NOT WORK</strong> correctly with GoCoder. There are internal issues in the GoCoder audio engine, which is based in the AudioQueue services instead of AudioGraph. This is also the reason why all of the above audio issues are present.</p><p>There are tradeoffs of using the .videoChat mode: using the built-in mic will cause your broadcast volume to be lower than expected, This is due to the device’s tonal equalization and automatic gain control kicking in, and once this happens, you cannot set the input gain manually anymore.</p><p>To overcome that, you need to use the low-level AudioUnit API (in C) from AudioToolbox, and tap into the Voice Processing I/O unit. I’m still in the middle of doing that as of the writing of this story. I’ll update it later to shed some light on how to do it.</p><p>You can find how I solved that issue <a href="https://medium.com/@itsprof/ios-setting-up-a-basic-voice-processing-i-o-audio-unit-in-swift-253b09c7d1b8">here</a>.</p><h4>Background Execution</h4><p>So far, you’ve been a good developer and implemented all the required handlers for networking, audio interruptions, and audio route changes. GoCoder provides a property that allows you to keep broadcasting in audio-only mode if, while live streaming, you send the app to the background. This sounds wonderful until you receive an interruption while in the background and your handlers attempt to start and stop the broadcast.</p><p>GoCoder’s startStreaming and endStreaming methods just go bananas when called in the background. By this time, your code looks horrible already with all of the above handlers. I decided that it’s just not worth the pain, and disabled background audio-only mode. Guess what I did? A start/stop cycle when notifications for UIApplicationDidEnterBackground and UIApplicationDidBecomeActive are fired.</p><p>You’ll also have to validate all of the above conditions for audio interruptions/route changes and phone call handlers with it. Flags everywhere!!!</p><h4>General Error Handling</h4><p>When GoCoder throws an error, you’d expect some error codes and messages describing what happened. Be ready to receive the exact same error messages for ALL errors. You missed or put an invalid value as your audio sampling rate? You get the same error message as if you got a connection loss. Let’s not forget the fact that there’s <strong>ZERO</strong> documentation on error codes in their API Reference, or anywhere.</p><p>You’ll have lots of fun with this, trust me, I barely slept and ate for 3–4 weeks trying to handle them, believing that I was the problem. In the bottom of my heart, I knew it wasn’t me, but found really hard to digest all of these findings and reporting them to QA and my CTO. I still find it hard to believe, and in some form, I feel scarred by it now. I spent all possible options inside my code to try to verify it wasn’t me, but them.</p><h4>My Takeaways and Recommendations</h4><p>By no means, GoCoder is a silver bullet for mobile live streaming on iOS. The framework needs to mature a lot more, to go through a lot more development, testing, and debugging. Don’t get me wrong, when it works, it produces beautiful live streams with amazing quality and device performance. This <strong>MUST</strong> be acknowledged, kudos for the team at Wowza for it. I only hope the product keeps improving, for us developers, and for our end users as well. GoCoder is a proprietary solution, and obtaining a license isn’t cheap. The least I’d expect is premium support because they advertise it as a premium product. We also paid good money for it.</p><h4>Other Alternatives</h4><p>There’s nothing better than open source software. It’s reliable, supported, and if something is broken, you can contribute and fix it yourself. Also, there’s transparency as to what’s happening and how things are done. I’ve recently been playing with an open source live streaming framework called <a href="https://github.com/shogo4405/HaishinKit.swift">HaishinKit</a>. It looks promising and the developer is friendly and open to solve issues on GitHub. It might be a better alternative, but again, you’d need to evaluate it thoroughly to determine if it’s your best choice.</p><h4>Let Me Help Share the Pain</h4><p>If you or your company decide to build a live streaming app, I want you to know that I’m an expert implementing GoCoder/HaishinKit. I’ve already gone to hell and back with it, and know exactly what to do to make it sing. Don’t hesitate to contact me for additional information about my consulting services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*kJ8ShKsBT5RUeniJxreuVg.png" /><figcaption>Image credit: Wowza Media Systems, LLC</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bca50d3eaab5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#NativeOrDie]]></title>
            <link>https://medium.com/series/nativeordie-768613adbdca?source=rss-e871e0257b33------2</link>
            <guid isPermaLink="false">https://medium.com/p/768613adbdca</guid>
            <dc:creator><![CDATA[Jorge Tapia]]></dc:creator>
            <pubDate>Thu, 09 Aug 2018 21:36:48 GMT</pubDate>
            <atom:updated>2018-09-18T17:58:38.242Z</atom:updated>
            <content:encoded><![CDATA[<p>These are real-life horror stories from the depths of cross-platfrom mobile application development.</p><p><em>All images used in these stories are provided by our friends at </em><a href="http://pixels.com/"><em>pexels.com</em></a><em>.</em></p><h4>A Brave New World…</h4><p>They promised you’d write your code once and it’d run everywhere.</p><p>They promised faster development times with “ the tools and skills you already know.”</p><p>They said it was going to be painless, effortless.</p><p>They said it would work with your existing native code.</p><p>They said you could easily extend it with your custom components and modules if needed.</p><p>They all lied…</p><h4>I’ve Been Click-Baited</h4><p>Let’s see how many of you recognize the authors of these slogans.</p><blockquote>1. Build amazing mobile apps powered by open web tech.</blockquote><blockquote>2. Build great mobile experiences faster<br>Native apps. Mobile APIs. Real-time analytics. One Platform.</blockquote><blockquote>3. Deliver native Android, iOS, and Windows apps with a single shared .NET code base.</blockquote><blockquote>4. With Ext JS, create data-intensive HTML5 applications using JavaScript</blockquote><blockquote>5. Build amazing apps in one codebase, for any platform, with the web.</blockquote><blockquote>6. Gorgeous native mobile app development with Java or Kotlin for iPhone, Android etc….</blockquote><blockquote>7. Quickly deliver stunning omni-channel apps — without compromising on user experience, features, security or cost.</blockquote><blockquote>8. Divide Enterprise Mobile Application Development time and costs by 10 to 50, and reconcile business and IT professionals!</blockquote><blockquote>9. Open source framework for building truly native mobile apps with Angular, Vue.js, TypeScript, or JavaScript.</blockquote><blockquote>10. Build Native Apps in the Cloud</blockquote><p>As for the worthy and memorable mention: the one I’m currently using…</p><blockquote>Learn once, write anywhere: Build mobile apps with React</blockquote><h4>Part 1: Can’t Even Resolve Your Own Imports!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*Afss2_Ns-rHHiOuTAnNDhQ@2x.jpeg" /></figure><p>While trying to rebuild a native module using Xcode 10 GM and the RC candidate of version 7.4.0 of the Appcelerator Titanium SDK (which claims compatibility with iOS 12), the build output contains lots of entries that look like this:</p><p><em>[TRACE] [xcode-dist] #import “TiViewProxy.h”</em></p><p>There are lines for ALL the other Titanium classes as well. How the hell are we supposed to work with something like this?</p><p>Yet again, the mission is to re-build a castle in the sky…</p><h4>Part 2: Can’t Even Resolve Your Own Imports!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*Afss2_Ns-rHHiOuTAnNDhQ@2x.jpeg" /></figure><p>I managed to resolve the imports issue, the module compiles and builds. I installed the freshly baked module into the application, started the build process, and BOOM!</p><p>The build tools have ‘unexpected duplicate <em>CodeSign</em> and <em>PBXCp </em>tasks’ everywhere in the output.</p><p>How are developers supposed to work like this? Their support on Slack sucks booty, and we’re paying customers of their platform.</p><p>Just another day working with magical cross-platform development tools…</p><h4>Final Part: Can’t Even Resolve Your Own Imports!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*Afss2_Ns-rHHiOuTAnNDhQ@2x.jpeg" /></figure><p>Looking at the log, I noticed a very curious flag turned ON: Use the new build system.</p><p>Since it’s Titanium, and they said it works with Xcode 10 and iOS 12, the first thought I had was that “this actually doesn’t work with Titanium.”</p><p>Went to edit my <em>tiapp.xml</em> file to tell the build tools to use Xcode’s legacy build system, and voilá, it worked!</p><p>So much for iOS 12 and Xcode 10 compatibility that is just not there.</p><p>Yet again, solving others’ issues by myself to save the day and wake up from another cross-platform nightmare.</p><h4>And Just When I Thought It Was Over…</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*Afss2_Ns-rHHiOuTAnNDhQ@2x.jpeg" /></figure><p>I was asked to also update the Android module with Titanium SDK 7.4.x. Guess my reputation for slaying giants precedes me. Will let you all know how it went.</p><p><em>Update: lost 5 hours trying to update the module in order for it to build in apps compiled against Ti SDK 7.4.0. It’s working now. Really hope it’s the last time I have to stain my hands with this.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=768613adbdca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rise a n00b]]></title>
            <link>https://medium.com/@profezy/rise-a-n00b-b349fa5f87ef?source=rss-e871e0257b33------2</link>
            <guid isPermaLink="false">https://medium.com/p/b349fa5f87ef</guid>
            <category><![CDATA[xbox]]></category>
            <category><![CDATA[esport]]></category>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[halo]]></category>
            <category><![CDATA[videogames]]></category>
            <dc:creator><![CDATA[Jorge Tapia]]></dc:creator>
            <pubDate>Wed, 18 Jul 2018 17:16:41 GMT</pubDate>
            <atom:updated>2024-10-08T08:32:17.780Z</atom:updated>
            <content:encoded><![CDATA[<p>I never really learned what it meant to be just a kid. A few months after my first birthday, I had to move with my parents from Quito to Morona Santiago. This province, located deep in the Amazon region of Ecuador, was where my father had to complete one of his tours as a Lieutenant in the Army. The weather conditions were tough; torrential rain fell from the sky every day, almost all day long, and that hasn’t changed. Roads were still being built by the Army Corps of Engineers, and the only way to get there was by taking a small biplane that flew in weekly. It was here, in this isolated place, that my story as a gamer began.</p><p>As the first-born child of a very young couple living in the harsh conditions of the Ecuadorian Amazon rainforest, my life revolved around finding happiness in a place filled with hazards. My mom had a hard time trying to protect me from the dangerous bugs, snakes, and relentless weather native to the region. There was no TV signal and only one radio station that didn’t broadcast all the time. You might wonder — what was fun about all of this? Well, my dad had an Atari 2600, and that’s where my love for video games first took root.</p><p>A few months before my second birthday, my dad began showing me how to use the joystick and the single orange button on the controller. Playing games like <em>Pitfall</em>, <em>Pac-Man</em>, <em>Tanks</em>, <em>Space Invaders</em>, and many others quickly became a part of me. Despite my young age, my dad tells me that I started to understand the connection between moving the joystick, pressing the button, and the pixels on the screen. He also noticed the sheer joy on my face every time he sat me on his lap to play. Sadly, that was the last time I played with him, but I’ll explain why later in this story.</p><p>I continued to play my beloved Atari 2600 until I turned three. It was time to move back to Quito, only to learn that my dad was reassigned to a small town on the coast. My grandparents weren’t too happy about it, and they decided that I would stay with them this time. My mom was the eldest of four siblings, including her three younger brothers. Living with my grandparents turned into another pivotal chapter in my life. My grandmother, a professional pianist, got me into music and taught me how to read and write. My youngest uncle also lived with us, and he owned an NES. My passion for gaming continued as we played games together. I raced through <em>Super Mario Bros.</em>, <em>Duck Hunt</em>, <em>Excitebike</em>, <em>Contra</em>, <em>Mega Man</em>, <em>The Legend of Zelda</em>, and many others. The big joystick with a single button had now been replaced by a small rectangular pad with directional buttons and two action buttons.</p><p>By the time I turned five, I was still living with my grandparents and enjoying a happy life. One of my uncles was graduating with a degree in Mechanical Engineering, and he introduced me to my first computer — a monochrome 286 running at a blazing 12.5 MHz. It had DOS installed and many of the programs my uncle used for his final project. Among them was this fascinating tool called QBasic. My uncle, patient and kind, taught me how it worked and introduced me to variables and basic flow control structures. By the time I was six, I fully understood how to perform basic operations and how to print shapes made out of asterisks (*) using loops, if statements, labels, and goto statements. I had just learned my first programming language! I also became comfortable navigating my way through DOS commands.</p><p>The most exciting discovery, however, was finding the infamous <em>cd games</em> command that lead to a special directory on that old machine. Thanks to my uncle, I played my first PC games, though some were a bit inappropriate for a six-year-old — <em>Strip Poker</em> (yes, I learned how to play poker at that age), <em>California Games</em>, <em>Sokoban</em>, and <em>Prince of Persia</em>. The latter captivated me with its beautiful graphics, animations, and dazzling level design. I was hooked.</p><p>Soon after that, the Super Nintendo arrived, bringing with it some of the best games I ever played — <em>Super Mario World</em>, <em>Super Street Fighter 2 Turbo</em>, <em>The Legend of Zelda: A Link to the Past</em>, <em>Mega Man X</em>, <em>Mortal Kombat</em>, <em>Super Metroid</em>, <em>StarFox</em>, and the <em>Donkey Kong Country</em> series. These were the best years of my childhood, with a SNES controller in hand.</p><p>The Nintendo 64, however, holds a special place in my heart. My all-time favorite game was released for it: <em>The Legend of Zelda: Ocarina of Time</em>. That game opened my mind to new possibilities, enriching my vocabulary more than any classroom could. Other standout titles were <em>GoldenEye 007</em>, <em>Perfect Dark</em>, <em>International Superstar Soccer 64</em>, <em>Mortal Kombat 4</em>, <em>StarFox 64</em>, and <em>Super Mario 64</em>. These games filled my teen years with joy and unforgettable split-screen gaming sessions with friends.</p><p>As I entered my teenage years, my love for PC gaming deepened. I discovered <em>Doom</em> and <em>Wolfenstein</em> when I was seven, and they sparked my passion for first-person shooters. In 1993, after much pestering, my dad bought me a SoundBlaster sound card and a CD-ROM drive for our old 486 machine. I installed them myself around my eighth birthday. That same year, I also got into real-time strategy games like <em>Dune 2</em>, later followed by <em>Warcraft</em>, which ignited a love for RTS games that lasted for years.</p><p>My PC gaming journey took off with titles like <em>Diablo</em>, <em>StarCraft</em>, and <em>Age of Empires</em>, which demanded a computer upgrade. I played countless hours on <em>Battle.net</em>, and my love for competitive gaming began. Later on, games like <em>Warcraft 3</em> introduced me to the world of local tournaments, where I found success.</p><p>My first experience with competitive gaming came when <em>WarCraft 3</em> was released. I played it extensively with my friends during my last year of high school and often found myself winning against them.</p><p>In 2003, LG organized the LG Latin American Cup, which featured games like <em>Quake 3</em> and <em>WarCraft 3</em>. My friends convinced me to participate, but I needed my parents’ permission. It was challenging to explain that video game tournaments were a legitimate thing, but after some persistence, they finally allowed me to go. I ended up winning the <em>WarCraft 3</em> tournament, and the prize included a DVD writer, a flat-screen monitor, and some cash. I was finally able to replace my old CRT monitor.</p><p>Along the way, I also experienced consoles like the PlayStation and PlayStation 2, falling in love with franchises like <em>God of War</em>, <em>Killzone</em>, <em>Crash Bandicoot</em>, and <em>Spyro</em>. When the original Xbox came out, games like <em>Halo</em> and <em>Doom 3</em>captivated me. But it was <em>Halo 2</em> and later <em>Halo 3</em> on the Xbox 360 that truly ignited my passion for competitive gaming. I followed the rise of the first Halo pros and began grinding games like <em>Call of Duty</em> when <em>Modern Warfare</em>was released.</p><p>Despite my late start in competitive gaming at age 22, I achieved one of my proudest accomplishments in 2014, placing in the Top 48 teams at UMG Dallas for <em>Call of Duty: Ghosts</em>. My competitive gaming career wound down as I focused on my professional career as a software engineer, but my passion for gaming remained.</p><p>Today, I’m a Lead Software Engineer at an incredible company called FanHero. I speak Spanish, Italian, English, French, and German, and I continue to love music, particularly the violin. Video games remain my favorite hobby, and I’ve fallen back in love with <em>Halo</em>, now ranked Champion in the SWAT playlist, among the top 200 Halo 5 SWAT players in the world.</p><p>One of my main goals now is to bring visibility to the Halo SWAT community. It’s a tight-knit, highly competitive mode that deserves more recognition, and I hope to lead this amazing community into the spotlight. Through streaming, organizing tournaments, and raising awareness, I want to show the world how talented, dedicated, and passionate the SWAT community is.</p><p>It took me 33 years to rise from a n00b, but now, nothing’s going to break my stride.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9qedeN1GSslQAf_ICga5YA.png" /><figcaption>Member of the Top 200 Halo players ins the world</figcaption></figure><p>If you want to know more about me, be sure to <a href="http://twitch.tv/SynapseIX">follow me on Twitch</a>. I stream my gameplay and community tournaments on a daily basis starting at 10pm EST. I am always open to have a good chat with everybody that tunes in.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b349fa5f87ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>