teleren/devto huggingface dataset:
Auditing Sony's Website with Web.dev
Published: 2021-05-04 07:55:26

Creating a website can be an arduous task at times. When you consider everything that needs to go into making a website it can be overwhelming even for professionals whos goal to reach as many users as possible. There are many tools that web developers use in this process. The two tools we will be focusing on today is Web.dev and wave. Both tools are useful for leaning the best methods of expanding the reach of a website.

##What is a website audit ?

Web.dev is a website auditing tool that evaluates four key factors when ranking how optimized a website is for a search engine: 

Performance
Accessibility
Best Practices
SEO

##What is SEO anyway ?

SEO stands for search engine optimization. It is commonly used as a means for how easy search engines can find any given website.

##What are the results from your Audit ?

I decided to audit Sony’s PlayStation Website with web.dev and here are the results:

Performance    -  12
Accessibility  -  93
Best Practices -  80
SEO            -  83

Surprisingly Sony's website scores one of the lowest performance levels of 12. and one of the highest Accessibility scores of 93. Wab.dev gives us the ability to learn more about the high impact issues of the website so that we can learn from them. The natural next step is to run the website through WAVE which is a tool for helping devs to learn about accessibility of their sites web content. I made a video below that dives deeper into both tools on Sony's website specifically. 

##Where can I learn more ?

Lean More from the official Web.dev website here : 
https://web.dev/about/
And from the official Wave website here: 
https://wave.webaim.org/

##My video

Check out my video auditing Sony Playstation website here : 
https://youtu.be/CPd9tWcBiIY
find() vs filter()
Tags: javascript, uiweekly, typescript
Published: 2021-05-04 08:12:07

Many of us are accustomed to using to two common functions in js, that is, filter() and find(). A lot of the times we use these functions without paying a lot attention to it. Let's discuss in which situations should you actually use them.

##find():
find is a function that iterates through an array and returns the first element in the array that matches the given predicate.
eg. find the person with name _Amy_
{%runkit%}
const arr = [{id: 1, name: 'Tom'}, {id: 2, name: 'Claudia'}, {id: 3, name: 'Richard'}, {id: 4, name: 'Amy'}, {id: 5, name: 'Rebecca'}];
console.log(arr.find((person) => person.name === 'Amy'));{% endrunkit %}

##filter():
filter is a function that iterates through an array and returns a new _array_ of all elements in the array that matches the given predicate.
eg. finding all person whose name's start with _'R'_
{% runkit %}
const arr = [{id: 1, name: 'Tom'}, {id: 2, name: 'Claudia'}, {id: 3, name: 'Richard'}, {id: 4, name: 'Amy'}, {id: 5, name: 'Rebecca'}];
console.log(arr.filter((person) => person.name[0] === 'R'));{% endrunkit %}

Now, that we have seen what these two functions essentially do let's see when should we use them.

filter() basically runs through the entire array to see if the given predicate is matched which means you should be only using it if you expect more than one item to match this predicate. Although, this seems like a pretty simple thing to remember a lot of the times we see people using filter in place of find().
When you want to search for an element in the array use find() instead of returning an array from filter and doing something like `resultOfFilter[0]`.

The main advantage of using find() in those cases is that find returns as soon as a match is found, but filter would run through the entire array even if a match is found in the `1 st index position` and you don't want to do that for large arrays when all you are concerned about is one match!

See below how filter iterates through all the elements while find returns on the first match.

{% runkit %}
const arr = [{id: 1, name: 'Tom'}, {id: 2, name: 'Claudia'}, {id: 3, name: 'Richard'}, {id: 4, name: 'Amy'}, {id: 5, name: 'Rebecca'}];
console.log(arr.filter((person) => { 
console.log('inside filter, current name: ',person.name);
return person.name === 'Tom' }));
console.log(arr.find((person) => { 
console.log('inside find, current name: ',person.name);
return person.name === 'Tom' }));{% endrunkit %}
Create CSS Gradient Animations Effortlessly 🌌
Tags: css, codenewbie, webdev, beginners
Published: 2021-05-04 07:42:08

Here's a preview of what we'll make 👇

{% codepen https://codepen.io/jordienric/pen/JjEVgXv %}

## 1. Create a gradient
I'll save mine in a variable for easy reuse.
```css
:root {
  --main-gradient: linear-gradient(-66deg, #15162a, #000, #291a33, #000, #381a2c, #000, #121e42);
}
```

## 2. Create a container div and add the background

We use background-size to zoom into the gradient.
```css
.container {
  background: var(--main-gradient);
  background-size: 400%;
}
```

## 3. Create the animation
This is a basic animation that changes the background-position. Since we zoomed into the gradient it will look like it's moving.

```css
@keyframes gradient {
  0% {
    background-position: 0% 50%;
  }
  50% {
    background-position: 100% 50%;
  }
  100% {
    background-position: 00% 50%;
  }
}
```

## 4. Add the animation to our container!

```css
.container {
  background: var(--main-gradient);
  background-size: 400%;
  animation: gradient 8s ease infinite;
}
```

You can check the codepen [here](https://codepen.io/jordienric/pen/JjEVgXv)

And that's it!

### Follow me on [twitter](https://twitter.com/jordienr) for more!
Clean Your Code
Tags: codequality, codereview, discuss, opensource
Published: 2021-05-04 07:40:42

![title](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/engpw4yxpik02dnzg5qt.png)

# So What Is It About
> Just chill and read 


So i was fixing some messy code as i dig deeper i noticed a set of code that could have been easily made better had the developer put a little effort into fixing it during the inception instead of leaving it “Latter ... ”. Legacy code is mostly the result of developers not trying to  “stay clean” . Small things that may seem little while you are doing them, could easily pile up and haunt you or the next developer at later time.you should have the habbit to keep it clean while you are coding. 

# If you dont follow the rules you'll end like this : 

(from yoyo code) :

![yoyocode](https://yoyo-www.yoyogames.com/images/pages/blog/finish/1.png)

## What about cleaning up the messy code that you wrote while  waiting for the PR approval ? 
Ans :  Bad code is going to attract more bad code and force you  to refactor it “later..”. Do it  yourself  teach yourself the habit of clean coding instead of leaving it for “refactoring later”.

### Fell free to discuss about you refactoring methods 

# Conclusion

# Keep Coding !!!

# 🙏 Share with your friends on [Twitter](https://twitter.com/intent/tweet?text=%22Clean%20Your%20Code%22%20by%20@alestor123%20%23DEVCommunity%20https://dev.to/alestor_123/clean-your-code-19dp)
7 pieces of advice I wish I knew when I started as a Junior Software Engineer
Tags: watercooler, codenewbie, career, beginners
Published: 2021-05-04 07:38:46

Photo by <a href="https://unsplash.com/@corinarainer?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Corina Rainer</a> on <a href="https://unsplash.com/s/photos/taking-notes?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Unsplash</a>
  

Someone asked this question recently and this are my thoughts about it.

## Write more & take notes

Writing is a really valuable skill for developers, the sooner you start developing it the better. Take notes so you have stuff you can write about later.

## Teach what you learn

The best moment to teach something is when you just learned it. Apply to do workshops with other developers, write articles, create videos. Teach what you learned and you will solidify that knowledge.

## Show your work

You'll feel imposter syndrome every time. Publish articles, create websites, try to get people to use them. You'll only find the things you can improve at when you see people reacting to your work. 

## Connect with people

Try not to be just a lurker and participate in conversations about topics you're interested in. Give your opinion and your thoughts. Learn from others.

## Ask more questions, even the stupid ones

Specially the stupid ones. Asking questions will start conversations that will make you learn 100% times more than tutorials and books.

Asking good questions is a great skill, and you develop it by asking stupid questions.

## Chill, you don't have to know everything by tomorrow

Learn things as you need them. Don't rush it or you'll burn out of tutorials, books and making projects for the sake of learning technologies.

## A healthy lifestyle will make you more productive

5 hours of work a day, exercise and healthy diet will get more done than 12 hours of work a day. If it's not sustainable don't do it.

Follow me on [twitter](https://twitter.com/jordienr) for more.
Terraform CLI Cheat Sheet
Tags: beginners, devops, terraform, iac
Published: 2021-05-04 07:33:04

---
title: Terraform CLI Cheat Sheet
published: true
description: Terraform CLI Cheat Sheet 
tags: beginners, DevOps, Terraform, IaC
cover_image: https://dev-to-uploads.s3.amazonaws.com/uploads/articles/hr81dtbcj3q83svnfk0b.jpg
---

Several years ago, when I started learning and using the Terraform infrastructure as Code (IaC) technology, I started looking for a cheat sheet and found none.

At first I thought to myself thin, it would be so useful to have one and then I started to think to myself what if I created one?
But who am I to be able to create one? I am not [Hashicorp](https://www.hashicorp.com/) ^^, I am a nobody.

And finally, I started to create the cheat sheet with all the tips I knew about the Terraform CLI and all the things I found important and useful to know.

Today, I updated my original Terraform CLI Cheat Sheet and I hope you'll like it and it can help you:

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/hr81dtbcj3q83svnfk0b.jpg)
![Alt Text](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/g7k33uozam8e67dhtsri.jpg)

You can find the Terraform CLI cheat sheet updated and complete PDF version in my [GitHub repository](https://github.com/scraly/terraform-cheat-sheet/blob/master/terraform-cheat-sheet.pdf).

If you like it, it would be nice to star it in order to increase its visibility and help other pople :-).
The most preferred way to add CI/CD to React Native 
Tags: help, discuss, reactnative
Published: 2021-05-04 07:20:41

---
title: The most preferred way to add CI/CD to React Native 
published: true
description: 
tags: #help #discuss #reactnative
---

I've got a few projects where I need to add in CI/CD for React Native and while I've got fastlane setup and React Native has the environment variables working, my main issue is with the bootstrapping of a new project and having to set all this again. 
- Service Accounts for Play Store 
- Gitlab Environment files
- Apple Account

While I know the above can't be given up , I was thinking something on the line's of a bash script that opens up the needed pages during the initial setup so I remember everything that needs to be taken care of before I let gitlab execute everything.

Would like to know if there's other solutions that people are following.
Become a Faster Developer with Vim
Tags: linux, vim, productivity
Published: 2021-05-04 06:55:14

Vim is the world’s most powerful text editor. It's available for nearly every computing platform in existence, and its core design philosophy is simplicity. Vim gives you the power to do what you want it to do with a minimal amount of effort. 

Vim is a **keyboard-based text editor** originally released in 1991. It is named after the word "vi" from the command line. You can do everything faster than with a mouse, it supports macros, jumping to lines and much much more.

Vim can be used in the terminal, over SSH, inside Jetbrains tools such as PyCharm, AndroidStudio, inside Visual Studio Code... and basically everywhere.

## How to Master Vim?

If you want to become a faster developer and are new to vim, you can try [this tutorial](https://vim.is/)

Vim is an amazing tool for editing text. If you don’t use Vim, you should seriously consider it. It makes writing code faster and more efficient.

The problem is that Vim isn’t easy for beginners and the learning curve can be steep, especially if you’re not coming from a background in hardcore operating systems or programming.

As a beginner, it can be discouraging to use vim. You'll be frustrated not understanding commands, not knowing the right timing to hit the key. 

The exercises make it easier and fun to learn Vim. 

![learn vim](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/9wm815yhfcdx95a593ec.png)

Personally I use Vim mode all the time in Visual Studio Code and the terminal. One workflow everywhere and much faster than not using vim.

![visual studio vim](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/mfvjfxj9i40gn5wo8qae.png)

Vim is your best friend because it's used by programmers, writers and developers all over the world. Learning Vim is a must to maximize your development speed and efficiency.
Day 51 of 100 Days of SwiftUI
Tags: swift, 100daysofcode
Published: 2021-05-04 06:52:57

I just completed day 51 of 100 days of SwiftUI. Today I completed the cupcake ordering app implementing an API call to simulate ordering the cupcake. I did so using https://reqres.in/

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/16fzvlmzugvh3rgsej83.png)![Alt Text](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/m3u46phi0o4syfjy8ns8.png)
Devops 25 Questions Asked In Interview In 2021
Tags: devops
Published: 2021-05-04 06:22:58

Here are the top 25 DevOps Interview questions which is asked in DevOps interviews..
Operating system
1) What is the distinction among Linux and Unix ?

2) What’s a KVM ?

3) How might you ensure a help begins an OS of your decision ?

4) Here’s a terminal. What kind of Linux is running ?

5) Write an order to erase all unfilled record under a registry.

6) What is Active Directory ? How would you make a worker join an area ?

Systems administration
1. What is the contrast among TCP and UDP ?

2. What is ICMP ? For what reason should you block it ?

3. What is IPv6 ? For what reason should we give it a second thought ?

4. In a professional workplace clients from London can ping a specific worker however clients from New York can’t, what steps will you take to investigate the issue ?

5. What steps are expected to change the host name on a Linux machine ?

6. Where is the host name document on a Windows worker ?

7. How is a host name settled on a Linux machine ?

8. What’s a SSL burrow ?

9. What’s a SDN ?

Scripting (inquiries here change on rating and rely practically upon advising the individual to compose a short content)
1. What is your most loved scripting language ? Why ?

2. What are configuration designs ?

3. Portray a few contents you have composed/computerization you have done/programs you have composed. Legitimize your decision of scripting language and configuration designs.

4. Would you be able to port a similar content to another dialect ? On another OS ?

5. What amount of time would it require for you to get familiar with another dialect ?

CI/CD Pipeline
1. How might you follow a twofold arrangement back to the source code ? How might you construction such a form ?

2. How would you oversee conditions in DevOps ?

3. CI must be utilized to figure out arrange time blunders rapidly. Valid/False. Clarify.

4. How might you structure CD for an application that relies upon 3 other applications ?

5. How would you plan limit with regards to your CI/CD workers ?

6. All your fabricated doubles ought to be registered to your git/svn for snappy sending and posterity. Valid/False. Clarify.

Thanks for going through the top 25 DevOps interview questions in 2021, we hope it served your purpose.

That is everything we can consider at this moment. we will continue to refresh these as I consider more inquiries and subjects relevant to DevOps and AWS.
Create a large number of C# applications at once
Tags: dotnet, cli
Published: 2021-05-04 05:37:42

---
title: Create a large number of C# applications at once
published: true
description: Create a large number of C# applications at once
tags: dotnet, cli
//cover_image: https://direct_url_to_image.jpg
---

I'm waiting for [Visual Studio 2022](https://devblogs.microsoft.com/visualstudio/visual-studio-2022/?WT.mc_id=DT-MVP-5002209)!

One of the most important features of Visual Studio 2022 is that it will be 64-bit.  
This means that Visual Studio will not run out of memory even when developing large applications.  
The above blog also shows the launch of the solution, which includes 1600 projects.

I want to experience the same thing when Visual Studio 2022 is released so that I can create huge solutions at once.

NET Core provides a command line interface (CLI), so you can create solution files and project files all with commands.  
Let's just keep on creating them with for statements!

```sh
SOLUTION_NAME=HugeDotnetSolution
dotnet new sln -o $SOLUTION_NAME
cd $SOLUTION_NAME

for i in `seq 1000`
do
  APP_NAME=ConsoleApp$i
  dotnet new console -n $APP_NAME --no-restore
  dotnet sln $SOLUTION_NAME.sln add $APP_NAME
done
```
When software meets social: Job and career
Tags: psychology, career
Published: 2021-05-04 06:18:54

Hi all. I'm proud to be a brand new member here at dev.to, and to hopefully reach out and have some good banter with everyone. 

I was recently fortunate enough to bear witness to an out-of-the-box presentation by a very intelligent and capable colleague of mine. I'll be frank here: the presentation could have been anything but interesting; given the title of the calendar invite, I may well have been able to half-listen and arrive on the other side of the meeting no more educated. But it wasn't that. 

By examining the workplace environment and paying attention to everything beyond the usual survey questions, this colleague inspired me to ask bigger questions, and moreover ask myself harder questions. You're likely familiar with them:

- What am I doing here?
- What is the purpose driven by my priorities?
- Do I even have priorities?

In the age of developers in 2021, the term _fast-paced_ is now overused and mundane; we know pace like the back of our hand. JavaScript libraries last about as long as vapour trails left by a jet plane. What this means, though, is that it's all too easy to be taken hostage by the details of a particular platform or bug, and forget the big picture. Stress often becomes more important than your own goals and priorities. 

It was with this realisation that I felt a sudden onset of motivation to capture what this colleague had awoken so effectively, and to make the message not only applicable to other colleagues, but also to all developers around the world who share the wish to make sure their job is their career, and to make their days and keystrokes meaningful.

I've finished the first cut of my blog, in which I include [my manifesto](https://thedylanboyd.com/manifesto) _(P.S. I have no tracking or advertising)_. Here, you'll find the manifesto itself, titled **The M/Movement**, as a downloadable PDF document. Designed to be as readable and applicable as possible, it walks through how your work environment should be a place you **enjoy**, and that **having fun** and **sharing ideas** are never something that you should feel excluded from doing. 

This document was not initially intended for public consumption, but by the time it was finished, I stood back to look at it and said _Wait a moment, this could be about anyone_, referring to developers, of course. 

**If you have any PMI (plus, minus, interesting) thoughts** regarding this manifesto, those thoughts are most welcome. Thank you for taking the time. All the best!
Go Crash Course Part I: Introduction
Tags: go, programming, beginners
Published: 2021-05-04 05:50:44

# Go

[Go](https://golang.org) is an open source programming language known for its simplicity and ease of use. It has great concurrency primitives. I have been an user of go for about 4 years now. I will try to collect things I have learned over the last few years to help you get GOing (pun intended 😄!)

## Installation

Go is available to download for all OS.

Instruction for installing go is [here](https://golang.org/doc/install)

> If you are Mac user you can use brew to install Go.

## Go features

There are many programming languages out there. Why would you choose go? I think there are a few reasons why Go can be very useful.

- It is compiled. So small binaries and great for building containers.
- It is fast. Probably not as fast as c/c++ or rust, but for most use cases Go is faster than Java, Python or JavaScript.
- It is simple. Although this is fairly subjective. But for most people familiar with any other language getting comfortable with the go syntax is a matter of days. The language does not have too much things. So the learning curve is not too steep.
- The standard library is very good. For most thing you want to do with go, you don't have to go looking for external libraries. The standard library does an excellent job in giving us the tool we need. For the things we need to use libraries for we can find it [here](https://pkg.go.dev/)
- The community around go is one the best around. From the Go team to the advocates of Go, I find the people very welcoming and helpful. 

## Get Coding

Talk is cheap, show me the code.

```go
package main

import (
    "fmt"
)

func main() {
    fmt.Println("Hello, World")
}
```

All Go source code is organized in `package`. For the entry point of our application we use package main. Our code execution starts at `func main`. That is also how we define a `function` in Go. Go code executes in sequence. All our `import` are at the top of the file. In this example we are importing the `fmt` package. `fmt` package has many io related functions. We use the `Println` method to print to console. 

We can access the source code for this [here](https://github.com/moficodes/go-crash-course)

```bash
git clone git@github.com:moficodes/go-crash-course.git
cd hello-world
go run main.go
```

> If you don't have your ssh keys setup in Github you can also clone using https. But ssh is preferred. 

We should see it output `Hello, World` in our terminal.

## Next Steps

This is Part 1 of this Go crash course series.