<?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 Vicente Plata on Medium]]></title>
        <description><![CDATA[Stories by Vicente Plata on Medium]]></description>
        <link>https://medium.com/@xnt?source=rss-8026a55b6170------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uHubPKP-xb_mz07YzgOVww.jpeg</url>
            <title>Stories by Vicente Plata on Medium</title>
            <link>https://medium.com/@xnt?source=rss-8026a55b6170------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:07:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@xnt/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[Algunas razones para adoptar TypeScript]]></title>
            <link>https://medium.com/@xnt/algunas-razones-para-adoptar-typescript-7cfb4abb0963?source=rss-8026a55b6170------2</link>
            <guid isPermaLink="false">https://medium.com/p/7cfb4abb0963</guid>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[español]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Vicente Plata]]></dc:creator>
            <pubDate>Mon, 20 Jul 2020 04:44:54 GMT</pubDate>
            <atom:updated>2020-07-20T04:44:54.622Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DLtecnBFzRECy48x" /><figcaption>Photo by <a href="https://unsplash.com/@earbiscuits?utm_source=medium&amp;utm_medium=referral">Juan Rumimpunu</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>En la encuesta de desarrolladores de Stack Overflow 2020, TypeScript <a href="https://insights.stackoverflow.com/survey/2020#most-loved-dreaded-and-wanted">destaca</a> como el 2o. lenguaje o tecnología más amada.</p><p>Durante casi un año, he trabajado con TypeScript todos los días: primero, migrando una aplicación legado enorme en React JS, poco a poco, conforme tocábamos o creábamos nuevos componentes. Después, haciéndolo parte de mi “toolbelt” para proyectos independientes (apps pequeñas en React JS o React Native + Expo). Y luego, en una app grande, desde cero, en React Native.</p><p>Antes de eso, la verdad es que no terminaba de entender el “hype”. De hecho, ponerle tipos a JavaScript me parecía anti-productivo. “Tanta lata para usar lenguajes más dinámicos en el backend, ¿y la idea es quitarle dinamismo al frontend?” pensaba mi viejito cuidarranchos interior. Pero bastaron algunas semanas para darme cuenta de que valía la pena. Y me gustaría compartirte por qué.</p><p>Originalmente, dediqué algo de tiempo durante unas semanas a crear <a href="https://github.com/xnt/nutrition-facts">una app en JavaScript</a> que mudaría a TypeScript, quizás en algún live stream. Pero creo que tuve un sesgo derivado de trabajar con la tecnología frecuentemente: la mera explicación de por qué es una buena idea, y los ejemplos básicos que eran necesarios para terminar de entender el concepto técnico, ameritaban una exposición independiente. De ahí este post.</p><h3>¿Qué es TypeScript?</h3><p>En corto, la idea de TypeScript es fungir como un “superset” de JavaScript que se “compila” a JavaScript. Ojo con el entrecomillado de “compila”: en sentido estricto es mas un transpilado o traducción (con lo que quizás estés familiarizado si has usado, digamos, Babel). Aclarado el “<a href="https://knowyourmeme.com/memes/ackchyually">ackchyually</a>”, continuemos.</p><h4>Tipos</h4><p>La parte probablemente mas conocida de Typescript es la declaración de tipos e interfaces y la manera en que anotamos variables y demás.</p><p>Por ejemplo, supongamos que una API regresa el siguiente usuario:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0add21c08820f69db5b050aef704141f/href">https://medium.com/media/0add21c08820f69db5b050aef704141f/href</a></iframe><p>Podemos declarar el tipo como sigue:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1b2b7220f8e2097313080ac350035c40/href">https://medium.com/media/1b2b7220f8e2097313080ac350035c40/href</a></iframe><p>Y empezar a hacer algunas cosas divertidas:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2Fxnt%2Fembed%2Fpreview%2FeYJbYQX%3Fheight%3D600%26slug-hash%3DeYJbYQX%26default-tabs%3Djs%2Cresult%26host%3Dhttps%3A%2F%2Fcodepen.io&amp;display_name=CodePen&amp;url=https%3A%2F%2Fcodepen.io%2Fxnt%2Fpen%2FeYJbYQX&amp;image=https%3A%2F%2Fassets.codepen.io%2F3864823%2Finternal%2Fscreenshots%2Fpens%2FeYJbYQX.default.png%3Fformat%3Dauto%26amp%3Bha%3Dfalse%26amp%3Bheight%3D360%26amp%3Bquality%3D75%26amp%3Bv%3D1%26amp%3Bversion%3D1595216771%26amp%3Bwidth%3D640&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/d9e0f6cd36c9a88f51b4ae10d53a167b/href">https://medium.com/media/d9e0f6cd36c9a88f51b4ae10d53a167b/href</a></iframe><h4>Qué bonito… ¿Y luego?</h4><p>Algunos otros trucos que TypeScript tiene bajo la manga, incluyen:</p><ul><li>Validación de catálogo de posibles valores (similar a enums)</li><li>Clases (obviamente)</li><li>Generics</li><li>Interfaces</li><li>Herencia</li><li>Archivos de declaraciones globales (.d.ts)</li><li>Tuplas/diccionarios</li><li>Tremendo soporte de la comunidad e IDEs</li></ul><p>Lo último no es de menospreciarse. Como desarrolladores, a veces nos vamos por lo más nuevo y brillosito porque hay reto técnico asociado. Pero desde una perspectiva de negocio, es importante considerar el nivel de soporte y la viabilidad a mediano plazo de la inversión que se está haciendo en un proyecto.</p><p>Por ejemplo: como podrás imaginar, la idea es ir expresando los tipos de las rutinas, datos y componentes en tu aplicación. Pero el desarrollo de software contemporáneo rara vez es una actividad aislada: parte del éxito de un proyecto depende de analizar e integrar dependencias de manera inteligente. ¿De qué serviría, entonces, crear tipos si las dependencias no tienen estas definiciones?</p><p>Por fortuna, existe una organización en npm (que parece mas un namespace, pero bueno 😂) donde la gente contribuye estas definiciones, y tú puedes contribuír también: <a href="https://www.npmjs.com/~types">@types</a> . Por ejemplo: soy fan de Ramda. Cada que comienzo a “TypeScriptear” un proyecto donde agregué Ramda como dependencia, puedo instalar <a href="https://www.npmjs.com/package/@types/ramda">@types/ramda</a> y obtengo el tipeado de todos los métodos y módulos.</p><h3>Lo que he observado</h3><p>Como ya he explicado, mi primer implementación real de TypeScript fue en un proyecto que, en cualquier caso, le quedaban solo unos meses de desarrollo activo antes de retirarse en dirección a la puesta del sol 🌇. Lo anterior me dio la oportunidad de analizar ventajas y desventajas a nivel proyecto/equipo, mas allá del lenguaje per se.</p><h4>Dónde comenzar</h4><p>Hay muchos tutoriales online sobre cómo convertir tu app de JS a TS. Aunque, como expliqué al principió, tal vez termine creando uno, creo que es más interesante hablar de lo que sucede después de que una aplicación existente ha sido “TypeScripteada”.</p><p>Hay 2 puntos de acceso relativamente simples donde agregar TypeScript incrementalmente:</p><ol><li>Utilerías</li><li>Componentes independientes</li></ol><p>Para ambos, hay que analizar 2 factores de riesgo y esfuerzo:</p><ol><li>Qué tan nuevo es el archivo-carpeta (porque en teoría hay menos dependencias <strong>hacia</strong> él)</li><li>Qué tan elaborado es su funcionamiento (porque en teoría hay menos dependencias <strong>desde</strong> él)</li></ol><p>Comencé con algunas de las utilerías más básicas: reglas y validaciones de atributos de usuario, selectores simples de redux, registro de eventos de telemetría…</p><p>Posteriormente, fui utilizando algunas de las ofertas mas nuevas que requerían la creación de componentes nuevos. Por ejemplo, sin entrar mucho en detalles de negocio, la oferta de <a href="https://www.forhims.com/covid-test">pruebas de COVID-19</a> requería elementos de interfaz hacia los proveedores médicos (ordenar pruebas, estado del kit, estado y resultado de análisis de laboratorio) que no teníamos hasta entonces. Como tal, fueron un buen candidato (casi ninguna dependencia <strong>hacia</strong>, y pocas dependencias <strong>desde</strong>).</p><h4>TypeScript vs PropTypes</h4><p>En el caso de React: Una duda bastante razonable es la utilidad de los PropTypes si, en teoría, las props también se pueden validar mediante TypeScript (tipos o interfaces). Y la verdad es que es más legible.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8c5c0d403f1fe5e89cd883b05c037169/href">https://medium.com/media/8c5c0d403f1fe5e89cd883b05c037169/href</a></iframe><p>Versus:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6c39b4284e3945424d1ef143739cc9ee/href">https://medium.com/media/6c39b4284e3945424d1ef143739cc9ee/href</a></iframe><p>🤔 a lo mejor hay typos, pero da la idea.</p><p>2 ventajas, de botepronto:</p><ol><li>La validación se realiza en tiempo de compilación (sic) versus ejecución</li><li>Se pueden reusar elementos y tipos que has definido anteriormente, como entidades de datos. Incluso, haciendo uso de herencia o composición. Obviamente esto también es posible si traes tus PropTypes de paseo de un lado a otro, pero solo en el contexto de componentes</li></ol><p>En mi experiencia, la única razón para mantener PropTypes en un proyecto con TypeScript es si existen componentes legado que aún no has podido mover a tsx. Los proyectos que hemos creado con TypeScript desde el arranque, ni siquiera lo tienen como dependencia.</p><h4>Paquetes</h4><p>Enlazando de alguna manera algunas ventajas anteriores: nada te detiene de crear un package con declaraciones de tipos que otros repositorios en tu organización pueden consumir, y otras personas pueden editar para que los cambios en contratos de llamadas de red sean mas transparentes.</p><p>La logística de cómo crear, integrar y versionar estos paquetes es un tema por sí mismo. Pero introduce un poco mas de rigor a los procesos de desarrollo de frontend (o incluso backend con lenguajes altamente “flexibles”) que suelen ser un tanto caóticos.</p><h4>IDEs</h4><p>Somos seres humanos, y cometemos errores. Otra ventaja sutil, a veces tomada a mofa, pero muy útil en tiempo y $$, es minimizar lo propensos que somos a tener typos (inserte dadjoke sobre typos vs tipos aquí). La mayoría de los IDEs contemporáneos tienen soporte para TypeScript que permite validar errores conforme escribes tu código.</p><p>Aún si no fuera así: al integrar el tsc a tu cadena de creación de bundle (independientemente del ambiente) hace el ruido suficiente para que te des cuenta de que algo no está bien, antes de lanzarlo o incluso hacer que tu equipo invierta tiempo en un PR.</p><h4>Problemas</h4><p>El proceso de meter TypeScript a un proyecto legado es relativamente transparente. Hay algunas cosas que por naturaleza suelen dar hipo:</p><ul><li>Dependencias y módulos demasiado viejos u oscuros</li><li>Ocasionales locuras de webpack (source maps, chunks, minificación), pero son raras</li><li>Procesos de integración continua y similares que estaban demasiado amarrados a sufijos de archivos (por ejemplo, que tu test harness busque solo *.js y no *.ts)</li></ul><p>Fuera de lo anterior, no recuerdo haber encontrado problema alguno. Y todos fueron resueltos con relativa rapidez.</p><h3>Conclusión</h3><p>Estoy convencido de que usar TypeScript es ideal para 9 de cada 10 proyectos, nuevos o legado. Favorece notablemente no solo aspectos técnicos, pero también de comunicación (por ejemplo, el término que usamos para referirnos a algunos datos) y hace, en general, que el código sea mas limpio.</p><p>Los ejemplos y tips anteriores son, con suerte, suficientes para que te animes a experimentar. O al menos sepas un poco más qué onda con TypeScript. En cualquier caso, quedo atento a tus comentarios vía twitter, en <a href="https://twitter.com/xnt">@xnt</a> .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7cfb4abb0963" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stonehenges]]></title>
            <link>https://medium.com/@xnt/stonehenges-5f7263c8b782?source=rss-8026a55b6170------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f7263c8b782</guid>
            <dc:creator><![CDATA[Vicente Plata]]></dc:creator>
            <pubDate>Tue, 11 Mar 2014 07:08:36 GMT</pubDate>
            <atom:updated>2014-03-11T07:08:36.410Z</atom:updated>
            <content:encoded><![CDATA[<p>Yes. This has to do with Software. Bear with me (or blame <a href="http://adrianpadilla.net/">Adrian</a> for saying this was a good idea).</p><p>What do we know about <a href="http://en.wikipedia.org/wiki/Stonehenge">Stonehenge</a>?</p><ul><li>It was built, most likely, by a group of people. If it was an individual, s/he must have been rather awesome (albeit not necessarily wise)</li><li>It was built a long time ago, by a <em>culture </em>that “left no written records”</li><li>All available sources of information basically say something in the lines of: “by the time we arrived, it was already there”</li><li>No one is 100% sure of what is it doing there</li><li>Some people assign it mystical powers, while other folks think it’s just a rudimentary attempt to display some skills</li><li>It’s likely the derivative of somebody having way too much power</li><li>We do know, though, that catastrophe is likely if it’s removed (touristic/economic catastrophe, but catastrophe in the end ☺ )</li><li>General consensus agrees that it was built on different phases -again, no clue of the reasoning behind each of these phases</li><li>The fact that the thing is there, pretty much justifies more jobs than if a more modern structure was in its place</li><li>Maybe the most interesting question is how in the hell the thing (or at least, a part of it) is still standing</li><li>Whoever built it, s/he likely lived in the nadir of what we currently understand as “civilization”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jB8q0Ra4XqKy8RnN7-c_bA.jpeg" /><figcaption><a href="http://www.flickr.com/photos/grandhi/4667627395/">http://www.flickr.com/photos/grandhi/4667627395/</a></figcaption></figure><p>Ring any bells? Think about the last time you dealed with a legacy system.</p><p>I mean, <strong><em>real</em></strong> legacy system. No, not the uncomfortable yet decently documented API, or that backend you know it’ll take a few months to actually understand.</p><p>I mean thousands over thousands of lines of code written as if they were SQL stored procedures. Maybe even real business logic living in Stored Procedures. Zero documentation. Strange dependencies against which your Google-fu has no power. Technologies long abandoned to their fate, only murmured in sarcastic references at forgotten usenet groups.</p><p>The kind of questions that get zero up-votes on Stack Overflow, and just 1 view every 6 months. Someone passing by, almost stalking you, while you whisper: “I know you’re there… I know you can see me…”</p><p>The very essence of nightmares. Curses. The kind of things that transform your good-willed antisocial nature into a master of profanity.</p><p>That thing you’re dealing with? That’s a Stonehenge. That phase you’re living? That’s what I call “<em>Stonehenge Driven Development</em>”.</p><p>I would love to hear your Stonehenge stories or any kind of feedback. I’m <a href="http://twitter.com/xnt">@xnt</a> on Twitter.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f7263c8b782" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Some Pros and Cons of Working Remotely]]></title>
            <link>https://medium.com/@xnt/some-pros-and-cons-of-working-remotely-7bcb5fd76ada?source=rss-8026a55b6170------2</link>
            <guid isPermaLink="false">https://medium.com/p/7bcb5fd76ada</guid>
            <dc:creator><![CDATA[Vicente Plata]]></dc:creator>
            <pubDate>Fri, 27 Dec 2013 22:39:09 GMT</pubDate>
            <atom:updated>2013-12-27T22:39:32.216Z</atom:updated>
            <content:encoded><![CDATA[<h4>Thinking About Taking a Remote Opportunity in Software Engineering?</h4><p>I’ve worked remotely for some years now. I started moonlighting in places like the now-defunct <a href="http://en.wikipedia.org/wiki/VWorker">vWorker</a> (“Rent A Coder”, back in the day) with my brother in law. Then I moved to full-time offshoring from Mexico, and ended up landing in Canada, working with a team in the US.</p><p>Working remotely has some pros and cons, some of which I’ll try to outline here. Needless to say, many of them are just a matter of personal preferences. But I hope it’s useful for someone considering a position in a geographically distributed team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hTBRY7N3HkGnVff5Ps9vpg.jpeg" /><figcaption>One day I’ll have my own home. And a dog. And it won’t be raining here. (Jessamyn West | <a href="http://www.flickr.com/photos/iamthebestartist/3703512976/">http://www.flickr.com/photos/iamthebestartist/3703512976/</a>)</figcaption></figure><h3>The Pros</h3><p>Here are some reasons why I think you’ll love working remotely:</p><ul><li><strong>Less chitchatting</strong> — Even though there can be a bit here and there through IM, it’s entirely up to you to answer or not, and when to do it.</li><li><strong>More learning</strong> — It’s easier to dedicate 5 or 10 minutes per hour to, say, PluralSight, or checking something on Github, or read a bit of a book. Those 5 or 10 minutes could basically be the time you spent on waiting for all your buddies to get their cups of coffee, or finish their cigs. So it’s not that much of an impact to your net work time.</li><li><strong>Minimize the Kool-Aid</strong> — The more you’re “vested” in the social circle surrounding your company or project (i.e. the more people around), the harder it tends to be to look outside and see if things are going OK. I’ve found that being remote tends to make me a bit more objective and critical, as well as having more exposure to other products and methodologies.</li><li><strong>More time for my family and myself</strong> — Since most, if not all the social events are in 3D and obviously based on the team’s main location, being remote means I don’t necessarily have to attend -many times I can’t attend at all ☺ . So I have a bit more time for my family and myself.</li><li><strong>Good things are a bit magnified</strong> — “Even being remote”… I love when my review summaries or recommendations begin like this. “Even being remote you’re doing an excellent job”. It could certainly mean, “you’d be even better if you were here”, for sure. But it can also be interpreted as “allow this guy to do stuff his own way, he’ll take care of it”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xTcd3rDmj7F_-BInVB7gVw.jpeg" /><figcaption>By “Thomas” | <a href="http://www.flickr.com/photos/icesabre/2219876290">http://www.flickr.com/photos/icesabre/2219876290</a></figcaption></figure><h3>The Cons</h3><p>Challenges and issues you’ll probably face:</p><ul><li><strong>You need to be more visible</strong> — People will often wonder what are you doing or, in the worst case, they can even forget that you’re a member of the team. Find ways for making yourself visible: IM, emails, Code Reviews, status updates. But please, please, don’t overact this or you’ll end up generating noise ad nauseum.</li><li><strong>You need to be more valuable</strong> — Either by mistake or on purpose, folks could leave you out in updates, requirement changes, etcetera. The best way to avoid this is to make your contributions and inputs valuable: preferably even more valuable than the teammates “on site”. Again keep a balance, though: you want to be valuable enough so you get the information you need without explicitly asking for it when things begin breaking, but you don’t want to be necessary enough so you have to sacrifice vacations or be overworked.</li><li><strong>Sometimes you’ll miss social interaction</strong> — This could be “not so bad” when you’re in a small, “satellite” remote team. But when you’re all on your own it can hurt a bit. Suggestions: find <a href="http://www.meetup.com/">local groups</a> (or create your own), try to go and meet and socialize with your team every now and then, or suggest them to come to your city for a weekend or on their vacations. It will hardly be “as good” as if you actually were there, but it can be quite bearable.</li><li><strong>Sometimes people just don’t get it</strong> — Yes, we’re way into the 2000&#39;s. And yes, I’ve worked mostly at tech companies. Still some people, no matter how technical the role is, need to be reminded of how to use the tools effectively, how to check for their mic not being muted, how to share their desktop… That’s cool if you’re the first remote person they talk with. But after a few months… Sigh.</li><li><strong>You need to FOCUS</strong> — More freedom inherently means more procrastination opportunities. This can end up nullifying the Pros and exponentially increasing the Cons. You’ll need to have a lot of discipline, way more than if you were on site, to enjoy the good things whilst tackling the bad ones and still delivering stuff.</li></ul><p>All in all, I honestly enjoy working remote. I’ve had the opportunity to be on-site but I feel the Pros are just awesome, while most of the Cons are nothing but challenges. Again -it’s up to you.</p><p>Did you like this article? Would you like me to talk with more detail about something? Please leave a note, or contact me on <a href="http://twitter.com/xnt">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7bcb5fd76ada" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Impostor Syndrome]]></title>
            <link>https://medium.com/@xnt/the-impostor-syndrome-e94565153c16?source=rss-8026a55b6170------2</link>
            <guid isPermaLink="false">https://medium.com/p/e94565153c16</guid>
            <dc:creator><![CDATA[Vicente Plata]]></dc:creator>
            <pubDate>Thu, 26 Dec 2013 23:48:30 GMT</pubDate>
            <atom:updated>2013-12-26T23:48:30.595Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*0c9uf-GYatT2ZHbBpMLoIA.jpeg" /><figcaption>Masks / http://www.flickr.com/photos/kawaii77/</figcaption></figure><h4>And how I deal with it</h4><p>Earlier this week, I was talking with a friend about the fact that she doesn&#39;t feel like she deserves a lot of what she has achieved (and she has achieved a lot, actually). I couldn&#39;t feel more empathy. The same thing happens to me.</p><h3>Why do I feel like I’m an impostor?</h3><p>Keep in mind that I am:</p><ol><li>Not precisely attractive</li><li>With an arguably acceptable level of formal education</li><li>Not quite brilliant, in my opinion (some folks discern)</li><li>With a terrible, terrible memory</li></ol><p>Still, I&#39;ve been lucky enough to work in great places and with extremely smart people, first in Mexico and now in Canada. How am I supposed not to feel like an impostor? I do have experience, I guess, and I generally work hard when I find something interesting. But I guess there are a lot of people with those qualities and even more who, nonetheless, have not been “lucky” or “fake” enough to be on my situation.</p><p>This, I learned a few months back, is called <a href="http://en.wikipedia.org/wiki/Impostor_syndrome">The Impostor Syndrome</a>. And although the Wikipedia article states that:</p><blockquote>The most effective technique to overcome impostor syndrome is to simply recognize that it exists.</blockquote><p>… I keep acknowledging the fact that I’m possibly an impostor, and not that I have a psychological issue (well, at least not that one).</p><h3>Let’s deal with it</h3><p>At some point in time, though, I realized that it is not a very healthy thought for starting or finishing my day. So here is what I did. You may argue that it’s a bit cynical and I certainly won’t deny it, but well, it helps somehow:</p><p>If I am indeed an impostor, and this gets reaffirmed every time I have to deal with a problem that I barely understand or talk with people whose intelligence seems to be considerably out of my league, then I only have 2 choices:</p><ul><li>Feel bad, worse every time I achieve something. Because I don’t deserve it, or,</li><li>Try to work hard, harder every time so I eventually feel like I deserve it.</li></ul><p>It’s that easy. The idea is not to convince myself that I’m not an impostor (at least not right now). But think of it as some sort of credit: Currently I’m possibly getting a bit more than what I deserve but, at some point in time, I’ll be able to say that I now deserve what I&#39;ve got.</p><p>Truth be told, this has helped a little bit. If I get a “kudo”, or a nice email, or a praise in a code review I likely still don’t feel like I deserve it. But the amount of time it takes until I do feel like it’s fair, keeps decreasing. Thus, I think at some point in time one of the following will happen. Either:</p><p>a. A time will come when I&#39;ve paid all my “debt”, and rewards are instantly gratifying instead of an after-guilt sensation, or</p><p>b. At the very least, I’ll retire or die with the less possible amount of guilt.</p><h3>But wait, there’s more!</h3><p>The good thing about this “technique”, “mind hack” or whatever you want to call it, is not only the gradual decrease of guilt. It’s more about the fact of leaving something.</p><p>When I try to see myself from the outside, as somebody who buys the lie, the continuous improvement driven by a secret sensation of guilt could be nothing short of admirable. May I say, perhaps even inspiring. That’s an added value that could even overcome the initial guilt itself. A liar that inspires other people to do their best, to keep working hard whenever a challenge arises or even when a compliment or reward is received -disregarding the cynical fact that, in the liar’s own opinion, it may be mere luck.</p><p>I’m not saying my influence reach is on that level. And it could happen that it will never be that strong. But, who knows? If I keep working and being sort of confident on my impostor skills, it may even happen. Now, that’s a good reason for being a hard working impostor :) .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e94565153c16" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>