DEV Community: Hooman Talakian

The Singularity: Exploring the Future of AI and the Impact on Humanity

Hooman Talakian — Fri, 24 Feb 2023 19:49:19 +0000

Singularity is a theoretical concept that has fascinated scientists and thinkers for years. It refers to a hypothetical point in time when artificial intelligence (AI) surpasses human intelligence, leading to a rapid acceleration in technological progress and the creation of new, super-intelligent entities. Singularity is not a new concept, but it has gained traction in recent years due to advances in AI and machine learning.

The idea of singularity was first introduced in 1965 by mathematician and computer scientist I.J. Good. Good predicted that machines would eventually become smarter than humans, leading to a future where technological progress would accelerate at an unprecedented rate. However, it was not until the 1990s that the term "singularity" was popularized by mathematician and computer scientist Vernor Vinge.

One of the key concepts behind singularity is the idea of exponential growth. This refers to a scenario where the rate of technological progress doubles every few years, resulting in an exponential increase in the rate of progress over time. Many experts believe that we are currently living in a period of exponential growth, and that the singularity may be just a few decades away.

There are a number of different theories about what will happen when singularity occurs. Some experts believe that it will lead to the creation of new, super-intelligent entities that are capable of solving complex problems and creating new technologies at an unprecedented rate. Others believe that it could lead to a dystopian future where machines become hostile and turn against humanity.

Despite the uncertainty surrounding singularity, there is no doubt that it is a topic of great interest to scientists and thinkers around the world. There are many different perspectives on what singularity might mean for the future of humanity, but most agree that it will have a profound impact on our world in the years and decades to come.

One of the most intriguing aspects of singularity is the potential for new, super-intelligent entities to emerge. These entities could take many different forms, ranging from sophisticated computer programs to physical robots or cyborgs. Some experts believe that these entities will be capable of solving complex problems and creating new technologies at an unprecedented rate, leading to a new era of technological progress and innovation.

At the same time, there are also concerns about the potential risks associated with singularity. For example, there is a risk that super-intelligent entities could become hostile or unpredictable, leading to catastrophic consequences for humanity. There is also a risk that singularity could lead to widespread unemployment and economic disruption, as machines replace human workers in many industries.

Despite these risks, there is no doubt that the singularity represents an exciting and potentially transformative moment in human history. Whether it leads to a bright future of technological progress or a dystopian nightmare of machines run amok, there is no doubt that it will have a profound impact on our world in the years and decades to come.

In conclusion, singularity is a fascinating and complex concept that has captured the imagination of scientists, thinkers, and futurists around the world. While there are many different theories about what singularity might mean for the future of humanity, there is no doubt that it will be a moment of profound transformation and change. Whether it leads to a utopia or a dystopia, the singularity will be a defining moment in human history, and one that we should all be paying attention to as it approaches.

Whether you believe it or not, ChatGPT wrote this article! And the cover photo is from DALL-E!
I only said this to ChatGPT:
"write a comprehensive article about singularity"
And said this to DALL-E:
"The Singularity: Exploring the Future of AI and the Impact on Humanity" (the title of this article, also by ChatGPT!)

The Singularity is so close! What is your idea?

Tabnine! a GitHub Copilot's Serious competitor!

Hooman Talakian — Mon, 11 Jul 2022 23:34:19 +0000

GitHub Copilot's AI pair programming app has been free for a year, but now it is no longer free! However, I think it's worth it.
But if you insist on using a free alternative, there is some good news. I've found a decent alternative: Tabnine! Of course it has a Pro plan with advanced and competitive features.
Give it a try and let me know what you think of it ...
👇 "Tabnine AI" in Visual Studio Marketplace :
https://lnkd.in/emCRmXbN

JavaScript Visualizer

Hooman Talakian — Mon, 11 Jul 2022 23:22:01 +0000

If you are curious about how JavaScript works, I recommend this online JavaScript tool, which visualizes every step of runtime!
You can simply load the predefined presets of the site, or copy/paste your own code and see the steps of execution .
It is totally free. Click below to try it out:
https://www.jsv9000.app/

Amazing tools for better understanding Scope and Block in javaScript!

Hooman Talakian — Fri, 25 Mar 2022 11:10:28 +0000

If you are reading this article, we assume that you are familiar with the concept of scope and block in JavaScript, and we only intend to introduce you to some practical tools in order to better understand this concept.

JS Scope Visualizer

In JavaScript, the "Scope" concept has always been tricky for programmers, no matter how experienced they are. here is a simple tool for visualizing the scope of every part of your code. this online tool illustrates your scopes with colors. code sections with the same color are in the same scope! enjoy.
🌎 https://js-scope-visualizer.firebaseapp.com/#visualizer

VS Code Trick

If you are a programmer seeking perfect control over your code, I strongly recommend copying these two lines from here (at the bottom) into your VScode "setting.json" file. Why?!
As you can see (in GIF), by doing this, you activate a built-in function that automatically colorizes the matching brackets and at the same time indicates the scope/block you are in! So what are you waiting for?
Copy these two lines into your VScode "setting.json" file :

"editor.bracketPairColorization.enabled": true,
"editor.guides.bracketPairs": "active",

There are, of course, other tools and methods that can be used to better understand Scope and Block. Please feel free to refer to it in the comments section so it can be included in the article if it is useful.

My name is "Hooman Talakian" and you can follow me on LinkedIn if you liked this article.

It's time to visualize your Git projects!

Hooman Talakian — Mon, 21 Mar 2022 09:30:03 +0000

Nowadays, everyone prefers to visualize any type of data, and "Git terminal" is no exception! Here is a free Git graphical user interface named "Sourcetree". It is available for Windows and Mac. If you prefer a more professional interface, I can recommend "GitKraken" which you will need to purchase, but you can try it for free.
These programs are well worth checking out.

SourceTree Website: 🌎 https://www.sourcetreeapp.com/

GitKraken Website: 🌎 https://www.gitkraken.com/

My name is "Hooman Talakian" and you can follow me on LinkedIn if you liked this article.

Are the codes written/read left to right ?! (a misconception among beginners)

Hooman Talakian — Sat, 15 Jan 2022 18:19:43 +0000

Before we begin, we would like to mention that if you are a professional programmer, this article will most probably be a repeat for you, But if you think you are just starting out, or even as an experienced programmer, you are looking to rethink this concept, reading this article is not a waste.
In this article, we are not going to talk about the direction or order of code execution in a programming language (that is the way a computer looks at and interprets code, which of course has a different architecture in different programming languages), But what we mean here is something else, and that is our mental path in writing code, "the way we look at code"! at first, these sentences may be a little vague or even clear, but let us explain further; Consider the following example:

A car designer receives an order from a company to design a vehicle specifically for a crowded city. Probably the first thing that comes to the designer's mind is to visualize the crowded city space and the image of a small and light car (possibly low-consumption) with a good design to reduce traffic. Let's pause here for a moment. has the designer ever thought about technical issues such as "Engine Type" or "Body Material"? No! because at this stage, it is better to just look at the data carefully and think about them very simply. after all the aspects have been considered, the designer will probably start drawing his own designs according to the company's budget and taste and will enter a more technical phase. Probably after a lot of trial and error in the design and arguing with the company, the final design will be approved and the car will be ready to use.

Let's get to the point

Why did we use this example at all? Let's go back to the beginning of the example. If you were asked to design this car, wouldn't you have started "Designing the Car" directly in the first place? (I.e. the opposite of the above steps). This means that our minds may confuse and don't distinguish the order of the stages of "Production of something", with the order of the stages of "Thinking" about the Production of that thing! Programming is very similar to this example! Just because a code is written/read from left to right (in most cases) does not mean that you should think the same way! Take a look at the image below:

The above code is part of a JavaScript file that stores a "name" in the MongoDB database; in a simple word, by writing this code, a name (for example: "Hooman") is stored in the server storage. now pay close attention. If we want to read this code "from left to right", This is how it is analyzed :

const result

In this part of the code, the whole storing process is assigned to a variable called "result" (so that it can be used with the same name and its result can be used and processed as needed).

await

In this part of the code, the program is commanded to wait for the storing process (and not go to the next line until the result of the storing operation is known).

name.save()

and In this part of the code, the program is commanded to save the "name"!

And now with a fresh new look...

Now let's look at it differently and as we said at the beginning of the article, see how it is better for us as a programmers to "look at the code", that is like the same car designer, in order to achieve our desired goal. So let's forget the left-to-right order and look at the image below:

Now think again with new fresh look. if our goal is to "save a name in the database", what is the first code that comes to mind?! Yes ... the following code:

name.save()

What was the explanation of this part of the code?

With this part of code, the program is commanded to save the "name"!

So far, we have met our first need. the next step, like the car designer, is for us to see what our next need is. We want to "make sure that our data is stored in the database" and this is exactly where we write the await code on the left instead of the left-to-right view. (Note that this code only makes sense for this example, and based on your programming language and work environment, you should make your own interpretation of this example).

await name.save()

As we mentioned above:

With this part of code, the program is commanded to wait for the storing process (and not go to the next line until the result of the storing operation is determined).

And now we decide in our minds to "save this process somewhere", so we can use it in the next lines. what should we do? Yes, the answer appears! Now on the left side of the code, we add const result to save it under the name "result":

const result = await name.save()

Wrapping up

Before wrapping up, I should clarify that the approach described above is not the only path, it is just an example. There is no doubt that you can rearrange the steps of thinking based on your mind and your program environment.
I hope instead of simplifying this, I didn't make it more difficult to understand, but considering all we have discussed, I would reach the following conclusion:

Don't think about the Order or Direction of code execution first when you are writing code. instead, write down what is on your mind, without thinking about the final complicated rules, and then, each code will find its place!

My name is "Hooman Talakian" and you can follow me on LinkedIn if you liked this article.