<?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 Arafath Misree on Medium]]></title>
        <description><![CDATA[Stories by Arafath Misree on Medium]]></description>
        <link>https://medium.com/@amisree?source=rss-f60941dba9ab------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*IVaVH6OzDAH8T5pGtbZbmA.png</url>
            <title>Stories by Arafath Misree on Medium</title>
            <link>https://medium.com/@amisree?source=rss-f60941dba9ab------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:53:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@amisree/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[What makes you a Software Engineer? Not a Software Developer!]]></title>
            <link>https://amisree.medium.com/what-makes-you-a-software-engineer-not-a-software-developer-f311636da02?source=rss-f60941dba9ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/f311636da02</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[softawaredevelopment]]></category>
            <category><![CDATA[software-engineer]]></category>
            <category><![CDATA[software-developer]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Arafath Misree]]></dc:creator>
            <pubDate>Sun, 13 Jun 2021 09:47:18 GMT</pubDate>
            <atom:updated>2021-06-13T09:47:18.176Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*82gOFDBmaQnJZmzY09d94A.jpeg" /></figure><h3>Who is a Software Developer?</h3><p>Let&#39;s try to understand what a software developer does. They are good at programming and at what they want to build. Also, they know most of the frameworks basically good at coding. Now you must be thinking okay, These people are good. This article is not about software developers are good or software engineers are good. It to understand the difference to help your career to choose who you want to become.</p><p>A software Developer uses tools and frameworks to build apps and systems to meet client expectations. You must be thinking isn’t it what we want? sort of but it’s not what everyone wants. A software developer can write a piece of software or an entire program looking at a set of feature requirements from a solution document.</p><h3>Who is a Software Engineer?</h3><p>Let’s try to understand who is a software engineer. The word engineer sound should give you a hint. A software engineer is a person who thinks above code. The above code sounds funny for a person who spends an entire 4-year undergraduate program to learn to code. Their goals are more oriented towards market problems than writing a piece of code. So does that mean they don&#39;t code? Obviously every software engineer code but not for long. But They transit themselves into solution specialist or Lead/architect roles in the future. Does this mean Software developers cannot become leads? if a developer starts to think like an engineer of course you have the table open.</p><p><strong>What is engineer-level thinking?</strong></p><p>An engineer-level thinking is about thinking about a solution that will impact a market or an industry thinking about the future of the solution.</p><p>Example: Let&#39;s think we are trying to build software for a Super Market complex to solve their inventory problem. This is one software that would impact only that specific supermarket. But what if we try to understand a common inventory problem in the supermarket industry while trying to solve this specific supermarket’s problem. We create a solution that would help solve the common problem. And solution it into a Software requirement specification with exact use cases tangled with it. Voila, there you have a solution now.</p><p>Software engineers are a group of people who construct an idea for a feature. They are good at escalating what others wanna build into solutions as well as verbally sound topics. They work as the intermediate line in gathering requirements from Stakeholders and engineering them into solutions. They build solutions/Tools that help lots of software developers code.</p><p>They design solutions that impact the market with a huge disruptive approach. Their solutions are a re-usable piece of software/architectures/tools/theories we follow on day to day basis to build software. This involves lots of computer science knowledge. They are pretty good at computer science rather than using frameworks. They worry about the science behind the code. They think about how their code would affect the hardware. Mostly they come up with frameworks that developers use.</p><p>This might bit interesting to <a href="https://youtu.be/P8KmdoeizU4">watch</a>!</p><h3>Key differences</h3><ul><li>A software developer usually starts the application development process by speaking to customers/Requirement Docs and figuring out what their software needs are.</li><li>Software developers tend to do everything that software engineers do but on a limited scale.</li><li>A software engineer should be able to do everything that a software developer does, but with a different design philosophy including the science behind it.</li><li>Software engineers take a bigger picture view than software developers, meaning they’re more focused on the structure design and eliminating technical debt.</li><li>Software engineers are interested in solving immediate problems while minimizing trade-offs to other parts of the system and its architecture.</li></ul><p><strong>Software Engineer pay scale?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lxUUpIcB0gMR5UDx8QLFxg.jpeg" /></figure><p><strong>Software Developer pay scale?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ROPglsHfLlLtDVcKAD7DEQ.jpeg" /></figure><p><strong>Conclusion?</strong></p><p>I hope now you might have an overview of this phenomenon where you stand in the industry. I personally stand behind being an engineer thinking about the bigger picture. Trying to solve big problems to achieve universal solutions. I personally think of a product approach for all the problems out there. So I take my chances in selling it. Maybe you could be a different person. But knowing what you do and where you stand will help you gain focus on where you want to go and who you want to become.</p><blockquote>If you like this Read Please share and show some love❤️ , Also follow me on Instagram <a href="https://www.instagram.com/arafath_misree/">@CodingCardio</a>. 🙂</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f311636da02" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Amazon Simple notification Service with React native.]]></title>
            <link>https://amisree.medium.com/author-arafath-misree-cc5da85888ef?source=rss-f60941dba9ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc5da85888ef</guid>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Arafath Misree]]></dc:creator>
            <pubDate>Thu, 14 Dec 2017 05:57:09 GMT</pubDate>
            <atom:updated>2017-12-14T11:15:47.067Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Services and Technologies used for the Poc :</strong></p><ul><li>React Native</li><li>Amazon AWS Simple Notification Service SNS</li><li>Google Cloud Messaging GCM / Firebase console</li><li>React-native-push-notification npm package</li></ul><p>The source code for this project is <a href="https://github.com/MitraInnovationRepo/react-native-base/tree/master/pushnotification_poc/pushApp">here</a></p><h3>Table of contents</h3><ol><li>Configure Google GCM</li><li>Configure Amazon SNS</li><li>Create react native project</li><li>Push notifications</li></ol><h3>1) Configure Google GCM (Google Cloud Messaging)</h3><ul><li>For this step i used Firebase console <a href="https://console.firebase.google.com/">https://console.firebase.google.com</a> and create a new project.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/467/0*nCw_U0PMq8TRfreO." /></figure><h3>2) Configure Amazon AWS SNS (Simple Notification Service)</h3><ul><li>Go to Amazon web services console <a href="https://console.aws.amazon.com/console/home">https://console.aws.amazon.com/console/home</a></li><li>Click on the Simple Notification Service link, or go to <a href="https://us-west-2.console.aws.amazon.com/sns/v2/home?region=us-west-2#/newuser">https://us-west-2.console.aws.amazon.com/sns/v2/home?region=us-west-2#/newuser</a></li><li>On the SNS Dashboard, click on the option<strong> Create Platform Application</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*uMWgTtKl1L1ruEln." /></figure><ul><li>Enter a name for the application, in this case I will call it PushTestAWS</li><li>Choose Google Cloud Messaging (GCM) in the <strong>Push notification platform </strong>option</li><li>In The <strong>API Key </strong>value, you have to enter the value of the <strong>Firebase Server Key</strong>. You can see that value in the settings of the firebase project. Go to the <strong>Cloud Messaging tab</strong> in the Firebase console.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*qBke-0yGIr2mctzH." /></figure><p>*Note you can use any cloud messaging service while configuring Amazon aws sns for this example i have used firebase as a cloud messaging service but you could choose any service from the drop down refer the image below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*r-padMvnOli95vbq." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*h1oG-GV46n37LEpq." /></figure><h3>3) Create react native project</h3><p>For this step we are going to create a sample app with react native CLI</p><ul><li>On terminal create a new react native project with the following command: <strong>react-native init PushSNSTest </strong>and wait until it finishes</li><li>Go to the project folder with <strong>cd PushSNSTest</strong></li><li>Run the project to see that everything is ok. Execute the following command: <strong>react-native run-android</strong></li><li>Now, install the package <a href="https://github.com/zo0r/react-native-push-notification">react-native-push-notification</a> in order to handle the notifications and to see the device token that we need in order to push the notification from Amazon SNS server to the device.</li><li>For this we run the command <strong>npm install — save react-native-push-notification</strong></li><li>In it’s GitHub <a href="https://github.com/zo0r/react-native-push-notification">page</a>, is the installation instructions, however.</li><li>To configure the native ios sdk for push notification follow this section on <a href="https://facebook.github.io/react-native/docs/pushnotificationios.html#content">facebook </a>and execute react-native run-ios.</li><li>Run the command <strong>react-native link</strong>. This should automatically modify the files settings.gradle, build.gradle, MainApplication.java</li><li>Next, modify the <strong>AndroidManifest.xml</strong> file. Add the following permissions that are needed by the react-native-push-notification plugin.</li></ul><blockquote>&lt;uses-permission android:name=”android.permission.WAKE_LOCK” /&gt;</blockquote><blockquote>&lt;permission android:name=”${applicationId}.permission.C2D_MESSAGE” android:protectionLevel=”signature” /&gt;</blockquote><blockquote>&lt;uses-permission android:name=”${applicationId}.permission.C2D_MESSAGE” /&gt;</blockquote><blockquote>&lt;uses-permission android:name=”android.permission.VIBRATE” /&gt;</blockquote><blockquote>&lt;uses-permission android:name=”android.permission.RECEIVE_BOOT_COMPLETED”/&gt;</blockquote><ul><li>In the same <strong>AndroidManifest.xml </strong>file add this lines <strong>inside the application element</strong>. I put this just before closing the application element.</li></ul><blockquote>&lt;receiver android:name=”com.dieam.reactnativepushnotification.modules.RNPushNotificationPublisher” /&gt;</blockquote><blockquote>&lt;receiver android:name=”com.dieam.reactnativepushnotification.modules.RNPushNotificationBootEventReceiver”&gt;</blockquote><blockquote>&lt;intent-filter&gt;</blockquote><blockquote>&lt;action android:name=”android.intent.action.BOOT_COMPLETED” /&gt;</blockquote><blockquote>&lt;/intent-filter&gt;</blockquote><blockquote>&lt;/receiver&gt;</blockquote><blockquote>&lt;service android:name=”com.dieam.reactnativepushnotification.modules.RNPushNotificationRegistrationService”/&gt;</blockquote><blockquote>&lt;service android:name=”com.dieam.reactnativepushnotification.modules.RNPushNotificationListenerService” android:exported=”false”&gt;</blockquote><blockquote>&lt;intent-filter&gt;</blockquote><blockquote>&lt;action android:name=”com.google.android.c2dm.intent.RECEIVE” /&gt;</blockquote><blockquote>&lt;/intent-filter&gt;</blockquote><blockquote>&lt;/service&gt;</blockquote><ul><li>In the PushSNSTest react Native project that we created earlier, we modify the file<strong> app.js</strong></li><li>We insert the following import <strong>import PushNotification from ‘react-native-push-notification’</strong></li><li>We add the <strong>componentDidMount function </strong>to the app.js file</li></ul><blockquote>/*</blockquote><blockquote>Extends Component {…….</blockquote><blockquote>componentDidMount()</blockquote><blockquote>console.log(‘Did mount’)</blockquote><blockquote>PushNotification.configure({</blockquote><blockquote>// (optional) Called when Token is generated (iOS and Android)</blockquote><blockquote>onRegister: function (token) {</blockquote><blockquote>console.log(‘TOKEN:’, token);</blockquote><blockquote>},</blockquote><blockquote>// (required) Called when a remote or local notification is opened or received</blockquote><blockquote>onNotification: function (notification) {</blockquote><blockquote>console.log(‘NOTIFICATION:’, notification);</blockquote><blockquote>},</blockquote><blockquote>// ANDROID ONLY: GCM Sender ID (optional — not required for local notifications, but is need to receive remote push notifications)</blockquote><blockquote>senderID: “719007178572”,</blockquote><blockquote>// IOS ONLY (optional): default: all — Permissions to register.</blockquote><blockquote>permissions: {</blockquote><blockquote>alert: true,</blockquote><blockquote>badge: true,</blockquote><blockquote>sound: true</blockquote><blockquote>},</blockquote><blockquote>// Should the initial notification be popped automatically</blockquote><blockquote>// default: true</blockquote><blockquote>popInitialNotification: true,</blockquote><blockquote>/**</blockquote><blockquote>* (optional) default: true</blockquote><blockquote>* — Specified if permissions (ios) and token (android and ios) will requested or not,</blockquote><blockquote>* — if not, you must call PushNotificationsHandler.requestPermissions() later</blockquote><blockquote>*/</blockquote><blockquote>requestPermissions: true,</blockquote><blockquote>});</blockquote><blockquote>}</blockquote><blockquote>……….</blockquote><blockquote>*/</blockquote><ul><li>In that function we have to configure the Pushnotification plugin. There are two important parts in this code. The <strong>senderID</strong> property has to be filled with the value of the <strong>Sender ID that we have in the firebase console</strong>. In the Cloud Messaging tab in the Settings of the project PushReactNativeTest that we created earlier</li><li>The other important thing that we need is the device token id. This token is needed when we want to send push notifications from Amazon SNS server to a specific user. In this case we are going to see the console in order to see what is the device token of my android phone. This token is unique for the current app and your device. The token is passed to the <strong>onRegister</strong> <strong>function</strong> that we declared earlier.</li><li>Run the application again with <strong>react-native run-android</strong></li><li>Enable <strong>Debug JS Remotely</strong></li><li>Open the chrome browser and open Be sure to have the developer tools open to see the console log.</li><li><strong>Reload the app</strong>, and you should see the device token in the console log.</li><li>Copy the token .</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*WsaTSsvpmVEsgLTR." /></figure><h3>4) Push notifications</h3><ul><li>Open the Amazon AWS SNS console. On the left menu, click on the Applications option. Then click on the ARN of the application PushTestAWS that we created earlier</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/609/0*6xLl78UBqsy0EBUI." /></figure><ul><li>Inside the application details page, we should see the button Create platform endpoint. We click on that button.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*J4aI3ytkb7KbQMGT." /></figure><ul><li>In the Add endpoints screen, we paste the device token that we copy earlier from the console log.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*1lUlg2Ou0exvsXtl." /></figure><ul><li>In the next screen, we choose the endpoint and then click in the Publish to endpoint button</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*AHN1cCgqxcXolbjb." /></figure><ul><li>In the Publish a message screen, we can send a message to the chosen device. Here we click the <strong>JSON message generator</strong> button. After we create a message we can click on the publish message button, to send the push notification to the device. Important: Be sure that the app is in the background, or it is closed in order to see the push notification. When the app is on the foreground, the notification is not shown. Only the onNotification function is invoked. You can see the behavior of the notifications <a href="https://github.com/zo0r/react-native-push-notification/blob/master/trouble-shooting.md">here</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/0*cF_Tqj94jJsNMq9Y." /></figure><p>At this point you should see the notification that arrived to the device.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/609/0*94oxuFzFrn6EAyNe." /></figure><p>Conclusion :</p><p>After we have configured our app to receive push notifications through aws sns service we need to automate this process from the api</p><p>I would recommend if the client app can have an api to check device token on launch of the application every time it launches. The api should contain a device token that was generated by the push-notification-sdk and if there is any mismatch between the generated token and the token saved earlier this newly generated token should be updated in the device token column in the database and register the device with sns service through “SNS Query API” , Refer to this documentation about sns query <a href="http://docs.aws.amazon.com/sns/latest/api/API_Operations.html">api</a>.</p><p>Higlevel architecture of the proposed solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2AuNeo8sKFGeuAzF." /></figure><p>Note in above diagram “Fire base Cloud messaging service” is optional you could choose any amazon approved cloud messaging service.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc5da85888ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>