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 Love to write code & Share Knowledge with my community.

TECHNICAL SKILLS

Programming Language: Kotlin, Java, Dart, Php, Python
Favorite Compiler: Android Studio, Intellij Idea, PHP Strome, Visual Studio Code, Pychamps
Development Methodologies: Solid Principle with SDLC, PSP, TDD, Agile/Scrum
Architecture & Design Pattern: Jetpack Compose, MVP, MVVM, Livedata, Coroutine, StateFlow, Flow, Singleton, Builder
Dependency injection: Dagger 2, Hilt
Technology: Text & Image recognitions, ML Kit, Cloud Messeging, Remote Config
OTP & Email verification. Authentication with all social network, Paging3.
Code Analysis Tools: PMD, Findbug, Checkstyle, Leak Canary.
Data Parser: JSON, XML, RSS, ATOM
Bug/Crash Monitoring Tools: Febric, Crashlytics, Bugfender, Newrelic, Timber, Sentry.io, App Center
Productivity Monitoring Tools: Wakatime
Database & Cache: Firebase Realtime DB, Firestore, Back4app(Parse), Mysql, SQlite, Realm, Room, Mutex, sharedpreference, DataStoreJetpack
Network Transmission: Retrofit, Volley, OkHTTP
Server & Client: Xampp, Wampp, Capel, Postman and other rest client
Project Management & Team Communication Tools: Trello, Slack, Mysqlworkbench, Jira
Version Control System: Git, Github, Gitlab, Bitbucket
Libraries: Able to implement any third party library,e.g Coil, Exoplayer, ZXing, Easy Permissions, Dexter
Life Cycle: Orchestrating background activity life cycle with background services.
Map: Google Map. Mapbox
API Development: Rest Api Development using PHP (Raw+OOP)
Development Practice: Agile, Scrum
Payment Gateway: Paypal,Paytm, Stripe & able to integrate others as needed based on project requirement.
Reverse Engineering: Proguard
Web Application Development: Wordpress (CMS)

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