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 modern, performant web applications and interactive systems. I work with contemporary frameworks and technologies, with an emphasis on thoughtful architecture, maintainability, and practical problem-solving. I also explore game development, gameplay systems, and technical prototypes.
I believe effective software engineering is about finding the simplest solution that delivers the greatest value. Instead of accumulating features and unnecessary complexity, I focus on refining core functionality, optimizing performance where it matters, and designing systems that remain maintainable and efficient over time.
I approach each project with curiosity and a willingness to explore different technologies. Rather than defaulting to familiar tools, I research available solutions, evaluate their trade-offs, and choose the technologies and patterns that best fit the problem at hand. Each project is an opportunity to deepen my technical understanding and make more informed engineering decisions.
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
What's your development style?
As an independent developer, I approach development from the user's perspective. I often encounter websites and tools overloaded with content and features that users may not have the time or need to engage with. Rather than adding features for the sake of complexity, I focus on keeping interfaces clear, purposeful, and easy to navigate—helping users find the information they need quickly and get lasting value from the product.
Why did you choose Svelte for this Portfolio 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.
Why haven't I released a commercial game yet?
As a player who has experienced many exceptional games, I understand how challenging it is to create something that genuinely impresses players. I'm constantly seeking inspiration and exploring technical approaches to bring my ideas to life. Rather than relying on previews or trailers that overstate what a game actually delivers, I want the finished experience to speak for itself and earn the player's appreciation through its own quality.