<?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 Gaetano Venezia III on Medium]]></title>
        <description><![CDATA[Stories by Gaetano Venezia III on Medium]]></description>
        <link>https://medium.com/@gvenezia?source=rss-aa7be9eadac0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*grte-My6TRx0uox5XyGQ7g.jpeg</url>
            <title>Stories by Gaetano Venezia III on Medium</title>
            <link>https://medium.com/@gvenezia?source=rss-aa7be9eadac0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:43:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gvenezia/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[Gender, Luck, and Peak Performance: The Olympic Task of Accommodating Fairness Among the…]]></title>
            <link>https://medium.com/@gvenezia/gender-luck-and-peak-performance-the-olympic-task-of-accommodating-fairness-among-the-3c090a2d308d?source=rss-aa7be9eadac0------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c090a2d308d</guid>
            <category><![CDATA[transgender]]></category>
            <category><![CDATA[gender]]></category>
            <category><![CDATA[competition]]></category>
            <category><![CDATA[justice]]></category>
            <category><![CDATA[olympics-2024-in-paris]]></category>
            <dc:creator><![CDATA[Gaetano Venezia III]]></dc:creator>
            <pubDate>Sun, 11 Aug 2024 20:32:25 GMT</pubDate>
            <atom:updated>2024-08-13T13:47:04.672Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Gender, Luck, and Peak Performance: The Olympic Task of Accommodating Fairness Among the Exceptional</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yj3km06zASnQR2leA2qt7A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tZyZvCJcciKEYEtauhjtVw.jpeg" /><figcaption>Exceptional Performers: Imane Khelif (left) and Michael Phelps (right)</figcaption></figure><p>The Olympics present a great opportunity to explore social problems. Events like the Olympics select precisely for the exceptional among us, whether that’s the very tall, the very stoic, or the very androgynous. One naturally wonders if any of these exceptional traits create unfair advantages, especially when it comes to gendered traits.</p><p>The debate around Imane Khelif is just one recent example. Distracting from the meaningful debate, many partisan and social media takes are mere reactions from the voluntary illiterate (vol-ills). They are intensely judgmental and minimally curious. But we should be minimally judgment and intensely curious given the the variety of factors that go into excellence and the sparse literature on uncommon gender expression and athletic achievement. There’s a lot we don’t know; what we do know complicates our educated guesses. I’ve written many thoughts exploring the implications of excellence and fairness below, which basically amount to these 5 hot takes:</p><ol><li>No one is in ultimate control of the primary factors responsible for peak performance.</li><li>We don’t know much about how genetic and endocrine factors, like DSD and hormone therapy, play into peak performance.</li><li>Since there are many factors out of our control that are poorly understood, the fixation on singular factors like XY chromosomes and testosterone reveals social biases more than sincere concern for fair competition and explanation of peak performance.</li><li>There are categorical differences in performance between biological sexes, but the differences between the sexes are less discrete and more complex than we assume.</li><li>Since there are at least two recognizable categories of performance and reason to believe a third category exists due to differences in sexual development, we should have three divisions or classes. The qualifications for these divisions should be based on a variety of factors in order to balance concerns about fairness of inclusion and fairness of competition.</li></ol><p>The Imane Khelif boxing debate — about intersex, DSD (differences in sexual development), and trans athletes — strikes me as bizarre: We are quick to judge certain unavoidable conditions as key differentiators of performance and then ignore all the others. A lot of the debate has been about gendered, genetic factors which are linked to peak performance. Yet these can be hard to identify and use as the basis for disqualification; they are not sufficient factors for peak performance. We still don’t have many studies on the performance differences of trans and DSD athletes. Plus, many other factors go into being an elite athlete. While it may be difficult to identify and quantify every factor, it is easy to call out general factors. And it is also easy to see that all these factors are obviously due to luck. Even what look like choices arise from chance processes and are constrained by factors outside our control. Luck leads to peak performance.</p><p>I keep alluding to primary factors, but what are they? What factors produce an elite athlete?</p><ul><li>Being born with great genes; unique gene mutations and rare genes can give one a further competitive edge.</li><li>Having the right environment for those genes to be expressed/turn on in the most advantageous way. Everything from a conducive embryonic environment to early childhood social support to nutrition to lack of trauma throughout life.</li><li>Being born into the right family. Everything from basic shelter and sustenance to financial support and psychological support from family is key.</li><li>Having the right mental fitness: willpower, mental clarity, and other character traits enable one to compete under the highest stakes. These are engendered by genetics and social conditions.</li><li>Having the right competitive environment to be challenged by other top performers — receiving the right amount of encouragement to excel and persist, receiving the right amount of criticism to improve without losing drive.</li><li>And on and on.</li></ul><p>We can find exceptions to any one of these factors, but that usually means the other factors are over-indexed. And it still doesn’t mean we have control over our Olympic eligibility. All of these factors are due to events outside of our control. This fact is obvious for the accident of birth — where you are born and what genes you have. But even for mental fitness and personality, it’s out of our control: one develops these characteristics due to genetic expression in a socially conditioned environment. From birth, the way one is gets determined by genetics, social conditions, and random events. Any decision made is the result of values, predispositions, instincts, and available options, all of which are ultimately out of our control. What made us consciously develop our values, predispositions, and instincts? What choices were we given? Did we control these options from birth? Or did we gradually become conscious of decisions made for us and decisions we were already making unconsciously? (See Galen Strawson’s “Basic Argument” for a systematic treatment of this argument.)</p><p>So we don’t have ultimate causal control over our ability to be Olympic athletes. No amount of positive psychology or strategic thinking alone can make you an Olympian.</p><p>Because of this lack of control, it seems bizarre to me that many people want to criticize and disqualify people merely for accidental features of their lives — without consideration for fairness to those disqualified, for other primary factors, or how these factors are conclusively linked to peak performance. That’s not to say that accidental features are immune from criticism. But unless there’s very strong evidence from transparent qualification measures and indications that those measures track categorical differences in performance, criticism seems unwarranted. Calling out and policing some characteristics while ignoring other differentiators reveals social biases more than measured concern for fair competition, especially when those characteristics are under dispute, do not unequivocally equal unfair advantage, and the policing would result in a whole class of people unable to compete at all.</p><p>Seen from my view, accidental advantages is exactly what the Olympics are about. The Olympics are an incredible realization of what humans can achieve physically and mentally. The Olympics select precisely for the most exceptional cases: the diamonds in the rough, the needle in the haystack, the edge cases. The Olympics are not simple, fair competitions for humans with identical upbringings and advantages. They are highly selective and biased competitions for those with exceptional genetics and backgrounds in one of two gender categories.</p><p>Genetic “disorders” or unusual variations seem like one simple way that we could disqualify people. However, there are tens of millions of people with identifiable genetic variations, so it’s not like we are dealing with one or two edge cases. Moreover, everyone who qualifies for the Olympics is an edge case in one way or another. And it’s not like any one factor is sufficient for excellence. Genetic, social, and performance edge cases are interlinked. Separating out the unfair precursors to performance is an extremely intractable problem.</p><p>With this complex backdrop of interlinked factors, how can we identify unfair advantage and test for it? Well, we can’t. Or at least, there isn’t going to be an easy answer that pleases everyone. We are only just starting to understand how edge cases may be identified and linked to exceptional performance. There have been many intersex and DSD Olympians already. As these conditions become more destigmatized or tested, we may realize there are many more intersex and DSD athletes. I could easily see specific conditions over-indexing on athletic achievement based on hormonal and developmental advantages (and others would under-index, which is a whole other consideration for fairness).</p><p>And these complications are just for gender. Who knows how many Olympians have other kinds of genetic advantages that we don’t even know how to identify. There’s clearly something exceptional going on with Simone Biles, Michael Phelps, and Wembayana. Are there advantages unfair? What if no one else has access to their combination of advantageous genes and mutations? How clear does exceptional performance have to be before we start questioning fairness? How clear do precursors to exceptional performance have to be in order to disqualify athletes? Do we want our diagnostic tools to dictate the limits of our competitions?</p><p>These questions bring us to the very purpose of the Olympics itself — what they have been and what we want them to be in the future: Do we want to use the Olympics as an opportunity to float all kinds of exceptional people to the top of any competition without restrictions? Do we want exceptional stars or a tight pack of undifferentiated athletes? If we are going to enforce qualifications: do we want to use the Olympics as an exercise in simple, discrete demarcation of two idealized gender categories or as an exercise in attempting to find meaningful differences in scalar categories? Do we want a False Binary or Real Gradations? Do Real Gradations create too many categories to realistically accommodate? Is there a middle ground?</p><p>Trans people present us with many of these problems — challenging our sense of fairness in the social sphere with fairness in the competitive sphere. <em>(Full disclosure: I’m AMAB and went through male puberty and identify as nonbinary, which is sometimes included under the trans umbrella.)</em></p><p>There are quantifiable differences between physical ability because of genetic markers of sex, like hormones. These genetic markers lead to differences in human development. These developmental differences show up as categorical differences in physiology which then result in categorical differences in certain kinds of physical ability. See <a href="http://boysvswomen.com/">boysvswomen.com</a> for example.</p><p>That said, transitioning mediates some of these categorical differences. It can even cause disadvantages. For example, MtF people transitioning after puberty have less muscle mass to support a larger skeleton than cis women (see <a href="https://www.nytimes.com/2024/04/23/world/europe/paris-olympics-transgender-athletes.html">this NYT report on a recent study</a>).</p><p>With the right qualifying tests for genetic markers, we could allow trans women to compete with cis women in a fair, equitable manner. I don’t even think we should aim for the average cis woman’s physical ability and gender markers, because Olympic athletes are exceptional. Perhaps we should treat the problem more as a statistical range of overall performance rather than as a limit on the outer bounds of gender markers. What matters is overall performance, not whether an athlete’s testosterone level is 1nmol/L over an arbitrary limit. <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5804043/">Studies of Olympians</a> have shown that there is wide variation in testosterone levels in both men and women across different forms of competition. So just qualifications likely need multifactor models tailored specifically for each sport.</p><p>What does this statistical model or category look like? I’m not sure, but it probably includes an endocrine profile and some performance tests to gauge lung capacity, muscle mass, etc. I recognize that I’ve mostly kicked the can down the road with a cliched call for “more research.” But that’s also where the state of trans studies and sports medicine is at. There’s too much we don’t know. And from a philosophical perspective, I think we can dismiss simple qualifications: there’s enough we do already know to show that peak performance is a complicated result of interlinked factors outside of our ultimate control.</p><p>Maybe this expansive, statistical view of performance means that a higher proportion of trans women athletes compete than cis women athletes. But so long as there are no categorical differences by which trans women completely dominate a sport, such proportions do not necessarily indicate unfairness. Remember, we already expect that some genetic variations, social backgrounds, and other primary factors of performance will over-index in Olympic athletes. We are only aiming at certain forms of fairness within statistical ranges, not fairness of identical genetics and backgrounds.</p><p>From that idea, here’s my proposal for three divisions, which would apply to sports where there are categorical differences in performance due to gendered development:</p><ol><li>Open/men’s division (for anyone, with maybe some interesting allowances for testosterone supplementation under a certain limit)</li><li>“Women’s” division (for cis women, trans people, intersex/DSD conditions that can pass gendered qualifications that use many factors, like testosterone and muscle mass, to reduce noisy signals and allow for a better approximation of the statistical range of performance)</li><li>Unusual genetic characteristics division (for anyone that doesn’t pass gendered qualifications in the women’s division and is disadvantaged in the men’s division due to differences in sexual development)</li></ol><p>This proposal seems to best preserve some just treatment for everyone while still acknowledging categorical differences in ability. What I want to avoid is over-inclusion: allowing everyone to compete in any division. I also want to avoid over-<em>exclusion</em>:<em> </em>unnecessarily disqualifying trans women when they are within the statistical range of cis women’s performance.</p><p>Trans people have been dealt a bad hand when it comes to social acceptance and their own physiology. We should be working hard to understand and respect them by showing care not to over-exclude in our qualifications for competitions. At the same time, cis women have only recently received fair treatment and representation in comparison to men. So we should be working hard to maintain a fair playing field for cis women.</p><p>If we want the Olympics to be a simple division of idealized gender categories, we will disqualify hundreds of millions of people. If we want the Olympics to be a simple inclusion of all people, we will disadvantage hundreds of millions. We need meaningful inclusion and qualifications. Finding middle ground, acknowledging nuance, and withholding harsh judgment are the principles that can get us there. And regardless of what criteria we decide on to best accommodate everyone, it will still be true that top performers have a confluence of advantages that most of us definitionally do not have. Luck’s role in gender and peak performance creates the exceptional world we all live in. Let’s appreciate it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c090a2d308d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Pragmatic Philosopher’s Code: How I taught myself programming and got a job in software…]]></title>
            <link>https://medium.com/@gvenezia/a-pragmatic-philosophers-code-how-i-taught-myself-programming-and-got-a-job-in-software-3b6ad1f57a34?source=rss-aa7be9eadac0------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b6ad1f57a34</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[career-paths]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Gaetano Venezia III]]></dc:creator>
            <pubDate>Sun, 21 Aug 2022 17:14:02 GMT</pubDate>
            <atom:updated>2022-08-21T17:35:30.298Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Pragmatic Philosopher’s Code: How I taught myself programming and got a job in software development</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0vWBdWEsQcVYCv9xTOTOag.jpeg" /><figcaption>Detail from an Anthony James sculpture</figcaption></figure><p>I’ve talked to many people about my process of transitioning from academic philosophy to the software industry, so I thought a standalone article with linked resources could be a useful reference. This article is meant to explain my process, but it’s not at all meant to be a step-by-step guide to anyone’s success. I’m one data point. Read other people’s stories and distill the main insights. Imho, the most important takeaways are to <strong>do your research, understand your skills, values, and preferences, treat the job search like a full-time job, and consistently create visible examples of the skills you’re building.</strong></p><h3>Background</h3><p>I’m a fully self-taught web developer with an academic background in philosophy. I’ve been working as a developer since 2018 and have worked in three different types of positions: front-end web developer, data visualization developer, and full-stack developer. My current position is SDE III (software development engineer) at Expedia, where I work on our ads platform. I’ve been promoted a few times and now work in a mid-level role where I mentor new hires and serve as tech lead on smaller projects. In the last few years I’ve also conducted 50+ interviews. These experiences have validated some aspects of my own career development and revealed other areas where I could have done better.</p><p>I started learning HTML and CSS in undergrad in order to get a better understanding of the internet. At that time, I had no intention of becoming a professional developer. I didn’t take any classes, learn computer science fundamentals, or go to any meet-ups. I just made a few static websites with <a href="https://www.codecademy.com/learn">Codecademy</a>. I graduated with a BA in philosophy and went on to pursue an MA in philosophy, preparing for a career in academia.</p><p>While I enjoyed grad school, a career in academia gradually seemed less interesting and less feasible. My philosophical interests in <a href="https://plato.stanford.edu/entries/pragmatism/">American Pragmatism </a>aren’t in high demand, simply getting through the MA required long, tedious hours of study (which is still no guarantee of acceptance to a good PhD), and the market for academic positions is oversaturated. So I decided to explore my options in better job markets. I took career assessment tests, read about professions I was interested in, researched market trends, and considered different short-term plans for life after graduation. Software development seemed the most promising and feasible career path: I’m fascinated by technology, I love logic, math, and pragmatic problem-solving, the tech sector is booming, and I could teach myself for free.</p><p>By the end of my second year I had made substantial progress on my thesis and only had one semester left of my MA, so I began focusing much of my free time on coding. This allowed me time to further explore different languages, technologies, and the industry in order to make sure that I would enjoy full-time coding after graduation.</p><h3>The Tech Job Market</h3><p>Software development consistently ranks as one of the fastest growing and most in-demand professions (U.S. Bureau of Labor Statistics <a href="https://www.bls.gov/ooh/computer-and-information-technology/software-developers.htm">1</a> and <a href="https://www.bls.gov/ooh/fastest-growing.htm">2</a>, <a href="https://www.bloomberg.com/news/articles/2018-03-08/demand-for-programmers-hits-full-boil-as-u-s-job-market-simmers">Bloomberg</a>). However, software development is a large and varied industry. Some technologies are in very high demand (e.g. JavaScript, Java, Python); some are quickly losing demand (e.g. Objective-C, Flash, Perl).</p><p>I’ve also learned that while all levels of developers are in demand, junior-level developers often don’t have the most crucial requirement for a job: past experience. Furthermore, most jobs “require” a CS degree (This is usually an HR requirement that is treated more as a nice-to-have by developers—unfortunately, HR usually makes the first round of cuts).</p><p>I talked to countless professional developers and recruiters about how to overcome these barriers to entry. Their resounding advice was to <em>prove</em> skills by building project, hosting these projects on your website, and putting the code on Github. So that’s <a href="http://gvenezia.com/">exactly</a> what I <a href="https://github.com/gvenezia">did</a>.</p><p>When considering what kind of position and technologies to focus on, I looked through trend reports for the relative popularity and demand. I used the reports from <a href="https://www.thoughtworks.com/radar">Thoughtwork</a>, <a href="https://insights.stackoverflow.com/survey/2018/">Stack Overflow</a>, and <a href="https://research.hackerrank.com/developer-skills/2018/">Hackerrank</a>. I chose to focus on JavaScript as my main language because it has consistently ranked as the most in demand language and is crucial to my area of interest: front-end web development. My other two main languages are HTML and CSS—also in high demand and necessary for web development.</p><p>Since I’m most interested in working as a front-end developer, I also used more specific guides and reports, like the <a href="https://frontendmasters.com/books/front-end-handbook/2018/">Front-End Developer Handbook 2018</a>.</p><p>As I explored programming, I narrowed my focus to front-end development because of my interest in design, user experience, aesthetics, because of the availability of free, quality resources, and because I actually like fiddling with CSS properties for hours (CSS is a language for styling elements on a webpage). Front-end demand and salaries are comparable to the average software developer position so it was also an economically reasonable choice.</p><h3>Timeline and Strategy</h3><p>The last 6 months of grad school, I devoted anywhere from 2 to 20 hours a week to coding. After graduation and winter holidays, I spent at least 50 hours a week coding. I tried to commit to <a href="https://github.com/gvenezia">Github</a> everyday during this period. I also went to about 1 networking event a week to get a feel for the Chicago job market and to start making connections.</p><p>After two months, I had a decent portfolio of projects on my website and github, so I started dedicating 4–7 hours a day to my job search. I would code the rest of the day then go to networking events at night. During this time I was averaging 3–4 networking events a week. I maintained my 50+ hour week.</p><p>Below, I explain what I worked on in more detail during these different periods.</p><h4>Technical</h4><p>Codecademy introduced me to HTML and CSS back in 2013. I didn’t start coding again until summer 2017, when I started slowly going through <a href="https://www.edx.org/course/cs50s-introduction-computer-science-harvardx-cs50x">Harvard’s CS50 course</a>, which is taught in C (an older, technically-demanding language that is good for learning the technical details that modern languages like Javascript hide behind abstraction; It’s also the basis for C++ and influential for many modern languages). I highly recommend this course for teaching the fundamentals of computer science since a chief complaint about self-taught coders and bootcamp grads is that they don’t have an understanding of CS concepts (esp. data structures and algorithms). The problem sets were really difficult for me to get through, but I learned a ton form this experience and got my first taste of the immense satisfaction that comes with fixing an infuriating bug and finishing a difficult problem. I also read Deitel &amp; Deitel’s <a href="http://index-of.es/C++/C%20How%20to%20Program.pdf"><em>C: How to Program</em></a><em> </em>in order to reinforce the concepts and to learn the material in a different medium.</p><p>After finishing CS50, I started focusing on web development, especially JavaScript. I started with <a href="https://www.freecodecamp.org/">Free Code Camp’s front-end curriculum</a>. The curriculum and structure is similar to professional bootcamps but it is completely free and self-paced. This difference comes with its advantages and disadvantages. Paid bootcamps offer external motivation, dedicated mentors, structure, soft skills and job search training, and immediate access to a professional network. However, bootcamps are often costly (~10k-20k), have questionable placement data, teach skills but not fundamentals of programming, and often have incentives that are misaligned with their students’ needs.</p><p>I found this <a href="https://thefirehoseproject.com/developer-guide">guide</a> helpful when deciding whether to go to a bootcamp. I was considering going to a bootcamp eventually, but wanted to try everything on my own first. <a href="https://techbeacon.com/app-dev-testing/coding-bootcamps-wont-make-you-developer-heres-what-will">Articles like this</a> gave voice to some of my main worries.</p><p>Midway through Free Code Camp I started two courses on Udemy: Colt Steele’s “<a href="https://www.udemy.com/the-web-developer-bootcamp/learn/v4/overview">Web Development Bootcamp</a>” and Anthony Alicea’s “JavaScript: Understanding the Weird Parts.” The web dev bootcamp was great because I was able to quickly build many projects to my portfolio. However, I worried about the tutorials leading to a false sense of competency, so for each project I added my own features and sometimes built the whole project before watching the tutorial.</p><p>Alicea’s course was good at the time, but ultimately I got the same information (and much much more) from Kyle Simpson’s <em>You Don’t Know JavaScript </em>book series (which is entirely <a href="https://github.com/getify/You-Dont-Know-JS/blob/master/README.md">free on github</a>). Simpson explains the fundamentals concepts of JavaScript in order to dispel common misconceptions. For example, many call JavaScript an object-oriented language, but Simpson argues that this is not technically correct and that the attempt to make JavaScript act in this way leads to more error-prone code.</p><p>I highly recommend finding a similar resource for your language of choice. I was able to mention some of these low-level details in interviews; these comments were received very positively by interviewers and led to some interesting conversations. Now having conducted over 50 interviews myself, I can see how rare and valuable it is to have this in-depth knowledge of a language.</p><h4>The Job Search</h4><p>When I started looking for jobs, I focused on the following:</p><ul><li>searching through job listings (mostly on LinkedIn, but I tried various other places like Dice, Indeed, StackOverflow, Hired, and local job boards)</li><li>updating my resume for different types of positions (front-end, software developer, web developer, etc.)</li><li>designing my resume and business card to match the style and content of my website</li><li>writing a generic cover letter with lots of specific details that I could pick and choose to cater to the job requirements and company culture</li><li>and perhaps most important of all… networking!</li></ul><blockquote>A mountain of research shows that professional networks lead to more job and business opportunities, broader and deeper knowledge, improved capacity to innovate, faster advancement, and greater status and authority.</blockquote><blockquote>—<a href="https://hbr.org/2016/05/learn-to-love-networking">Harvard Business Review</a></blockquote><p>After reading statements like this over and over and then doing some research, I realized the importance and power of networking. However, as an introvert that prefers to have a small group of close connections, networking didn’t have any inherent appeal. Plus, it’s way easier to just quickly send out 25 generic applications online (which I did once through an automated site). It felt like I was covering a lot of ground through such digital tools, but many of the jobs weren’t actually a good fit and my generic resume/cover letter weren’t doing me any favors. I unsurprisingly received no replies to those 25 applications.</p><p>So I tried to shift my mindset to think about in-person networking more as a game. The Harvard Business Review article quoted above has some great strategies for learning to approach networking in a more satisfying way. It wasn’t comfortable, but it didn’t need to be. Some interactions didn’t lead to anything; the job market is large and complex.</p><p>Even though difficult and discouraging at times, networking led me to a loose group of people to consult and share knowledge with. I learned about various other networking events, technologies, learning resources, and job opportunities through networking.</p><p>One of these recommendations actually led to my first job as a web devev intern. One connection recommended a job fair and another gave me a discount code to go for free. Luckily, a branding and design company I had been wanting to work for, <a href="https://vsapartners.com/">VSA Partners</a>, was at the job fair. I met with a recruiter and some designers from the company, which gave me a chance to convey my excitement for the role, form personal connections, and learn about the company culture and work environment. After a quick follow-up email the next day, I got scheduled for an interview!</p><h3>Applications</h3><p>I applied to 55 different positions. Thirty positions seemed like a good match for the culture I wanted and technical skills I had. For these positions, I spent extra time researching the company and modifying my resume and cover letter to match the phrasing of the job posting and the company’s website. I wasn’t lying about any of my qualifications or values (why would I set myself up for a position I wouldn’t like or wasn’t prepared for?). Rather, I was expressing why I was interested in the company and role, expressing my qualifications in language they could immediately understand, focusing on my relevant qualifications, and showing that I knew what the job required.</p><p>I contacted a few recruiters that were recommended to me, but they ultimately didn’t lead to any applications. Recruiters that contacted me first were obviously taking a shotgun approach and never offered anything relevant.</p><p>80% of the applications were for internship/apprenticeship positions and 20% were for entry-level positions. I figured I had a better chance at getting an internship because there is less risk to hire me. The company wouldn’t be committing to anything long term and wouldn’t be paying me as much. I never figured out whether this was a good strategy—I never got any strong advice against or for it. The full-time positions that I did apply to were ones for which I was a great fit or had a strong recommendation from a connection.</p><p>I applied for about three weeks and then sent a follow-up email to all of the places I had applied. Most of the recruiter’s emails weren’t listed, so I did some research by searching for “HR tech talent lead recruiter acquisition” and the companies name on LinkedIn. Few listed their emails publicly, so I would then use <a href="https://hunter.io/">Hunter</a> to get their email. I had maybe a 15% response rate. This felt sketchy to me, but it was recommended and it worked: two of these responses moved me to the interview stage. Indeed, I’ve rarely had interview candidates reach out to me after an interview, so it definitely will differentiate you and signal interest.</p><h4>Interviewing</h4><p>In total, I was advanced to the interview stage for three positions. One interview had a take home short answer test with questions that indicated strong desire for experience with a LAMP stack (Linux, Apache, MySQL, and PHP). While I had experience with most of the technologies on the original job posting itself, I had basically no experience with a LAMP stack, so I withdrew my application, telling them that I didn’t think I’d be a good fit.</p><p>For the second company I was given an hour-long coding challenge on Hackerrank. I did well given that I had never made the specific algorithms and data structures they were testing for, but understandably, I wasn’t advanced to the final round of interviews.</p><p><em>Aside: In retrospect, these kinds of Hackerrank challenges are standard fare for interviews, so I probably would have improved my chances for most interviews had I spent more time on data structures and algorithms. Focusing on these technical skills and practicing via </em><a href="https://leetcode.com/"><em>leetcode.com</em></a><em> made the difference in getting my second job at Expedia and getting interviews at Amazon, Nintendo, Nordstrom, and Oracle. More importantly, knowing hundreds of algorithm patterns helped me feel at ease in these interviews. Once you’ve done enough algorithms and interviews, you’ll notice a distinct pattern and approach to solving these problems. This skill at designing efficient algorithms is also generally useful as a problem-solving technique in coding jobs and even outside of the tech world.</em></p><p>For the last company, the first interview was a 20-minute HR interview where I was told more about the position and asked about how I taught myself to code, challenges and success in my projects, and my responses to interpersonal conflict.</p><p>The second interview was with VSA Partners. It consisted of 15 informal minutes with the HR person I had originally interviewed with, and then 30 minutes with one of the lead engineers who would serve as the mentor for the summer internship. I was again asked about my background and projects, but I gave more technical answers that highlighted the workflows and technologies that I was using. We then talked about the specifics of the internship and I asked for feedback on my resume and application. I left feeling really good about the interview and company. I followed up with a thank you email and also brought up some questions that we hadn’t had time for during the interview. After a week, they called me back and told me I had gotten the internship!</p><p>For those who have interest in the area, are self-driven, enjoy math, logic, or systems problems, and can network well, self-teaching is a viable path to a software job. Learning to code takes a lot of work, discipline, and time, but programming is such a rewarding skill to develop and there is an abundance of free or cheap resources. And even if you don’t want to pursue software development, learning a little bit of code and how computers work will give you invaluable insight into the future of work and culture.</p><p>For simplicity, I’ve left out discussions of finances, nutrition, social life, sleep, exercise, and mental health. However, I believe the time I spent on these areas were crucial to my ability to learn how to code and enjoy the process.</p><p>I’ve also left out compensation, but I’m happy to talk about what I make and how that has changed over time. I will just say that the local labor market makes a huge difference in compensation. While software developers are in demand almost everywhere, different cities can lead to widely disparate compensation packages.</p><p>There’s plenty more I could talk about, so please send me a message if you’d like to talk further. I’m happy to share any knowledge or insight.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b6ad1f57a34" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Notes on the history of singular ‘they’]]></title>
            <link>https://medium.com/@gvenezia/notes-on-the-history-of-singular-they-793de17225fc?source=rss-aa7be9eadac0------2</link>
            <guid isPermaLink="false">https://medium.com/p/793de17225fc</guid>
            <category><![CDATA[dictionary]]></category>
            <category><![CDATA[linguistics]]></category>
            <category><![CDATA[non-binary-identity]]></category>
            <category><![CDATA[cultural-criticism]]></category>
            <category><![CDATA[lgbtq]]></category>
            <dc:creator><![CDATA[Gaetano Venezia III]]></dc:creator>
            <pubDate>Mon, 25 Apr 2022 17:28:41 GMT</pubDate>
            <atom:updated>2022-04-25T17:28:41.008Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m non-binary. Here on my brief thoughts upon reading <a href="https://public.oed.com/blog/a-brief-history-of-singular-they/?fbclid=IwAR0NjFGg2-Ao2nFxrLGzfn6bDLgaNt4vCMYlds1TA2WdT2ELCdDPakv1XX0">this short history of singular ‘they’ provided by the Oxford English Dictionary</a>.</p><p>To be fair, the use of singular ‘they’ has changed contexts over time. Many people are still adjusting to using ‘they’ pronouns for a friend or family member who is right in front of them.* I get that.</p><p>I’m non-binary and prefer ‘they’ pronouns for myself. I know many people who have switched their pronouns to ‘they’ or something else. And yet many of us have had to adjust and occasionally still slip up.</p><p>That said, the frequent objection that singular ‘they’ is ungrammatical doesn’t hold up when you look at the history of English. And it especially doesn’t hold up when you consider the various approaches to creating a dictionary and standard grammar for standard usage.</p><p>There isn’t one standard. Only the standards which best balance established usage and new usage remain useful.</p><p>Language changes. That’s how ‘you’ became you; that’s how I became them.</p><p>— — —</p><p>* There’s also political and moral pushback on the identities behind ‘they’ pronouns, but I’m not super interested in those objections. I’ve yet to hear an interesting argument made in good faith (I’m open to hearing them, but my bar is pretty high at this point).</p><p>The usual appeal to science is superficial because science is an evolving field itself; much of the emerging research shows the importance of gene-environment interaction and the non-deterministic complexity of human behavioral development. We also just don’t understand that much about the brain or genes period. I’d also argue that most aspects of gender we care about are social norms which are learned and have no obvious connection to genes.</p><p>The usual appeal to the usefulness of knowing people’s biological sex in all settings is superficial and uninteresting, too. Why do I need to know what someone’s genitalia are when meeting them or looking over documents? When that info is needed (for medicine, dating, etc.) it can be provided easily and privately in the same way that sexual preference, chronic diseases, and special accommodations are shared currently.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=793de17225fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>