<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Stenio Wagner</title>
    <description>The latest articles on DEV Community by Stenio Wagner (@steniowagner).</description>
    <link>https://dev.to/steniowagner</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F238508%2Fb53937c3-ca38-4dd2-b576-aa46a47886bc.jpeg</url>
      <title>DEV Community: Stenio Wagner</title>
      <link>https://dev.to/steniowagner</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/steniowagner"/>
    <language>en</language>
    <item>
      <title>Image recognition with NodeJS + AWS Lambda + Rekognition + Translator</title>
      <dc:creator>Stenio Wagner</dc:creator>
      <pubDate>Thu, 25 Jun 2020 16:25:52 +0000</pubDate>
      <link>https://dev.to/steniowagner/image-recognition-with-nodejs-aws-lambda-rekognition-translator-2dmk</link>
      <guid>https://dev.to/steniowagner/image-recognition-with-nodejs-aws-lambda-rekognition-translator-2dmk</guid>
      <description>&lt;p&gt;Hey, guys!&lt;/p&gt;

&lt;p&gt;I wanted to share with you an implementation that I made using NodeJS, AWS-Lambda and Serverless-Framework for image recognition and classification.&lt;/p&gt;

&lt;p&gt;The objectives are:&lt;/p&gt;

&lt;p&gt;1 - Download a certain image&lt;br&gt;
2 - Extract classification labels related to this image using AWS-Rekognition&lt;br&gt;
3 - Translate the labels from step # 2 to another language using AWS-Translate&lt;br&gt;
4 - Return the results as follows:&lt;/p&gt;

&lt;p&gt;[EnglishLabel, LabelTranslated] - Percentage of confidence that this label makes sense for the input image.&lt;/p&gt;

&lt;p&gt;Ex (en =&amp;gt; pt): [Dog, Cachorro]: 99.87%&lt;/p&gt;

&lt;p&gt;It's a very simple project, but it shows how easily these services are accessible and simple to be used.&lt;/p&gt;

&lt;p&gt;Cheers!&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/steniowagner/serverless-aws-lambda-studies/tree/master/demo03-image-analysis"&gt;https://github.com/steniowagner/serverless-aws-lambda-studies/tree/master/demo03-image-analysis&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>A FULL-STACK TYPESCRIPT APP TO SEND PUSH-NOTIFICATIONS USING EXPO</title>
      <dc:creator>Stenio Wagner</dc:creator>
      <pubDate>Sat, 28 Dec 2019 00:27:13 +0000</pubDate>
      <link>https://dev.to/steniowagner/a-full-stack-typescript-app-to-send-push-notifications-using-expo-2k1o</link>
      <guid>https://dev.to/steniowagner/a-full-stack-typescript-app-to-send-push-notifications-using-expo-2k1o</guid>
      <description>&lt;p&gt;HEY, PEOPLE!&lt;/p&gt;

&lt;p&gt;Well, I don't use Expo, but I ended up working on a recently done Expo project where one of the features I was supposed to develop was&lt;br&gt;
a way to connect the server and some other internal APIs and services (such as a payments API) so they could send notifications to the App made with Expo.&lt;br&gt;
In addition, another requirement was that Marketing personnel could also send notifications to specific users through a user-friendly interface that was connected to the Company database.&lt;/p&gt;

&lt;p&gt;And to solve this problem, I created a Dashboard using React (which Marketing people will use) that lists all Company users and sends notifications to a RESTful API made with NodeJS (which will also be used by internal APIs and services) that forwards&lt;br&gt;
notifications to Expo servers to be delivered to their vendors (FCM for Android and APNs for iOS). - More info on repos!&lt;/p&gt;

&lt;p&gt;NOTE: The projects listed here are just a simplification of the modules I made, ok?&lt;/p&gt;

&lt;p&gt;Without further ado, follow the repos!&lt;/p&gt;

&lt;p&gt;Dashboard: &lt;a href="https://github.com/steniowagner/expo-notifications-dashboard"&gt;https://github.com/steniowagner/expo-notifications-dashboard&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;App: &lt;a href="https://github.com/steniowagner/expo-notifications-app"&gt;https://github.com/steniowagner/expo-notifications-app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Api: &lt;a href="https://github.com/steniowagner/expo-notifications-api"&gt;https://github.com/steniowagner/expo-notifications-api&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A great 2020 to you! 😘&lt;/p&gt;

</description>
      <category>node</category>
      <category>typescript</category>
      <category>react</category>
      <category>reactnative</category>
    </item>
    <item>
      <title>[A RESTful API BUILT IN NODEJS USING JUST NATIVE MODULES - NO NPM HERE!]</title>
      <dc:creator>Stenio Wagner</dc:creator>
      <pubDate>Sat, 07 Dec 2019 12:59:51 +0000</pubDate>
      <link>https://dev.to/steniowagner/a-restful-api-built-in-nodejs-using-just-native-modules-no-npm-here-9ob</link>
      <guid>https://dev.to/steniowagner/a-restful-api-built-in-nodejs-using-just-native-modules-no-npm-here-9ob</guid>
      <description>&lt;p&gt;Hey, people!&lt;/p&gt;

&lt;p&gt;Well, I've been using express for routing and mongoose/sequelize to connect my server with my database for a while, and just wanted to try to build my own router and my own database-connector and use them to build a RESTful API using just native modules. :man-shrugging::skin-tone-5:&lt;br&gt;
In this project, I implemented (and much more):&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Instant updates on the sever when some file is edited (as nodemon does).&lt;br&gt;
Routing using the Middleware pattern (as express does).&lt;br&gt;
Schema definition to define the data structures used to define the API entities.&lt;br&gt;
Validate the data before save or update using the pre-defined Schema.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Ok, now you're maybe thinking: "What? We already have some libs that someone else created that helps us to do it all (as express and mongoose and mongoose/sequelize that I mentioned)! Why re-invent the wheel"?&lt;/p&gt;

&lt;p&gt;And I'll answer you: And I answer you: I know we don't always have time to implement our own ideas to solve certain problems that we face in our daily lives as engineers who use programming to create solutions, but I really want to encourage you, whenever possible, to try to build your own solutions and codify your ideas for these problems, this will make you a much more independent developer and of course much more confident in using a programming language. Apart from the fact that of course this experience will make you expand your knowledge&lt;br&gt;
and make you feel amazing while implementing each feature (as I'm feeling now)!&lt;/p&gt;

&lt;p&gt;PS: Treat this project as a personal challenge that I set myself, so there is no intention of running this API in production. Therefore,&lt;br&gt;
This project is not a perfect solution and certainly not better than the ones that already exist in the market, but I want to share this knowledge I learned and implemented with the community so that everyone can benefit from what I did!&lt;/p&gt;

&lt;p&gt;Without further ado, here's the repo!&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/steniowagner/restful-npmless-api"&gt;https://github.com/steniowagner/restful-npmless-api&lt;/a&gt;&lt;/p&gt;

</description>
      <category>node</category>
      <category>opensource</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
