Full-Stack Depeloper & Game Development Enthusiast _
Full-Stack Depeloper & Game Development Enthusiast _
Full-stack developer building modern web applications and exploring game development with a focus on clean architecture, performance optimization, and maintainable code.
Projects
// Full-Stack Applications, Backend Systems & Interactive Prototypes
Technical Skills
// loaded modules, dependencies & production stack
About
// Developer Profile
I am a full-stack developer focused on building robust, performant web applications and interactive systems. I enjoy exploring game development, gameplay systems, and technical prototypes through modern tools and technologies.
I believe great software is more than just functional or visually polished. I focus on building reliable systems and interactive experiences that are fast, responsive, maintainable, and thoughtfully designed. Every technical decision should contribute to a better long-term user experience.
I enjoy exploring different frameworks instead of repeatedly building similar projects with the same stack. Understanding different approaches helps me make better engineering decisions, and every project becomes an opportunity to experiment, validate ideas, and refine my engineering approach.
Engineering
// Lessons from real-world development
// Component manages fetching, loading state,
// error handling, and cache behavior.
const [data, setData] = useState([]);
const [loading, setLoading] = useState(false);
const [error, setError] = useState(null);
useEffect(() => {
setLoading(true);
axios.get("/api/items")
.then((res) => setData(res.data))
.catch((err) => setError(err))
.finally(() => setLoading(false));
}, []);// Server state is managed by RTK Query,
// providing automatic caching and request lifecycle management.
const {
data,
isLoading,
error,
} = useGetItemsQuery();
// ✓ Automatic caching
// ✓ Request deduplication
// ✓ Cache invalidation
// ✓ Background refetching
// ✓ Separation of concerns// CreateProduct.tsx
<CreateProductForm />
// EditProduct.tsx
<EditProductForm />
// Duplicate validation
// Duplicate form fields
// Duplicate submit logic// Create
<ProductForm
mode="create"
/>
// Edit
<ProductForm
mode="edit"
initialData={product}
/>
// ✓ Shared validation
// ✓ Shared UI
// ✓ Shared business logic// Error handling is repeated
// inside every controller.
export const createUser = async (req, res) => {
try {
const { email, password } = req.body;
const existing = await User.findOne({ email });
if (existing) {
return res.status(400).json({ error: "User exists" });
}
const user = await User.create({ email, password });
res.status(201).json({ success: true, user });
} catch (err) {
res.status(500).json({ error: "Server Error" });
}
};// Error handling is delegated to
// asyncHandler and centralized middleware.
export const createUser = asyncHandler(async (req, res) => {
const { email, password } = req.body;
const existing = await User.findOne({ email });
if (existing) throw new AppError("User exists", 400);
const user = await User.create({ email, password });
res.status(201).json({ success: true, user });
});
// ✓ Less repetitive controller code
// ✓ Centralized error middleware
// ✓ Consistent API responsesFAQs
// Questions you might have
Why don't you have a released commercial game yet?
I believe a prototype should answer technical questions, not just create a visually impressive trailer. As a solo developer, I handle every aspect of development, including gameplay systems, architecture, optimization, and iteration. I prioritize validating core mechanics and building reliable foundations before expanding into a full production, making the final project more realistic and maintainable.
What kind of team do you like to work with?
I prefer working in teams that look beyond simply completing requirements. Delivering a feature is only part of the job; understanding how people actually use it and refining it based on usability, performance, and long-term maintainability is what creates real value. A long list of features means little if the product isn't intuitive, responsive, or enjoyable to use.
Why did you choose Svelte when React and Next.js are more widely adopted?
I evaluated several frontend frameworks, including Rust-based options such as Dioxus, before choosing Svelte. For this portfolio, I prioritized simplicity, performance, maintainability, and a lightweight user experience over ecosystem popularity. Svelte's compiler-first approach aligned well with those goals.