Skip to content

Instantly share code, notes, and snippets.

@zobayer1
Forked from AbuAbir/Good practice.md
Last active November 2, 2022 06:08
Show Gist options
  • Save zobayer1/7ed91ab9986fd83817bea868fa4a012f to your computer and use it in GitHub Desktop.
Save zobayer1/7ed91ab9986fd83817bea868fa4a012f to your computer and use it in GitHub Desktop.
Good practice to showcase achievement

GIST and BLUR

*collected from "Zobayer Hasan", Solution Architect, TigerIT Bangladesh

Works that you can show are always lot more impressive than works that you can only talk about. So yes, your projects on GitHub should carry a good amount of weight, or consideration in a recruitment phase, granted that they are relevant to the position or field you are trying to get in, and you are able to explain / answer relevant questions. When it comes to group projects, it is a bit sketchy. But these are great for showing how honest you are. Because, trust me, interviewers are usually good enough to catch you if you try to fool them (if they can't, they're probably from a bad company, and you don't want to get in there anyway). Next, the open source projects. If you just use a project without understanding the inner workings, it carries barely any value, but this is subject to how much your own project depends on the open source projects that you are using. The best way to go on about this is to declare their usage, instead of hiding them, and explain what they are used for, and be prepared to answer questions about them, and the possible alternatives. I would like to mention here, in almost all companies, recruitment evaluation generally try to answer the following questions (more or less) about you:

The Good (GIST):

  • Genius - What is ingenious or original about his thoughts and ideas? Can I harness it?
  • Intelligent - What kind of complexity can he comprehend? Do I have use for it?
  • Scholar - What does he know more than anyone else? Do I need it?
  • Talented - What is he extraordinary or super good at? Can I apply it?

The Bad (BLUR):

  • Bizarre - What is strange or weird about his behavior? Can I overlook it?
  • Lazy - What is he unwilling to do? Can I tolerate it?
  • Untimely - What unusual work hours does he need? Can I accommodate it?
  • Rude - What makes him go hulk? Can I inhibit it or counsel him?

The Essential:

  • Honesty - Can I trust him on the things that matter?

The ideal score would be having as much from GISTs as possible, no BLURs at all, and surpassing the expectations on the Essentials. Now you can prepare your GitHub project showcasing accordingly that shows your GIST, confirming that you aren't a BLUR, and above all, you are honest and sincere in your works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment