<?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: lonewolf_zlife</title>
    <description>The latest articles on DEV Community by lonewolf_zlife (@lonewolf_zlife).</description>
    <link>https://dev.to/lonewolf_zlife</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%2F624002%2Fd357f3b8-a866-458e-b5e1-b49e6b1845a1.jpeg</url>
      <title>DEV Community: lonewolf_zlife</title>
      <link>https://dev.to/lonewolf_zlife</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/lonewolf_zlife"/>
    <language>en</language>
    <item>
      <title>Will ChatGPT Replace the Work of Software Engineers?</title>
      <dc:creator>lonewolf_zlife</dc:creator>
      <pubDate>Sun, 05 Feb 2023 16:07:16 +0000</pubDate>
      <link>https://dev.to/lonewolf_zlife/will-chatgpt-replace-the-work-of-software-engineers-333m</link>
      <guid>https://dev.to/lonewolf_zlife/will-chatgpt-replace-the-work-of-software-engineers-333m</guid>
      <description>&lt;p&gt;Recently, OpenAI's language model ChatGPT has been making headlines for its ability to generate human-like text. This has sparked a debate among the tech community about whether ChatGPT and other AI systems could eventually replace the work of software engineers.&lt;/p&gt;

&lt;p&gt;On one hand, ChatGPT and similar AI systems are capable of producing code snippets and performing tasks such as bug fixing, code refactoring, and even creating new software applications. This could potentially lead to faster and more efficient development processes, saving time and resources for businesses.&lt;/p&gt;

&lt;p&gt;However, while ChatGPT and AI systems can handle certain tasks, they lack the ability to understand the overall context and problem-solving abilities that a human software engineer brings to the table. This includes the ability to think creatively, communicate effectively with a team, and make complex design decisions based on a deep understanding of software engineering principles.&lt;/p&gt;

&lt;p&gt;Additionally, AI systems are only as good as the data they are trained on, and their outputs can be limited by the quality of that data. This means that AI systems can only generate code that is similar to what they have seen before, rather than coming up with entirely new solutions to problems.&lt;/p&gt;

&lt;p&gt;In conclusion, while ChatGPT and AI systems can certainly assist software engineers in their work, they are unlikely to replace them in the near future. The human touch and critical thinking skills that software engineers bring to the table cannot be replicated by machines, at least not yet. Instead, ChatGPT and AI systems will likely serve as valuable tools to help software engineers complete their work more efficiently and effectively&lt;/p&gt;

</description>
    </item>
    <item>
      <title>React Native vs Flutter</title>
      <dc:creator>lonewolf_zlife</dc:creator>
      <pubDate>Sun, 05 Feb 2023 16:00:52 +0000</pubDate>
      <link>https://dev.to/lonewolf_zlife/react-native-vs-flutter-3o97</link>
      <guid>https://dev.to/lonewolf_zlife/react-native-vs-flutter-3o97</guid>
      <description>&lt;p&gt;React Native and Flutter are both popular frameworks for building cross-platform mobile applications. Both frameworks have their own advantages and disadvantages, and the choice between them largely depends on your project requirements and preferences.&lt;/p&gt;

&lt;p&gt;React Native Pros:&lt;/p&gt;

&lt;p&gt;Large community and mature ecosystem: React Native has been around for a while and has a large and active community of developers. There are many resources available and a lot of third-party libraries that you can use.&lt;br&gt;
Strong support from Facebook: React Native is maintained by Facebook and has strong support from the company.&lt;br&gt;
Use of JavaScript: React Native uses JavaScript, a language that is widely known and used by many developers, making it easier to find and hire developers.&lt;br&gt;
React Native Cons:&lt;/p&gt;

&lt;p&gt;Slow performance for complex apps: React Native is not as performant as native apps and can be slow for complex applications.&lt;br&gt;
Steep learning curve: React Native has a steeper learning curve than some other frameworks and can be more challenging to learn, especially for those who are new to mobile development.&lt;br&gt;
Flutter Pros:&lt;/p&gt;

&lt;p&gt;High performance: Flutter is known for its high performance and smooth animations, which is important for visually appealing apps.&lt;br&gt;
Quick development time: Flutter's "hot reload" feature allows developers to see changes in real-time, which can speed up the development process.&lt;br&gt;
Beautiful and unique UI: Flutter has a unique and beautiful UI, which makes it possible to create visually appealing and custom apps.&lt;br&gt;
Flutter Cons:&lt;/p&gt;

&lt;p&gt;New and relatively small community: Flutter is a relatively new framework compared to React Native, and the community is still growing, which means that there are fewer resources available and fewer third-party libraries.&lt;br&gt;
Dart language: Flutter uses Dart, which is a less popular language compared to JavaScript, making it more challenging to find developers with experience in Dart.&lt;br&gt;
In conclusion, both React Native and Flutter have their own strengths and weaknesses, and the best choice depends on the specific requirements of your project. If you need a fast and efficient framework with a large community and support, React Native might be the better choice. On the other hand, if you need a beautiful and high-performing UI, then Flutter may be the better option.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Generating a Zoom Meeting Url Using Firebase Cloud-Functions</title>
      <dc:creator>lonewolf_zlife</dc:creator>
      <pubDate>Sun, 02 May 2021 03:53:14 +0000</pubDate>
      <link>https://dev.to/lonewolf_zlife/generating-a-zoom-meeting-url-using-firebase-cloud-functions-2lh4</link>
      <guid>https://dev.to/lonewolf_zlife/generating-a-zoom-meeting-url-using-firebase-cloud-functions-2lh4</guid>
      <description>&lt;h2&gt;Introduction&lt;/h2&gt;

&lt;p&gt;Hello, everyone! I hope you all are doing well. In this blog, I will share and demonstrate how to generate the Zoom meeting url using the Cloud-Functions in the fastest way. This is my very first blog writing about what I have just learned or completed in order to leave it as an example for those who might come later having same requirements or problem as me.&lt;/p&gt;

&lt;h2&gt;Let's get started&lt;/h2&gt;

&lt;p&gt;Firstly, you should go and create the Zoom for developer account in (&lt;a href="https://marketplace.zoom.us/"&gt;https://marketplace.zoom.us/&lt;/a&gt;).&lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--vwSeIBeC--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/mdt3xnm8u8dlkgrvenay.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--vwSeIBeC--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/mdt3xnm8u8dlkgrvenay.png" alt="Screen Shot 2564-05-02 at 09.33.54"&gt;&lt;/a&gt;&lt;br&gt;
 You should see this above image after you signed up successfully. Then, go create the app in the Zoom marketplace for JWT as the following image.&lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--amcTCLST--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/qd5h8sd3yue4bda2al81.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--amcTCLST--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/qd5h8sd3yue4bda2al81.png" alt="Screen Shot 2564-05-02 at 09.33.30"&gt;&lt;/a&gt;&lt;br&gt;
&lt;b&gt;JWT&lt;b&gt;&lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--R07QQQI7--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/n9depza8usj61bgag9u1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--R07QQQI7--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/n9depza8usj61bgag9u1.png" alt="Screen Shot 2564-05-02 at 09.45.05"&gt;&lt;/a&gt;&lt;/b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;After you created successfully, you will be redirected to this scene and try to fill out all the required informations. &lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--PH8GluIy--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ctzadsdc29v2wtqhr49o.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--PH8GluIy--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ctzadsdc29v2wtqhr49o.png" alt="Screen Shot 2564-05-02 at 09.46.57"&gt;&lt;/a&gt;&lt;br&gt;
 &lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--_fZ749SA--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/kgu4vxngifzvgrr6s5bl.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--_fZ749SA--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/kgu4vxngifzvgrr6s5bl.png" alt="Screen Shot 2564-05-02 at 09.47.09"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Next, you have to set the expiration time of the JWT token and for me I set it to expire in one year for the token. It might not be a good practice but it's the fastest way to generate the Zoom meeting url.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Calling to the Zoom Api endpoint&lt;b&gt;&lt;br&gt;
 &lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--33kmeMYh--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/e47n4z1t8r98x3vtz7qp.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--33kmeMYh--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/e47n4z1t8r98x3vtz7qp.png" alt="Screen Shot 2564-05-02 at 10.02.17"&gt;&lt;/a&gt;&lt;/b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;Now, let's try to call to the endpoint to generate the Zoom meeting url via Postman.&lt;br&gt;
&lt;b&gt;Zoom endpoint&lt;/b&gt;: &lt;a&gt;&lt;/a&gt;&lt;a href="https://api.zoom.us/v2/users/me/meetings"&gt;https://api.zoom.us/v2/users/me/meetings&lt;/a&gt;&lt;br&gt;
&lt;b&gt;Token&lt;/b&gt;: for the token here is the JWT token of the JWT app we just created in the Zoom developer. So, you can just copy and paste it here.&lt;br&gt;
&lt;b&gt;Post Request Body&lt;/b&gt;&lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--GnznPwHU--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/elcz4el47r24e0i3sohh.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--GnznPwHU--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/elcz4el47r24e0i3sohh.png" alt="Screen Shot 2564-05-02 at 10.12.19"&gt;&lt;/a&gt;&lt;br&gt;
For the settings of the body request, you can set it to control over the attendees like allowing screen sharing or not ...&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Response&lt;/b&gt;&lt;br&gt;
 &lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--S3whRoL4--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/xoaxpayrc60buor5kvxv.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--S3whRoL4--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/xoaxpayrc60buor5kvxv.png" alt="Screen Shot 2564-05-02 at 10.31.38"&gt;&lt;/a&gt;&lt;br&gt;
 You will receive this as the response if the post request is successful. And for the join_url is the url which you can spread to the attendee for attending the Zoom meeting.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Making request using Axios&lt;b&gt;&lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--8seJj_F_--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ykgrri0dbe8px63rzs10.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--8seJj_F_--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ykgrri0dbe8px63rzs10.png" alt="Screen Shot 2564-05-02 at 10.38.25"&gt;&lt;/a&gt;&lt;/b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;Everything here is pretty much the same as in the Postman. In the header of the request, you just have to pass the JWT token there and if the request is successful, the same response will be returned as in the Postman. &lt;br&gt;
You can make it as onCall, onRequest or pubsub is as your need for Firebase Cloud-functions.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--imG-cNjk--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/vlf9hhi08s61n4ktbpni.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--imG-cNjk--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/vlf9hhi08s61n4ktbpni.png" alt="Screen Shot 2564-05-02 at 10.44.28"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;Conclusion&lt;/h2&gt;

&lt;p&gt;I hope it might be helpful and any constructive comments are always welcomed.&lt;br&gt;
Thank you!&lt;/p&gt;

&lt;p&gt;&lt;b&gt;References&lt;/b&gt;&lt;br&gt;
&lt;a href="https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate"&gt;https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate&lt;/a&gt;&lt;br&gt;
&lt;a href="https://marketplace.zoom.us/docs/guides"&gt;https://marketplace.zoom.us/docs/guides&lt;/a&gt;&lt;/p&gt;

</description>
      <category>zoomapi</category>
      <category>node</category>
      <category>react</category>
      <category>firebase</category>
    </item>
  </channel>
</rss>
