From real projects, I've extended my scale.
A Volary dashboard homepage for founder-side planning, weekly rhythm, task entry, and project launch.
A public-facing UAV brand portal being shaped for Malaysian drone practitioners, buyers, partners, and service conversations.
A collaborative AI education kit with a web-based student onboarding demo and product-facing hardware render.
Simulation work for UAV autonomy, formation behavior, obstacle avoidance, and path-planning study.
Final project work around lower-machine sensing, remote transmission, MySQL-style storage, and monitoring interfaces, with logic transferable from mine gas detection to agriculture irrigation.
Coordination work across lab planning, technical discussion, research framing, meeting notes, and project follow-up.
The training was physical, experimental, and constraint-driven: model the system, understand failure, and document what changed.
I worked across technical, supplier, design, and production stakeholders, where unclear requirements and missing records quickly become real delivery risk.
ROS, Gazebo, RViz, Python, and C++ turned abstract autonomy ideas into runnable workflows that need setup, debugging, validation, and handoff.
At Universiti Malaya, my work connects robotics research, AI-assisted engineering, documentation, and practical software delivery.
Curiosity makes me a robotics system problem solver.
Whether the domain is UAV autonomy or an internal business module, I start by making requirements, edge cases, and review criteria explicit.
My strongest current stack is Python with robotics tooling, Linux, Git, Markdown documentation, and front-end basics for technical interfaces.
I treat implementation, test notes, technical explanation, and follow-up risks as one delivery package.
Real project based challenges need real working flows.
Clarify the real user problem, input data, constraints, and acceptance criteria.
Break the work into reviewable steps, risks, and checkpoints.
Use AI tools to accelerate coding, review, explanation, and documentation.
Check behavior, logs, edge cases, runtime output, and visual quality.
Write what changed, why it changed, and how someone else can continue.
Package the result as a usable artifact, not just a progress claim.
I focus not only on writing code, but also on making engineering work reproducible, reviewable, and maintainable.
This will be the blog layer, but not a diary. The point is to show how I organize technical work, debug systems, and write reusable notes.
Prompt structure, task planning, human review, source control, and handoff notes.
Practical notes for ROS Noetic, Gazebo, RViz, environment setup, and reproducible simulation work.
Branching, commit hygiene, review checkpoints, and how to avoid losing useful work.
Requirement notes, implementation summaries, decision logs, known limitations, and next steps.
Best-fit conversations: business software, Python development, internal tools, AI-assisted engineering workflows, robotics software, and documentation-heavy delivery.