Even developers make mistakes

Yeah, sometimes we won't agree and things will be working fine in our machine, but we are at not fault if it doesn't run on client's machine :). So we need to be like Bear Grylls and improvise ourselves with time, starting with admitting a few mistakes.

This Thursday (31st march, 2022) We had an amazing discord event with our community. The event was about โ€œTop ๐—บ๐—ถ๐˜€๐˜๐—ฎ๐—ธ๐—ฒ๐˜€ ๐—บ๐—ฎ๐—ฑ๐—ฒ ๐—ฏ๐˜† ๐—ฑ๐—ฒ๐˜ƒ๐—ฒ๐—น๐—ผ๐—ฝ๐—ฒ๐—ฟ๐˜€โ€.

From the dev's side, we had with us Shlok, Emilio, headflake, Mario and Sunil. After a brief introduction, we started discussing about various mistakes devs make and their possible solutions.

1. Issues with the Git ย  ย 

Devs often commit to main branch and fail to write off simple and precise commit messages. This is a very common mistake and can be easily rectified. It is suggested to create a separate branch for each feature one implements. For the commit messages, it should be short and simple. Message should be able to convey the purpose of pull request. Additionally, one can also use Conventional Commits in the message.

Screenshot of conventional commits summary

2. Social media presence ย  ย  ย  ย  ย  ย  ย  ย  ย  ย  ย  ย 

Devs believe social media presence is a waste of time and often leads to decreased productivity, which is partially true, but in today's scenario, where Learning/building in public is a popular belief, this digital absence turns out to be a mistake. Therefore, its important to have somewhat of a social media presence. This have many advantages but in particular we discussed about two of them. First one is accountability. When you post about a future/ongoing project on your socials, you feel somewhat accountable to yourself and to people who follow your updates. Thus binds you to work hard and make your work a reality. Secondly projects and learnings helps get attention of potential recruiters and open various opportunities for professional growth

3. Fear of asking ย  ย  ย  ย  ย 

Devs sometimes feel it awkward to ask. They hesitate to ask for help or for more details about project. In either case, they end up wasting time and ultimately doing the thing they fear doing, asking others. What we need to realize is that, no one is mr-know-it-all. So its okay to don't know some things. So let go of hesitation and ask. This saves time, helps you improve and bond well with your team. Go, explore and experiment, and whenever you are stuck, ask for help. But don't go for asking as the first option though.

Well, these were some of the most amazing mistakes we devs make unknowingly quite often. Other than these, other mistakes that we talked about were, not documenting one's journey, not referring to docs, not working on project's responsivity ( frontend ), and many more.

Thanks for staying till the end, I know you are excited to hop in ย the next weekly community meetup right?! so join our discord and see you next Thursday!

๐Ÿ“จ discord.gg/JdqGX7YvHm

Glimpse of community call