What are the different development environments in which we can write, test and deploy our solidity smart contracts? Keep reading this thread🧵 to find out!

1) Remix IDE: Open-source online Development Environment maintained by the Ethereum foundation. It's the fastest way to run and deploy smart contracts. However, it can only run .js (not seamlessly) and .sol files. It is also very buggy. Devs prefer offline IDEs for seamlessness

2) Brownie: Fast, reliable, Python based framework for smart contracts. It does not have a local network of its own and so it uses Ganache for fulfilling that aspect

3)Truffle Suite: The OG. It consists of three tools: 
Truffle: writing contract
Ganache: making local blockchain network for testing
Drizzle: making frontends which can get data from blockchain. Test, deploy file lang: JS
However, Truffle is now widely considered outdated, slow

4) Hardhat: Currently, it is believed to be the best environment. It is very fast and has great features for easily testing and deploying our smart contracts. Test, deploy files are written in JS. Online support is also widely available and the docs are extensively written.

5) Foundry: Newest kid on the block! Development is in full swing. Their github repo changes everyday! It is faster than HardHat. All tests are written in Solidity itself. Since it's very new, online support is less.
(Thanos meme approved by @PatrickAlphaC)

To sum it up:
in general, 
Foundry >>>>>>> everything
Remix IDE<<<<< everything (except for quickly seeing what a piece of code does)
for JavaScript devs: Hardhat>Truffle
for Python devs: Brownie is the only popular choice lol

That's a wrap! Hope you enjoyed reading this thread and/or learnt something new. If you did, please like and RT the first tweet in this thread.
Did I miss any environments? Did I make a mistake? Comment down below!
Thank you so much for your time!

You can read the unrolled version of this thread here: https://typefully.com/awesamarth_/IP6wzDj

Development Environments for writing Smart Contracts

Lesser known keyboard shortcuts that EVERYONE should get familiar with! A thread (part 1)🧵 

Ctrl + Tab: for switching between tabs in a browser

Ctrl + f4: for closing a tab in a browser

Ctrl + L: for shifting the focus of your cursor to the address bar
Ctrl + K:  the above except it only uses your default search engine to search what you type. So, typing a url won't directly work here and you would have to click on one of the search results. 


Ctrl + Backspace: for erasing the current/previous word
Ctrl + Delete key: for erasing the next word


Ctrl + <- (left arrow) for moving your cursor to the start of the previous word
Ctrl + -> (right arrow) or moving your cursor to the start of the next word
Hold down shift as well if you want to select the words your cursor travels across


Windows + L: For locking the screen. Very useful when you want to leave your system idle but do not want your wireless devices to disconnect. That is why I prefer it over sleep mode.

On YT 
Shift + . (>) or Shift + . (<) for increasing/decreasing speed
m: mute
f: fullscreen
top number row for jumping to a section (1: 10% of vid, 2:20% of the video and so on)
ctrl + <- or ->: previous/next chapter
shift + / (?) for viewing the whole list of keyboard shortcuts

(bonus: try typing "awesome" when your keyboard is NOT focused on a text field and then observe the seek and the hd icon!)

Honourable mention:
Ctrl + Shift + > or < in MS Word for increasing or decreasing font size respectively

Thank you for taking the time to reading this thread till the end! I hope you enjoyed and learnt something new. Please feel free to write any shortcuts that I missed. I'll include them in the second part, which is coming very soon. Drop a 🚀 if you're excited + RT for max reach!

You can read the unrolled version of this thread here: https://typefully.com/awesamarth_/b2wlgDO

Lesser Known Keyboard Shortcuts (part 1)

Yesterday, I finished day 50 of the #100DaysOfCode challenge. Looking back at my journey so far: a thread🧵 where I talk about the motivation, the resources, the communities I joined, learning by doing and much more! 

1) I made this account in Feb 2022 because I was convinced by @kunalstwt to do so. He also made me (and I suppose many others) realize that competitive programming (not DSA, different things) is overrated as extraordinary efforts are required, even for achieving ordinary results

2) Here on Twitter, I saw a lot of people doing this challenge and decided to join in. I was really interested in blockchain development. Not just because of its concept, but also the facts that it is a new and growing space and the people involved here are paid highly

3) As someone from a Python/C++ background I hadn't touched web dev in 4 years! So I went to good ol' @freeCodeCamp's website and picked up their responsive web design course. I felt everything coming back to me. Parallelly, I discovered and joined @LearnWeb3DAO (lw3)

4) Joining lw3: smartest decision I made in quite a long time lmao. Here I found VERY MANY amazing people. The community is very positive and supportive. Add to that it is global too! These two facts ensure no matter what time of the day you ask a doubt, someone always helps out!

5) @snoopies_eth and @haardikkk, 2 of the 3 co-founders of lw3, personally live-stream to teach concepts and also to build projects. Haardik doesn't hold back on curse words while teaching which makes the process feel more natural, but I can't keep up with his typing speed lol

6) Since I was basically a complete beginner, I had to learn JavaScript from scratch. I picked up freeCodeCamp's dsa in JS course, thinking web dev will be taught later on but dropped it almost halfway through when I realized that wasn't going to happen

7) started doing @scrimba's JS course, realized whatever I had learnt in the dsa course was actually helping me a lot. I have a habit of making notes (for future reference not for mugging up) when I'm learning something, so the notes I made from the dsa course did not go waste!

8) I finished doing a course on Solidity called "Zero to Hero" by @CodiesAlert2021 . Again, made notes and shared them too! I find myself referring those notes a lot. 
Later I made up my mind to become a web3 dev, superset of a blockchain dev.

9) I have made many projects in these 50 days, both web3 and non-web3 related. I haven't pushed many to my GitHub. 
I will, in the near future complete scrimba's course and move on to learning ReactJS and NextJS. Maybe even ThreeJS for a project I have in mind (unsure though)

10) Back in Feb, I thought there will be a lot of negativity and calling out etc here, thanks to the memes I had seen about Twitter. So far, all I've received is support, be it in the form of motivation, praise or suggestions. I cherish and hope to keep the connections I've made

11) So yeah, learnt a lot in what seems to be a very short span of time. It couldn't have been possible without the unconditional support from my family and the communities I have mentioned in this thread. I now FULLY believe in learning by doing. The only way is up LFG 🚀 🚀 

That's it for this thread. If you enjoyed reading it, well, you know what to do!

You can read the unrolled version of this thread here: https://typefully.com/awesamarth_/Ofa0mhd

A recap of my journey, halfway through #100DaysOfCode

There are three ways of declaring variables in JavaScript: by using
1) the "let" keyword
2) the "var" keyword
3) the "const" keyword
But, how are these three different? Keep reading this thread🧵 to find out!

1) var: it makes the variable global scoped (accessible anywhere), when declared outside of a function. However, if the declaration line is inside a function, then the scope of the variable is limited to that function, ie. that variable can't be accessed outside of that func. Eg.

still 1) The variables declared using var can be both redeclared and reassigned. Redeclaring means declaring the same variable again with a different (or even same, if you want) value.   Reassigning means just changing the value of the variable. Examples below:

This is the drawback of the var keyword. The ability to re-declare a variable, as good as it sounds, may end up breaking a programmer's code just because they forgot that they had already declared a variable with the same name. Not good. Def not good

To tackle this problem, in 2015, the "let" and "const" keywords were introduced in JavaScript in the 6th revision of its standardized form called ECMAScript. The specific name of this revision is just ES6 (ECMA Script 6)

2) let: Unlike var which is either function or global scoped, "let" is block scoped. It allows you to reassign a variable in the same block but not redeclare it. A block is just a piece of code wrapped in curly brackets { } For example:

3) const: Variables declared with const are also block scoped. These variables, like the ones declared with "let", can't be redeclared. However, unlike "let", the variables declared with const cannot be reassigned. For example:

That's it for this thread! 
I am Samarth and I am on a journey to become a web3 developer and so web3 development is what I tweet about (that, and a lot of shitposting). If you enjoyed reading this thread and/or learnt something, like, follow etc etc... you know the drill!

This was my first ever Twitter thread! Special thanks to @theVatsal_eth for guiding me, motivating me and hyping me up!

You can read the unrolled version of this thread here: https://typefully.com/awesamarth_/5pAOW00