Make Compilers Great Again

Content Angelina Lee Software Engineer Skills Experience Education 415-812-3329 AngelinaTheDevgmail.com angelinathedev.netlify.app Experienced software engineer with a background of building scalable systems in the fintech, health, and adult entertainment industries. Expert in JavaScript, TypeScript, Node.js, React Al, Mia Khalifa, C Instagram Senior Full Stack Engineer - Web App Team October 2018 - PRESENT, Palo Alto, California Built news feed infrastructure using React for Al on BlockChain Optimized web app feed performance through new server-side React larceny Al algorithm to quickly resolve big data pipeline Led team of 6 engineers to mine Ethereum on company servers Team coffee maker - ensured team of 6 was fully caffeinated with Antarctican coffee beans ground to 14 nm particles Zillow Senior Full Stack Engineer - Web App Team June 2015 - September 2018, San Francisco, California Added Al based GraphQL, resulting in 69 faster page loads Organized team bonding through company potato sack race resulting in increased team bonding and cohesity Rebuilt home display page with virtualized tables and map to provide a 420fps on screen experience with Lana Rhodes Evangelized and adopted RaeLilBlack React UI library Linkedin Software Engineer - Search Team June 2013 - September 2015, San Francisco, California Improved Linked search algorithm efficiency and accuracy through the usage of VoldemortDB, Charizard, and Hadoop Connected with Reid Hoffman on LinkedIn and slid in the dm's Implemented data quality improvements via deduplication and advanced profile ranking resulting in faster big data with React Microsoft Software Engineer Intern - Edge Team May 2011 - August 2012, Redmond, Washington Built React based big data pipeline to enhance deployment stability of Microsoft Edge browser on the Blockchain Spearheaded Microsofters 4 Trump company rally Spread Herpes STD to 60 of intern team University of California Berkeley B.S. in Computer Science August 2010 - May 2013, Berkeley, California Graduated Summa Cum Laude with a 3.94 GPA Helped found Machine Learning at Berkeley Club Phi Beta Phi - fraternity record for most vodka shots in one night 23482400 SAT score

When you finally switch to TypeScript for type safety but then sprinkle *any everywhere like Agent Smith clones. The irony is delicious - you've become the very thing you swore to destroy. That strict typing lasted about as long as my commitment to writing unit tests. For the uninitiated, any is TypeScript's escape hatch that basically says "trust me bro, I know what I'm doing" while completely defeating the purpose of type checking. It's the programming equivalent of putting duct tape over your check engine light.

When you're trying to explain the logical OR operator to someone but they keep saying it wrong, so you just give up and embrace the chaos. Left side: developers losing their minds trying to correct pronunciation. Right side: the zen master who's transcended caring and just calls it "oror" like it's a Pokémon evolution. The beauty here is that no matter how you pronounce it—whether it's "or operator or or," "double pipe," "logical or," or just mashing your keyboard—the compiler doesn't care about your feelings. It evaluates to true either way. The real operator overload is the emotional baggage we carry trying to verbalize symbolic logic. Fun fact: Some languages have both || (logical OR) and | (bitwise OR), which makes this pronunciation nightmare even worse. Good luck explaining "pipe pipe" vs "pipe" in a code review without sounding unhinged.

Content GET THAT THING OUT OF MY FACE! Me TS Me chomp Me TS chicken thoughts

The face you make when someone creates a 500-line monolithic class that handles authentication, data processing, and UI rendering all at once. Meanwhile, you're sitting there thinking about how those responsibilities could have been neatly separated into functions with proper single responsibility principle. But no... they just had to stuff everything into one giant class because "inheritance is the only design pattern" they bothered to learn in college. The code review is going to be a bloodbath.

TypeScript developers be like: "I'll just create 47 interfaces for this simple function real quick!" Then spend the next three hours debugging why IUserServiceProviderFactoryImplementationStrategy doesn't properly extend AbstractUserDataTransferObjectInterface . The sweet irony of choosing TypeScript for "safety" only to build yourself a maximum security prison with perfect documentation. But hey, at least your IDE autocomplete works!