DEV Community: Arun K C

A Brief Introduction to Blockchain

Arun K C — Sun, 13 Feb 2022 15:47:42 +0000

Unless you have been living under a rock, you might have heard about "Blockchain". It's incredibly popular nowadays and the whole tech community is excited about it. Some are crazed over the concept, some ambivalent, and some oppose. Nevertheless to say the concept itself is revolutionary if it can be fast and efficient.

Personally, I believe this is a groundbreaking technology and it can bring wonders to the Web we know as of now. It's still in its infancy stage though, anyway, we gotta start somewhere!

Let's get into the article now.

How it all started

Surprisingly a blockchain-like idea was proposed long back in 1982 by a cryptographer named David Chaum in his dissertation "Computer Systems Established, Maintained, and Trusted by Mutually Suspicious Groups."

Further work on a cryptographically secured chain of blocks was described in 1991 by Stuart Haber and W. Scott Stornetta. They wanted to implement a system wherein document timestamps could not be tampered with.

The technology actually came into life when the first decentralized blockchain was conceptualized by a person (or group of people) known as Satoshi Nakamoto in 2008. It was non-other than the most famous cryptocurrency that we are all familiar with, Bitcoin. Slowly after that different chains were formed such as Ethereum, Polygon, Avalanche, etc.

The use of a blockchain confirms that each unit of value was transferred only once, and the ingenious mechanisms put forth by Satoshi Nakamoto solved the long-standing decentralized double-spending problem.

What is a blockchain?

A blockchain is a distributed decentralized immutable ledger or database open to anyone. As the name indicates, the blockchain is a chain of blocks that contains information. It's a growing list of records, called blocks, that are linked together using cryptography. Each block contains a cryptographic hash of the previous data, a timestamp, and the information.

The timestamp proves that the data existed when the block was published in order to get into its hash. As each block contains information about its previous block, they form a chain, with each additional block reinforcing the ones before it. Therefore, blockchains are resistant to modification of their data because once recorded, the data in any given block cannot be altered retroactively without altering all subsequent blocks.

How does a blockchain works?

Imagine three friends Alice, Bob, and Jack meet up for dinner. After their dinner's done Jack pays the bill. And all of them decide to split the expense amongst each other. Let's assume both Alice and Bob have a balance of 3 bitcoins each and Jack have 7 bitcoins.

First Alice sends 2 bitcoins to Jack. A record is created in the form of a block and the transaction details between them are permanently inscribed within the block. This transaction should be verified by the nodes through mathematical calculations and determines whether they are valid based on agreed-upon rules.

A number of nodes(miners) will be competing with each other to verify the transaction. Once consensus has been achieved by the fastest node, the transaction is considered verified and the block is added to the blockchain. And thus Jack receives the 2 bitcoins. The same process is done when Bob sends 2 bitcoins to Jack. These blocks are chained together thus forming a ledger.

So the steps are:

New transactions are broadcast to all nodes.
Each node collects new transactions into a block.
Each node works on solving difficult consensus methods for its block.
When a node solves the consensus method, it broadcasts the block to all nodes.
Nodes accept the block only if all transactions in it are valid and not already spent.
Nodes express their acceptance of the block by working on creating the next block in the chain, using the hash of the accepted block as the previous hash.

Blocks

A block in a blockchain consists of two main parts, the block header, and the block body

The block header consists of

Hash of the previous block
Root hash of the Merkle tree
Timestamp
The Nonce: It is the variable incremented by the proof of work. In this way, the miner guesses a valid hash, a hash that is smaller than the target.

The block body contains all transactions that are confirmed with the block.

What is a Merkle tree?

The Merkle Tree takes its name from the mathematician Ralph Merkle. The discovery was that much information can be represented in a single hash. For this, the data itself is first hashed. Then the hashes are hashed again and merged. Finally, the Merkle Tree is merged into a single hash. This last hash is also called the root hash / Merkle root, the root of the tree. It represents all the information of its “leaves” (individual transactions) and “branches” (hashes of the leaves) in a relatively short string.

The Merkle Root summarizes all of the data in the related transactions and is stored in the block header (a block header is the unique identity of a particular block on a blockchain and is hashed by miners for rewards). It maintains the integrity of the data. If a single detail in any of the transactions or the order of the transactions changes, so does the Merkle Root. They are extremely robust and are at the heart of several peer-to-peer networks such as BitTorrent, Git, Bitcoin, Ethereum, etc.

Nodes

A blockchain network is managed autonomously through a peer-to-peer distributed network of computer nodes. Nodes are nothing but computers that are designated to keep a copy of the distributed ledger and serve as communication points that execute various essential network functions.

A blockchain node’s main purpose is to verify the validity of each succeeding batch of network transactions, called blocks. Each node has a unique identifier attached to its device that allows it to be distinguished from others in the network.

State management

As you know everything has a starting point. The point where it originated. Likewise, blockchain also has an initial state called Genesis state. Bitcoins genesis state happened in 2009 when the network was launched publically. And for Ethereum, it was in 2015. Every transaction on a blockchain modifies the global state that is replicated across all nodes.

As you know blocks are chained together in a cryptographically verifiable way so they are historically traceable. The current state of a blockchain can be recalculated at any point in time by starting from the genesis block and transitioning the state according to each block's information up until now.

Consensus methods

Naturally, the first question that pops into your mind might be "What the heck is consensus?". Let me explain. Consensus is nothing but mutual agreement. Let's take an example. You are going out for a film with your friends. If you propose a film and all of your friends agree, then consensus is achieved.

In regards to blockchain, the process is formalized, and reaching consensus means that at least 51% of the nodes on the network agree on the next global state of the network.

Currently, there are two main consensus methods/protocols

Proof-of-Work (PoW)

Both Bitcoin and Ethereum currently use proof-of-work (PoW) consensus protocol.

Block creation: Proof-of-work is done by miners, who compete to create new blocks full of processed transactions. The winner shares the new block with the rest of the network and earns some freshly minted ETH. The race is won by whosever computer can solve a math puzzle fastest – this produces the cryptographic link between the current block and the block that went before. Solving this puzzle is the work in "proof-of-work"
Security: The network is kept secure by the fact that you'd need 51% of the network's computing power to defraud the chain. This would require such huge investments in equipment and energy. You're likely to spend more than you'd gain!

Proof-of-Stake (PoS)

Ethereum is planning to switch to PoS soon. There are many other famous chains that are already using PoS such as Polygon, Avalanche, Polkadot, Solana, Tezos, etc.

Block creation: Proof-of-stake is done by validators who have staked ETH to participate in the system. A validator is chosen at random to create new blocks, share them with the network and earn rewards. Instead of needing to do intense computational work, you simply need to have staked your ETH in the network. This is what incentivizes healthy network behavior.
Security: A proof-of-stake system is kept secure by the fact that you'd need 51% of the total staked ETH to defraud the chain. And that your stake is slashed for malicious behavior.

Decentralization

By storing data in a peer-to-peer network of nodes, the blockchain is a decentralized network. This has significant benefits over the traditional approach of storing data in a centralized manner. There are significant examples of problems with centralization, some of them are :

Data breaches in centralized systems expose a lot of data
Centralized authorities can censor and shut down speech
Reliance on a central authority means upstream problems affect downstream consumers (e.g. AWS going down means most of the internet goes down with it)

On the other hand, decentralization brings about the opposite benefits.

No censorship as there is no single authority or middleman that can censor you
No downtime as the overall network is running across 1000's of nodes across the globe
Highly attack resistant making it infeasible to manipulate or destroy data

Peer-to-peer network

The underlying blockchain technology leverages the power of Peer-to-Peer (P2P) networks and provides a shared and trusted ledger of transactions. Peer-to-peer networks are defined as the group of devices that are connected together to create a network that is often known as peer to peer network(P2P) network.

The network, once formed, can be used to share files and store them as well. In any of the peer-to-peer networks, all the nodes generally have equal power and can use the same tasks. So essentially this network is what blockchain is using. So yea, it's not a new concept and most of you might have already used it unknowingly. Don't be surprised, it's BitTorrent.(Piracy!!! XD How many times have you used torrent? ) If you paid attention till this point, then it's not surprising to you because I already pointed it out in the Merkle tree section XD

Conclusion

If you read till now, well done!! This really was a long article, if you sticked together with me till this point then you are awesome! Seems you are really interested in this technology.

Now as this article came to an end you have a basic understanding of what a blockchain is, how it works, and it's core components.

Let's summarize :

A blockchain is a distributed decentralized immutable public ledger or database
It's a chain of blocks that contains information
A block contains two main parts, a header, and a body
Blockchain utilizes the Merkle tree as its data structure and it's a fundamental part of the blockchain
Nodes are the verifiers of the blockchain and each of them has a unique identifier that fundamentally distinguishes them from other devices in the network
In a blockchain, we are able to recalculate the current state with the information stored up in each block
Consensus methods are used to achieve mutual agreement - Proof of Work and Proof of Stake are the most famous ones
Blockchain is a peer to peer decentralized network

That's it for today folks!! Thanks for reading this long article. I hope it was a great read for you and you learned one or two from it. If you have any doubts or feedback shoot them away in the comments.

If you found this article helpful, please like and hit the follow button on the top right corner. Subscribe to my newsletter if you don't wanna miss any content!

Let's connect on Twitter

Evolution of Web

Arun K C — Fri, 04 Feb 2022 04:07:56 +0000

Throughout the history of mankind, the Internet is without a say one of the best inventions and revolutions. Thankfully we have been in the right generation to see the drastic changes Internet have brought to our life.

We have been accustomed to the Web so much so that we can't even think of a day without it. Nevertheless to say it's the best thing that ever happened to us. We are walking around with the world's largest library in our pockets (even though most of us don't see that point XD).

Information is just a click away!!

This Web that we are so much into has gone through an intriguing evolutionary phase. Let's discuss these phases in today's article. Web from its inception to what we know it as now is an amazing journey.

Inception - Where it all began

In 1962 J. C. R. Licklider proposed the idea of a network of computers that could talk to one another. He is one of the first to foresee modern-style interactive computing (such a visionary!!). He has been called "computing's Johnny Appleseed", for planting the seeds of computing in the digital age.

In 1969 the first-ever message was sent from one computer to another over the ARPANET. Advanced Research Projects Agency Network (ARPANET), was the government's computer network at the time. Did you know that the first-ever message sent was "LOGIN"? And did you know that only the first two letters, "LO", of the message were successfully received by the other system? (yea, sadly it crashed in between) It sounds funny now, but you gotta start somewhere XD.

In 1971 Ray Tomlinson built the first-ever program to send mail back and forth between the users of ARPANET. This was eventually called Electronic mail or email for short. The @ symbol was used to tell a person's name and hostname apart. During the same year, Vint Cerf invented a way to let computers communicate with each other in a virtual environment. This invention was called Transmission Control Protocol or TCP for short. Shortly after that Internet Protocol (IP) was also introduced.

Web 1.0

It was back in the 1990s when it all began. In 1991 Tim Berners-Lee invented the World Wide Web (WWW). Yes!! It's the fucking Web. This changed everything. Internet was not just for scientists anymore. It was accessible for anyone. Anyone with an internet connection could access an abundance of information.

This is the first phase of the Web usually referred to as read-only web. Back then it was purely static content and the role of the user was limited to reading. There was no way for the user to communicate back to the content creators. No logins, no interaction with posts, no likes, no comments, nothing. Did you know at this period content creators could be counted on hand? The majority of the Internet users were consumers.

Web 1.0 truly lifted the geographic restrictions on information sharing

Web 1.0 can be characterized as a Content Delivery Network (CDN) that allowed information to be displayed on websites. Web 1.0 allowed people to search for information and consume it. There was no interaction with or between users, and there was no user-generated content (such peaceful times!).

This is what the first-ever website looked like.

Key features of the Web 1.0 period:

Everything was static pages.
Site content is served from the server file system.
Pages were built using Server Side Includes or Common Gateway Interface (CGI).
Frames and tables are used to position and align elements on a page (surprised right? )

Web 2.0

Web 2.0 is the second phase in the development of the Internet. It was called as read-write web and it was the stage when websites grew in terms of user interaction. Finally, the internet became a place where users could actually share their views, opinions, thoughts, and experiences. The users started to be the content creators and we no longer could count them with one hand.

Web 2.0 allows users to interact and collaborate with each other through social media dialogue as creators of user-generated content. During Web 2.0, terms like blogs, social media, and video streaming gained popularity. It opened the doors for podcasts, blogging, tagging, curating with RSS, image sharing, video sharing, social networking, and whatnot.

All the popular sites that you are familiar with, this is where they were born. Youtube, Google, Facebook, Wiki, Twitter, etc. The web technologies like HTML5, CSS3, and Javascript frameworks like ReactJs, AngularJs, VueJs, etc., enabled startups to innovate new ideas which enable users to contribute more to this Social Web. Web 2.0 brought a fundamental shift where people were allowed to share their perspectives, opinions, thoughts, and experiences via several online tools and platforms. It brought us the concept - ' Web as Platform', where software applications are built upon the Web.

Every day, we create roughly 2.5 quintillion bytes of data.

Web 2.0 has revolutionized the perception of the Internet in a short time. A prime example of the evolution of Web 2.0 is YouTube, which has relied and still relies on user content. It was the age of targeted advertising and lack of privacy for its users. To be fair, we willingly gave up our privacy for using some cool apps like Facebook and Twitter. Remember that check box you are checking every time creating an account? That's the privacy policies, I bet you haven't read any of that till now XD.

Web 3.0

Web 3.0 is the third phase of the Internet also termed as executable web or read- write-execute web. It is an idea for a new iteration of the World Wide Web-based on the blockchain, which incorporates concepts including decentralization and token-based economics.

The term "Web3" was coined by Polkadot founder and Ethereum co-founder Gavin Wood in 2014, referring to a "decentralized online ecosystem based on blockchain." In 2021, the idea of Web3 gained popularity. Particular interest spiked toward the end of 2021, largely due to interest from cryptocurrency enthusiasts and investments from high-profile technologists and companies.

The rise of technologies such as distributed ledgers and blockchain storage will enable data decentralization and the creation of a transparent and secure environment, overthrowing Web 2.0's centralization, surveillance, and exploitative advertising. Decentralized infrastructure and application platforms will take the place of centralized tech giants, allowing individuals to rightfully own their data.

Yes, you heard that right, you will actually own your data!! Did you really think you owned your data till now? XD You were giving it away for free lol. One of the most significant implications of decentralization and blockchain technology is in the area of data ownership and compensation. As we move towards a mature and stable Web 3.0, the blockchain protocols will allow us to connect to an internet where we can own and be properly compensated for our time and data, outshining an exploitative and unjust web in which giant, centralized entities own and profit from it.

Web 3.0 is already on move, don't misunderstand it's still in its early stages. There are a lot of entities coming up that live in this new decentralized web. Let's take Odysee for example. It is a blockchain alternative to YouTube where videos can be posted and the creators can get library tokens, which is basically a reward for enticing users to watch their videos.

In Web 3.0, companies will be run by a decentralized group called DAO which stands for Decentralized Autonomous Organization. About DAO we can discuss that in a later article. However, in DAO's there is no central authority like CEOs or Presidents. Those with the most tokens get to vote on how the company changes. That means one controlling authority cannot shut it down.

Lastly, one interesting thing about Web 3.0 is that your digital identity is not 100% connected to your real-world identity. This means I can view pages, download things, make purchases, and any other activity on the internet without being traced back to the real me. Sounds like a second life right? XD. Metaverse is coming buddy!! It reminds me of Ready Player One (awesome movie btw XD)

Conclusion

So now we have come to the end of this article. To summarize:

In the 1960s the seed to the era of the Internet was planted
In the 1970s World Wide Web was born
Web 1.0: The era of consumers and a teeny tiny bit of content creators
Web 2.0: Users became the content creators, social media became the super cool kids thing, content sharing was easy, we lost our privacy willingly, unlimited amount of data got created.
Web 3.0: It's the future!! A decentralized open web where users own their data, entities are run by decentralized groups, the token economy is the thing now, everyone's crazed over crypto and NFTs, developers are going on an amazing adventure discovering golds!!

There are a lot of things in Web 3.0 like Crypto(yea I know you are familiar with that XD), DAOs, NFTs, DeFi, Protocols, and whatnot. It's still an emerging space, a lot of things to explore, some of it might be bubbles but it will be the future.

WAGMI 🚀

That's it for today folks!! Thanks for reading this long article. I hope it was a great read for you and you learned one or two from it. If you have any doubts ask them away in the comments. What will be Web3's future according to you? I would love to hear about your views on this.

If you have any feedback please share it in the comment below. Also, if you find it helpful, please like and hit the follow button on the right top corner. Subscribe to my newsletter if you don't wanna miss any content.

Let's be friends on Twitter

IPFS - The superpower of Web 3.0

Arun K C — Tue, 01 Feb 2022 07:55:45 +0000

This article was originally published at Hashnode

If you are paying attention to the tech field and business you might have heard about "Web3" a lot. It's a newly evolved version of the web that we all are familiar with. I myself am fascinated by the technology and the concept of decentralized and distributed internet.

When you start exploring Web3, one of the first things you will hear about is IPFS. So what the hell is this IPFS? Hold your horse's buddy. Before getting into what IPFS is let's see how the current internet works and what the problem with it is.

Issues with the current Internet

As of January 2021, there are 4.66 billion active internet users worldwide which roughly equals 60 percent of the global population! The current internet is a centralized system, which means each node in the network is connected to a central node that controls the entire system. All the information on the internet is centralized since all data is kept in large server farms controlled by specific entities such as companies. This means that these entities are prone to censorship and it also creates a single point of failure. Say the servers of Youtube go down, how will you access it? Doesn't that mean it's a single point of failure?

It's not like the current internet has no benefits at all. The speed at which we are able to access information is the biggest advantage of the current internet. Accessing files, blogs, websites, or any other content is possible in a matter of seconds with a single click of a button.

Location-based addressing

The internet is dominated by client-server relationships, which rely on the Internet Protocol suite. Of these, Hypertext Transfer Protocol (HTTP) is the basis for communication. Data is stored in centralized servers and accessed by location-based addressing. This makes it easier to distribute, manage, secure the data, and to scale the capacity of both servers and clients.

"IPFS aims to surpass HTTP in order to build a better web for all of us."

In location-based addressing, data is identified by where it is located rather than its content. This limitation means you have to go all the way to a specific location to access a piece of data, even if that same data is available somewhere closer. There is also no way of telling if the data has been altered since the client only needs to know where it is, not what it is.

This means that when we ask our computers to fetch a file, we essentially provide the computer with the location where the content is, and in return, we are provided with that information. An example of a “location” in this context can be either an IP address or a domain. Say you googled for https://en.wikipedia.org/wiki/Main\_Page, it's essentially the location where the data is stored.

Ownership of data

No one really cares about the monopolization of information by specific entities. But it does matter a lot. We really don't own our own data even though we should. Say you are browsing through Facebook or Instagram and liking and commenting on posts, you are inevitably creating data. Whether it’s your online activity, what you like and dislike, your buying habits, or a whole range of other sensitive information, it is almost worthless in isolation.

The data value arises when organizations use advanced analytics programs to help inform business decisions. If your data can help companies save or make money, then suddenly it becomes important.

Make no mistake, you are not the customer, you are the data generator.

Facebook and Instagram are literally designed to promote endless scrolling so that you reveal your likes and dislikes. Your data is one of the most valuable resources on the planet.

This is exactly the problem with the current web. Ownership of the data, its centralized. Everything changes if our internet was decentralized, where we own our data and actually get benefit from it.

In a decentralized world, you would own your data as an asset. If the data economy wants to continue, they will need to meet your personal data valuation. Essentially, each individual will be in charge of data monetization for themselves.

A decentralized solution to storing and accessing files comes in the form of the InterPlanetary File System or IPFS. To shift from the present version of the web to a distributed version of the web, we need IPFS. Essentially, the aim is to replace HTTP. Moreover, a decentralized network is a key prospect for the promise of Web3!

What is IPFS (InterPlanetary File System)?

Now back to our question, what the hell is this IPFS? IPFS, which stands for InterPlanetary File System, began development in 2015 by the company Protocol Labs. Back in its early days, the team working on IPFS was a small team of developers led by Juan Benet, CEO of the company. IPFS was initially designed to be a P2P (peer-to-peer)-based decentralized solution for storing and accessing files.

IPFS is a distributed system for storing and accessing files, websites, applications, and data designed to make the web faster, safer, and more open

Fast forward to today, IPFS can be described as a decentralized protocol for storing content – including data, websites, files, and applications – as well as accessing this data in a decentralized way. IPFS eliminates the problems of censorship and a single point of failure. So, now you may ask how does this solution different from our current centralized Internet?

Content-based addressing

As mentioned earlier, the current web retrieves data from a location that we mentioned. IPFS on the other hand utilizes content-based addressing. This essentially means the content is located based on the content itself rather than the location of the content.

An HTTP request (location-based addressing) would look like http://1.2.3.4/main/mypic.png

An IPFS request (content-based addressing) would look like /ipfs/QxmT42vH7/main/mypic.png

So instead of telling the computer where the content is located, IPFS lets us request the content based on the content itself. Amazing right? But there is one problem, the computer must know how to find a specific file.

For content-based addressing to work, there must be a working system to uniquely identify the content. And that is done by assigning a unique ID to the content called a hash. Since each hash is entirely unique to the content it represents, it is possible for the computer to find the content based on the hash.

A request to retrieve data from the web must provide the content identifier, from which the system can determine the physical location of the content and retrieve it. One thing to note here is that since the identifier is created based on the content, any change in content ideally changes the identifier itself, i.e the content address itself.

Content-based addressing and utilizing hashes is not something that IPFS introduced, as other systems use the same methods.

The InterPlanetary Name System (IPNS)

As we have discussed, IPFS uses content-based addressing. It creates an address of a file based on data contained within the file. If you were to share an IPFS address such as /ipfs/QmbezGequPwcsWo8UL4wDF6a8hYwM1hmbzYv2mnKkEWaUp with someone, you would need to give the person a new link every time you update the content.

The InterPlanetary Name System (IPNS) solves this issue by creating an address that can be updated.

A name in IPNS is the hash of a public key. The owner of the public key can sign a piece of information containing the IPNS hash linking to the most recent version of the content. New records can be signed and published at any time.

That means that if I shared the IPNS hash, I could direct users to the same website and it would still allow me to make updates.

There is one drawback though, IPNS hashes are not human-readable as you can see. This issue is actually solved by ENS. Ethereum Name Service (ENS), is a protocol for human-readable crypto addresses and decentralized domain names. We can discuss more in a later article.

Directed Acyclic Graphs (DAGs)

Directed Acyclic Graphs (DAGs) are a form of data structure utilized by various distributed systems. IPFS specifically utilizes DAGs structures known as Merkle DAGs. In this data structure, each node has a unique hash representing the content of that specific node. This means that identifying an object or a node by the value of that node’s hash is possible, which is what content-based addressing is.

There are different ways in which we can construct a Merkle DAG, but IPFS structure is optimized to follow a file system (as the name says!). This means that the system splits the content into different blocks for the IPFS protocol to create a DAG representation of the content. This structure forms a Merkle DAG graph since each file has a content ID, files in the same folder have their own content IDs and the folder itself has a content ID. So many content IDs, I know XD.

Another beneficial effect of using this data structure is that similar files can share parts of the Merkle DAG. This means that if we update any project, only the updated files will receive a new content ID. This also means that the old and new versions can refer to the same blocks for all unaltered parts!

IPFS is an interesting solution for storing files on the web and will most likely be an important protocol for Web3.

How does IPFS store the data?

Now we do have a basic understanding of what IPFS is and how content-based addressing comes into the picture. However, we still haven't learned how IPFS stores the data.

IPFS Objects

When storing files in IPFS, the system creates an IPFS object. These objects can store up to 256KBs worth of data. They can also contain links to other IPFS objects. Now you may wonder how it stores larger files like an image or video.

Those are actually split up into multiple IPFS objects of the size 256KB and afterward, the system will create another IPFS object that holds the links to all the pieces of the files. It's a straightforward simple yet powerful architecture.

Versioning in IPFS

The IPFS objects are actually immutable objects. Then how do we change stuffs you ask? That's where versioning comes into the picture. IPFS supports the versioning of the files. If you happen to be working on a file, IPFS will create what they call a commit object for you.

The commit object simply refers to the commit that came prior to that one and then links to the latest version of the file. All these different versions of a specific file are then available to the nodes of the system. IPFS will make sure that your files, plus their entire history is accessible to the other nodes in the network.

Further information on how IPFS stores data can be found in the official documentation on their website.

Is there any catch?

Yes, there is a catch. If the nodes that hold these pieces of files are offline then the file becomes unavailable and no one can grab a copy of it. It will be like BitTorrent swarms without seeders. There are actually two solutions to this problem, either we can incentivize the nodes or proactively distribute the files and makes sure there is a certain number of copies always available. This is exactly what Filecoin intends to do. It is again a project of Protocol Labs.

How does IPFS locate the data?

You may now wonder how the system locates the data. That is essentially solved by the Distributed Hash Tables. A hash table is a data structure that stores information as key/value pairs. In distributed hash tables (DHT) the data is spread across a network of computers, and efficiently coordinated to enable efficient access and lookup between nodes.

The main advantages of DHTs are decentralization, fault tolerance, and scalability. Nodes do not require central coordination, the system can function reliably even when nodes fail or leave the network, and DHTs can scale to accommodate millions of nodes. Together these features result in a system that is generally more resilient than client-server structures.

The fact that the hash table is distributed means that it is split across all the nodes in the network. Then to locate the content you are after, you ask the peers in the system. IPFS has something they call the ”libp2p project”, which provides DHTs and enables the peers in the system to communicate with each other. Once the content is located, which happens by finding out which peers in the system host the blocks that make up a file, then the next step is to find out where these peers are located. This means that the system uses the DHT twice in the process of locating the desired content.

As soon as the process of locating the content and the peers are done, an exchange needs to occur. When requesting or sending a block, IPFS uses something called Bitswap. This is what enables the peers in the network to connect with each other and to send the requested content. Once the content arrives, you are able to compare the content ID of the requested block and the one you have received to determine that it is the correct file.

Conclusion

Now as this article came to an end now you have a basic understanding of what an IPFS is, what content-based addressing is, how it stores data and how it locates the data.

Let's summarize :

IPFS is a distributed system for accessing and storing files.
IPFS uses a content-based addressing system.
IPFS uses a Merkle DAG that is optimized for representing directories and files
IPFS have IPNS which acts as a DNS in a decentralized world.
IPFS stores data as an immutable object called IPFS object and supports versioning of the files.
IPFS locates the peer that hosts the data using Distributed hash tables (DHTs)

IPFS is pretty cool, right?

There are some advanced concepts in IPFS called Block exchanges, IPLD (Interplanetary Linked Data Project). We can discuss those in a later article.

That's it for today folks!! Thanks for reading this long article. I hope it was a great read for you and you learned one or two from it. If you have any doubts ask them away in the comments.

Let's be friends at Twitter

6 Useful Python Tricks

Arun K C — Wed, 12 Jan 2022 17:25:40 +0000

Hey folks 👋, welcome back to another post!!

Let me introduce myself to those who don't know me, I'm Arun, a Data Engineer and Web3 fanatic. And for the ones who know me, thank you so much for the support 🙌 and love 💜

In this article, I will be sharing some of the tips and tricks I usually use while coding in Python. As a developer, we should be writing efficient code that's clean, easy to read and debug, and maintainable.

The tricks that I will be sharing in this article will help you achieve the ultimate goal of writing clean and efficient code. So without any ado let's jump into it!!

1. Executing string as a code

exec() function is used for the dynamic execution of Python code. It can take a block of code containing Python statements like loops, class, function/method definitions and even try/except block.

This function doesn’t return anything but you can reuse the variables used in the string as shown in the example below.

code_as_string = '''
a = 1
b = 2
return_value = a + b
'''

exec(code_as_string)
print(return_value) #using return_value variable that's defined inside the string

2. Arguments Packing

Argument unpacking is very commonly used in Python. You must have seen *args and **kwargs in some functions.

def sum(*args):
   result = 1
   for i in args:
      sum += i
   return result

print(sum(1)) #1
print(sum(1,2)) #3

3. F String

It is a common practice to add variables inside strings. F strings are by far the coolest way of doing it.

Let's first see how we will be performing the operation with the usual format function

name = 'Luffy'
age = '19'

print("{} is {} years old".format(name, age)) # Luffy is 19 years old

We specify the values that go inside the curly braces by using the format function. Now F string allow us to specify the variables inside the string itself. Cool isn't it?

print(f"{name} is {age} years old") # Luffy is 19 years old

4. Swapping variables

Python have an easier way for swapping without using any temporary variable.

a = 10
b = 20

a, b = b, a

print(a, b) # 20, 10

5. Reversing a list

We can easily reverse a list using reverse() function or slicing technique

list1 = [1, 2, 3, 4]
list2 = [5, 6, 7, 8]

list1.reverse()
print(list1) # [4, 3, 2, 1]

list3 = list2[::-1]
print(list3) # [8, 7, 6, 5]

One thing to keep in mind is that reverse() will reverse the original list itself, unlike the slicing technique.

6. Using generator inside a function

We can use generators directly inside a function to write shorter and cleaner code.

print(sum(i for i in range(10))) # 45

Conclusion

So now we have covered 6 simple yet highly practical tricks that you can use. At a glance these are small changes, but small improvements added up always gives magical results. You will eventually be writing code that is more efficient, easier to read and debug, and more maintainable as you find more practical tricks like these.

I hope you enjoyed this article. If you did show some love 💜 by liking 👍, and sharing 🔃 this article in your socials.

I will be back with more useful articles!!

Do not hesitate to share your feedback. I am on Twitter @arunkc97 and LinkedIn arun-kc. Give a follow and support!

💜 Thank you for reading 💜

🌏 Like | Follow | Share 🌏

My first Hacktoberfest !!✨

Arun K C — Fri, 15 Oct 2021 15:59:39 +0000

"I don't think I can" to "Wow!! This is pretty good!!"

Now that was my experience in a one-liner!

Hi folks, welcome back to another post. To the folks who's new to my posts, I'm Arun, a developer from India.

So this is just a post on my experience of my first ever hacktoberfest!!

How was it??

It was pretty awesome. At first it felt overwhelming. A variety of thoughts went through my mind at first like "Can I do it?", "Will I be able to really help?", "What if I make a mistake?" and all sort of questions like this popped up in my head. It was really scary. Since I was scared I knew that I should do it.

How's the progress??

Well.., my number of contributions will be a 2 digit number soon. My work life was a bit hectic these past few weeks. But still I knew I had to do this and squeezed out time for open source contributions. It was worth it!! Watching my PRs getting merged with the codebase, it felt so awesome.

I was literally like this 🤭

What were my contributions??

I really didn't knew where to start. So like usual I just googled about Hacktoberfest and the projects participating in the events. Dev community really helped me on that. There were a lot of posts on this. So after reading through all of those I just went to Github and searched for some projects. Some of the projects I contributed are:

sourcegraph / learn

Sourcegraph Learn: an educational hub to support all developers

Sourcegraph Learn

Sourcegraph Learn is Sourcegraph's open source and Creative Commons licensed developer education hub and learning center.

Public URL: https://learn.sourcegraph.com

How the site is built

The website consists of static content generated using Next.js and hosted on Netlify.
The website code is written in TypeScript and React.
The content is written in Markdown.

Deploy previews (staging branches)

When a pull request is created in this repository, Netlify will automatically build and deploy the branch. You can find the link to the deploy preview in the Checks section of the pull request.

For developers

If you are actively developing Sourcegraph Learn or are looking to extend this repository, please see our development documentation.

For content writers

If you are actively contributing to Sourcegraph Learn as a technical writer or video creator, please see our content documentation.

See also our archived Hacktoberfest 2021 contributors' guide.

View on GitHub

PrefectHQ / prefect

Prefect is a workflow orchestration framework for building resilient data pipelines in Python.

Prefect

Prefect is a workflow orchestration framework for building data pipelines in Python It's the simplest way to elevate a script into a resilient production workflow With Prefect, you can build resilient, dynamic data pipelines that react to the world around them and recover from unexpected changes.

With just a few lines of code, data teams can confidently automate any data process with features such as scheduling, caching, retries, and event-based automations.

Workflow activity is tracked and can be monitored with a self-hosted Prefect server instance or managed Prefect Cloud dashboard.

Getting started

Prefect requires Python 3.9 or later. To install the latest or upgrade to the latest version of Prefect, run the following command:

pip install -U prefect

Then create and run a Python file that uses Prefect flow and task decorators to orchestrate and observe your workflow - in this case, a simple script that fetches the…

View on GitHub

bridgecrewio / AirIAM

Least privilege AWS IAM Terraformer

AirIAM is an AWS IAM to least privilege Terraform execution framework. It compiles AWS IAM usage and leverages that data to create a least-privilege IAM Terraform that replaces the exiting IAM management method.

AirIAM was created to promote immutable and version-controlled IAM management to replace today's manual and error prone methods.

Introduction

AirIAM scans existing IAM usage patterns and provides a simple method to migrate IAM configurations into a right-sized Terraform plan. It identifies unused users, roles, groups, policies and policy attachments and replaces them with a Least Privileges Terraform code modelled to manage AWS IAM.

By moving all IAM configurations into Terraform code, admins can start…

View on GitHub

Yea, some of the projects I contributed don't have hacktoberfest tags. And yea I know that those won't be considered as a valid PR in Hacktoberfest. At the end of the day the main purpose of this event is to let 'opensource contribution' as a habit for developers. I'm doing it for the fun of it. It felt really good while doing each PR's.

Reflections

If you got till this point reading through this post then you might have already guessed how my experience was and I how feel about it. I have learned a lot with each PRs. Each maintainers are so helpful and friendly. All my anxiety was gone thanks to them.

I will be continuing doing open source contributions whenever I get time. I would really encourage everyone to do the same and help each other out. And thank you for reading till this point 😄

Open source is changing the world – one contribution at a time ✌️

🎃 Happy Hacktoberfest 🎃 and Happy hacking 🙌🙌

Now that you heard about my experience I would like to know how your experience was. How was it for you??

I am on Twitter @arunkc97 and LinkedIn. Give a follow!

💜 Thank you for reading 💜

🌏 Like | Follow | Share 🌏

Get started with Apache Airflow

Arun K C — Sat, 25 Sep 2021 13:49:32 +0000

Hey Folks!

Welcome back to another post!!

This article is on Apache Airflow. Before getting into authoring our first workflow lets look into what Apache Airflow actually is.

What is Airflow?

Airflow is a platform to programmatically author, schedule and monitor workflows.

Airflow uses directed acyclic graphs (DAGs) to manage workflow orchestration. Tasks and dependencies are defined in Python and then Airflow manages the scheduling and execution.

Basically its a tool that we can use to orchestrating workflows using code!! Pretty neat right?

What is DAG?

In Airflow, a DAG – or a Directed Acyclic Graph – is a collection of all the tasks you want to run, organized in a way that reflects their relationships and dependencies.

Its just a structure that we define using python scripts. To put it simply, it defines how we want to run our tasks.

We can say all workflows are DAGs. A DAG consists of operators, which we refer to as tasks. There are different type of operators available such as BashOperator, PythonOperator, EmailOperator etc.

When we run a DAG all the tasks inside it will run the way we have orchestrated. It can be parallel runs, sequential runs or even runs depending on another task or external resource.

Let's get our hands dirty!!

Assuming that Airflow is up and running, lets jump into our first DAG creation. If Airflow is not yet installed in your system please check the documentation for more info. If you have an AWS account you can use MWAA. Its the same thing, the only catch is that its managed by AWS as a service.

Below is a simple code for DAG

from datetime import datetime
from airflow import DAG
from airflow.operators.dummy_operator import DummyOperator
from airflow.operators.python_operator import PythonOperator

args = {
    'owner': 'Airflow',
    'start_date': '2021-01-01',
    'retries': 1,
}

def print_hello():
    return 'Hello world from first Airflow DAG!'

dag = DAG(
    dag_id='FIRST_DAG',
    default_args=args,
    schedule_interval='@daily',
    catchup=False
)

hello_task = PythonOperator(task_id='hello_task', python_callable=print_hello, dag=dag)

hello_task

So what this above code basically does is it just invokes the python callable function print_hello using a PythonOperator. We are assigning that operator to a variable called hello_task. Now this variable is essentially our task.

We place this code (DAG) in our AIRFLOW_HOME directory under the dags folder. We name it hello_world.py.

Below is a sample folder structure of DAG

AIRFLOW_HOME/
├── common
│   └── common_functions.py
├── dags
│   └── hello_world.py

You can modularize the functions you want and store it as python scripts under the folder common and use it inside the DAG.

For running the DAG you can go to Airflow scheduler and turn on the DAG by clicking the toggle button and click on the run button besides your DAG.

Once its successful your task border will turn to dark green color.

That's it!! We just created our first DAG. Airflow is a neat and simple tool that helps us to orchestrate tasks / workflows like this. It doesn't seem that big of a deal with just one task. But in real world we have to orchestrate a large number of workflows. When the scale increases Airflow is such a life saver for all of us.

Conclusion

This was just a small intro on Airflow to those who have never heard of it. For the experienced folks this article won't do much. Its just a byte sized article ✌️

Hope you enjoyed the article. Do not hesitate to share your feedback. I am on Twitter @arunkc97. Give a follow!

💜 Thank you for reading 💜

🌏 Like | Follow | Share 🌏

My experience in building a Discord bot!!

Arun K C — Sun, 30 May 2021 14:02:12 +0000

I have been working on Zoro, a discord bot, for the last few days. To be honest, this all started when I wanted to build an open source project. I didn't had any idea on what to build at first. I have been using discord for the past few years and I always wanted a bot of my own. So why not build a discord bot? That's how I decided to build a bot.

But...how to build a bot?

Yeah, that's the exact question I had at first, How? Just like any other developer I too started googling on "How to make a discord bot" (Funny but without google or stack overflow most of us wouldn't be here 😝). Thanks to the whole developer community, there were many articles and tutorials on this.(phew, thank god I found those somehow 😌)

Then what?

I then started going through all those articles and tutorials to get an idea on how to start. Created an application and bot on discord developer portal and GitHub repo for this project(yea, it's open source, feel free to check it out and contribute✨).
And then it was time to put on coding cap and start coding....

How was it?

It was fun! I mean, really fun!! I always loved building stuffs. We use discordjs for building the bot. It's a nodejs module. If you are familiar with nodejs or vanilla js then this won't be really difficult for you. All that matters is your imagination. You can make the bot do whatever you want. When I first went through the docs on discordjs I was overwhelmed, there was a lot to grasp.

Wait, wait...don't jump into conclusion that it's hard and not for you. It's fairly simple, it's well documented and most of the tutorials and articles will give clear picture on the whole thing.

Can I build a bot too?

Of course you can. You can build a fully functional bot on your own. Don't underestimate your skills. I will list down some of the resources that I used.

DiscordJS: Don't ignore the docs. Doc's are really a life savers.
TheCodingTrain
Worn Off Keys
freeCodeCamp
npm packages There are a lot of packages already build by lot of awesome developers to ease out your burden

Oh yea I forgot to mention something, Discord bot can be build both using JavaScript and Python. What I used is JS but if you are comfortable with python just go with that.

Conclusion

Building a discord bot is not that hard. If I can do it, then you can too. Just don't overestimate the time needed to build it. You really can't build a multi purpose bot over night(may be the ones who already build one can do that, or some super geniuses 😅). It takes some time, but no worries, it's fun.

If you are interested in the bot I made feel free to check it out, contributions are welcome ❤️

Arun-kc / novicebot

⚔️ A fun-oriented discord bot made using DiscordJS, NodeJS, and MongoDB

Don't forget to show some ❤️ by giving a star ⭐

💜 Thank you for reading 💜

🌏 Like | Follow | Share 🌏

Solve "MongooseError: Operation 'x.find()` buffering timed out after 10000ms"

Arun K C — Sun, 16 May 2021 06:47:01 +0000

This error ate me out for at most 2 days. When I first saw this error I was like, Whhaaattt?? 😵 The connection was ok since the console said so. Or was it?

The problem I faced

When I tried connecting to mongodb it didn't through any error as you can see.

In my case, I had mongo.js file with the following code that I utilized in index.js file.

mongo.js



const mongoose = require('mongoose');
require('dotenv').config();

module.exports = async () => {
    await mongoose.connect(process.env.MONGOPATH, {
        keepAlive: true,
        useNewUrlParser: true,
        useUnifiedTopology: true,
        useFindAndModify: false,
    })
        .then(x => {
            console.log(
                `Connected to Mongo! Database name: "${x.connections[0].name}"`,
            );
        })
        .catch(err => {
            console.error('Error connecting to mongo', err);
        });
    return mongoose;
};

index.js



const mongo = require('../mongo');

module.exports = async (arg1, arg2, arg3) => {

            await mongo().then(mongoose => {
                try{
                    console.log('Connected to mongo!!');
                    command.execute(client, message, args);
                }
                finally{
                    mongoose.connection.close();
                }
            });

};

But when I tried to execute the function that uses a find() operation on the model it threw the following error.

As you can see it threw the buffering timed out error.

So what was the error actually?

According to the documentation of mongoose:

Mongoose lets you start using your models immediately, without waiting for mongoose to establish a connection to MongoDB.

That's because mongoose buffers model function calls internally. This buffering is convenient, but also a common source of confusion. Mongoose will not throw any errors by default if you use a model without connecting.

So that means we are trying to call the model without even establishing a connection with the database.
(Yea that was the problem)

So how to solve this??

That's simple (yea I know, so simple that it made me crazy for 2 days 😵), we need to use async/await with connect() or createConnection().

Updated indes.js



const mongo = require('../mongo');

module.exports = async (arg1, arg2, arg3) => {

            await mongo().then(async mongoose => {
                try{
                    console.log('Connected to mongo!!');
                    await command.execute(client, message, args);
                }
                finally{
                    mongoose.connection.close();
                }
            });

};

As you can see the only change I had to do was to utilize async/await in this code.

Here the function that utilizes the model will be called into this code via command.execute(). Since we are turning in the arrow function into an async function and using await so that command.execute() runs first, we won't face the buffer problem anymore.

How to connect MongoDB Atlas with your Node.js driver?

For setting up MongoDB Atlas and connecting with Node.js, you could check out this article.

Set up MongoDB Atlas and connect with Node.js (avoid MongooseError: Operation x.findOne() buffering timed out after 10000ms)

Vero ・ Apr 17 '21

#mongodb #node #javascript #database

Conclusion

During development we will all face problems like this, be it big or small, share it with others. If this article could at least help one of you and save your time, then the objective of this article is fulfilled.

Note: If you wanna check out the project in which I faced this problem, here is the link, contributions are welcome ❤️

Arun-kc / novicebot

⚔️ A fun-oriented discord bot made using DiscordJS, NodeJS, and MongoDB

💜 Thank you for reading 💜

🌏 Like | Follow | Share 🌏

The first bug I Smashed in Bug Smash!!

Arun K C — Fri, 07 May 2021 16:28:59 +0000

Imagine an awesome intro here!!😜

Hi all, I'm pretty new to this community. So let me share a bit about myself. I'm Arun, a CS graduate, from a small town in Kerala, India. I love to build things. I found this community somehow from Github. I really don't remember how but I'm really glad to be part of this community.
Yea yea... I know you want me to get into the post asap. So here goes nothing....

Open Source Background

I'm brand new to Open Source as a contributor. I have some experience in coding as that was pretty much what I was interested in and what I enjoy.

(What?? Is it the meme? I do enjoy it even though it makes me crazy! and stop grinning 😅)

It's really an awesome experience and feeling when you collaborate with different people and build stuffs. Collaboration first, coding second!! Some of you, who are part of EddieHub, may have thought that I just copied Eddie Jaoude(No I didn't). I'm part of an amazing community called EddieHub. They were really helpful when I first entered this forest called Open Source.

Ok, now let's move into my experience in Bug Smash!!

About This Bug

Remove extra space from readable_publish_date #13612

hadiidbouk posted on May 02, 2021

I am using the GET latest articles endpoint in my project.

The readable_publish_date property added an extra space between the day and the month, this could be fixed on the front end, but if it's a readable publish date why not be better readable 😅

View on GitHub

The bug was really a small one. It was actually an extra space in readable_publish_date property.

How I Smashed It

I was able to smash it by tweaking the format specifier. Even though it was a small bug, this PR was a huge step for me in Open Source contributions.

Update format specifiers in readable_publish_date #13660

Arun-kc posted on May 05, 2021

What type of PR is this? (check all applicable)

[ ] Refactor
[ ] Feature
[x] Bug Fix
[ ] Optimization
[ ] Documentation Update

Description

Removed extra spaces from readable_publish_date by changing format specifiers

Related Tickets & Documents

Fixes #13612

QA Instructions, Screenshots, Recordings

I'm not sure about this since the only change done is updating format specifiers

UI accessibility concerns?

N/A

Added tests?

[ ] Yes
[x] No, and this is why: I guess old test will still work
[ ] I need help with writing tests

[optional] Are there any post deployment tasks we need to perform?

N/A

[optional] What gif best describes this PR or how it makes you feel?

View on GitHub

Reflection

I had a great experience by being part of this bug smash event. The community members were really helpful and encouraging. Especially rhymes, I'm really thankful for your help.

rhymesFollow

Such software as dreams are made on. I mostly rant about performance, unnecessary complexity, privacy and data collection.

I learned a lot through this experience. This was the first time I had to use WSL and work on it for a project. Setting up the environment and running tests in it was a new encounter for me.

As for the next steps I'm planning to explore this wild forest called Open Source more. I'm sure that I will learn a lot and meet new people through this...(hopefully 🤞)

Suggestions for DEV Community Bug Smash

I only have one thing to say to this community. 🎉Keep up the good work!!🎉. Stumbling upon this community was such an awesome thing that happened to me this year🤩.

Confession: Yea I did copy Eddie earlier 😋

Cover by Eclectic People

What is an NFT?

Arun K C — Sun, 02 May 2021 11:28:31 +0000

This is the first question that popped in my head when I came across CryptoKitties. CryptoKitties is a game centered around collectibles. You can trade and sell these virtual kittens. I'm not gonna dig deep into how this game works. I haven't played it yet so no comments on that. Let's just say, it's how we used to collect poke cards or similar collectibles.

So why I bring this up now is because each cryptokitties are unique. How? Cryptokitties use NFT's i.e, Non-fungible token. "Non-fungible" means that it's unique, it can't be replaced by anything. To be precise we cannot actually determine the worth because of its uniqueness. So now you get why I brought up cryptokitties? Each tokens are one of a kind, if we want to trade it we will get something completely different.

To make it clearer cryptocurrencies like Bitcoin or let's just say the currency we use daily are fungible. Means its interchangeable, a bitcoin in your hand is of the same worth as one that I have (not that I really have one!!)

How do NFTs work?

Most NFTs are part of the Ethereum blockchain. The majority of them follow ERC-721 and ERC-1155 standards. NFTs work differently from the usual cryptocurrencies, say a BTC or ETH coins. Why? you ask. Because it stores extra pieces of information that make them unique. Now you might have a doubt like does only Etherum blockchain have NFTs? No, absolutely not, any blockchain can have its own NFTs (Some already have)

So if it's like bitcoin can we buy/sell it?

Yes, you can. You can buy/sell NFTs at marketplaces like OpenSea, Rarible etc. There are many more, you can read about them here. NFTs can be anything digital, be it a simple gif, memes, drawings, you name it. Recently the famous Disaster Girl meme was sold for $500,000. Twitter co-founder Jack Dorsey even sold his first tweet as NFT for under $3 million. Yea people do buy them!!
// Detect dark theme var iframe = document.getElementById('tweet-00000000000020-772'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=00000000000020&theme=dark" }

Digital assets can be copied, so what's the point?

Yes again, you are right, digital assets can indeed be copied. But NFTs are designed to give you something that can't be copied, ie the ownership of the work. It's just like how some famous art pieces are owned by an individual or a museum, but still, its prints are available in the market for anyone to buy.

Can I build my own NFT tokens?

Yes, you can, just like how you can build your own cryptocurrency you can build an NFT too. If you are interested in that, you can read further here.

Final thoughts

The trend of NFT is far from over. It's just the tip of the iceberg. More than $2 billion was spent on NFTs during the first quarter of 2021. The demand for NFT is continuing to surge and it's not showing any sign of slowing down. As more and more blockchains are coming up with their own NFT services, we are witnessing the emergence of a new market. It's a hot topic that everyone's interested in.

DEV Community: Arun K C

A Brief Introduction to Blockchain

How it all started

What is a blockchain?

How does a blockchain works?

Blocks

What is a Merkle tree?

Nodes

State management

Consensus methods

Proof-of-Work (PoW)

Proof-of-Stake (PoS)

Decentralization

Peer-to-peer network

Conclusion

Evolution of Web

Inception - Where it all began

Web 1.0

Web 2.0

Web 3.0

Conclusion

WAGMI 🚀

IPFS - The superpower of Web 3.0

Issues with the current Internet

Location-based addressing

Ownership of data

What is IPFS (InterPlanetary File System)?

Content-based addressing

The InterPlanetary Name System (IPNS)

Directed Acyclic Graphs (DAGs)

How does IPFS store the data?

IPFS Objects

Versioning in IPFS

Is there any catch?

How does IPFS locate the data?

Conclusion

6 Useful Python Tricks

1. Executing string as a code

2. Arguments Packing

3. F String

4. Swapping variables

5. Reversing a list

6. Using generator inside a function

Conclusion

💜 Thank you for reading 💜

🌏 Like | Follow | Share 🌏

My first Hacktoberfest !!✨

How was it??

How's the progress??

What were my contributions??

sourcegraph / learn

Sourcegraph Learn: an educational hub to support all developers

Sourcegraph Learn

How the site is built

Deploy previews (staging branches)

For developers

For content writers

PrefectHQ / prefect

Prefect is a workflow orchestration framework for building resilient data pipelines in Python.

Prefect

Getting started

bridgecrewio / AirIAM

Least privilege AWS IAM Terraformer

Table of contents

Introduction

Reflections

💜 Thank you for reading 💜

🌏 Like | Follow | Share 🌏

Get started with Apache Airflow

Hey Folks!

What is Airflow?

What is DAG?

Let's get our hands dirty!!

Conclusion

💜 Thank you for reading 💜

🌏 Like | Follow | Share 🌏

My experience in building a Discord bot!!

But...how to build a bot?

Then what?

How was it?