Visual Studio Code is one of the most popular code editors for writing Typescript and Javascript. I use VS Code for all my Typescript and Javascript projects.
<a href="http://www.youtube.com/watch?v=BnTy4IIa2hE"><img src="http://img.youtube.com/vi/BnTy4IIa2hE/0.jpg" alt="How to rapidly prototype Javascript in Visual Studio Code"></a>
If you are like me, using VS Code for writing Typescript / Javascript, you know that sometimes quick prototyping or testing is needed. For this kind of situations I use this extension called Quokka.js.
Read also: <a href="/blog/how-to-write-javascript-and-react-with-vs-code-faster/">How to write Javascript and React with VS Code FASTER!</a>
After installing the extension you can launch a new Typescript / Javascript file with live code execution and results, value explorer, live code coverage and much more. Or if you want to check your existing code, you can also start the extension for an existing file.
I made a <a href="https://www.youtube.com/watch?v=BnTy4IIa2hE">video</a> introducing the extension more throughly so go watch that if you want to learn more! Or if you just want to give it a try, you can install the extension from here: <a href="https://marketplace.visualstudio.com/items?itemName=WallabyJs.quokka-vscode">https://marketplace.visualstudio.com/items?itemName=WallabyJs.quokka-vscode</a>.
What do you think about the extension? Let me know in the comments!


Visual Studio Code is one of the most popular code editors for writing Typescript and Javascript. I use VS Code for all my Typescript and Javascript projects.

[![How to rapidly prototype Javascript in Visual Studio Code](http://img.youtube.com/vi/BnTy4IIa2hE/0.jpg)](http://www.youtube.com/watch?v=BnTy4IIa2hE)

If you are like me, using VS Code for writing Typescript / Javascript, you know that sometimes quick prototyping or testing is needed. For this kind of situations I use this extension called Quokka.js.

_Read also: [How to write Javascript and React with VS Code FASTER!](/blog/how-to-write-javascript-and-react-with-vs-code-faster/)_

After installing the extension you can launch a new Typescript / Javascript file with live code execution and results, value explorer, live code coverage and much more. Or if you want to check your existing code, you can also start the extension for an existing file.

I made a [video](https://www.youtube.com/watch?v=BnTy4IIa2hE) introducing the extension more throughly so go watch that if you want to learn more! Or if you just want to give it a try, you can install the extension from here: [https://marketplace.visualstudio.com/items?itemName=WallabyJs.quokka-vscode](https://marketplace.visualstudio.com/items?itemName=WallabyJs.quokka-vscode).

What do you think about the extension? Let me know in the comments!


If you are using VS Code for writing Typescript / Javascript, you know that sometimes quick prototyping or testing is needed.

How to rapidly prototype Typescript & Javascript in VS Code

First of all, Happy New Year!
I have been blogging for about three years now. Back in 2018 when I first started, I created a Wordpress blog and gave it a name CodePulse.blog. This blog has also served as my personal website but the main focus has been on the blog though.
<img src="./images/codepulse-frontpage.png" alt="CodePulse blog">
Now, three years later, I decided that I want to update the blog and website. In the process I decided to move the blog under my own name. So from now on you find my blog and website from <a href="https://www.tuomokankaanpaa.com">tuomokankaanpaa.com</a>.
<img src="./images/tuomokankaanpaa-com-frontpage.png" alt="New tuomokankaanpaa.com website">
I have coded the new website on my own using JAMstack and I no longer use Wordpress. I had such a good time working on this new website and I learned a bunch of new stuff along the way. I will be writing more detailed explanation of the process, so <a href="/newsletter">go and subscribe</a> to my email newsletter so you don't miss those posts.
That's all for now. I am excited of this upcoming year and I have lots of stuff planned, so stay tuned!


First of all, Happy New Year!

I have been blogging for about three years now. Back in 2018 when I first started, I created a Wordpress blog and gave it a name CodePulse.blog. This blog has also served as my personal website but the main focus has been on the blog though.

![CodePulse blog](/blog-posts/codepulse-blog-is-now-tuomokankaanpaa-com/images/codepulse-frontpage.png)

Now, three years later, I decided that I want to update the blog and website. In the process I decided to move the blog under my own name. So from now on you find my blog and website from [tuomokankaanpaa.com](https://www.tuomokankaanpaa.com).

![New tuomokankaanpaa.com website](/blog-posts/codepulse-blog-is-now-tuomokankaanpaa-com/images/tuomokankaanpaa-com-frontpage.png)

I have coded the new website on my own using JAMstack and I no longer use Wordpress. I had such a good time working on this new website and I learned a bunch of new stuff along the way. I will be writing more detailed explanation of the process, so [go and subscribe](/newsletter) to my email newsletter so you don't miss those posts.

That's all for now. I am excited of this upcoming year and I have lots of stuff planned, so stay tuned!


CodePulse.blog is now TuomoKankaanpaa.com. I decided to update my blog and website and move it under a new domain.

I updated by blog - CodePulse.blog is now TuomoKankaanpaa.com

<a href="http://www.youtube.com/watch?v=ugegu6lSWaY">
<img src="./images/rubber-duck-thumbnail.jpg" alt="What is rubber duck debugging">
</a>
In this post I will explain what "rubber duck debugging" is.
If you are hearing the term first time, you might be thinking "What an earth is that!?". And you are not alone. That was the exact reaction I had back when I first heard the term.
Even though it sounds silly it is actually one of the best debugging techniques out there. And it works on all languages and platforms.
I also made a video on Youtube explaining what rubber duck debugging is. You can watch it <a href="https://www.youtube.com/watch?v=ugegu6lSWaY">here</a>.
<h2>Rubber duck debugging explained</h2>
<img src="./images/rubber-duck-sunglasses.jpg" alt="rubber duck debugging">
The idea behind the term is that you have a rubber duck on your desktop and whenever you hit a wall or can't figure out a solution to your problem, you take the rubber duck and start to explain your problem to it.
This might sound stupid but it actually works. Think about it. Have you ever asked your co-worker or friend help for some problem and while you explain your problem and how your code should work, you actually have an "ahaa" moment and solve the problem while explaining it. It's the same thing but instead of you explaining your problem to a co-worker, you explain it to the rubber duck, quietly sitting and listening on your desktop.
This has happened to me so many times. It really helps to explain the problem and your code line by line to someone because then you get out of your own head and usually see things more clearly which in return really helps on finding a solution.
<h2>Origin of the term</h2>
Of course it doesn't have to be a rubber duck you explain your problems to. It can be some other object or even a pet. Only requirement is that it is right there when you need it and it can listen (not talk!).
The reason for the name of this method is that the book <a href="https://amzn.to/3a7WJZN">Pragmatic Programmer</a> (must read for any serious developer) introduced this method and in the book a programmer would carry around a rubber duck, hence the name of the term.


[
![What is rubber duck debugging](/blog-posts/what-is-rubber-duck-debugging/images/rubber-duck-thumbnail.jpg)
](http://www.youtube.com/watch?v=ugegu6lSWaY)

In this post I will explain what "rubber duck debugging" is.

If you are hearing the term first time, you might be thinking "What an earth is that!?". And you are not alone. That was the exact reaction I had back when I first heard the term.

Even though it sounds silly it is actually one of the best debugging techniques out there. And it works on all languages and platforms.

_I also made a video on Youtube explaining what rubber duck debugging is. You can watch it [here](https://www.youtube.com/watch?v=ugegu6lSWaY)._

## Rubber duck debugging explained

![rubber duck debugging](/blog-posts/what-is-rubber-duck-debugging/images/rubber-duck-sunglasses.jpg)

The idea behind the term is that you have a rubber duck on your desktop and whenever you hit a wall or can't figure out a solution to your problem, you take the rubber duck and start to explain your problem to it.

This might sound stupid but it actually works. Think about it. Have you ever asked your co-worker or friend help for some problem and while you explain your problem and how your code should work, you actually have an "ahaa" moment and solve the problem while explaining it. It's the same thing but instead of you explaining your problem to a co-worker, you explain it to the rubber duck, quietly sitting and listening on your desktop.

This has happened to me so many times. It really helps to explain the problem and your code line by line to someone because then you get out of your own head and usually see things more clearly which in return really helps on finding a solution.

## Origin of the term

Of course it doesn't have to be a rubber duck you explain your problems to. It can be some other object or even a pet. Only requirement is that it is right there when you need it and it can listen (not talk!).

The reason for the name of this method is that the book _[Pragmatic Programmer](https://amzn.to/3a7WJZN)_ (must read for any serious developer) introduced this method and in the book a programmer would carry around a rubber duck, hence the name of the term.


Rubber duck debugging is actually one of the best debugging techniques out there. And it works on all languages and platforms.

I updated by blog - CodePulse.blog is now TuomoKankaanpaa.com

Subscribe to the newsletter