Skip to content
View abircse's full-sized avatar
๐Ÿ 
Working from My Workstation
๐Ÿ 
Working from My Workstation

Block or report abircse

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this userโ€™s behavior. Learn more about reporting abuse.

Report abuse
abircse/README.md

Nayeem Shiddiki Abir

Senior Software Engineer || Mobile Application Engineer || Technical Lead [Project Management]

๐Ÿ”ญ Iโ€™m currently working as a Technical Lead (Project Management) at Global Dynamic Solutions LLC-United State with full time Remote support & 6Years+ Experienced In Mobile Application Engineering. I'm a passionate & expertise in both native Android development and cross-platform mobile app development using Flutter. With a strong foundation in computer science and years of hands-on experience, I enjoy crafting robust and user-friendly applications that solve real-world problems. I Love to write code & Share Knowledge with my community.

Total time coded since Mar 25 2019

TECHNICAL SKILLS

Programming Language: C, C++, JAVA, Kotlin PHP
Development Architecture: MVVM, MVI, MVC
Development Flatform: Android, iOS, Cross (Flutter)

github linkedin facebook instagram twitter stackoverflow website

Notes for Programmer

git Commit message guideline

Would be something like that. <type>(<scope>): <subject>

type

  • build: Build related changes (eg: npm related/ adding external dependencies)
  • chore: A code change that external user won't see (eg: change to .gitignore file or .prettierrc file)
  • feat: A new feature
  • fix: A bug
  • docs: Documentation related changes
  • refactor: A code that neither fix bug nor adds a feature. (eg: You can use this when there is semantic changes like renaming a variable/ function name)
  • perf: A code that improves performance
  • style: A code that is related to styling
  • test: Adding new test or making changes to existing test
  • fix: A bug fixing
  • config: Project Root Architecture & Design pattern configuration

subject

  • use imperative, present tense (eg: use "add" instead of "added" or "adds")
  • don't use dot(.) at end
  • don't capitalize first letter

emoji

  • ๐Ÿ›  build
  • ๐Ÿ‘€ chore
  • ๐Ÿ“ฆ feat
  • ๐Ÿ› bug
  • ๐Ÿ“ docs
  • ๐Ÿ—œ๏ธ refactor
  • ๐Ÿš€ perf
  • ๐ŸŽจ style
  • ๐Ÿงช test
  • ๐Ÿ”จ fix
  • โš™๏ธ Config

example

๐Ÿ›  build(app gradle): add new itextpdf library

Pinned Loading

  1. KotlinStateFlow KotlinStateFlow Public

    Best Practive Repository for Kotlin State Flow instead of Live data (Offline)

    Kotlin 1

  2. Back4App Back4App Public

    CRUD Operation for Parse (Back4app) Backend Server in android

    Java

  3. Coroutines-Kotlin Coroutines-Kotlin Public

    Simple Repository with practice Coroutines Kotlin

    Kotlin

  4. AndroidArchitecture AndroidArchitecture Public

    An Implementation of Google Recommended New Android Architecture with Kotlin.

    Kotlin 5 1

  5. Algorithm-Practice Algorithm-Practice Public

    Java 1

  6. Exoplayer Exoplayer Public

    Implementation of Exoplayer an androidโ€™s MediaPlayer API for playing audio and video both locally and over the Internet.

    Kotlin 2 1