Solana Faucet - Blockchain Development tool

Photo by Hitesh Choudhary on Unsplash

Hello to all Solana blockchain developers today we are going to learn about “What are Solana Blockchain Faucets?” 

 

What is a blockchain faucet? 

A Solana faucet is a developer tool to get TestNet and DevNet Solana Token (SOL) in order to test and troubleshoot your decentralized application or protocol before going live on Solana MainNet , where one must use real Solana Tokens.  

 

What solution have we got for it? 

We have developed a chrome extension using the latest version of Angular as a framework with bootstrap for making a modern interactive UI 

For the blockchain part we have used the Solana web3 library and the public RPC API for Solana blockchain TestNet and DevNet 

We are using the Airdrop endpoint to trigger the transfer of Solana tokes into your development wallets 

Currently Solana blockchain allows to transfer 2 SOL/10 sec to DevNet wallet and 1 SOL/10 sec to TestNet wallet 

  

How to install our Solution? 

Click on the link below using any Chromium browser 

https://bit.ly/3zuq1yb 

 

Click on “Add to Chrome” Button 

 

 

Click on “Add extension” Button 

 

 

 

Click on puzzle icon, then click on pin icon to pin extension to top 

  

 

Click on the extension logo and follow the steps below

1. Enter the wallet address of your devnet or TestNet wallet 
2. Enter the number of tokens to transfer max 2  
3. Select the network from dropdown  
4. Click on the airdrop button 

  

2. 
   

 

A successful airdrop message will be shown after completion of the transaction

  

 

 

You can check your wallet for sol transfer 

  

 

Sometimes due to high traffic some errors might be displayed, you need reopen Solana Extension and try again to circumvent this error 

  

 

Upcoming Projects 

We are planning on creating an extension to create your very own crypto currency for learning purposes on developer network and to understand how cryptocurrencies are made and distributed e.g., Bitcoin, Solana etc. 

How to plan a Sprint?

Photo by Eden Constantino on Unsplash

 Agile is the most sought-after delivery framework in today’s fast paced technology-oriented world. While people working in Agile environment become adept in the process while learning on the job, it is important for those who are new in this field to have some knowledge prior to taking up a project. 

Well, when we read or hear about ‘Ceremonies’, we may tend to look at the literal meaning. Ceremonies are formal activities conducted in some important occasions. In Agile too, 'Ceremonies' have the same meaning. Ceremonies in ‘Agile’, refer to the meetings/activities, which the team should follow for a project to be delivered well. 

Prior to focusing on ceremonies on Agile, it is important to know ‘Scrum’. So what is 'Scrum'? ‘Scrum’ is a time boxed, iterative approach to Agile. 

In today’s article let us talk more about one of the ceremonies of Agile, and that is known as ‘Sprint Planning'. 

So what is a 'Sprint' in Agile? 

In 'Sprint', the scrum team works to complete a decided amount of work in a specific time boxed period. Sprints are the spine of Scrum and Agile methodologies. If the team gets the 'Sprints' right, the product delivery is smooth with very few hurdles. 

Here are few steps to ensure a smooth sprint: 

1) Prepare product backlog: Preparing product backlog is the most important aspect of any sprint. It is a comprehensive list that talks about what is needed in the product and in what order. Since the product backlog is iterative in nature, it is always changing and is never complete. 

2) Back log refinement: Before a sprint begins—and prior to a sprint planning meeting—it is always ideal for the product owner to groom all existing product backlog. It is also known as backlog refinement. It is necessary to make continuous improvements to re-prioritize, add new details, remove certain items, and adjust estimates. The backlog is the essence of every sprint and hence it is mandatory for the scrum master to ensure the backlog is up to date so that every team member knows what is in queue and what is the capacity of the developers. 

3) The product owner should describe the goal of the sprint and what backlog items contribute to that goal. The scrum team then can decide what can be done in the coming sprint and what they will do during the sprint to make that happen. 

4) The development team should plan the work necessary to deliver the sprint goal. The developers and product owner can then finally decide on the sprint plan based on value and effort. Sprint planning is always a teamwork. 

Sources: https://www.atlassian.com/agile/scrum/sprint-planning

Requirement Analysis - Writing good user stories

Photo by Jason Goodman on Unsplash

 

The Agile Framework calls for perfect user stories. When we say ‘perfect’, can user stories be perfect? Well, they don’t have to be ‘perfect’. They have to be easy to understand. 

Here are some tips: 

1) Write User Stories from the point of view of a user: Understand who are the prospective users and learn why they want to use this product. Interview the users, do some research first. Writing user stories based on speculation and theory never helps. 

2) Personas: What are personas? Personas are imaginary characters created based on the users who would be using the product. Personas usually comprise of a name, picture, characteristic, attitude and a goal. For example. ‘This is Ron. Ron wants an app through which he can order a variety of food from different restaurants and not just one restaurant. This helps in understanding the functionality of the product better. Templates for personas can be found online.’ 

3) User stories should be created collaboratively: There should be a detailed discussion between the product owner, scrum master, development team and the testing team. By taking ideas, feedback and Data from the teams involved, user stories can be created better. 

4) Keep the user stories simple and short: The key is to focus on answering these questions: 

a) As a user, I want…………… 

b) So that I can get……….. 

5) Focus on solving the problem of the user. 

6) Write in first person. It is easy to understand when we write in first person. 

7) Write the Epic first including even the minutest of details. Then break it into user stories. 

8) Ensure the user stories fit well in such a way that one user story can be completed in one sprint. 

9) Do not forget the acceptance criteria. Focus on the following acceptance criteria: 

a) Try to ensure that user stories are independent. 

b) User stories should be short (concise). 

c) User stories should be negotiable. 

d) User stories should be valuable. 

e) User stories should be estimable. 

f) User stories should be testable. 

 

Sources: 

https://www.romanpichler.com/blog/10-tips-writing-good-user-stories/ 

https://www.boost.co.nz/blog/2010/09/acceptance-criteria

Switching Jobs? Here is what you need to know…..

Photo by Amy Hirschi on Unsplash

‘One in 5 workers, who quit their job, wish they had remained in their old position, and only around a quarter of job switchers say they’re satisfied enough with their new position to stay.’ 

There are times when we look for better job opportunities. And then suddenly we are in for a surprise. We hear from some recruiter, and we get an interview call regarding a position we had been eagerly waiting for. So, we go ahead and attend the interview. The interviewer is happy with our answers. He/She tells us about the job role. We are elated that we are going to be at the pedestal of a new role and will be sailing smooth in our learning journey. We are given a tour of the office, the conference rooms. We are told we will be getting pivotal knowledge from the seniors here. Perhaps we grabbed a senior role, and we think we will get an opportunity to lead the team, put forth our ideas, our ideas will be implemented and whoa! What a beautiful work life! Well, sometimes, we are told something and once we join, something else happens....

For example, you may be offered a position in the finance segment, where you hoped you will be shadowing the work responsibilities of the program manager and will eventually get more responsibilities. However, once you join, you realize, the program manager travels frequently and you barely get a chance to communicate with him/her, forget about shadowing and learning new work skills, you will regret your decision of joining this new workplace. 

So, what are the things you need to look at before switching jobs: 

1) Deciding the right way: Getting selected for a new job always makes one feel that he/she is super skilled and is perfect for the role, and hence he/she got selected. However, it is necessary to think above and beyond what the hiring team conveyed and what could be the reality. Once you reason yourself with the truth, only then go ahead and decide whether you want to join or not. 

2) Ask questions: Have your own sets of questions ready. The hiring team may paint a rosy picture of your new role. But you need to know that whatever is being told may or may not be true. Hence ask more questions to be sure about your exact role. 

3) Do not let confirmation bias overpower you: Confirmation bias is the tendency of human brain to confirm an information we already believe in, even though the information that we believe may not be true. For example, you were hired to take over the vital HR responsibilities while the HR manager was on leave. You presume you will get to manage those roles till you are here in this organization. However, you have the slightest idea that once the HR manager joins, you will be given less significant responsibilities. Always be aware of such bias taking over your mind. 

4) Research a little about the organization: Find out more information about the work culture of that organization by reading reviews and talking to employees working there. You can always find connections on job sites liked LinkedIn. You might get more information about the company’s values and principles. Based on that, go ahead with your decision. Always remember, sometimes we switch jobs for salary. However, despite getting a fat salary, we may not be able to work peacefully in our new organization. So, while deciding, it is necessary to take every aspect into consideration. Getting a job is sometimes easier that being able to continue the job. And being able to continue a job peacefully is what every employee desires. 

Sources: https://hbr.org/2022/05/switching-jobs-heres-how-to-make-sure-you-wont-regret-it

How to be a supportive leader?

Photo by krakenimages on Unsplash

There are times when certain projects seem to be challenging and meeting clients’ expectations and solving their problems look difficult. That’s when we see our team members getting anxious, stressed, and worried. At this point, what can the team leader do to ensure he is lending the support the team needs, along with getting the requisite tasks done. 

Here are some tips for the leader: 

1) Acceptance: Anxiety is contagious. If your team is getting anxious, if your team members are getting cold feet, it is quite possible that you will also get it. Hence, accept and acknowledge what is happening. 

2) Understand your own emotions: Put a line between what you are feeling and what they are feeling. Don’t be biased here. Ask yourself, are you feeling the same as them. Based on that, take a decision respecting your values. Say for example, you believe in compassion and cooperation. So, go ahead, talk to your team. Be kind, collaborate with them and see what you can do provide the support they need so that they can complete the tasks. 

3) Talk to you team members: Talk to your team members. Talk to them to know what they are feeling. Try and understand that feeling even if you do not agree with certain things they talked about. Yes, your views and their views may be different. However, in tough times, empathy and compassion is the basis of trust. Perhaps they need extra guidance. Go ahead, guide them, teach them. 

4) Encourage self-care: Self care is all about eating well and eating on time, getting enough sleep, exercise and getting less distracted with gadgets. Deep breathing also helps. Once you advocate self-care for yourself and your team, things get much better and easier. After all, taking care of ourselves in whatever ways we can, can help build resilience. 

Stress and anxiety can happen. What matters is how we handle them. Take care of yourself and extend support. Things do get better soon.

Listening Matters

Photo by Mimi Thian on Unsplash

 

Listening matters. Yes, it does. In a world where everyone wants to talk, talk, and talk, very rarely, we come across people, who listen. People who listen, are indeed great communicators. 

Here is why: 

1. When we listen, we try to feel and understand what the other person is saying. 
2. Listening helps in building trust. People feel comfortable in sharing their thoughts with people who listen keenly. They know you are listening with ardent attention and hence they consider you as a person to go to. 
3. Listening helps in avoiding misunderstandings. It is very easy to misunderstand and interpret things the wrong way. And misunderstandings result in big problems. Hence, listening attentively helps. 
4. Listening helps in removing conflict. Well, we don’t have to agree all the time, nonetheless, if we listen calmly, the other person knows that, since we listened, we will consider all the angles before coming to a decision. 
5. Listening helps in increasing productivity. Good listeners retain information well and have clear understanding about what is expected from them. 

How to be a good listener: 

1. Maintain eye contact with the speaker. Give the person undivided attention. 
2. Pay attention to what the other person is saying. All the same, be relaxed. Keep all distractions aside. 
3. Listen without judging. Don’t jump into conclusions. 
4. Don’t give your own solutions without the person asking you. 
5. Do not interrupt. 
6. If you have any questions, wait for the speaker to pause. 
7. Ask questions, not to judge or demean, but to understand. 
8. Look for nonverbal cues to understand more. For example, is the speaker tense or upset or worried? Do look for those. 
9. Give the speaker some proof that you are listening, be it nodding or saying something like, ‘You must have been elated!’, ‘Wow! That’s so cool.’, ‘Oh! That’s sad’, etc. 

 Sources: 

https://www.insidehighered.com/advice/2019/10/24/why-and-how-academic-leaders-should-become-better-listeners-opinion 

https://www.forbes.com/sites/womensmedia/2012/11/09/10-steps-to-effective-listening/?sh=b3fef2b38918