teleren/devto huggingface dataset:
Update Package Version in Package.json
Tags: javascript, npm
Published: 2021-11-20 02:14:36

As a developer, you might have seen some warning of deprecation over the terminal when you use old versions of packages. This situation mainly occurs when you work on a long time project and updating an existing project. Since in an application, there is a need of so many packages and its very difficult to update each package one by one.

For the first time, When I came to such a situation I was a beginner and I do the task manually. But next time when I got time to search this over google I found a very easy way to update all the code at once.

In this article, I am going to explain the way in which is most easy to update the package in our application.

##Check outdated package
For checking the list of the outdated package in our application which needs to update to the latest version. We can use below command to see the list of outdated package.

``````npm outdated``````
With the above command we can see the list of outdated package with their versions and also the latest versions in the application. See the below image:
![npm outdated packages](https://jsonworld.com/images/npm-outdated-packages.png)

##Ways to update NPM package

There are two ways for updating any package :
1. Using npm update
2. Using npm-check-update package 

##Using npm update 

We need to write the below command and all the packages will be updated within a minute based on number of packages and internet speed, just write command and your package will be updated. 

``````npm update``````

##Using npm-update-check package

It works same as npm update command. This package is available at npmjs.org.The difference is that it's a utility that automatically adjusts packages which are listed into package.json file , whenever any updates are required. For that we need to install it via command: 

``````
npm install -g npm-check-updates 
``````

After installing the above package to a global location, now we will be able to update packages automatically. The next step is to update all the packages by running the command:

``````ncu -u ``````

Finally,  install it via npm install.

[Click here](https://jsonworld.com/articles) to find more content on JavaScript libraries/frameworks.
Project Universe, an opensource humanity-focused metaverse...
Tags: gamedev, metaverse, showdev, contributorswanted
Published: 2021-11-20 02:08:54

Project Universe is an opensource growing global community developed metaverse like platform led by altruistic honest unconditional love! Development starts in Unity3D as a single-player to massively-multiplayer sci-fi RPG, from there we expand into a metaverse-like platform. The game provides the infrastructure, framework, funding necessary for creating a future-of-humanity oriented platform!

Check out our latest video here: https://www.youtube.com/watch?v=4ilL3jyktuw
OSD600 - Doing Code Reviews
Tags: opensource
Published: 2021-11-20 01:52:33

## 1. Introduction
For reviewing, I did code reviews for 3 other students pull requests on the [IPC144 repo](https://github.com/Seneca-ICTOER/IPC144). Since I also work on auditing and fixing markdown file, when I check their works I might find out what I have missed to fix for my task.

## 2. The first issue
The first issue I found were pretty minor. It is almost about some address values were forgot to be wrapped in `backticks`. Other issues in the repos were addressed well by the contributors or found by other reviewers. [PR1](https://github.com/Seneca-ICTOER/IPC144/pull/74) [PR2](https://github.com/Seneca-ICTOER/IPC144/pull/101)

## 3. The second issue
The second issue is the redundancy of whitespace in source code. This makes the source code's style become inconsistent. Sometimes, if there is a redundant whitespace before `bullet point` it will produce different  result than we expected. [PR3](https://github.com/Seneca-ICTOER/IPC144/pull/98)

## 4. Overall
The review process was very enjoyable. Many people work on the same task will make it be perfect and error-free.
Contribution to Wrap-nd-Go
Published: 2021-11-20 01:41:53

# Process
I helped the owner to fix the Search bar UI. Since the site is just started, there were a lot of works need to do. Firstly, I asked the project's owner to assign the task for me. After getting accepted and reading all the rules of the project, I forked and cloned it. 
After installing all the packages, I ran the project locally and started working on it.

I Created a component for search bar. This also included a package named react-ioicons, which is used for creating wonderful icon.
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/5y89az7hbu43c88ncgca.png)
Since the owner told me to work on a single CSS file, which was <code>public/style.css</code>, I did not create a CSS module file.
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/yn8vtz6obn3jyffw4yc9.png)

Here is the design of the search bar:
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/a0nhrk5q1pvbblhhk018.png)

That was a combination of 2 <code>input html element</code>. I removed all the border of the inputs and instead put them in a <code>div</code> that is a <code>flex-box</code>. After adding the Icons, I added a big border around the <form> and rounded it. Some margins were added so that the search bar would be in proper position.

# Challenge
For the first time, I had no idea what I would do. I went to Youtube to look for some tutorial of flexbox to myself, and some that showed how to style a button element. Finally, I did it, and my job got merged. Still, the owner told me that I need to submit another PR since the first one faced some error.
 
#Links
Repo: https://github.com/Wrap-and-Go/Wrap-nd-Go
Issue: https://github.com/Wrap-and-Go/Wrap-nd-Go/issues/7
PR: https://github.com/Wrap-and-Go/Wrap-nd-Go/pull/9
I made a pretty logger for flutter
Tags: flutter, dart, plugin, android
Published: 2021-11-20 01:15:20

A flutter package that developers have pretty logs instead just printing everything like a newbie.

![Terminal](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/rtpywku1017wahcy5p2s.PNG)

## Features

Makes it easy to log to console without using print in a colorful way, with multiple colors, and it works only in debug mode, makeing it perfect for pros.


## Getting started
### Installing
Add the following to your pubspec.yaml file:

```yaml
dependencies:
  pretty_logger: any
```

Import the package.
```dart
import 'package:pretty_logger/pretty_PLog.dart';
```



## Usage

```dart

void main() {
  PLog.info('Hello buddy');
  PLog.success('Welcome');
  PLog.warning('I am a bad man. Be careful');
  PLog.error('Ops. We ran into some trouble');

  PLog.black('black');
  PLog.red('red');
  PLog.white('white');
  PLog.cyan('cyan');
  PLog.green('green');
  PLog.yellow('yellow');

  runApp(const MyApp());
}
```
[Pretty Logger on pub.dev](https://pub.dev/packages/pretty_logger)

[Pretty Logger on github](https://github.com/Baronsindo/pretty_logger)
OSD600 - Adding New Feature To Weather App
Tags: opensource, android, java
Published: 2021-11-20 00:59:25

## 1. The issue
In last contribution for Hacktoberfest, I created a Weather Forecast App. However, users can watch the weather information of one city at a time that is a little inconvenient. I want to update the app so it will have a list of searched locations with some information in another page.

## 2. Modification process
Here are modifications I did to update the app:
- Refactor source code by reconstructing the architecture 
Putting all source code in the `main` class is not a good practice so I decided to split the code into smaller models. 
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/h9n4su6w8hbnbr03ntm0.png)
  * `AppController` gets data from API and return the `JSON` object to other models.
  * `Main` starts the app, prepares views. 
  * `Weather Data` stores information of a weather data object
  * `City Adapter` describes how to display each City's info to `ListView`
  * `HistoryListAcitivity` displays info and listens for event on each `ListView` item.

- Add new `List` button to the main screen which links to the `History List Activity` and passes an `ArrayList` of city's name to this activity.
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/j9wb8x15720ousarbhac.png)
- Design view for `History List` Activity
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/7m5zihxlhb8gyndt4zut.png)

View more details in [PR](https://github.com/aadityamp01/Androapps/pull/73)

## 3. Throwback
During the modification process, the hardest part will be splitting the source code. I faced a problem with multi-thread in Java. The data was set to the view before it was returned from API. I tried to apply some knowledge about `Thread` learning from JAC444 but it did not work well. 

As such, I started seeking help from an Android Dev Senior. He is very helpful and enthusiastic. After communicating with him, I found out the solution and got a lot of useful tips for working with Android App.

All in all, thank you so much for reading the post. 

Happy coding!
Code Reviews and Pull Requests - Release 0.3
Tags: javascript, cpp, opensource
Published: 2021-11-20 00:40:04

For my third release, I focused on contributing to the community with code reviews and pull requests. In both external and internal school projects, I helped to fix issues. 

I helped to [improve image viewing](https://github.com/redxzeta/Awesome-Adoption/issues/213) in a React app called [Awesome Adoption](https://github.com/redxzeta/Awesome-Adoption) that I had previously worked on during Hacktoberfest. Importing the Carousel component from Bootstrap, I was able to make images more accessible on mobile. I am still working on ensuring the image size is correct for all. 

I also contributed to my internal school project called [Telescope](https://github.com/Seneca-CDOT/telescope), a great tool for aggregating blog feeds. I helped fix an issue [improving local development setup](https://github.com/Seneca-CDOT/telescope/pull/2493) of the status dashboard for development purposes. My work was later merged with the help of the community. 

I also did a few code reviews for the first time on Github.  I reviewed two pull requests on Telescope. I had never checked out a pull request before and it was interesting working to test others contributions. I approved a change for [updating the CSS of the build log dashboard](https://github.com/Seneca-CDOT/telescope/pull/2480#pullrequestreview-811760996) and 
[adding a port redirect for nigx](https://github.com/Seneca-CDOT/telescope/pull/2485#pullrequestreview-810706413). I hope to contribute more to Telescope in the future!
OSD600 - Lab 09
Tags: opensource, javascript, beginners
Published: 2021-11-20 00:09:37

## Hey,
Lab 09 is here, this time its time to add continuous integration to our SSG using (Github Actions)[https://docs.github.com/en/actions]!

---


## What Continuous Integration Do For Us?
The continuous integration allow us to keep coding, committing and pushing and for each of these actions a series of tests will be automatically run to make sure we are not breaking anything.

This way we can be sure that no matter how many people are working on a project, it will be always working acordingly.

---

## The Yml File
To be honest this was the first time I worked with a Yml file.
It was pretty simple to be honest, it was automatically created and it contained the information for the tests to run.

It looked something like this:

```yml
name: learn-github-actions
on: [push]
jobs:
  check-bats-version:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v2
        with:
          node-version: '14'
      - run: npm install -g bats
      - run: bats -v
```

---

## My Partner Testing

My partner was [Dhillonks](https://github.com/dhillonks).
His SSG worked really well, he did a really good job on making it a Script so I dont need to type `node` to make it work.

His tests were concise and precise. I added test to his convertFileToHtml().
My tests made sure that the output was Defined, not Null, True and if called without parameters it also should throw an error.

You can see the PR [here](https://github.com/dhillonks/cli-ssg/pull/27).

Thank you for Reading!
OSD600 - Auditing And Fixing Markdown File
Tags: opensource
Published: 2021-11-20 00:04:40

## 1. Issue
The [IPC144 notes](https://ict.senecacollege.ca/~ipc144/pages/content/index.html)  are written in 30 Markdown files. These files have been automatically translated to Markdown so it might contain typos and some misuse syntaxes. My task is to find and fix those issues to make the Markdown file become consistent and readable.

## 2. Modification Process
After getting assigned to `string-library.md` file which I want to work on, I forked, cloned [IPC144's repo](https://github.com/Seneca-ICTOER/IPC144) to my local machine and read through the `CONTRIBUTING.md` to set up and run the project locally. 

Then I created a new branch and started finding and fixing existing errors. Here are some modifications I made:

 * Fix typo
 * Replace block quotes with admonitions

Thanks to [Docusaurus](https://docusaurus.io/) which supports admonitions, I can make use of this feature to display **note** for a better readability.

```
:::note

We have allocated 62 characters to accommodate 30+30 characters plus the blank space separator and the null terminator byte.

:::
```
The above code will be displayed as:

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/0393wzmg64doj4x21iqg.png) 

 * Remove extra white spaces in code blocks
 * Fix frontmatter

I update the frontmatter with more information:
```
---
id: string-library
title: String Library
sidebar_position: 2
slug: /refinements/string-library
description: String library is a standard library to process character strings
---
```
 * Add inter-site links to other page

Linking to another page which has related information helps learners to review the knowledge so I decided to add some links to the file:

```
The standard library that ships with [C compilers](/A-Introduction/compilers#the-c-compiler "C compiler") and processes [character strings](/F-Refinements/character-strings "Character Strings") is called the string library. 

```
 * Add bold emphasis for some words 

## 3. Getting reviewed
After summitting a [PR](https://github.com/Seneca-ICTOER/IPC144/pull/75/commits/e12fc316b14cc9e2403a0b203e443272acef2319), Leyang Yu suggested me to replace the headings for String Length, Copy, Compare, and Concatenate with the third level heading. It's totally appropriate so I applied it and here is the final result:
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/liull4qkw37e0ej6v890.png)
 
The process was interesting and enjoyable!
Why AI isn't replacing writers anytime soon
Tags: ai, machinelearning
Published: 2023-03-30 17:08:41

---
title: Why AI isn't replacing writers anytime soon
published: true
date: 2021-11-20 00:00:00 UTC
tags: ai, machinelearning
canonical_url: https://blog.brainstory.ai/ai-wont-replace-writers/
---

The rise of another AI model like Dall-E has some people wondering if it will replace graphic designers. GPT-3 didn’t replace writers, GitHub Copilot isn’t going to replace engineers, and Dall-E won’t be replacing visual artists either.

## What is machine learning good at?

Machines are good at automating and scaling manual tasks. A machine processes a 12 hour Twitch stream quickly and efficiently. They don’t get bored like humans.

Machine learning excels in a well defined problem scope, when you can tell the machine exactly what you want. For example, machines can follow instructions like:

1. “Go through this Twitch stream and return timestamps when someone is happy. Here’s a definition of happy.”
2. “Take this timestamp and find the closest silent moment from before and 30 seconds after. Here’s the threshold for silence. Clip just that moment.”
3. “Watch this clip and transcribe what the people are saying. Then summarize what’s happening into 1-2 sentences.”

The above process outlines the work required to create social media clips from a long Twitch stream. Without software, it’s work that creators and editors often have to manually do if they want to prevent engagement loss for their long form content.

## What can’t machines do?

Humans have to be the ones strategizing, thinking abstractly and supplying creative direction. Their expertise on the “who”, “what”, and “why” can’t be outsourced to a machine.

Content strategy is figuring out what types of content to make and for who. That planning is necessary for content to have the most impact. Writing code tutorials for a print newspaper doesn’t make sense. On the other hand, creating video tutorials for YouTube is a great place to reach many developers. Understanding what motivates the audience (the “why”) is a human to human experience.

By automating the boring and time consuming tasks, humans can get back to doing the work that energizes and motivates us.

**Are you doing something boring, manual, and necessary with your content? Let us know - we’d love to help.**
Adding Continuous Integration
Tags: cpp, opensource
Published: 2021-11-19 23:51:56

This week we learned how to use the tests we made last week and directly implement them into our GitHub repositories. By adding continuous integration we no longer have to run our tests manually every time we make a new commit to our repos, instead it does it automatically every time we make a new pull request or merge into the main branch!

Since I've been coding my project using Visual Studio I used MSBuild as my workflow template, because Visual Studio uses MSBuild to compile and build projects when running the built in debugger. So that makes it easy to make sure that it will compile properly on GitHub's side. Other than that decision it was really easy to setup the YAML file, I just needed to add two lines:
```yaml
run: msbuild LennahSSG.sln /p:OutDir=D:\a\LennahSSG\LennahSSG\LennahSSG
```
to build the executable and
```yaml
run: D:\a\LennahSSG\LennahSSG\LennahSSG\LennahSSG.exe -t
```
to run the test.

After setting up my own CI and ensuring everything was working properly I teamed up with [Andrew Tassone](https://dev.to/drew5494) to work on [his SSG](https://github.com/drew5494/the-great-site-generator). I added a new test case to his that would check for proper markdown conversion with the `<h1>` tag, you can check out the PR [here](https://github.com/drew5494/the-great-site-generator/pull/14). It was a bit more difficult to add a new test case to a different project, mainly because his structure for his project was still a larger collection of code, rather than many smaller functions. He did not refactor his project like I did so I had to think of how to test things with the project in one piece.

After setting up CI for the first time it is incredibly convenient. It is a bit annoying to set up tests the first time and then making sure they cover as many things as possible but once you have it up and running. Turning tests into CI is very simple to do and in the long run it makes adding new features and just making changes in general so much better, because then you will know when something breaks and where it breaks.
Code Reviews
Tags: opensource, seneca, codereview
Published: 2021-11-19 23:28:06

For my release 0.3 I did code reviews for 2 other students pull requests on the [IPC144](https://github.com/Seneca-ICTOER/IPC144) repo. It was a bit tough to find anything valuable to add, many students were leaving comments on pull requests as they came in and in one case I was looking through one only for someone to comment before I got to the end of the commit. I don't think either of my suggestions got added either, both were merged before the other students implemented my feedback. 

In any case, the [first code review](https://github.com/Seneca-ICTOER/IPC144/pull/91) I did looked at [this issue](https://github.com/Seneca-ICTOER/IPC144/pull/60). This student added a tutorial to convert tables from the [IPC144](https://github.com/Seneca-ICTOER/IPC144 notes to images. I looked through and everything looked good, but I caught a spelling mistake and mentioned that "Alt test for accessibility" should probably read "Alt text for accessibility".

The [second code review](https://github.com/Seneca-ICTOER/IPC144/pull/116/files/aa027d6ef4457296fc140a241b6999bf1411fe5d) I worked on was for a student working on auditing and fixing [records-and-files.md](https://github.com/Seneca-ICTOER/IPC144/issues/85). Again, I couldn't find much to critique with this one - it seemed pretty thorough and another reviewer commented before I could find anything. Ultimately I just posited that `newline` could be enclosed in backticks to emphasize its status as a control character, just a stylistic suggestion if anything. 

This was a neat exercise, I haven't been on the other side of a code review before so it was cool to take a look at other students' code and look at how they approached working on similar issues to mine.
Telescope code reviews
Published: 2021-11-19 23:25:08

While working on a new [feature](https://dev.to/menghif/fetching-the-github-api-119e) for [telescope](https://github.com/Seneca-CDOT/telescope), I got involved in **reviewing** code from other students.

The **first** [PR](https://github.com/Seneca-CDOT/telescope/pull/2472) I reviewed was for the [issue](https://github.com/Seneca-CDOT/telescope/issues/2433):

>**"Customize the dashboard so it looks like it belongs to Telescope"**

This was a fun PR to review, I like what [Suhhee](https://github.com/suhhee1011) did to customize the layout. I offered some suggestions on what to fix and/or improve.
Once this PR gets merged, the dashboard will look more like it belongs to Telescope.

---

The **second** [PR](https://github.com/Seneca-CDOT/telescope/pull/2476) I reviewed was for the [issue](https://github.com/Seneca-CDOT/telescope/issues/2419):

>**"Show Posts count on status dashboard"**

At first I had problems testing it locally since some steps were necessary to make it work but the instructions were not present in the PR description. Fortunately [Hung](https://github.com/nguyenhung15913) posted the instructions and I was all set for the review.

I wrote some suggestions, while other reviewer wrote theirs and we went back and forth for some time. I also made use of the [Gitpod](https://www.gitpod.io) integration to test in the cloud and it was a good experience (expect it's too slow when launching compared to my local setup).

---

### Time consuming!
I can't believe how much time it takes to review pull requests. There must be some time management secrets that only repo maintainers know about.

Despite this, I found it great to see how other people approach solving a problem. I am also getting used to check for GitHub notifications throughout the day to make sure I am not missing something important.