<?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 Alicia Rae on Medium]]></title>
        <description><![CDATA[Stories by Alicia Rae on Medium]]></description>
        <link>https://medium.com/@arrowsrp?source=rss-d67e3cf83b85------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*KTeO7NlVZpTnO9_L</url>
            <title>Stories by Alicia Rae on Medium</title>
            <link>https://medium.com/@arrowsrp?source=rss-d67e3cf83b85------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:59:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@arrowsrp/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[How Skills I learned in Fraud Analysis Helped Uncover My Family's History.]]></title>
            <link>https://medium.com/@arrowsrp/how-skills-i-learned-in-fraud-analysis-helped-uncover-my-familys-history-7f8b5b6468b8?source=rss-d67e3cf83b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f8b5b6468b8</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[fraud]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[genealogy]]></category>
            <category><![CDATA[history]]></category>
            <dc:creator><![CDATA[Alicia Rae]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 01:47:54 GMT</pubDate>
            <atom:updated>2026-11-11T17:26:50.392Z</atom:updated>
            <content:encoded><![CDATA[<h3>How Skills I learned as a Fraud Analyst Helped Uncover My Family History.</h3><p><em>I had no idea at the time I was investigating possible banking fraud, that the skills I was learning (research, data management, and using AI-powered tools) would become instrumental in tracing my family history over 200 years and counting.</em></p><figure><img alt="Black and white photograph of the author’s great grandmother and in-laws." src="https://cdn-images-1.medium.com/max/954/1*deBxWvklD0N-SJHU22mlNg.png" /><figcaption>A ~1920 photograph of my great grandmother (third from the left) along with her sister and sister’s in-laws.</figcaption></figure><p>When I was younger, I used to see my skills and interests as scattered and lacking focus. Part of my personal and career growth has been to see the connections between seemingly disparate interests and realize the common threads between areas where I’ve found enjoyment and success. One of these threads being the success I found as a fraud analyst and as an amateur genealogist researching my family history.</p><p>It may be difficult to believe that success as both a fraud analyst <em>and</em> genealogist rely on a shared underlying skillset but that has been my experience. Both are fields where advances in AI technology has advanced processes, but still require an understanding of how to best utilize these tools, and how human insight to interpret their output for maximum benefit.</p><ol><li><strong>Utilizing AI powered tools</strong></li></ol><p>What’s the frontier of artificial intelligence advancement got to do with exploring the past? Well, up until recently, doing genealogical research meant scouring records from the pre-digital era requiring expertise, interpretation, and time-consuming manual searching and indexing of handwritten records.</p><blockquote>“With handwriting recognition technology, what previously took years to index, now will only take weeks.” — <a href="https://careers.ancestry.com/blogs/ancestry-corporate/ancestry-to-apply-handwriting-recognition-artificial-intelligence-to-create-a-searchable-index-of-the-1950-u-s-census">Ancestry Blog</a></blockquote><p>Ancestry’s proprietary AI tool and others have made huge amounts of information accessible at a rate never before possible. In fraud detection, similar models are processing huge amounts of data on financial transactions and user behavior to recognize assign a numbered score to each transaction that indicates the likelihood that is it fraudulent.</p><p>In both these areas, knowing and having the best tools for the job make accomplishing the goal possible in a way it has never been before. Just as I can now go to a handwritten archive and type in a name or phrase, and find results for that value, I can type in a user’s name or email and receive an instant score of how trustworthy that email or user is. Fraud detection and genealogy are both a search for truth, and in these searches AI powered tools are a light in a formerly dark room.</p><p>2. <strong>Understanding the limitations of technology</strong></p><p><em>While AI has revolutionized historical research and fraud detection, just as important as understanding what these tools are capable of, is understanding their limitations.</em></p><p>Human error and bad data is one weak link. Exhausted census workers might record incorrect information, or misspell names (e.g. Maggy vs.Maggie). Similarly, I frequently noticed users making legitimate payments late at night frequently mistyped their own name or address. Recognizing these patterns helped me when distinguishing between fraud and human error.</p><p>As far as limitations of the tools themselves, I also found with the particular fraud scoring model my company used, first names and surnames that were one or two letters, (e.g. O, Le, Pi) often resulted in a high fraud score. Lack of understanding of these shortcomings could not only have led to missing actual fraud, but could even lead to inequitable handling of financial transactions of people with non-anglican surnames.</p><p><em>Human error aside, AI cannot account for the messy complexities of the human experience such as the historical context of emancipation in the 1860’s that lead my family (like many other newly freed people) to abandon the surname they had used up ’til then, essentially turning them into ghosts.</em></p><figure><img alt="An exerpt from an old document that reads: “Q. Was he ever known by the name of Beck? A. They said when they went to enroll us that they didn’t know us by the name of Hill, but to put down my owner’s name, and that was Beck.”" src="https://cdn-images-1.medium.com/max/1024/1*IGyzVot5YK0nphc4Qn0hXg.png" /><figcaption>A sworn affidavit given by my great-great-great grandmother to the federal government in 1901 explaining why her surname differed from her documents.</figcaption></figure><p>My family did not fall off the face of the earth in 1863. They simply changed their surname from the one that had been forced upon them by bureaucracy and the institution of slavery.</p><p>During my research, I also discovered the propensity for handwriting recognition models to confuse two consecutive letter “r”s with the letter “m”. Discovering this, replacing the double “r” in my surname with an “m” did yield results that I would not have discovered had I assumed AI-powered searches were foolproof.</p><figure><img alt="An image of a handwritten census record from 1896." src="https://cdn-images-1.medium.com/max/1024/1*6hdUy1ZzVtSoh4N1zsPr_A.png" /><figcaption>A handwritten census record from 1896 ‘Indian Territory’ that my ancestors appear on. Prior to these records being digitized it would have taken countless hours to find their names.</figcaption></figure><p>3. <strong>Managing the data</strong></p><p>While detecting fraud and researching genealogy are similar to putting together a puzzle in that they require large amounts of time to put together small pieces of information which by themselves are meaningless, but together make a bigger picture. They differ from the traditional puzzle in the sense that, the puzzle pieces do not come neatly bundled in a box. Not only must you go searching for the puzzle pieces, some pieces of the pieces will be impossible to access, they will look like they belong to the puzzle but do not, and some will be pieces that you already have.</p><figure><img alt="An example of a simple family tree template from freefamilytreetemplates.com" src="https://cdn-images-1.medium.com/max/1024/1*enEz0s-A5d3kXGilry9KOg.png" /><figcaption>An example of a simple family tree template.</figcaption></figure><p>This is where data management comes into play. While AI has can makae access to data much easier than before, the sheer amount of data can be overwhelming if not handled properly. Documentation is vital, because if you do not keep track of your findings, research can quickly get muddled.</p><p>Bad data can skew results and obscure the picture of both fraud detection and genealogy. One suspicious transaction pulled from multiple sources can lead to an inflated fraud score. One bad record from multiple sources can make false facts appear credible. Data cleansing is vital to ensuring that decisions are well informed. The consequences of false fraud detection can be grave for customers such as late fees, credit score impacts, or vital service interruption.</p><p>While at the end of the day, fraud detection and genealogy are two very different disciplines with vastly differing goals, the shared determination to dig deep, question results, and unearth hidden truths are what helped me discover so much about my family that I never would have gone searching for, if I hadn’t began researching strangers to protect their financial assets.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f8b5b6468b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’m not applying for 50 dev jobs a day, and why you shouldn’t be either.]]></title>
            <link>https://medium.com/@arrowsrp/im-not-applying-for-50-dev-jobs-a-day-and-why-you-shouldn-t-be-either-b4f8ffb3911c?source=rss-d67e3cf83b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4f8ffb3911c</guid>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[career-change]]></category>
            <dc:creator><![CDATA[Alicia Rae]]></dc:creator>
            <pubDate>Sat, 14 Oct 2023 20:40:56 GMT</pubDate>
            <atom:updated>2023-10-14T21:42:56.223Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gy9nDIhx2XyXmlYdaiY1VQ.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@keira-burton/">Keira Burton</a></figcaption></figure><p>I recently saw a LinkedIn post that said the reason most boot camp graduates aren’t finding jobs is that are not applying enough (at least 50 positions a week). My response was instant incredulity. I gave some thought as to why that figure seemed so unreasonable in my own job search. Here’s what I came up with.</p><blockquote>The first reason I can think of is time/energy.</blockquote><p>Applicants are almost expected to tailor their resume for individual employers. With such high numbers of applicants for most junior developer positions (many receive well over 1k applicants), I would almost say it’s nearly impossible to get noticed without doing so. Tailoring your resume for 50 employers a week beyond copying and pasting the company name would consume an unfeasible amount of time and mental energy. Time and energy that could be spent sharpening my skills, learning new frameworks, or building projects that will make me a better more well-rounded developer.</p><blockquote>My reason, preserving my mental health. It’s a marathon, not a sprint.</blockquote><p>While someone who is flooding the airwaves with their resume may get more response initially, the pure number of rejection emails coming from sending out that many resumes a day sounds just plain depressing.</p><p>The job search can last weeks, or even months for some, and a big part of being successful is persistence. That means avoiding burnout. All those rejections for jobs you weren’t that interested in to begin with, can slowly chip away at your confidence and positive attitude toward your job search.</p><p>Third, the most impactful employment advice I’ve ever been given came from my mom to me at 19 years old.</p><blockquote>“Be as choosy about them as they are about you.” I stand by that approach to this day.</blockquote><p>With that in mind, I take the time to research a company (policies, mission, work culture, values, philanthropic activities or lack thereof, etc.) before even applying.</p><p>Come the end of that process (which involves checking out the company website, looking for any available news or blogs, and seeking reviews from either Glassdoor or existing employees), what remains is a relatively small number of positions (average 5–10) that I’m qualified for and align with my values.</p><p>While that number is nowhere near what a job coach would recommend, I think in the long run I’m ok with that.</p><blockquote>I have had the experience of being called for an interview, being really excited, then after reviewing the details of the position or company feeling my excitement level drop off a cliff.</blockquote><p>I want to be certain that if I receive a call, that excitement and thrill for the possibilities remain throughout the interview process and ideally into my employment there. I want to be able to answer truthfully and enthusiastically if I’m asked in the interview, “Why &lt;insert-organization-name&gt;?”</p><p>As an entry-level engineer with no prior work experience, I know many would advise me to take what I can get, but I believe in the long run sticking to my values and going for quality over quantity will pay off.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4f8ffb3911c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using server-side logic to make forms more functional]]></title>
            <link>https://medium.com/@arrowsrp/using-server-side-logic-to-make-forms-more-functional-684be956986e?source=rss-d67e3cf83b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/684be956986e</guid>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Alicia Rae]]></dc:creator>
            <pubDate>Fri, 21 Oct 2022 16:16:32 GMT</pubDate>
            <atom:updated>2022-10-21T16:59:46.469Z</atom:updated>
            <content:encoded><![CDATA[<p>In the first two phases of my education with The Flatiron School, the focus was on front end development. Many front end developers know the pain of trying to translate API data that’s often formatted for tables into the type of data that we can show on a front end interface that will be understood by a user.</p><p>The opposite is also true, collecting data on the front end and translating it into data that is the proper data type and format for the database. The beauty of full stack design, is being able to manipulate data from both ends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KiXXcjHZUSS01z5FiQ00yw.png" /></figure><p>I ran into this problem in building my first full stack project Skate!, where users need to be able to check into skatepark locations and include what type of category they are, or what type of wheels they are on (e.g. skateboard, inline skates, roller skates etc.) On the front end, users expect to choose from a list of category names strings, but the database expects to receive an integer category_id to be stored as a foreign key in the users table.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CxlcoXxqn3hdlmPpsuKFeg.png" /></figure><p>Therefore, the route below will result in an error for the simple reason that our users table is expecting integers as values for our skatepark_id and category_id columns, and our form is sending it a string.</p><pre>@user = User.find(params[:id])</pre><pre>@user.update(<br>checkedIn: true,<br>skatepark_id: params[:skatepark_name],<br>category_id: params[:category_name]<br>)</pre><pre>@user.to_json</pre><pre>end</pre><p>We could hard code in these relationships into the event handler in the front end, like code snippet below,</p><pre>function onCategoryChange (e) {<br>if (e.target.value === &quot;skateboard&quot;) {<br>     setCategoryId(1)<br>} else if (e.target.value === &quot;roller skates&quot;) {<br>     setCategoryId(2)<br>} else if (e.target.value === &quot;inline skates&quot;) {<br>     setCategoryId(3)<br>} else if (e.target.value === &quot;scooter&quot;) {<br>     setCategoryId(4)<br>} else {<br>    setCategoryId(5)<br>     } <br>};</pre><p>but there are problems with that solution. For one, we run into a scalability issue if in the future we expand our app to accept more categories as new wheels make their way to the skatepark such as rip-sticks, circular skates or other categories, this would break our code unless we do the hard work of manually updating.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4YLSMaHmq65gee9dK8yYtg.png" /></figure><p>In addition, all this client-side logic will make our app more and more sluggish as we add more and more permutations.</p><p>A much better solution is to go straight to the source and bake this logic right into our API route and perform it on the server-side. The first step is to add a class method called get_id_by_name to our skatepark.rb and category.rb models that queries our Skatepark and Category class by name and returns their id.</p><pre>/models/skatepark.rb</pre><pre>def self.get_id_by_name name</pre><pre>@park = self.find_by(name: name)</pre><pre>@park.id</pre><pre>end<br></pre><pre>/models/category.rb</pre><pre>def self.get_id_by_name name</pre><pre>@category = self.find_by(name: name)</pre><pre>@category.id</pre><pre>end</pre><p>Now that our class variables are in place, in our application_controller.rb file, we can call the get_id_by_name method in our custom patch route, and pass it the parameter that is being collected from the form, the <em>names</em> of the skatepark and category. We store the return value of that method into its own variable, and pass that variable to our .update method so that the table receives an integer rather than a string.</p><pre>patch “/users/checkin/:id” do</pre><pre>@user = User.find(params[:id])</pre><pre>@skatepark_id = Skatepark.get_id_by_name(params[:skatepark_name])</pre><pre>@category_id = Category.get_id_by_name(params[:category_name])</pre><pre>@user.update(<br>checkedIn: true,<br>skatepark_id: @skatepark_id,<br>category_id: @category_id<br>)</pre><pre>@user.to_json</pre><pre>end</pre><p>Success! Now regardless of how many oddball categories get added to our categories table, our custom route will always be able to find the corresponding id and update our user’s data accordingly!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=684be956986e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to sniff out fraud as a job seeker]]></title>
            <link>https://medium.com/@arrowsrp/how-to-sniff-out-fraud-as-a-job-seeker-b7785cec66ab?source=rss-d67e3cf83b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7785cec66ab</guid>
            <category><![CDATA[fraud-detection]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[job-search]]></category>
            <category><![CDATA[fraud]]></category>
            <dc:creator><![CDATA[Alicia Rae]]></dc:creator>
            <pubDate>Tue, 18 Oct 2022 17:16:06 GMT</pubDate>
            <atom:updated>2022-10-18T17:16:06.210Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SrmN0wWNw0JTLVthKxG_Bg.png" /></figure><p>I was contacted by someone yesterday claiming to have found my resumé online and inviting me to an interview. Had they actually looked at my resumé they would have known I used to work in fraud detection.</p><p>Detecting fraud is about looking at the available information, trying to contextualize why things may not add up, and making an educated guess based on the information you have and the risk involved vs. benefit.</p><p>Here was my thought process in sniffing out this fraudulent hiring manager:</p><p>🚩 I was contacted without applying to this company.</p><p>While I have been contacted based on resume’s I’ve left around the internet before, it does automatically raise my suspicion levels. Yellow flag.</p><p>🚩 They contacted me via text rather than email.</p><p>I have communicated with recruiters and hiring managers via text before, but this is usually after an initial email introduction.</p><p>🎉 I looked up the company, it was a legitimate company with employees and job postings.</p><p>Great!</p><p>🎉 I was able to find an active LinkedIn profile of the individual contacting me listed as a hiring manager for the company they claimed to work for.</p><p>Even better!</p><p>🚩 While there were tons of job listings, I didn’t see the position I was being contacted about.</p><p>🚩 The job listing was a bit too perfect. Remote, pay was slightly above average.</p><p>This was another yellow flag, such jobs exist, but I always remember the old adage, “If it sounds too good to be true, it usually is”. This is also a method used by fraudsters to make individuals ignore red flags. For a well paying remote position it is usually not necessary for companies to reach out to applicants to fill such a desirable position.</p><p>Ok, at this point there are some yellow flags along with some confirming details. After going back and forth I couldn’t think of any other independent methods of confirmation, and accusing the hiring manager/recruiter contacting you of being a fraudster is not a good foot to start of on.</p><p>At this point I could message the LinkedIn profile, and ask if they were the one I was speaking with, but not everyone responds to random LinkedIn messages, and with this being a great opportunity I did not want to miss out! So instead I responded to the alleged hiring manager:</p><p>Me: Would you kindly share a link to the job posting for this position?</p><p>Hiring manager: Here are the details of the position! Pay range, hours, etc.</p><p>Hm, I did gain some information, but nothing that confirms the identity of this individual. This could be a red flag, or just what seems like a faster way to share information.</p><p>So I try a different tack. Since I am interested in the position, I decide to lay all the cards on the table.</p><p>Me: Could you kindly reach out to me via a company email, so that I can confirm the company you are with? You can never be too careful.</p><p>🚩🚩🚩Hiring manager: …</p><p>Case closed. At this point I can’t ignore the sound of all the red flags fluttering in the breeze, and I don’t engage with them further.</p><p>Of all the tools you can use to prevent being scammed, research, cross-confirmation, asking questions, one of the most valuable tools for detecting fraud is your gut. If something doesn’t feel right, trust your instincts. A legitimate individual will be more than happy to verify their identity with you in whatever way makes you feel comfortable.</p><p>Be careful out there fellow jobseekers! Good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7785cec66ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Art of Asking Questions]]></title>
            <link>https://medium.com/@arrowsrp/mastering-the-art-of-asking-a-question-68570ab6cd0f?source=rss-d67e3cf83b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/68570ab6cd0f</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[softskillsimprovement]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <dc:creator><![CDATA[Alicia Rae]]></dc:creator>
            <pubDate>Tue, 26 Jul 2022 23:18:45 GMT</pubDate>
            <atom:updated>2022-07-27T07:22:18.066Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*usmAK35u6X1FU10P8UQs0w.jpeg" /></figure><p>The idea of asking questions being an art may sound silly to some, but as I grow as a software developer, I’m finding it is one of the most valuable skills I’ve acquired over my professional career. From the time we learn to speak, we begin asking questions. All parents are well acquainted with that perpetual head-scratcher, “Why?”</p><p>As we grow older, and the information we seek becomes more specific, figuring out the right questions to ask can also become more complicated. This is when the ability to ask questions shines as the key skill it truly is.</p><p>During my time as a tiny home builder, I stumbled across an insane amount of people who were willing to take their time to help me understand a process, or plan a project, whether it was setting up a solar-powered energy system, a self-contained plumbing system, or finding a way to put a yacht hatch on the roof of a school bus.</p><p>This is one of the many points of crossover I’ve found between tiny house building and software building.</p><p>When people are generous enough to offer their time and expertise expecting nothing in return, part of showing my respect and appreciation for them includes coming equipped to learn. Here are five methods I have employed to master the art of asking a question.</p><ol><li><strong><em>Enter the conversation as informed as possible.</em></strong> Gather whatever easily digestible information you can on the subject before the conversation begins. You will save time by bypassing explanations of basic terms and can pose more targeted and useful queries. Brainstorming potential questions to ask is also a great idea.</li><li><strong><em>Subtract your ego from the equation.</em></strong> If I have seen anything get in the way of what should be a free and easy exchange of knowledge, it is ego. There is no shame in not knowing, and a good mentor will want to see you progress, not make you feel inferior for not knowing everything. The need to always project knowledge and confidence can lead to glossing over areas of confusion or lead the information supplier to mistakenly think you don’t really need their insight.</li><li><strong><em>Have the end goal in mind and have a plan for how to express it.</em></strong> Give as much and as detailed information as possible on your end goal. Don’t deem anything irrelevant. Explain how you think the subject might work, and any initial information you have about it in depth, using multiple methods of communication like photos, drawing diagrams, etc.</li><li><strong><em>Take notes and confirm the information you’re being told.</em></strong> As important or relevant as the advice someone is giving you may be, it does not prevent your brain from confusing or forgetting key parts. Write down and confirm key points so that you don’t need to ask for repeat of information or misunderstand.</li><li><strong><em>Express gratitude.</em></strong> Never feel or behave as if entitled to someone’s time or help. Show and tell them how appreciative you are for their time!</li></ol><p>Being able to ask clear questions about complex ideas, spare no relevant detail, and confirm the information being communicated definitely proved difficult at first. Shyness, lack of preparation, and lack of experience communicating technical ideas were a few of the barriers I had to overcome in the quest to learn to ask questions. But I can say that solidifying and employing these methods in my queries about software development has paid off in spades.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68570ab6cd0f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everything is boxes.]]></title>
            <link>https://medium.com/@arrowsrp/everything-is-boxes-db224df9784a?source=rss-d67e3cf83b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/db224df9784a</guid>
            <category><![CDATA[tiny-house]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Alicia Rae]]></dc:creator>
            <pubDate>Mon, 27 Jun 2022 18:55:52 GMT</pubDate>
            <atom:updated>2022-07-05T22:56:23.094Z</atom:updated>
            <content:encoded><![CDATA[<h3>Lessons from tiny-home building I use in software engineering.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1WB5SwxF5Drn9cmMbOtP_A.jpeg" /></figure><p>Looking at my latest two resume entries, Tiny Home Build, and Software Engineer, I consider how for some, that might evoke confusion. While I can certainly imagine someone thinking those two activities seem completely dissimilar, I’m here to tell you that they’re not!</p><p>While I could go for far too long about the parallels between my journey building an off-grid tiny home on wheels and that of becoming a software engineer, from a high level, here are six areas where my experiences building in the physical, mirror that of building in the virtual (DOM that is):</p><ol><li>Planning what type of structures to will build. Knowing the limitations of my tools and my own knowledge, while being open to innovative possibilities. Nothing can be planned esoterically, but rather requires looking at the growth and evolution of the project as a whole.</li><li>Matching which tools are best for the individual task at hand, and staying in the loop about new tools that may expand my building capabilities.</li><li>Building in a way that takes into consideration my future self or others that may need to disassemble, add to, or maintain the project. Understanding how adhering to conventions makes for a more universal understanding.</li><li>Using experimentation, testing, revising, refining, and of course, failing to find solutions. Realizing that the most artful solutions are the simplest, and accepting that there will always be improvements to be made.</li><li>Avoid attaching my ego to plans and ideas in a way that makes it easy to overlook missteps and to seek help from reliable resources when I recognize I am out of my depth or just plain stuck. Building up trusted communities of like-minded people to help expand my pool of knowledge.</li><li>Lastly, breaking what seems like enormous undertakings into simple essential functions. Learning to look at the desired end result and reverse engineer solutions to make those activities possible. Hence the realization, that everything is just boxes.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NHNj4vIkxTY0Wuy_X0YvKA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VPwqEcQ_FGbmr7vMODK9pA.png" /></figure><blockquote>Whether it’s a complex piece of furniture, or a complex website or app, they are all comprised (sometimes literally) of small boxes that each have unique functionality. I may be following instructions, or building creating something innovative, but if all goes well, those boxes come together to form something beautiful and functional.</blockquote><p>I hope it has provided a small insight into how I evolved from a builder of physical structures, into a builder of software! I also hope it inspires anyone who is pivoting to or considering pivoting into tech to consider what crossover skills they are bringing with them from their life experience. What unlikely connections are there along the path to where you are today?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db224df9784a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Community Powered By Programming]]></title>
            <link>https://medium.com/@arrowsrp/community-powered-by-programming-82daaa57d097?source=rss-d67e3cf83b85------2</link>
            <guid isPermaLink="false">https://medium.com/p/82daaa57d097</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[black-in-tech]]></category>
            <dc:creator><![CDATA[Alicia Rae]]></dc:creator>
            <pubDate>Wed, 06 Apr 2022 19:06:19 GMT</pubDate>
            <atom:updated>2022-04-06T19:06:19.221Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ywPVVjFypVZLBagg0JWY5A.jpeg" /></figure><h4><strong>The WHY of Cul-de-sac?</strong></h4><p>I have always found great value in community. Some of the most enriching parts of my life are the result of completely random meetings and interactions, during which I discovered a neighbor/friend who was willing to share knowledge, skills, or gear/tools with me. This led me to the question, how could I use programming to facilitate these types of interactions?</p><p>I recalled my upbringing living in a cul-de-sac, and how the unique arrangement of a cul-de-sac where all houses faced one another, facilitated getting to know our neighbors and allowed our community to easily identify and meet each other’s needs. For instance, my neighbor, who was a mechanic, noticed the brakes on my bicycle were loose, grabbed his tools, and fixed them for me. Or, us kids seeing our elderly neighbor’s dogs always barking at us from behind her fence and offering to take them on walks for her. Living on a regular linear street, it seemed much harder to establish those types of relationships with neighbors.</p><p>While I can’t rearrange the physical shapes of neighborhoods, my project app, Cul-de-sac is meant to allow neighbors to face each other figuratively, and see and meet each other’s needs and those of their community as a whole. Users of the Cul-de-sac app can both post and view:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EHSF5oR-qMZmzxbuYHf7Jg.gif" /></figure><ul><li>events (e.g. food or clothing drives),</li><li>calls to action (e.g. support a struggling local business),</li><li>personal or community needs(e.g. trash cleanup), or</li><li>resources (e.g. knowledge/skill/tool sharing).</li></ul><p>But that’s just the beginning…</p><h4>How Class Constructor Methods Make Cul-de-sac as diverse as community needs.</h4><p>The variety of post types listed above, demonstrate the variety of types of data keys and values the form will need to handle. While it currently handles just one type of post (events), the use of parent classes and sub-classes allows the flexibility to handle both the common and unique pieces of information that a user will enter depending on the type of event they are posting.</p><p>The PostEvent class below receives data from the form input.</p><p>My project uses forms in conjunction with class constructor methods to instantiate data objects that are posted to the JSON file when the user submits the form.</p><pre>class PostEvent {<br>            constructor(title, facilitator, image, goals, date, startTime, startTimeAmPm, endTime, endTimeAmPm){<br>            this.title = title;<br>            this.facilitator = facilitator;<br>            this.image = image;<br>            this.goals = goals;<br>            this.date = date;<br>            this.startTime = startTime+startTimeAmPm;<br>            this.endTime = endTime+endTimeAmPm;<br>            this.participants = 0; <br>            } }</pre><p>As the app is expanded to accept more types of events, the data objects will need to change. For instance, a person who is attempting to post their skills as a community resource will not need to enter a date or time. A more generic parent class can be used to instantiate the data that all the posts share in common, such as the title, facilitator, image, and goals.</p><pre>class Post {<br>            constructor(title, facilitator, image, goals){<br>            this.title = title;<br>            this.facilitator = facilitator;<br>            this.image = image;<br>            this.goals = goals;<br>            } }</pre><p>With the parent superclass in place, a subclass can then be used that extends the Post class while including other pieces of information unique to the specific post types.</p><pre>class Event extends Post {<br>            constructor(title,facilitator, image, goals, date, startTime, endTime, participants){<br>            super(title, facilitator, image, goals)<br>            this.date = date;<br>            this.startTime = startTime;<br>            this.endTime = endTime;<br>            this.participants = 0; } }</pre><p>This child class makes use of the super method, the invocation of which will instantiate the title, facilitator, image, and goals value, which will be inherited by the Event subclass before instantiating the properties unique to the Event class. These constructor methods and super methods will make handling the variety of data keys and values much easier than manually creating objects and using interpolation as the app grows in functionality and complexity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82daaa57d097" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>