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
// Talk is cheap. Let's see what I built.
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 also enjoy exploring game development, gameplay systems, and technical prototypes through modern tools and technologies.
While a feature can be implemented in countless ways, I start by researching modern architectures and proven patterns. By considering scalability, modularity, and performance from the beginning, I aim to build systems that remain maintainable and efficient as they evolve.
I avoid churning out repetitive projects with the same stack. While this naturally results in a leaner portfolio through continuous exploration, every build is a fresh technical deep dive. This helps me develop a broader understanding of different frameworks and technologies, while learning to pragmatically choose the right tool for each real-world challenge.
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 — or even a public title?
I believe a prototype should answer technical questions, not just create a visually impressive trailer or a premature brand. As a solo developer, I handle every aspect of development, from core gameplay systems and architecture to optimization. I prioritize validating mechanics and building reliable foundations before giving a project a commercial title or expanding into full production, ensuring the project is actually shippable and completable.
What are your core standards for professional web development?
After finishing a project, I always run performance and reliability tests using tools such as Catchpoint and Google PageSpeed Insights to ensure all messurable metrics meet industry standards. This helps identify issues that may not be visible during local development and provides objective metrics for evaluating performance and real-world usability. From what I've observed, this validation step is often skipped in local development workflows.
Why did you choose Svelte when React and Next.js are more widely adopted?
I chose Svelte simply because of its performance, development experience. React and Next.js are clearly more widely adopted, especially in local enterprise development environments where React and Next.js is often the default choice. Svelte is a relatively newer frontend framework in comparison. After working with it, I found that its compiler-first approach, development workflow, and lightweight output aligned extremely well with my priorities. For my own projects, I simply haven't found a compelling reason to give up those advantages purely for ecosystem popularity.