<?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 Stefanos Ugbit on Medium]]></title>
        <description><![CDATA[Stories by Stefanos Ugbit on Medium]]></description>
        <link>https://medium.com/@stefanosu422?source=rss-bfa46709ff51------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*ktsHAU2Y7oU73LFZE9bqVw.jpeg</url>
            <title>Stories by Stefanos Ugbit on Medium</title>
            <link>https://medium.com/@stefanosu422?source=rss-bfa46709ff51------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:04:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@stefanosu422/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[The Plain-English Guide to Webhooks]]></title>
            <link>https://levelup.gitconnected.com/the-plain-english-guide-to-webhooks-7befe8daf987?source=rss-bfa46709ff51------2</link>
            <guid isPermaLink="false">https://medium.com/p/7befe8daf987</guid>
            <category><![CDATA[webhooks]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Stefanos Ugbit]]></dc:creator>
            <pubDate>Wed, 01 Apr 2020 18:45:12 GMT</pubDate>
            <atom:updated>2020-04-24T14:54:55.970Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="image showing how webhooks work server sending data automatically to user phone in contrast to request response cycle." src="https://cdn-images-1.medium.com/max/396/1*_X8lkX31ovfPriBq-9akRA.png" /><figcaption>image showing an example of how webhooks work in contrast to a traditional request/response cycle.</figcaption></figure><p>Web-apps have increasingly become so interconnected through the use of APIs which are essential for sharing data across different web applications. They have also become essential especially for Software-as-a-service (SaaS) applications. Users want updates fast and regularly; to address this need developers have added webhooks to their APIs. Web-hooks is the process in which data from an API can be delivered without having to receive a request for each response. This post gives an overview of what web-hooks are, why you should include it in your web app and how to add it in your API.</p><p><strong>What are Web-hooks?</strong></p><p>A Webhook is a method for one app to update other applications with real-time information. Webhooks operate on the concept of <em>event reaction </em>(no need to call me, I’ll call you when I have something new), avoiding the need for the (user) client-side application making constant requests to the server for real-time data.</p><p>A more concise definition, for those who are of a more technical persuasion, is:</p><p><em>“Webhooks are user-defined HTTP callbacks which are linked to a web app and are triggered by specific events.”</em></p><p>A webhook delivers data to other applications in real-time so that data is received immediately. <em>What is an API?</em> API stands for Application Programming Interface, but what does that mean? APIs can share data and functionality. For example, you might use Google Maps API to look for museums by location or name, pulling out a lot of data from each place. Then you can use that data and display it to your UI user interface.</p><p>Contrary to typical APIs where the user would need to make an action (request) to get data from the server. A request isn’t required for a webhook it just sends the data when it’s available. For example, when you subscribe to your bank you’ll get a push notification to your phone when you make a transaction on your card or if your balance is below a certain amount. This makes it a better experience for the user and developer because it reduces server costs and makes the web app more efficient.</p><p>This is the core concept of webhooks. To use a webhook, you need to register with a URL with whichever company that is providing the service. The URL is a place within your application that will accept that data and do something with it. When there’s some new information the webhook will send it to your URL. With webhooks, you can get push notifications when certain events happen on the server. For example, when you subscribe to your bank you’ll get a push notification to your phone when you make a transaction on your card or if your balance is below a certain amount.</p><p>The first step in using webhooks is given the webhook provider a URL where you deliver your requests to. This can be done by configuring your backend or API. This means that you need to set up a URL in your app that’s accessible from the web. The vast majority of webhooks will POST data as XML or JSON which is a form of data that you receive from the server.</p><p><em>So what do webhooks look like?</em></p><p>An API calls the server-side app which provides the client-side app with end-point URLs that the client can call. The server-side might expose the following API endpoint URLs for a simple chat application.</p><pre><br>POST /messages createNewMessage <br>GET /messages/{messageId} readMessage<br>POST /messages/{messageId}/comments postComment<br>GET /messages/{messageId}/comments/{commentsId} readComment</pre><p>If the client-side app wants to post a new message to the server, the client-side app makes a call to the server to <em>POST /messages</em></p><p>Also if the client-side app wants to read a comment that has been posted to a particular message on the server, the client-side application calls <em>GET/messages/{messageID}/comments/{commentsID}</em></p><p>The messages and comments are created and stored on the server’s database, and read from the server database, using the server-provided APIs (end-point URLs).</p><p>Webhooks, it is the client-side application that provides the server-side application with a URL to call, and the server-side application calls that URL, whenever the server has been updated with some new information that needs to be sent to the user. <em>Essentially a webhook is just an end-point URL provided by the client-side application to the server-side application.</em> In the case of our simple chat app example it may look like this:</p><p>{ “newCommentWebhook” : “https://clientchat.com/webhook/newComment&quot; }</p><p>A webhook is nothing but a simple client-side provided end-point URL. This end-point URL has to be passed by the client-side application to the server-side application at some point before the webhook call by the server-side. If we want the server to notify the user whenever a new comment has been posted against a particular message. In this instance, whenever a new comment is posted to the database, the server-side application should (after posting the comment to the database) call the above webhook URL, to let the client-web app know that a new comment has become available.</p><p>Using webhooks, the server can notify the client of new events that occur (i.e. a new message has been posted). The API needs to be configured in the API end-points such that there is a placeholder, that allows webhook URL to be passed from the client-side apps. This can be done through the server-side API by providing a parameter for webhook URLs. The server-side application should have some mechanism of storing the client provided webhook end-point so that it can be called by the server-side when required. Thus in our example the server-side API request the body should have some parameter, where the client-side application can include their webhook URL.</p><p>Webhooks are an essential tool to include due to the ever-growing interconnectivity in our web apps. It is a way for users to receive updates immediately and saves server costs. If you want your web application to be more dynamic and flexible in serving the needs of today’s users than adding a webhook in your web app will be paramount.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7befe8daf987" width="1" height="1" alt=""><hr><p><a href="https://levelup.gitconnected.com/the-plain-english-guide-to-webhooks-7befe8daf987">The Plain-English Guide to Webhooks</a> was originally published in <a href="https://levelup.gitconnected.com/">Level Up Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI and Refugee Resettlement]]></title>
            <link>https://medium.com/@stefanosu422/ai-and-refugee-resettlement-9118e5b75d7b?source=rss-bfa46709ff51------2</link>
            <guid isPermaLink="false">https://medium.com/p/9118e5b75d7b</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[refugees]]></category>
            <dc:creator><![CDATA[Stefanos Ugbit]]></dc:creator>
            <pubDate>Tue, 20 Aug 2019 17:06:58 GMT</pubDate>
            <atom:updated>2019-08-20T17:07:44.629Z</atom:updated>
            <content:encoded><![CDATA[<p>The AI software program called Annie MOORE was named after the first immigrant registered at Ellis Island in 1892. MOORE stands for Matching and Outcome Optimization for Refugee Empowerment. The software uses what’s known as the matching algorithm to place refugees with no ties into the United States if they have family or community support then they are placed within that specific location.</p><p>According to Hebrew Immigrant Aid Society (HIAS) “Of the 496 employable refugees that HIAS resettled in 2017, 159 were able to secure some form of employment in the first 90 days. However the data shows that had Annie been used to automatically match refugees to new homes, over 200 — or over 20 percent more — would have found a job in this same time frame.”</p><p>Annie’s algorithm is based on a machine learning model that takes in huge amounts of data from past refugee placements, which it refines to make better future recommendations. There are certain variables that it takes into making these placements such as work experience, education level, age, and the number of languages spoken.</p><p>Annie places refugees were their most likely to succeed. The software can swift through thousands of data points and arrive at a decision instantly. This drastically cuts down the time it takes to process and resettle refugees. According to the UN Refugee Agency, “less than 5 percent of the 1.2 million refugees who were in need of resettlement last year were actually placed.”</p><p>There are concerns that as Annie continually improves that it will take over humans jobs that help resettle refugees. Although as Annie makes recommendations the final decision is made by a person. There are many positive results from using Annie it cuts down on routine cases that people have to do so they can focus on special cases that require more time and nuanced approach.</p><p>Overall the use of AI programs can be very beneficial but we should be wary of the biases that are built into these tools because of the lack of differences in perspectives, experiences, and people that are building these tools.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9118e5b75d7b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Observer Pattern]]></title>
            <link>https://medium.com/@stefanosu422/the-observer-pattern-166def0a7479?source=rss-bfa46709ff51------2</link>
            <guid isPermaLink="false">https://medium.com/p/166def0a7479</guid>
            <dc:creator><![CDATA[Stefanos Ugbit]]></dc:creator>
            <pubDate>Thu, 08 Aug 2019 18:16:01 GMT</pubDate>
            <atom:updated>2019-08-13T15:09:04.426Z</atom:updated>
            <content:encoded><![CDATA[<p>There are three main types of software design patterns structural, creational, and behavioral. Design patterns are important because they are used to help us solve commonly reoccurring design problems within a specific context.</p><p>The observer pattern is a behavioral pattern in which an object, called the subject, maintains a list of its dependents, called observers, and notifies them automatically of any state changes, usually by calling one of their methods. In which the observers react to that change.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/854/0*PVR_-fqsm67_6q58.png" /></figure><p>In this illustration, the object (subject) maintains a collection of objects (observers) which gets notified when changes to the state occur. Then the observers based on that notification change their behaviors accordingly.</p><pre>import React from &#39;react&#39;;<br>import { observable } from &#39;mobx&#39;;<br>import { observer } from &#39;mobx-react&#39;;<br><br>@observer class MyComponent extends React.Component {<br>  onClick = () =&gt; {<br>    this.active = true;<br>    // ...<br>  };<br><br>  @observable active = false;<br><br>  render() {<br>    return (<br>      &lt;a onClick={this.onClick} disabled={this.active}&gt;click works only once&lt;/a&gt;<br>    );<br>  }<br>}</pre><p>This is an example of the observer pattern in React. Here we’re passing a boolean into the @ component. When the observable changes the render method will be reevaluated by React. Passing objects with observable properties make it easier to control the state of a child component both from within itself and from its parent.</p><p><strong>The advantages of the observer pattern are:</strong></p><ol><li>It allows sending data easily to other objects without changing the subject or observer classes.</li><li>The Observers can be added or removed at any time.</li><li>It supports loose coupling between objects that interact with each other.</li></ol><p><strong>The disadvantage of the Observer pattern is:</strong></p><ol><li>If not implemented correctly the observer can add unnecessary complexity and lead to performance issues.</li></ol><p>Overall the benefits of using the observer pattern outweigh the drawbacks and it is very useful within a specific design context. So the next time you create your application consider implementing a design pattern that best fits the needs of your application. This will help with performance, debugging and the scaling of your application.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=166def0a7479" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[REST API VS GraphQL]]></title>
            <link>https://medium.com/@stefanosu422/rest-api-vs-graphql-ef555271a344?source=rss-bfa46709ff51------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef555271a344</guid>
            <category><![CDATA[flatiron-school]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[rest-api]]></category>
            <dc:creator><![CDATA[Stefanos Ugbit]]></dc:creator>
            <pubDate>Thu, 25 Jul 2019 16:21:08 GMT</pubDate>
            <atom:updated>2019-07-25T17:18:35.803Z</atom:updated>
            <content:encoded><![CDATA[<p>What is the REST API:</p><p>RESTFUL API is an application interface program that uses HTTP requests to GET, PUT, POST, and DELETE data. It follows restful conventions. Rest API is the most commonly used and widespread standard in the creation of APIs for internet services and web applications. REST is an interface between systems that uses HTTP requests to retrieve data and generate operations based on that data in formats such as JSON and XML.</p><p>What is GraphQL:</p><p>GraphQL is a query language for your API, and a server-side runtime for executing queries by using a type system you define for your data. GraphQL is written into the schema in your backend. This schema serves as the contract between the client and the server to define how a client can access the data. It’s used to load data from a server to a client. It was created by Facebook in 2012 and publicly released in 2015. GraphQL allows the client to specify exactly what data it needs. It also makes it much easier to aggregate data from multiple sources. With GraphQL, you’re able to make a single call to fetch the required data that you need instead of having to make several requests.</p><p>This example demonstrates fetching data using Rest API vs GraphQL. Here we have to make requests to different endpoints to get the data that we want back from the server. Using a Rest API we also get extra information that we may not need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Up9tSbf0XuZFlIU_.png" /></figure><p>In GraphQL we only need to send a single request and specify what data we want to get back from the server. The response is sent back as a JSON object.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*diDRToY4lNKIHJzr.png" /></figure><p>The benefits of GraphQL over REST GraphQL prioritizes efficiency over reliability. It’s more efficient because it’s less taxing on the server by making fewer requests and gives you back only the data that you specify. GraphQL allows you to use a single HTTP endpoint to run multiple queries and mutations for any HTTP action. This lessens the number of requests that are made between the client and the server. It helps make our applications more efficient.</p><p>The images were sourced from <a href="https://www.howtographql.com/basics/1-graphql-is-the-better-rest/">https://www.howtographql.com/basics/1-graphql-is-the-better-rest/</a> which is a really good resource on how to get started with and the fundamentals of GraphQL.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef555271a344" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IMPOSTER SYNDROME!!!]]></title>
            <link>https://medium.com/@stefanosu422/imposter-syndrome-7d806bd54359?source=rss-bfa46709ff51------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d806bd54359</guid>
            <category><![CDATA[imposter-syndrome]]></category>
            <dc:creator><![CDATA[Stefanos Ugbit]]></dc:creator>
            <pubDate>Thu, 13 Jun 2019 11:53:17 GMT</pubDate>
            <atom:updated>2019-06-13T13:12:03.196Z</atom:updated>
            <content:encoded><![CDATA[<p>What is imposter syndrome? Imposter Syndrome was first defined in 1978 by psychologists <a href="http://paulineroseclance.com/impostor_phenomenon.html">Pauline R. Clance</a> and Suzanne A. Imes as a feeling of “phoniness in people who believe they are not intelligent, capable or creative despite evidence of high achievement.” “A 2011 study was published in the International Journal of Behavior Science <a href="https://www.tci-thaijo.org/index.php/IJBS/article/view/521">International Journal of Behavioral Science</a> found that an <a href="https://www.tci-thaijo.org/index.php/IJBS/article/view/521/pdf">estimated 70 percent</a> of people experience impostor syndrome at one point in their lives.”</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FUQ5RWDvwujyc8%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FUQ5RWDvwujyc8%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FUQ5RWDvwujyc8%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/5bbc238ab8e7a350f8cf831e8a9d6048/href">https://medium.com/media/5bbc238ab8e7a350f8cf831e8a9d6048/href</a></iframe><p>Imposter syndrome is very common especially amongst software developers because technology is always changing and you have to always learn new tools to solve more complex problems. I think it’s a feeling that most people feel because there are always new things to learn and that can feel overwhelming at times. I mean even Albert Einstein and Maya Angelou have felt that they didn’t deserve the attention their work received.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FZQUxL4Jm1Lo%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DZQUxL4Jm1Lo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FZQUxL4Jm1Lo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/72b3c5feca477518ea7daf4db30c61d5/href">https://medium.com/media/72b3c5feca477518ea7daf4db30c61d5/href</a></iframe><p>There are many ways to overcome the feelings of imposter syndrome. First, start speaking with others around you, they might feel the same way you do and that might help because others went or are going through the same thing. Secondly, reinforce positive thoughts and accomplishments that you have made or contributed to. This will help you feel more confident and competent in your abilities. Lastly, open and honest conversations about your insecurities are helpful because they help you realize where you may need to improve and that your colleagues may have those same feelings.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d806bd54359" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[git commit -am “My Grow With Google Scholarship Story”]]></title>
            <link>https://medium.com/@stefanosu422/git-commit-am-my-grow-with-google-scholarship-story-6379e467b0c6?source=rss-bfa46709ff51------2</link>
            <guid isPermaLink="false">https://medium.com/p/6379e467b0c6</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[google-udacity-scholars]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Stefanos Ugbit]]></dc:creator>
            <pubDate>Tue, 01 Jan 2019 00:55:35 GMT</pubDate>
            <atom:updated>2019-01-01T00:55:35.630Z</atom:updated>
            <content:encoded><![CDATA[<p>This year has been a whirlwind of emotions that words won’t completely do justice to. I was tested mentally and physically in ways that nearly broke me. Some people say there are always lessons to be learned from our mistakes but sometimes there isn’t, somethings just happen. Shortly after graduating from college and finishing my internship at the NYC Mayor’s Office in 2017 I found that my Political Science degree meant nothing in the job market. I was consistently unemployed and underemployed and (in a twisted irony) dealing with food insecurity while working as a waiter in the food industry. In between choosing to pay bills or eat. I would ask myself how I got here…</p><p>I started my programming journey in January of 2018; a friend urged me to apply for the Grow With Google Scholarship. Soon afterward I learned that I was accepted into the program and was excited to learn something that could hopefully change the quality of my life. My body, unfortunately, wasn’t in agreement. My health was already deteriorating due to the demands of my job and my stress levels but my knees were rapidly failing in a way that I couldn’t understand. I was suspicious but deferred to the judgment of my physician. I can remember limping up and down the long hallways which felt like a lifetime at work. Fortunately, ten years in the hospitality industry gave me the experience to work efficiently enough that my supervisors would still often compliment my speed. At the end of each of those days I would hobble up the train station and limp back home to repeat the process and each day my body would cave in a little more. Not only were my knees getting worse but I had two herniated discs that gave me severe lower back pain. I could not sit for too long because my back would hurt but I couldn’t stand for too long because my knees would hurt too much. The only way I could work was by laying on my stomach every day for a few hours to avoid aggravating either. Eventually, my knees completely gave out on me and I couldn’t walk at all and had no income. For a few weeks Id use a crutch walk around and subsist on peanut butter and oatmeal.</p><p>The Nanodegree program became the one thing in my life that I felt like I was making progress in so I latched on to it as if my life depended on it. To cope with the pain I took painkillers in the day drank vodka nightly. I subsisted on oatmeal and peanut butter and meditate on how my life could transform from being a developer.</p><p>The rigor of the program was enough to also keep me distracted and focused while the rest of my life was in shambles. I loved solving problems, doing the assigned projects, reviewing topics on Codeburst and Free Code Camp. The chaos of my life was quieted with understanding Javascript, API’s, components, state and dreams of building applications that could transform people’s lives. Eventually, I was able to undergo surgery to help repair my knee and had to take a 1-month hiatus from programming so I could return more focused and healthy.</p><p>After my surgery, I began physical therapy and slowly stabilized support on my knees I was elated. Things were slowly but gradually getting better. I still had a pronounced limp and being inactive for such a long time worsened my back. In spite of my body failing me, financial hardships, anxiety and coping with repeated job rejections I was able to catch up and graduate on time.</p><p>Currently, I am trying to land an internship while trying to make ends meet, however, remain hopeful because of how far I’ve come and the supportive network of the Udacity community. I hope my story provides a little encouragement to other aspiring developers from underserved communities trying to rise above the conditions of their current circumstances.</p><p>Happy New Year’s,</p><p>Stefanos Ugbit :)</p><p>P.S.</p><p>If my story has been helpful to you in any way and you’d like to chat or you have any advice on how I can move the ball forward in landing my first role in the tech industry or are aware of internships I could apply to, feel free to reach out to me at: <a href="/service/mailto:stefanosu422@gmail.com">stefanos.ugbit@gmail.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6379e467b0c6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>