<?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[Queers In Tech - Medium]]></title>
        <description><![CDATA[An inclusive community of queers and allies in technology - Medium]]></description>
        <link>https://medium.com/queers-in-tech?source=rss----4b4bb9b4168---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Queers In Tech - Medium</title>
            <link>https://medium.com/queers-in-tech?source=rss----4b4bb9b4168---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:31:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/queers-in-tech" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Time to Refactor, or: Lessons of Attending a Dying Bootcamp.]]></title>
            <link>https://medium.com/queers-in-tech/time-to-refactor-or-lessons-of-attending-a-dying-bootcamp-f310ad517d18?source=rss----4b4bb9b4168---4</link>
            <guid isPermaLink="false">https://medium.com/p/f310ad517d18</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[queer]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[James McCormack]]></dc:creator>
            <pubDate>Fri, 13 Apr 2018 20:15:23 GMT</pubDate>
            <atom:updated>2018-04-13T20:15:23.389Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dhtbZon7OPebZuUO9-yyjw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/_UeY8aTI6d0?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Sergey Zolkin</a> on <a href="https://unsplash.com/search/photos/education?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I had worries when enrollment got paused and months went by with no news. I began to notice the groups of strangers that came walking through the space in the early morning hours, pointing at walls and windows. In February, the first full time staff member was dismissed.</p><p>Soon after, we were told — there would never be more students. In the first week of April, most of the previous cohorts had graduated and the full time technical staff was gone. It is now just seven of us, sitting among rows of empty desks.</p><p>Human beings are more strongly affected by our environment than we think. I have found myself feeling the energy and enthusiasm withering around me, and unconsciously, it was doing so within me, too. I found focusing on code harder and was developing a fatalistic attitude toward succeeding in my career.</p><p>Two days ago, I allowed myself to really fully stop and feel my anger and sadness and frustration at this turn of events, and then I felt the energy sucking spell of this place break. <strong>Time to refactor!</strong></p><p>I love coding. I loved it before I came here, and I am going to continue to love it. <em>I am going to love it even if my journey doesn’t look quite like how I imagined it to look, and I should never give anyone the power to take that away from me.</em> I am going to love it even if I have to work a non-technical or tech-adjacent job to pay the bills while I continue to build, learn, and collaborate with all of the new friends I have made.</p><p>For the month I have remaining here, I am going to continue coding and striving and chasing down those interviews as I assemble a back-up plan. I am beyond excited to be traveling to my hometown of NYC in May to attend <a href="http://codelandconf.com/">Codeland</a>, and to see my family. I am going to ride the subways, meet up with old friends, and make lots of new ones. And then?</p><p>If I am not happily employed as a software engineer, I will make that rent money while I attend local meet ups and work on open source projects. I may take some computer science courses at my local community college to get stronger on my CS fundamentals. I’ll take up an entirely different programming language just for fun! (<a href="https://java.com/en/download/">Java</a> and <a href="https://www.python.org/">Python</a> are high on the list. If anyone has any recommendations, I welcome them!)</p><p>I now have serious reservations about the bootcamp industry, and want to think of ways to bring people from non-traditional tech backgrounds into this world without debt. I, for one, am happy to meet with folks locally (particularly in queer and trans community) who want to go from zero to beginner level and teach you what I know, just for the joy of it!</p><p>It feels good to see this transition as the end of a chapter, and not of a story. I am so much stronger than that. I am grateful for the mentors who gave me great advice, and pushed me to write cleaner code and better tests, and to the folks on Twitter and Medium that have given me feedback and encouragement. I want to continue to get to know more of you, and I am confident that I will!</p><p><em>Want to give me a high five, your stories, or an awesome job lead? Hit me up in the comments and check out my </em><a href="https://github.com/Framinus"><em>GitHub</em></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f310ad517d18" width="1" height="1" alt=""><hr><p><a href="https://medium.com/queers-in-tech/time-to-refactor-or-lessons-of-attending-a-dying-bootcamp-f310ad517d18">Time to Refactor, or: Lessons of Attending a Dying Bootcamp.</a> was originally published in <a href="https://medium.com/queers-in-tech">Queers In Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Server Side JSON Web Token Implementation with PostgreSQL and Node.]]></title>
            <link>https://medium.com/queers-in-tech/server-side-json-web-token-implementation-with-postgresql-and-node-7278eb9dc1b2?source=rss----4b4bb9b4168---4</link>
            <guid isPermaLink="false">https://medium.com/p/7278eb9dc1b2</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[postgres]]></category>
            <category><![CDATA[jwt]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[expressjs]]></category>
            <dc:creator><![CDATA[James McCormack]]></dc:creator>
            <pubDate>Wed, 28 Feb 2018 02:16:24 GMT</pubDate>
            <atom:updated>2018-02-28T02:16:23.754Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*arvjhTc-xcxqE1aGhUSD2Q.png" /><figcaption>These are collector’s items now.</figcaption></figure><p><em>This article is going to walk through the process of creating a JSON Web Token and the Passport strategies needed on the server to authenticate a user. I am using Node.js and Express to create my server.</em></p><p>Have you heard of <a href="https://medium.com/@ste.grider">Stephen Grider</a>? He’s a software engineer and fantastically thorough teacher of many courses on <a href="https://reactjs.org/">React</a>, <a href="https://redux.js.org/">Redux</a>, data structures, and more. Whenever I need an in-depth exploration of a new library or framework, I look to see if he has taught it first.</p><p>I recently started the authentication module of his <a href="https://www.udemy.com/react-redux-tutorial/learn/v4/content">Advanced React and Redux course on Udemy</a> as a guide to setting up tokens that can be passed from a server to a React/Redux front end. Why? My team is trying to build a project with that exact setup. I excitedly started this course, only to realize that he was using <a href="https://www.mongodb.com/">MongoDB</a>, and our project was committed to <a href="https://www.postgresql.org/">PostgreSQL</a>.</p><p>Cursory searches for PostgreSQL and JWT did not show promise. So, I went ahead and figured out how to make it work myself, using the course’s overall concepts as a guide, and I am excited to share that knowledge with you. Just a caveat — this article does not include the front end setup, just the backend.</p><p>First, briefly — what is a JSON Web Token (commonly called JWT)? Traditionally, a user logs in to a service, a call is made to a backend API, and the server creates a cookie that is sent along to the front end. This cookie will often contain encrypted user data, and whenever a user attempts to access a protected resource, the credentials in the cookie will be sent along to the server in the request.</p><p>A JSON web token is similar, but functions slightly differently. It is commonly used with libraries like React, which renders components within the scope of a single page app (even if it mimics a “regular” website with tools like <a href="https://reacttraining.com/react-router/">React Router</a>.) When a user signs up, the request is sent to the back end, an encrypted token is created and sent to the browser, and that token gets checked on each subsequent request of a protected resource. This token does not contain much user data — it’s just literally an encrypted string. All changes to a user’s profile happen on the server, but the token just knows that this is a valid user.</p><p>Let’s get started! I am going to assume that you have a basic Express server and connection to your PostgreSQL database set up already. I am using <a href="https://github.com/vitaly-t/pg-promise">pg-promise</a> here, which is an important point, as I later modify the Passport callback functions to work with the returned data from the promises returned from my queries. After that, we are going to need a bunch of packages.</p><pre>npm install bcrypt jwt-simple passport passport-jwt passport-local</pre><p>Let’s start with our file structure:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/296/1*b4iCnncjHilPFL88FoOXpQ.png" /></figure><p>Don’t worry about the getAlbums and getAlbumById files in the action folder — this template is modified from an existing project and it just creates data on the page upon a successful login. Here’s a quick peek at the schema.sql file I’m working with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/438/1*ZoWWhq5SlajP9OcTcSRxsg.png" /><figcaption>I like my color theme!</figcaption></figure><p>I am going to continue working forward from our model. In the actions folder, in the signUp.js file, I am going to write and export the query that will create a user in our database:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/532/1*JxRqZIna5V6aK3t_bkdNvg.png" /></figure><p>If you aren’t bothering with Webpack on the back end, just replace that import statement with const db = require(&#39;../db) , assuming that you exported your database connection under that name. Next, let’s finish up queries by adding the following two functions into signIn.js:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/518/1*Vfs8rIfwVhkmK_ybw0ozsg.png" /></figure><p>I used db.oneOrNone here instead of db.one for a very specific reason having to do with the three options Passport gives you for authenticating a user in its callback. More on that later!</p><p>I am next going to move along to index.js in our routes folder. This is essentially the way station for all of our routes, and where we insert custom middleware that will block unauthenticated users:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*XRX_r1Z8X02AitWnSN_a3Q.png" /></figure><p>You will notice my linter yelling at me for declaring passportService and never using it. This is a false alarm. You absolutely need to require this file (which we will get to writing) in order for passport to understand which strategy you are passing to it.</p><p>Let me break down what we’re doing here a little more. Passport.js is a library used for various authentication strategies, such as OAuth (logging in with Google or Facebook, for example), JWT, and local, which essentially means that your own server is storing and serving authentication credentials. In this file, we are requiring passport, a services files that will contain our strategies, and then setting the value of requireAuth to equal our JWT strategy, which I will explain in length. Then, we are inserting that middleware before the protected route — which is, in this case, some album review pages.</p><p>Let’s move over to the controllers folder, and go into authentication.js. This is where our token will be created and we will do most of the work of signing up a new user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/805/1*IuvJeAx9AvlRRMZQLvXMDA.png" /><figcaption>Now we are getting somewhere! This is the top half of this file.</figcaption></figure><p>Here, I am requiring jwt-simple, which is the token creation package. I am requiring a config file, which just exports an object with the key of secret and a string of… whatever the heck you want. The important point here is that you put this config file into your .gitignore and never, ever commit it. If a malicious actor gets a hold of it, they can potentially decode your token. I am also importing the createUser query function from earlier, and bcrypt, which is a hashing library for passwords.</p><p>The tokenForUser function takes in a user object, and returns an encoded token that is created with a subject (conventionally called sub) set to the user’s id and a timestamp (also conventionally called iat), along with the imported secret. A magical algorithm returns a very long string out of this information. The signin function near the bottom simply takes in a logged in user and calls the tokenForUser function and sends that token along to the front end. It doesn’t do more than that because we’re going to be creating middleware with Passport that handles de-encrypting the hashed password in the relatively near future. The real fun in the file happens in the signUp function:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZLLCYJ2444Ge0Y3-CJQ73Q.png" /></figure><p>What are we doing here? We’re getting the user data from the sign up form (or Postman) that is getting passed to the server in the request body. We are declaring a number of saltRounds, which essentially decides to what power bcrypt’s hashing algorithm runs. Caution — it’s not the number of times it hashes, but actually an exponential increase. Ten used to be the standard, and now twelve is the recommended, but if you bump it up too high, it can literally take an entire day to run.</p><p>Then we’re saying if that the user sends either no email or no password, don’t even bother querying the database. Hopefully you have form validation set up on the front end, but this covers a case where that hasn’t happened.</p><p>Now we hash that password! I am using the promise version of the hashing function here, because I avoid callbacks whenever possible. This takes the user password and the salt and returns a promise that resolves to a string that we can pass into our createUser function in place of the plain text password. Then, createUser either resolves to a shiny newUser object to pass into our tokenForUser function to generate and send a token, or the database has a bad day and doesn’t send anything back, and we catch that error. Whew. Let’s export these signin and signup functions and move along.</p><p>Let’s create an authentication.js file in our routes folder, shall we? This will be nice and simple.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*-wi1KShSvXrw4QEfS4QkRw.png" /><figcaption>routes/authentication.js</figcaption></figure><p>The Authentication variable just requires the signin and signup functions we just wrote. requireSignIn is passport middleware we will write shortly that will handle the login request to the server. Note that we are setting session to false because JWTs don’t require sessions on the server. Then, we call the signup function when the user submits a request to the /sign-up post route. The /sign-in route is a little trickier — we are first going to route the user through Passport, and if they pass, they will move on to the signin function, which will pass them a token.</p><p>Take heart, for we are almost done! The last big piece of this puzzle is passport.js file in the services folder. It’s a big one, so I am going to break it in half again:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R8vA0XzhRVxXm4p_jHUbVA.png" /></figure><p>We are going to be using two Passport strategies here — one is the JWT strategy, and the other is the local. The local strategy is going to log our user in on our server. Passport expects particular information about usernames and passwords, so if the variable getting passed from the form varies from username, we need to explicitly tell Passport that. I am using the email as the username, so I passed that in. However, since I am using password for the password, I don’t need to bother telling them.</p><p>localLogin is an instance of Passport’s LocalStrategy class. It gets passed the localOptions object we defined and a callback function with the user info and done, which you will see everywhere in Passport and generally async land. Here, I am passing the user email into the verifyUser database query created earlier, and if the user exists, I am comparing the password the user entered into the form against the hashed password returned for that user from the database using bcrypt’s .compare function. This returns a promise that resolves to a boolean. If it’s true, we return Passport’s done function with null and the validUser. Passing that user object along is super important, because remember this line in routes/authentication.js:</p><pre>router.post(&#39;/sign-in&#39;, requireSignIn, Authentication.signin)</pre><p>The Authentication.signin function needs that user to make a token.</p><p>Now for the JWT Passport strategy:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*d0TDFtitAFtf_yfDMKbdXQ.png" /></figure><p>First is the JWT options object. jwtFromRequest uses the ExtractJwt method from the jwt-simple package to tell the server where to look for the JWT. In this case, it’s going to be placed in the header under authorization. This function essentially decodes the encrypted JWT and allows us to pull out whatever user id we set, in order to compare it to a real user in the database. The secretOrKey key is the string of random nonsense we placed in the secret object in our config file early.</p><p>jwtLogin is a little thornier to understand. We’re implementing a new Passport strategy designed specifically for JWTs. We’re passing it the jwtOptions we just created — saying, “here — this is how you decode the token.” The second argument is a callback function with a payload parameter and done. Payload is the unencrypted token data. Do you remember how we created that token with an object? (Okay, it’s been a while and I’ve thrown a lot at you, so let’s just share that again…):</p><pre>const tokenForUser = (user) =&gt; {<br>  const timestamp = new Date().getTime()<br>  return jwt.encode({sub: user.id, iat: timestamp}, config.secret)<br>}</pre><p>So payload.sub is equivalent to the user.id. If we were to console.log payload.iat, we would see the time the token was created printed out.</p><p>returnUserById is a database query that does what it says it does. Once the promise resolves and assuming the user is successfully retrieved, we pass that user into Passport, and send them on their merry way to protected resources!</p><p>Okay, let’s test this all out. I am going to head over to Postman and sign up a new user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bDUx1ClI-E907OWUI0L1Ow.png" /><figcaption>I almost cried with joy the first time it worked.</figcaption></figure><p>Success! Now I am going to change the route to /sign-in and just enter the email and password, and behold the beauty:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UzNxKtKVA9cvKawJaMI5Mw.png" /><figcaption>Even more tears were shed.</figcaption></figure><p>I really, really hope this will be helpful to anyone out there trying to take on this task. As always, constructive criticism and high fives are welcome!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7278eb9dc1b2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/queers-in-tech/server-side-json-web-token-implementation-with-postgresql-and-node-7278eb9dc1b2">Server Side JSON Web Token Implementation with PostgreSQL and Node.</a> was originally published in <a href="https://medium.com/queers-in-tech">Queers In Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploying a Node.js App with a Database to Heroku, for the Uninitiated, Part 1.]]></title>
            <link>https://medium.com/queers-in-tech/deploying-a-node-js-app-with-a-database-to-heroku-for-the-uninitiated-pt-1-66a651ed0f3a?source=rss----4b4bb9b4168---4</link>
            <guid isPermaLink="false">https://medium.com/p/66a651ed0f3a</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[postgres]]></category>
            <category><![CDATA[queer]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[heroku]]></category>
            <dc:creator><![CDATA[James McCormack]]></dc:creator>
            <pubDate>Mon, 29 Jan 2018 22:46:41 GMT</pubDate>
            <atom:updated>2018-01-29T22:46:50.546Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dCNRsZvF0KVjcYG8SMyOwA.jpeg" /><figcaption>You will scale this wall soon! — Photo by <a href="https://unsplash.com/photos/htVDDIigFfo?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Lance Anderson</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I may not be the first to broach this subject, but I am going to attempt to break my process down as clearly as possible, define my set-up, and hopefully provide enough pretty pictures to get you on your way.</p><p><strong>Section 0:</strong> (Because everything is zero-indexed.) First of all, congratulations. You have come a long way from declaring your first variable. Did you ever think you would have built a full stack app that queried your own database? Now you’re here, and ready to share it with the world. Treasure that.</p><p><strong>Section 1:</strong> The specs I used:</p><p>My terminal: <a href="http://ohmyz.sh/">oh-my-zsh</a>. Bash will work equally well.</p><p>The back end is written in <a href="https://nodejs.org/en/">Node.js</a>, with Express as the router and <a href="http://ejs.co/">ejs</a> for the templating language.</p><p>The database is <a href="https://www.postgresql.org/">PostgreSQL</a>, and I used <a href="https://www.npmjs.com/package/pg-promise">pg-promise</a> to connect to it. I also use <a href="https://eggerapps.at/postico/">Postico</a> as a GUI tool for Postgres, so I can obsessively refresh it and see my users populating the database in real time.</p><p>Session management happened with <a href="https://www.npmjs.com/package/express-session">express-session</a> and <a href="https://www.npmjs.com/package/connect-pg-simple">connect-pg-simple</a>, and I stored my sessions in a separate table in my database.</p><p>Finally, I used git and Github as my version control, and this is a pretty integral part of how we’re going to deploy to Heroku.</p><p>If any of these are different for you, you may be able to follow along with some of this, but there will be a point where you’ll have to go off and find docs for your variant. I’m sorry — I’ve been there and know the pain.</p><p><strong>Section 2:</strong> Preparing your app for its first day at school…</p><p>Does your project have a .env file?</p><p>If it does and you are familiar with process.env variables, you can probably scroll a bit. Otherwise, this is important!</p><p>A .env file hides the process.env variables in your project. You do NOT commit this file to git, ever. Create it in the root of your project, and then immediately go to your .gitignore file (if you don’t have one, create it now, also in root, and type node_modules with no quotation marks as the first line) and put your .env file in there.</p><p>Are you back? Good! npm install dotenv and then require it at the VERY TOP of your main server.js file like this: require(&#39;dotenv&#39;).config() Note that you have to call config at the end of the statement. You do not need to assign this to a variable like most other requires.</p><p>There is at least one that you’re going to have to create, and it has a standard name. It’s called process.env.DATABASE_URL and the caps there are intentional. The connection string that you used to connect to pg or pg-promise probably looks like this: postgres://localhost:5432/yourproject</p><p>You will now want to change that line to this:</p><pre>const db = pgp(process.env.DATABASE_URL || &quot;postgres://localhost:5432/yourproject&quot;)</pre><p>And in your .env file, do this:</p><pre>process.env.DATABASE_URL=&quot;postgres://localhost:5432/yourproject&quot;</pre><p>Here’s why, in a nutshell. On your localhost, you are telling the program to either go to your .env file to find connection string, and in case of failure, to fall back to a hard-coded version. You can omit the “or” and just direct your connection string to your .env file, and as long as everything is set up, you’re fine. Test it out either way, and it should run. Then why does it matter? Heroku sets its own process.env.DATABASE_URL to the connection string you will need to connect to the database on their servers, and this bit of code allows you to run your app on localhost or Heroku without a problem.</p><p>If you used express-session or a similar package, you will have a session secret inside of a session object. It usually looks like this:</p><pre>app.use(session({<br>  store: new pgSession({<br>    conString: process.env.DATABASE_URL || &quot;postgres://localhost:5432/yourproject&quot;,<br>  }),<br>  key: &#39;user_sid&#39;,<br>  secret: process.env.SESSION_SECRET,<br>  resave: false,<br>  saveUninitialized: false,<br>  cookie: { maxAge: 10 * 10 * 6000000 },<br>}));</pre><p>If the new pgSession thing looks unfamiliar, it’s a connect-pg-simple thing, and your configuration may vary. In any case, if your secret is exposed in your app, change it to a process.env variable, too: process.env.SESSION_SECRET=&quot;macandcheese4ever&quot;</p><p>Whew! We’re done with that. Other important little things that can cause your app to go haywire when it’s deployed: 1) If you’re making an AJAX/Fetch call to an api, make sure you’re using https instead of http. 2) Check your absolute versus relative paths. 3) I’m sure there are more, but we will learn how to discover them with heroku logs . Spoilers!</p><p><em>Next up is </em><a href="https://medium.com/@thejamesmccormack/deploying-a-node-js-app-with-a-database-for-the-uninitialized-part-2-9710b639f94f"><em>Part 2</em></a><em>, where we get started on Heroku and do some Bash scripting! I promise it won’t hurt…</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66a651ed0f3a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/queers-in-tech/deploying-a-node-js-app-with-a-database-to-heroku-for-the-uninitiated-pt-1-66a651ed0f3a">Deploying a Node.js App with a Database to Heroku, for the Uninitiated, Part 1.</a> was originally published in <a href="https://medium.com/queers-in-tech">Queers In Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploying a React App to Heroku]]></title>
            <link>https://medium.com/queers-in-tech/deploying-a-react-app-to-heroku-50c3f7626aa5?source=rss----4b4bb9b4168---4</link>
            <guid isPermaLink="false">https://medium.com/p/50c3f7626aa5</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[heroku]]></category>
            <category><![CDATA[queer]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[James McCormack]]></dc:creator>
            <pubDate>Mon, 29 Jan 2018 22:46:17 GMT</pubDate>
            <atom:updated>2018-01-29T22:46:21.982Z</atom:updated>
            <content:encoded><![CDATA[<p>I have been learning React. It’s an amazing tool, and I plan to build a lot of my frontends with it going forth. I would also love to revisit older projects and update them to have a clearly defined RESTful API on the backend that is called by my shiny new React frontend.</p><p>I have deployed simple sites to Heroku (easy!) and sites with Postgres connections to Heroku (a little harder — see my guide here), but I have never deployed a React app until today.</p><p>My first attempt was a React app with no backend — my portfolio. I made this with create-react-app, a tool that generates all of the files your React app needs to run optimally with little fuss. I knew that React worked a little differently than standard JS files and would need to be built in some way to work properly. After googling around, I discovered that the answer was right on Heroku all along — <a href="https://blog.heroku.com/deploying-react-with-zero-configuration">Deploying React with Zero Configuration</a>.</p><p>However, I was faced with a much more complicated situation than my portfolio. My coding partner and I created a full stack app last week with Node, Express and PostgreSQL on the back end and React on the front end, and we wanted to deploy it. To get the project to run on our localhost, we ran our Express server on port 3001 so that the React app would run on the default port of 3000. Then, we pointed the React app to our Express Server through a proxy line in our package.json, like this:</p><pre>{<br>  &quot;name&quot;: &quot;client&quot;,<br>  &quot;version&quot;: &quot;0.1.0&quot;,<br>  &quot;private&quot;: true,<br>  &quot;dependencies&quot;: {<br>    &quot;axios&quot;: &quot;^0.17.1&quot;,<br>    &quot;react&quot;: &quot;^16.2.0&quot;,<br>    &quot;react-dom&quot;: &quot;^16.2.0&quot;,<br>    &quot;react-scripts&quot;: &quot;1.0.17&quot;<br>  },<br>  &quot;scripts&quot;: {<br>    &quot;start&quot;: &quot;react-scripts start&quot;,<br>    &quot;build&quot;: &quot;react-scripts build&quot;,<br>    &quot;test&quot;: &quot;react-scripts test --env=jsdom&quot;,<br>    &quot;eject&quot;: &quot;react-scripts eject&quot;<br>  },<br>  &quot;proxy&quot;: &quot;<a href="http://localhost:3001/">http://localhost:3001</a>&quot;<br>}</pre><p>This worked on our local host, as long as we had both servers up and running in our terminal. React called our API through Axios calls and rendered the data we needed. I figured that this set-up would not work on Heroku. What were my options?</p><p>My first thought was that I knew how to deploy a backend app to Heroku with a database, and I also knew how to deploy a React app. Why not deploy them separately?</p><p>That was the answer, but I needed to do a little configuring to avoid CORS issues. CORS stands for Cross Origin Resource Sharing. Modern browsers will not allow you to make a call from a browser to a different server due to security issues. There is a simple npm package that will help you bridge the gap —<a href="https://www.npmjs.com/package/cors"> cors</a>. Install it into your project, and then the setup is super simple.</p><pre>const cors = require(&#39;cors&#39;);</pre><pre>const corsOptions = {<br>  origin: &#39;https://your-app-name.herokuapp.com&#39;,<br>  optionsSuccessStatus: 200<br>}</pre><pre>app.use(cors(corsOptions));<br>app.options(&#39;*&#39;, cors());<br>app.use(&#39;/&#39;, routes);</pre><p>Your setup needs may vary, so check the docs for more specific options.</p><p>After this, I made sure that all of the links in my React app’s AJAX calls were pointing to my deployed server like this:</p><pre>fetch(&#39;https://your-deployed-api.herokuapp.com&#39;, {<br>  method: &#39;POST&#39;<br>})</pre><p>How have you structured your React projects with a backend API? I would love to hear feedback!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50c3f7626aa5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/queers-in-tech/deploying-a-react-app-to-heroku-50c3f7626aa5">Deploying a React App to Heroku</a> was originally published in <a href="https://medium.com/queers-in-tech">Queers In Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploying a Node.js App with a Database for the Uninitialized, Part 2.]]></title>
            <link>https://medium.com/queers-in-tech/deploying-a-node-js-app-with-a-database-for-the-uninitialized-part-2-9710b639f94f?source=rss----4b4bb9b4168---4</link>
            <guid isPermaLink="false">https://medium.com/p/9710b639f94f</guid>
            <category><![CDATA[heroku]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[queer]]></category>
            <category><![CDATA[postgres]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[James McCormack]]></dc:creator>
            <pubDate>Mon, 29 Jan 2018 22:45:15 GMT</pubDate>
            <atom:updated>2018-01-29T22:45:15.346Z</atom:updated>
            <content:encoded><![CDATA[<h4>In <a href="https://medium.com/@thejamesmccormack/deploying-a-node-js-app-with-a-database-to-heroku-for-the-uninitiated-pt-1-66a651ed0f3a">Part 1</a>, we got our project ready for the birthing process. Now, it’s time to head over to Heroku.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4UypW9gNprFY0w898LXvcA.jpeg" /><figcaption>Just go for it! — Photo by <a href="https://unsplash.com/photos/uwQlgl4NbSg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Danka &amp; Peter</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Sign up for an account if you haven’t already. Basic accounts are free with restrictions on usage, so choose wisely. You will need to create a new app. Don’t worry about the database part just yet.</p><p>You then have two options to connect your app to Heroku. Go to the “deploy” tab in your created app and you’ll see a screen like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mM05FHk48jJ5ijTqh6CupA.png" /><figcaption>Soothing, muted colors to calm your nerves.</figcaption></figure><p>You can simply connect your app with Github, but Heroku Cli has a bunch of handy tools that I’m going to use shortly, so let’s install it. And create a SSH public key. I wish I could walk you through this, but I did this months ago and have forgotten. Ignore the “clone the repository” links on that image, as we have no Heroku repository yet. Soon, soon!</p><p>Remember those process.env variables from Part 1? We’re about to see them in action now. On Heroku, click on the ‘settings’ tab of your main app page and then on ‘Reveal Config Vars’. You will see DATABASE_URL filled in for you as the first key, with your new database connection string as the value. You will need to add your other process.env variables (like SESSION_SECRET) here, as the .env file has not been deployed to Heroku.</p><p>Next, let’s set up a git connection to Heroku. Navigate to the root folder of your project repository if you aren’t there already, and use this magic command, substituting ‘your-weird-appname’ with your new heroku app name:</p><pre>heroku git:remote -a your-weird-appname</pre><p>Congrats! In addition to your usual remote branch on Github, you now have a remote branch on Heroku. Make sure you’re on your local master branch and it is clean and updated. The next step is super easy:</p><pre>git push heroku master</pre><p>This takes longer than a regular git push because there is a build step happening. If you get “build successful” near the end of the wall of text, your app <em>might</em> be ready, but any database functionality will still need to be configured. Type heroku open in the command line and a browser window will open. If you see a landing page, great! If not, go back to your command line and type in heroku logs, which are helpfully color-coded:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IdjuUuxBULf7H7Au2xUXPQ.png" /><figcaption>I soon learned to fear the teal.</figcaption></figure><p>This is essentially how I fixed all of those little things that were keeping my basic site from working once deployed. But you’re not here for basic. You are here because your database is the lifeblood of your app. Let’s carry on.</p><p>Back on Heroku, navigate to the resources tab. Go to the “add-ons” section and type in ‘Postgres” to quickly find the Heroku Postgres database add on. Add the appropriate plan for your price (hobby is free).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M7uVL0pyLdeydPpGjJ092Q.png" /><figcaption>Heroku’s gentle colors and minimalist font are still helping, right?</figcaption></figure><p>Once you have created it, click on it. Go to the settings tab on the next page. In the ‘Database Credentials’ section, click on ‘View Credentials.’ Here is everything you need to set up and seed your database. You’re going to be copying and pasting from here to the command line (or a text editor) soon, so set your windows up for ease of making that happen.</p><p><em>Warning — if you are deploying a large app or planning on making changes to your schema in the future, you may want to stop here and learn about migrations, as they are easier to set up from the get-go. I don’t have a solid enough grasp quite yet to explain them to other people. Look for a Part 4 addendum to this series in the (hopefully) near future.</em></p><p>We’re about to do something fun. We’re going to open up a bash terminal INSIDE of our project directory on Heroku. Type heroku run bash in your terminal. Your normal (probably jazzed up) command prompt will disappear and be replaced with the old, familiar $. Take a look around, and then navigate to the folder that contains your schema.sql. We’re about to create a bash script that loads your schema.sql into your heroku database. Whether you want to type this directly into the command prompt or create a script is up to you. I’ll just tell you what to type, and remember that you’re replacing ‘host’, ‘username’, ‘db’ and ‘password’ from the values in that View Credentials tab, and therefore your script will look much longer than this one.</p><pre>psql -h host -U username -d db -w password &lt; schema.sql</pre><p>You can opt to leave off the -w flag and you will be prompted for your password after hitting enter. I did this because heroku bash does not prevent wrapping text over the command prompt when entering in a long string, and it was getting hard to read. If all went correctly, you now have tables and columns in your database.</p><p>If you have Postico, let’s configure that now to make it easier to track our success. On the entry screen, click ‘new favorite.’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/838/1*V9TmVvrHaAsxdK8fF7Ml6Q.png" /><figcaption>We’re almost there!</figcaption></figure><p>Give it whatever nickname you want, keep the port as 5432, and now go back to that “View Credentials” section on Heroku and copy the host, user, database and password into these fields. Click ‘connect’, and now you can view your database the same way you can access your local ones. If the schema file was copied correctly, you should now have some tables visible. If you need to seed your tables with data for your app to function, run the same bash script as above, but replace “schema.sql” with your seed file. If you’re using connect-pg-simple, you will have to add in that extra script from the docs that loads a table from your node_modules:</p><pre>psql -h host -U username -d database -w password &lt; node_modules/connect-pg-simple/table.sql</pre><p>I was dubious that it would work, but it did. It makes sense, in retrospect. Heroku builds your project from your file system and your package.json, so even though your .gitignore normally (should) excludes node_modules, they are being rebuilt from the versions listed in your package.json.</p><p>Moment of truth… go to your project’s shiny new url. Do something on your site that would cause data to be entered or changed. Go to Postico and click that refresh arrow. See data magically appear. Do a dance.</p><p><em>Part 3 will eventually cover database migrations. Check out </em><a href="https://medium.com/@thejamesmccormack/deploying-a-node-js-app-with-a-database-to-heroku-for-the-uninitiated-pt-1-66a651ed0f3a"><em>Part 1</em></a><em> if you missed it. Kind, constructive feedback and corrections welcome. Much love to my fellow adventurers in code!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9710b639f94f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/queers-in-tech/deploying-a-node-js-app-with-a-database-for-the-uninitialized-part-2-9710b639f94f">Deploying a Node.js App with a Database for the Uninitialized, Part 2.</a> was originally published in <a href="https://medium.com/queers-in-tech">Queers In Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using the Hired platform to land a job. Part 2: In it!]]></title>
            <link>https://medium.com/queers-in-tech/using-the-hired-platform-to-land-a-job-part-2-in-it-57f334cf3c46?source=rss----4b4bb9b4168---4</link>
            <guid isPermaLink="false">https://medium.com/p/57f334cf3c46</guid>
            <category><![CDATA[queer]]></category>
            <category><![CDATA[technical-interview]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Patrick Porche]]></dc:creator>
            <pubDate>Wed, 17 Jan 2018 01:12:32 GMT</pubDate>
            <atom:updated>2018-01-17T01:12:31.869Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*1EbHRCxi1-PdgpAU6RkAZw.jpeg" /></figure><p>Well it’s been a little over a week since I went “live” on the Hired platform and I can only say that I definitely feel like I’m “IN IT.” Since starting on the platform I’ve received 7 interview requests! One company threw me straight into a technical challenge. I had to build a tic tac toe game, logic and UI. I unfortunately only made it through the logic section and was sent a rejection email later that evening.</p><p>Surprisingly, I haven’t really been discouraged though. There is definitely something to say about keeping the volume of interviews up, for that Hired has been wonderful. I know that I will inevitably get rejections, but the whole thing seems a lot easier since I still have so many interviews coming up. On top of that, the iterations have been so rapid that I actually feel like every interview gets exponentially better.</p><p>At this point I’m still in the early stages of my process. I’ve mostly been getting through phone screens and completing coding challenges. I’ll keep you updated about what happens in the later stages… but for now, I’m pleasantly surprised. I’m hoping a few more invitation requests come through this week. I was happy to get one today! But apparently traffic generally slows down in your second week live on the platform. We will see how this proceeds.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57f334cf3c46" width="1" height="1" alt=""><hr><p><a href="https://medium.com/queers-in-tech/using-the-hired-platform-to-land-a-job-part-2-in-it-57f334cf3c46">Using the Hired platform to land a job. Part 2: In it!</a> was originally published in <a href="https://medium.com/queers-in-tech">Queers In Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Parsing Technical Documentation, or: I’m New! How Do I Read This Thing?]]></title>
            <link>https://medium.com/queers-in-tech/parsing-technical-documentation-or-im-new-how-do-i-read-this-thing-4f4094120179?source=rss----4b4bb9b4168---4</link>
            <guid isPermaLink="false">https://medium.com/p/4f4094120179</guid>
            <category><![CDATA[technical-documentation]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[queer]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Monica Estella Williams]]></dc:creator>
            <pubDate>Fri, 12 Jan 2018 21:43:40 GMT</pubDate>
            <atom:updated>2018-01-12T21:43:39.720Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been studying Javascript full time for more than a year now, and since I’ve begun I’ve come to grasp so much. I’ve learned how to write code that reads like poetry and minimizes potential for error, how to write effective tests that give me the confidence to change code without fear, and how to use some of the myriad libraries and frameworks in the Javascript ecosystem. And of course, before jumping headfirst into the fire, I learned how to use vanilla Javascript to write basic programs.</p><p>There’s a wealth of information available with the right Google search, and those of us who use Javascript are especially lucky because most of the APIs, frameworks, and libraries we use are well documented. With a bit of problem solving, we can figure out what method we should be using to manipulate the data we’ve returned from the database or how best to pass that data from one component to another.</p><p>The downside to a lot of technical documentation is that they are largely written for folks who are already in the know. That can be great for folks who are only referring to the docs to double check that they’re remembering something correctly, but can be utterly terrible for those of us who are trying to implement a technology for the first time. The process is especially rough if you’re someone who is also new to coding. Though it’s become easier, it wasn’t always smooth sailing for me to find the information I needed, even solid sources like <a href="https://developer.mozilla.org/en-US/docs/Web">MDN</a>. Here’s what I wish I had known when I started.</p><h3>I Want To Develop The Long-Term Skill!</h3><h4>Read, Read, Read</h4><p>In the same way that the only way to get good at programming is to program, the only way to really get good at reading docs is to <em>actually</em> <em>read them</em>. Take even half an hour daily to read some docs until you finish them. Documentation uses more formal and technical language than normal speech. With practice you’ll find that the particular patterns and language that these docs use, and when you need to find an answer to a problem, you’ll be able to locate what you need and understand how to use it much more quickly.</p><h4>Go Slightly Down The Rabbit Hole</h4><p>Don’t get completely lost in there, but do get clarification on concepts you don’t understand. If the section you’re reading references another method or data type, take the time to read the referenced page. Try to understand secondary concepts at least on a surface level; get just as much information as you need to make the original concept make sense.</p><h4>Start With The Easy Stuff</h4><p>You want to build confidence that you will be able to find your way through any docs. Don’t dive headfirst into the most complicated and intricate methods before you look at the simpler implementations.</p><h4>Pay Attention To Structure</h4><p>Notice how the particular docs are laid out. There will be patterns. Are optional parameters to methods denoted with square brackets? Is navigation on the left-hand side and is a methods’ list grouped by the different data types that can call the method? Are there frequent or sparse examples of how to use the code? Is there an explanation about what form each parameter to a method can take or do you have to figure that out on your own? Paying attention to these patterns will help reduce cognitive load as you learn, and some of the structure will be consistent with the documentation of different technologies.</p><h4>Make A List</h4><p>It’s likely that you’ll find methods and data types that you’ll run into over and over again during your use of the library/framework/API you’re reading through. Make note of the ones that come up often in your code and really prioritize learning those, and use your understanding of these common foundational pieces to increase your comprehension of other ones.</p><h3>I’m Actually Looking For Something!</h3><ol><li>Read the short summary of what the method is or how the data is structured. Understand at least that. Don’t dive deeply into the bulky explanation of the documentation yet.</li><li>Look at an example case. Hopefully the docs show a few different use cases. Open up your favorite REPL and type the exact code out for yourself to get a feel for how it’s used. Then, try substituting some of your code in for the code in the example. Can you see any patterns or reusable blocks here?</li><li>Now that you’ve played with the code, if you have time, read the longer explanation about how the code works. This often directly precedes or directly follows the example code given. After priming yourself twice (with the short, easier to digest summary and the example code), do you find the longer, more explicit description easier to understand?</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*yO2Q_iwxFhItts1zWC2n2A.gif" /></figure><p>Internalize these guidelines. Master them, and any blockage that you might come across will crumble at your feet. Remember, though, that the power doesn’t lie solely in how much of the docs you’ve memorized, but in being able to find the appropriate solution (in someone else’s spellbook) to vanquish the problems that are thrown at you. Did I miss your favorite method of understanding and working with technical documentation? Leave me a comment below and let’s start a conversation!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f4094120179" width="1" height="1" alt=""><hr><p><a href="https://medium.com/queers-in-tech/parsing-technical-documentation-or-im-new-how-do-i-read-this-thing-4f4094120179">Parsing Technical Documentation, or: I’m New! How Do I Read This Thing?</a> was originally published in <a href="https://medium.com/queers-in-tech">Queers In Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Searching for Validation in a Selfish World (The Obstacles of Becoming a Developer)]]></title>
            <link>https://medium.com/queers-in-tech/searching-for-validation-in-a-selfish-world-the-obstacles-of-becoming-a-developer-86f4a9bbb28e?source=rss----4b4bb9b4168---4</link>
            <guid isPermaLink="false">https://medium.com/p/86f4a9bbb28e</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[queer]]></category>
            <category><![CDATA[dev]]></category>
            <dc:creator><![CDATA[Michael Masterson]]></dc:creator>
            <pubDate>Fri, 12 Jan 2018 21:42:39 GMT</pubDate>
            <atom:updated>2018-01-12T21:42:39.025Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*vLlaykRWLmjjM8aIRuPUVg@2x.jpeg" /></figure><p>I guarantee that a good percentage of us go throughout our days with the need to prove to someone, anyone, that you are good at what you do. It feels good right? Receiving the validation that you are on the right path. Someone finally acknowledges the skills you have worked so hard to obtain. Then you go throughout the rest of your day with a little more perk in your step. Become more motivated to work harder and be better. Searching for that next compliment to be sent your way. The problem with this is that you become so reliant on the opinions of others, that the moment their opinion no longer aligns within your ideal image. You feel defeated, and go through the rest of your day, with a little black cloud floating over your head. Struggling to get back into the flow of things and regain that much required motivation.</p><p>Traveling through this path of becoming a Software Developer is a bit of a brain wrench if you ask me. If I could compare it to anything. It kind of feels like playing a never ending game of Super Meat Boy. Now if your asking yourself what kind of weird game would be called Super Meat Boy, and are expecting me to give you a brief synopsis of what this game entails? Well, since “developer” is in the title of this article, I’m going to assume you are a like me, and have become a master at google search. So… I’ll pause here until you tab back.</p><p>Okay, so now that you possibly have watched a quick video of the wonderful game of Super Meat Boy, and have an idea of where I may be going here. It’s basically a crazy hard platform game. You beat one level, only to then be presented with a harder level, which requires you to amass more skills in order to move forward. You become frustrated at times, maybe step away from the computer every now and then to cool down, maybe your so stressed out from not being able to pass this one level, that you find yourself going a little crazy. You see the resemblance now? Add onto that, the society ingrained need for reassurance from others, can lead to a roller coaster of emotions and ultimately lack of self confidence, which can in turn, limit your ability to progress.</p><blockquote><em>The best revenge is to live on and prove yourself -Eddie Vedder</em></blockquote><p>What I’m getting at here is that in order to succeed in this field. We need to learn how to accept and enjoy this crazy game, that at times, may lead us to pull out our hair. Or in my case, since I don’t have any hair, grab my fidget spinner and start spinning it like a mad man. But most of all, learning how to <strong>prove to yourself</strong> that you are exactly where you need to be, and finding that validation, confidence and motivation within yourself to continue on the path of growth and knowledge. This form of self validation puts you in the exact position you need to be, to then prove to others that you are the beautiful, amazing, talented and oh so skilled person that you are! The beauty of it all, is that you no longer have to wait for someone else to validate your accomplishments because you have already proven it to yourself. I bet you, that when the time comes and you figure this all out, you will receive that validation without spending a single bit of energy towards it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86f4a9bbb28e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/queers-in-tech/searching-for-validation-in-a-selfish-world-the-obstacles-of-becoming-a-developer-86f4a9bbb28e">Searching for Validation in a Selfish World (The Obstacles of Becoming a Developer)</a> was originally published in <a href="https://medium.com/queers-in-tech">Queers In Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using the Hired platform to land a job. Part 1: Accepted]]></title>
            <link>https://medium.com/queers-in-tech/using-the-hired-platform-to-land-a-job-part-1-accepted-f4ad426882fa?source=rss----4b4bb9b4168---4</link>
            <guid isPermaLink="false">https://medium.com/p/f4ad426882fa</guid>
            <category><![CDATA[employment]]></category>
            <category><![CDATA[job-interview]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[job-search]]></category>
            <category><![CDATA[queer]]></category>
            <dc:creator><![CDATA[Patrick Porche]]></dc:creator>
            <pubDate>Sun, 07 Jan 2018 16:41:18 GMT</pubDate>
            <atom:updated>2018-01-09T19:52:07.356Z</atom:updated>
            <content:encoded><![CDATA[<p>I woke up this morning to the BEST news! My Hired profile has been approved! If you don’t know what Hired is, it’s a platform that matches employer’s with candidates that meet their skills and technology requirements. Employer’s reach out to candidates (not the other way around) with an interview request including a base salary and job description. Then candidates have to power to accept or decline interview requests on the platform. The whole process lasts 2–6 weeks depending on company demand. AND, if I land a job through the platform, I’ll receive a $300 signing bonus!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/1*OxjStaWgWy3F5Jj9PVl4EA.png" /></figure><p>So why am I so excited!? I initially signed up for an account on Hired about a year and a half ago. I bootstrapped my projects (quite literally, I think bootstrap was in every single project), added some work experience, and expected to be flooded with interview requests. Only to get a rejection email within a day or so.</p><p>Months went by and around last summer (2k17) I reapplied. I had been at the <a href="https://medium.com/u/730ba2acfa00">Learners Guild</a> for about 4 months, had learned a ton, and felt like I was ready. But low and behold… rejection email #2 landed in my inbox within another 24hours. I knew people were being accepted so I was devastated and just gave up.</p><p>Fast forward to January 2k18… I received some sounds advice from our career outreach coordinator <a href="https://medium.com/u/7d25bd6eab8a">Kamrin Klauschie</a> and promptly put a hard end date on the endless edits and todos on <a href="http://patrickporche.com/">my portfolio</a>. I made the changes on my profile and voila!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/465/1*7PdqyldTuY-txD-elasEFg.jpeg" /></figure><p>There is a queer Jesus up there! Ultimately I know now (especially in the industry) to never put all your eggs in one basket, but for now I’m happy for this little win. And since I “go live” on Monday. I’d be happy to share a bit more about my experience on the platform.</p><p>Hired says the only accept 5% of people on their platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OMy1MkeZ9Xo1N7NalocbAA.png" /></figure><p>But there were some changes that I made that made me fairly confident that this was my time to be accepted. If you want to try out Hired <a href="https://hired.com/x/1lyf6">please use my link!</a> I’ll get a little kickback if you get a job, AND I’d be happy to take a look at your profile and give you tips on getting accepted to the platform.</p><p>Please check out this series. I’ll be posting more about my experience as it moves forward.</p><p>Happy tech-ing queers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4ad426882fa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/queers-in-tech/using-the-hired-platform-to-land-a-job-part-1-accepted-f4ad426882fa">Using the Hired platform to land a job. Part 1: Accepted</a> was originally published in <a href="https://medium.com/queers-in-tech">Queers In Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a React App out of a Static Site for a bunch of Beautiful Queers! Part 1: Hello Queers]]></title>
            <link>https://medium.com/queers-in-tech/creating-a-react-app-out-of-a-static-site-for-a-bunch-of-beautiful-queers-part-1-hello-queers-1ed36f39675f?source=rss----4b4bb9b4168---4</link>
            <guid isPermaLink="false">https://medium.com/p/1ed36f39675f</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[queer]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[lgbtq]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Patrick Porche]]></dc:creator>
            <pubDate>Sun, 07 Jan 2018 04:25:42 GMT</pubDate>
            <atom:updated>2018-01-07T04:31:58.073Z</atom:updated>
            <content:encoded><![CDATA[<p>Hope this article finds you well lovely human! I wanted to really get my head on straight and commit to getting some blog posts out. I thought of know other way to do this but to start documenting what it is I’m actually working on. I wanted to get some traction with Queers in Tech and consequently needed a refresher in React/Redux.</p><p>For the purposes of Queers In Tech I highly doubt that I’ll find any super pressing need to use Redux in this application, but I’m working on a Blockchain/Ethereum project that most definitely will. What better way to prepare than riding with the training wheels on for a few days!?</p><p>So I did a few things just to get my Hello Queers working! I’ll go over them now, but I’ll first explain a little bit about what I have to do.</p><p><a href="http://queersintech.com/">Queers In Tech</a> is (maybe not so much at the time of this reading?) a static site that I built in HTML/CSS. My business partner <a href="https://medium.com/u/d52388feefd6">Spencer Dezart-Smith</a> and I had a great idea to start bringing queer techies together, which you can read more about in our <a href="https://github.com/pporche87/queersintech/blob/master/README.md">README</a>. Long story short he was offered a job across the planet in Sydney, Australia and had to leave in 10 days 😳! Needless to say we scrambled and pushed something up to commit to our intent to start this project.</p><p>So, now I want to transform our site into an app so we can authenticate users, and provide a centralized place for content and conversation around queer tech issues. In order to do that, I had to create a client side react app, and a server side express app(which already exists and is just serving the static page).</p><p>To get started I ran npm install concurrently just so I could run my server and client at the same time on separate ports. I’ve personally done a bit of development with react, but if you’re not sure if you have create-react-app or that it may need updating you may want to run npm install create-react-app if you get an error run sudo npm install create-react-app .</p><p>After that I created my app with the name client create-react-app client . This installs a react app into a client folder. In the src folder I added to following directory structure…</p><pre>- src<br>  -components<br>    - queers.css<br>    - queers.js</pre><p>In my package.json(the one in the main directory) I added the following scripts…</p><pre><em>&quot;scripts&quot;</em>: {</pre><pre><em>&quot;client:install&quot;</em>: &quot;cd client &amp;&amp; npm install&quot;,</pre><pre><em>&quot;start&quot;</em>: &quot;node index.js&quot;,</pre><pre><em>&quot;server&quot;</em>: &quot;nodemon index.js&quot;,</pre><pre><em>&quot;client&quot;</em>: &quot;npm start --prefix client&quot;,</pre><pre><em>&quot;dev&quot;</em>: &quot;concurrently \&quot;npm run server\&quot; \&quot;npm run client\&quot;&quot;,</pre><pre><em>&quot;test&quot;</em>: &quot;echo \&quot;Error: no test specified\&quot; &amp;&amp; exit 1&quot;</pre><pre>}</pre><p>Additionally in the client package.json I had to add the following script, so that my fetch request wouldn’t require me typing out the absolute path when I called my route.</p><pre>&quot;proxy&quot;: &quot;http://localhost:5000&quot;</pre><p>Note I used port 5000 as not to interfere with port 3000 that create-react-app uses by default.</p><p>Here is the route in the index.js file, we’ll attempt to receive the json data on the client side and render it.</p><pre>app.get(&#39;/api/queers&#39;, (<em>request</em>, <em>response</em>) <em>=&gt;</em> {</pre><pre><em>const</em> queers = [</pre><pre>{id: 1, firstName: &#39;Patrick&#39;, lastName: &#39;Porche&#39;},</pre><pre>{id: 2, firstName: &#39;Spencer&#39;, lastName: &#39;Dezart-Smith&#39;},</pre><pre>{ id: 3, firstName: &#39;Michael&#39;, lastName: &#39;Masterson&#39;}</pre><pre>]</pre><pre>response.json(queers)</pre><pre>})</pre><p>Finally to render the app, I created the queer component, and queer css.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/87888f0c665240371dcbc66d23531a54/href">https://medium.com/media/87888f0c665240371dcbc66d23531a54/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/76a1cc48d3ffe53e101ba6f24ac65d62/href">https://medium.com/media/76a1cc48d3ffe53e101ba6f24ac65d62/href</a></iframe><p>Finally in App.js I put the queer component under the header.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ee6516619caf8862520a7fa41e780631/href">https://medium.com/media/ee6516619caf8862520a7fa41e780631/href</a></iframe><p>And with that Hello Queers! was born.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xrTy_YmP5Bl_RgDRkb5BGg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ed36f39675f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/queers-in-tech/creating-a-react-app-out-of-a-static-site-for-a-bunch-of-beautiful-queers-part-1-hello-queers-1ed36f39675f">Creating a React App out of a Static Site for a bunch of Beautiful Queers! Part 1: Hello Queers</a> was originally published in <a href="https://medium.com/queers-in-tech">Queers In Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>