DEV Community: Karthik Pariti

The fundamentality of building projects and how is it useful in the overall development

Karthik Pariti — Tue, 14 Dec 2021 10:51:12 +0000

If you have read my previous article, which was about Why you should not work on projects, you might be a bit uneasy seeing the title of this article, because, in a sense, both of them are quite the opposite in regard to building projects.

But why? As they say, a coin has 2 sides associated with it. The same applies to building projects. Hence I decided to explore both the facets of this concept.

So, if you were convinced not to build projects from the previous article, maybe this one convinces you to do the contrary.

Let's get started!

In the previous article, I've described the hardships, difficulties, and hurdles during project development. But as I previously said, there is also another facet to this.

There are not only disadvantages and problems regarding project development, there are many advantages and enriching aspects. This article elaborates and details these positive instances about projects.

Projects enrich creativity -
When you think of ideas for projects, you are utilizing your creative skills. We all know how important creative skills are. Your projects signify how creative you are. But that is not an end to it. Building projects frequently enrich your creativity, leading you to perform better.
Projects comprehend teamwork -
Developing projects with a group comprehends teamwork, communication skills, coordination with others and makes you compatible with team members. These skills are known to be extremely important and vital in workplaces.
Projects nourish vital skills -
Projects enrich skills like problem-solving skills, and project-specific skills, and so on. Almost everyone is familiar with this point that projects improve the existing skills as well as develop new ones during the process.
Projects make you curious -
Being curious is very advantageous for nourishing the mindset of people to always question their surroundings, learn from what they do, and self-derive answers from their questions. Curiosity is vital for a critical thinking approach.
You build confidence in yourself -
When you build your project you are confident of yourself, about your skills and are further motivated to keep progressing.
You learn how to manage your surroundings -
Project management is an essential factor that needs to be taken care of while making a specific project. While managing your project, you also learn how to be organized, plan in advance, etc. In the process, you also learn to manage other parts of your life more efficiently than before without problems.

So these were some of the advantages/pros of building projects. Note that these aren't the end to the positive side of building projects.

But one thing that I've observed to be common among people building projects is that they abandon their current projects in the process of building itself and move on to new ones, this creates a virtuous cycle where you do not focus on one thing and always look for alternatives.

This in the long term leads to major commitment issues where your lack the important trait of being committed to what you do and always abandon your responsibilities halfway through itself.

It's completely normal when you think that you don't feel the same interest as before about a specific thing, this may lead to not achieving anything at all in the epilogue.

So how do you overcome this? Just keep faith in what you do. Even if you think you don't have the same enthusiasm as you did before, but you still know that what you did until now ran for a good cause. This must become the motivation for you to progress in what you do. But if you think your idea isn't valid anymore or it doesn't apply to anything anymore, maybe abandoning it is for the good.

You can reach out to me on any of these platforms listed here for any further queries!

Top 5 reasons to not work on any projects

Karthik Pariti — Wed, 06 Oct 2021 15:14:36 +0000

Everyone aspires to do amazing projects and tries to impress everyone with those projects. But why should you not do any projects?

Here are the Top 5 reasons to not work on any projects

So let's get started!

Reason 1: Doing projects is hard! Rather not do it at all!

I give up on projects before even doing them. Why to waste my time on a thing that is hard? I'll rather continue doing the same old things which I please to do.

Doing projects is hard indeed!

Reason 2: You shouldn't do projects so that you can have a noob resume

Don't do projects so that you can have a very noob and basic portfolio/resume having nothing other than your degree certificate

Reason 3: To be in the tutorial loop forever

Why do projects when you can watch tutorial after tutorial and keep on doing whatever the guy making the tutorial says and follow them blindly? A very captivating reason indeed! Yes sir!

Reason 4: Don't do projects to have zero confidence in yourself and in your skills

Taking up a project, doing it, and finishing it gives you confidence in yourself and in your skills. But that is exactly what mustn't be done!

Reason 5: Don't do projects to not learn things faster

Why learn faster by doing projects when you can just do it at your own slow pace and especially when it's said The learning process must be slow and steady for everyone to grasp it easily. Another captivating reason! Yes sir Yes sir!

Reason 6: Doing projects makes you an expert in your field!

The reason is fine, but who actually said it? Absolutely NO one. So it is something you absolutely mustn't and shouldn't do!

And finally, don't react to this article, don't comment your views in the comments section, and don't forget to not do any projects!

Hoping that you are convinced to NOT work on any projects now!

Also, don't join the ByteSlash Community to NOT work on amazing projects with a supporting and fun community, and let's not connect!

What is Typescript and why should you be using it?🤔

Karthik Pariti — Mon, 27 Sep 2021 15:35:59 +0000

I am sure that in your web development career you must have used JavaScript at least once. And I am sure you must have found it very useful and very powerful. But what if I say there is another language that is just as powerful as JavaScript and has way lesser bugs when compared to when you use JavaScript in your app.

Now, what's the language that I'm talking about?

That language is TypeScript.

What is TypeScript?

TypeScript is a programming language developed and maintained by Microsoft licensed using the Apache License 2.0. TypeScript is a superset of JavaScript, meaning that all the concepts of JavaScript are present in TypeScript which is combined with TypeScript's own concepts that make the language increasingly powerful.

If you know JavaScript, it mustn't be a problem switching to TypeScript as it essentially has the same concepts as JavaScript except a few of TypeScript's own concepts.

So what are the advantages of using TypeScript?

Concepts similar to JavaScript

TypeScript has similar concepts as JavaScript which makes the switch seamless

TypeScript is type-safe

TypeScript is type-safe meaning that you have to define the type of the variable before initializing it.
Making your code type-safe decreases the number of bugs evolved in your app over time and makes it cleaner.
Types give superior integration to your editor which improves editor support meaning increased developer productivity and gives you a better codebase.

It keeps JavaScript in check

TypeScript keeps your JavaScript in check. Meaning that it validates your code before it's even run which gives you an edge over using simple JavaScript.

Runs on multiple places

TypeScript runs in multiple places. It converts your JavaScript which can be run on the web, on a phone, or on Node.js.

Type Inference

It uses something called type inference which is nothing but adding types to your code which gives safety enabled without you writing long and additional lines of code making your app faster and scalable.

It is developed and maintained by Microsoft

TypeScript is developed and maintained by Microsoft and widely used by many companies which means it's nowhere near to reaching its end. So you can expect regular updates and fixes to the language.

Those were some advantages, let's move on to some testimonials!

TypeScript is widely used and loved by developers around the world. Here are some testimonials given by popular companies which is another indication that switching to TypeScript is worth it.

Slack:

According to slack, the switch to TypeScript made their life a lot easier in terms of bug-fixing and productivity.
They also said Static Analysis which analyzes your code and tries to infer types and warns the developer in advance before the code even runs.
They were overwhelmed by the amount of bugs found when they were converting their code to TypeScript.
They were also surprised about how powerful editor integration is. Editor integration can be game-changing when your code editor has autocomplete where TypeScript suggests what your next piece of code can be and makes your editor do the same.

Airbnb: According to Airbnb, TypeScript prevented 38% of the bugs based on their analysis.
According to them, TypeScript lets developers be productive and safe at the same time.

So those were some of the popular testimonials! Moving onto some surveys!

In StackOverflow's developer survey in 2020, TypeScript was declared to be the 2nd most loved programming language
TypeScript was used by 78% of the 2020 State of JS survey and 93% went on to say that they would use it again. It was also awarded the Most Adopted Technology based on year-to-year growth

Moving onto how to install TypeScript in your machine

Run this command in your terminal to install Typescript

To install TypeScript in your project

npm install typescript --save dev #for npm

yarn add typescript --dev #for yarn

To install TypeScript globally

npm install -g typescript #for npm

What is the difference between installing typescript globally and in your project?

Installing TypeScript globally requires you to install it only once meaning that you don't have to install it every time when you start a new project.

Whereas installing it on your project adds TypeScript only in that project directory meaning that it is not installed globally. I recommend installing it globally if you want to use TypeScript for future projects as well.

Now let's see how TypeScript is different from JavaScript in implementation.

Let's start off by writing a function in JavaScript that takes in your name as a prop and prints it on the console.

JavaScript:

function print_name(name) {
  console.log(`Hello ${name}!`);
}

print_name("charles")

TypeScript:

function print_name(name: string) {
    console.log(`Hello ${name}!`);
}

print_name("charles");

The only difference that you might notice is where you define the props. In JavaScript, you just enter the name of the prop whereas in TypeScript you need to enter the type of the prop as well. Here is the difference that you might have noticed

JavaScript:

print_name(name)

TypeScript:

print_name(name: string)

So why should I go with TypeScript instead of going for JavaScript when the output is the same?

This upcoming example will say why

Example 2: In this example, we will print the age of the person and we would want the function to print it on the console.

function print_age(age) {
  console.log(`Your age is ${age}`);
}

print_age(20)

Here I entered the age of 20 and it ran successfully. Let's try giving something other than numbers and see if it works.

function print_age(age) {
  console.log(`Your age is ${age}`);
}

print_age("Karthik")

And the output which was given by the console was "Your age is Karthik". So this is quite troubling right. In a situation when you want only a number you need to write additional code that looks somewhat like this for the program to accept only a number.

JavaScript:

function print_age(age) {
  if(typeof age === "number") {
    console.log(`Your age is ${age}`);
  } else {
    console.log("Please enter a valid type");
  }
}

print_age(20);

Output: Your age is 20

This program only accepts a Number data type. But you can write this same program in TypeScript in way lesser lines of code.

TypeScript:

function print_age(age: number) {

    console.log(`Your age is ${age}`);
}

print_age("Karthik");

Here the age prop can take only a number hence when the string Karthik is given as input, the console throws this error.

Argument of type 'string' is not assignable to parameter of type 'number'.

Hence if we mend our ways and give only a number an input like this, the code should run.

function print_age(age: number) {

    console.log(`Your age is ${age}`);
}

print_age(20);

Output: "Your age is 20"

Useful Links:

TypeScript Website: https://www.typescriptlang.org

Let's connect:

Social Media's: https://links-app-kardev07.vercel.app