Skip to content

Latest commit

 

History

5 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 

Repository files navigation

Nguyen An Khang

Software Developer with a foundation in Network Infrastructure & IT Operations.
Building pragmatic backend services, Flutter mobile applications, and reliable systems.

Portfolio • Email • GitHub • LinkedIn


01 / Background & Approach

Having practical experience in both software development and network administration, I don't treat operating systems and networks as black boxes.

My working philosophy is straightforward:

  • Choose proven, sensible tools rather than chasing trends.
  • Write clear, maintainable code with explicit business boundaries.
  • Build applications with real-world constraints in mind (network drops, hardware limits, and system maintenance).

02 / Tech Stack

[Software & Services] Languages : Python, Dart, Java, C#, TypeScript Frameworks : Django, Django REST Framework, Flutter, Next.js, Spring Boot Databases : PostgreSQL, MySQL, SQLite, Redis, Firebase

[Systems & Infrastructure] Platforms : Linux (Ubuntu/Debian), Docker Networking : Cisco CCNA (Routing, Switching, VLANs, Network Troubleshooting) Operations : Nginx, IT Support, Internal Infrastructure Maintenance


03 / Selected Projects

FM Dictionary

Offline-First Mobile Application (iOS)

  • Cross-platform dictionary built with Flutter and Firebase.
  • Designed for speed, offline search capability, and minimal resource usage.

Hotel Management System

Full-Stack Web & AI Integration

  • Management platform built with Django, PostgreSQL, and REST APIs.
  • Implemented room booking workflows, operational dashboards, and an AI-powered assistant for handling guest queries.

Phishing Detection Platform

Applied Machine Learning & Web Security

  • Web-based security scanner built with Django to detect malicious URLs and phishing emails using ML classification models.

04 / Principles

  1. Keep it simple: Avoid accidental complexity. If a monolithic or standard REST pattern solves the problem, use it.
  2. Handle failures gracefully: Assume connections will fail, requests will timeout, and inputs will be malformed.
  3. Readable over clever: Code is read far more often than it is written.

About

My personal Github profile README

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors