DEV Community: Tamal Das

Getting a Tech Job, Internship, Remote work in 2022

Tamal Das — Fri, 28 Oct 2022 14:39:04 +0000

Summary

This blog is going to be about getting an internship, Remote work, improving your LinkedIn profiles, and where to apply to get offers. For anyone looking for a full-time role, stay tuned until the very end to get a surprise!

⭐ A good Linkedin Profile

Having a well maintained LinkedIn profile is extremely important if you want to get a job, internship, or any kind of professional work. You would want to tell the user viewing your profile maximum details about who you are and how good you are at the work you do.

Include a minimal yet professional profile picture and cover picture.
Make sure you write a proper bio and also a proper header that attracts the maximum attention.

⭐ A good resume

A resume is one of the most important things in your professional career. It is not such a thing that can be perfected in one try, you need to always edit and customize your resume based on the type of job or the job description.

Make sure you provide it clean and neat resume highlighting important keywords about your projects, your work experience, education, skills, activities, and so on.
Make it simple but let it have an impact on the people that are viewing it

⭐ A portfolio

The best way to show all of your works, builds, projects and other activities is to build out a portfolio.

Make sure it is mobile responsive and optimized.
Keep it clean and minimally styled while adding your most attractive works in it

⭐ Applying to internships/jobs

There are alot of other portals, some of the best are Turing, JunoHQ, Angellist, Glassdoor, Optimhire and so on.

Whenever applying for an internship take a good look at the job description and try to mention your projects in your resume that have the same keywords as the job description.

Conclusion

For full-time jobs, my recommendation is Juno HQ as there are a ton of startups that would pay you a lot with great perks, but you just are not aware of them. Get paid what you deserve!

With that said I won't write much because I want you all to explore also let me know about your experience in finding your internship, jobs, and remote work in the comments below.

5 Ways to level up your Opensource project

Tamal Das — Mon, 10 Oct 2022 06:10:15 +0000

What do I mean by Leveling up a project ?

Leveling up simply means having your project set up in such a way that it is accessible to all. Even if someone very new to the world of tech, looks at your project, they should able to tell, at the very least what's the project about and how the basics of it work.
It also means to have the project neatly - so that folks who code can easily contribute and maintainers/owners of the project can maintain it more easily.

Does this matter for an Opensource project ?

Yes ! , it matters a lot. Opensource projects are likely to have a lot of diversified audiences. They might be having different code practices, different types of thinking, and even different levels of experience than the others. So when you have a set of standards, a set of rules, and proper guidelines for how to make changes to the project, it makes the task for a contributor as well as a maintainer much easier.
They can contribute with more ease.

As for maintainers, they can work out stuff easily. They would know which code to take a look at first, which code does what, and also reject codes that are invalid/broken.

So, How do I make my Opensource project better ?

1. Issue Templates 📝

What you see above are called Issue Templates - when raising an issue in an Opensource project, the contributor gets to choose what type of issue they'd like to raise and have the experience of filling up a form. Of course, this can be customized by customizing their .yml files. In this way, the issues will be cleaner and sorted. Maintainers would know which issue is of which type and gets the most priority !

To add these you need to make a .github folder in your repository and add the .yml files there. It depends on what you want to add but most standards are bug, docs, feature requests.

2. Code of conduct 💂‍♂️

A code of conduct defines standards for how to engage in a community. It signals an inclusive environment that respects all contributions. It also outlines procedures for addressing problems between members of your project's community.

You can add a code of conduct to your project by using a template or manually creating a custom code of conduct. If you use a code of conduct written by another person or organization, be sure to follow any attribution guidelines from the source. To add Code of conduct, you'd just need to head over to Insights > Community Standards > Code of conduct > Add

Then choose which you want to use and go ahead with it !

3. Contributing Guidelines 🔐

A Contributing Guidelines, in your open source repository or site, provides potential project contributors with a short guide to how they can help with your project or study group.

You'd need to have a CONTRIBUTING.md file in the root directory. It is a convention to capitalize the word "contributing" as the file title and to save it as a resource in markdown (hence the extension .md). The CONTRIBUTING.md should be one of your priorities in putting an open source/science project online to solicit contributions. If you have yet to define possible avenues of contribution, consider creating the file with a "check back later, we will populate this soon" message, and the contact information of the project lead for follow-up. Head over to Insights > Community Standards > Contributing > Add

Resource on how to make guidelines : Example guidelines

4. Labels 🏷

*Like these fancy little tags ? * - That's exactly what labels are.
Using labels like these helps you to organize issues, and pull requests with ease. You can tell from all the issues in the above picture that some of them are simply bug fixes while the others are new features and so on. The labels can even be automated such that whenever someone makes a new issue the label is added based on the type of issue they chose to raise !

A detailed guide to adding the labels to your repository : GitHub Docs

5. Pull-request template 👨‍💻

Pull request templates help guide developers to make better software, and a better software development experience. They are extremely useful for open source projects that get many contributions from outsiders, but they can also be very useful for internal projects where all contributors are insiders. It is better to have a set of details to be filled in while making a PR rather than everyone making their customized pull requests.

This is what a Pull request template (blank) looks like :

It is made by adding a pull_request_template.md file in the .github folder.
This is highly customizable and recommended because you can get a more detailed list of the changes that were made to the code by using such a template.

A detailed guide to making a pull request template : GitHub Docs

Conclusion

That's it ! - That is how you take your Opensource project to a whole new level !
Almost everything can be automated with workflows and contributed to by others !

Also , using community standards helps you more to level up your project !
Go to Insights > Community Standards and you'll have a checklist of all the stuffs that needs to be done

If you like whatever I wrote, feel free to give me a shout-out on your socials.
Share the blog with others. Keep contributing 💚

The ultimate place for all your wallpapers !!

Tamal Das — Wed, 20 Apr 2022 14:35:49 +0000

Overview of My Submission

Hello everyone out there.
It's my first time building with Appwrite and here's what I've built - WallHub

So what exactly is WallHub ?

WallHub is a webapp made with ReactJs , styled with Bootstrap 5.0, CSS and also using Appwrite, Docker as the backend. This webapp can be used to get acess to all the best quality UHD wallpapers for all your screens !!

After reading the docs, asking around in discord, watching tutorials, stack-overflow building this project of mine was a fun experience. This is my first time using AppWrite, Docker to build something and i really liked the way it came out. Excited to learn more and build some amazing stuffs.

The inspiration behind WallHub was pretty simple, i wanted to cover all the basics like Databases, Authentications, Buckets, Image upload, Image preview and so on my first time. So here it goes.

Submission Category

Web2 Wizards

Link to Code

Here's the link to the code, check it out !!

tamalCodes / appwrite-docker-wallHub

A basic demo application with ReactJS, using appwrite and Docker

What is WallHub ? 🤔

WallHub is a webapp made with ReactJs , styled with Bootstrap, CSS and also using Appwrite, Docker as the backend. This webapp can be used to get acess to all the best quality UHD wallpapers for all your screens !!

Available Scripts 👾

To setup the project in your local machine :

git clone the repository
npm install to run all the commands.
Replace the project IDs, endpoints with your own.
In Login.jsx change the URL for googleAuths.

What did i learn ? 🍁

Making this app was an amazing experience.

Got to learn about setting up Docker in your local machine.
Setting up config for Appwrite
Storing the registered user in the storage and creating a local session.
Using Google Authentication for signing up !!

Here's how it works ⚙

Here's a sneak peek 👀

A demo of how it works 🎥

…

View on GitHub

Additional Resources / Info

Architecture of the App ⚙

A sneak peek into the Homepage 👀

Working demo 🎥

Thankyou

It was an awesome experience learning so much and i am really excited to go much further with all these. Hope you liked the mini project for the Hackathon !!
Have a good day.