Frontend
Interfaces became one visible part of a larger application flow.
Rishav Poudel is a software developer from Nayathimi, Bhaktapur, Nepal.
He builds web and mobile systems, follows technology beyond the requirements of the job, and makes room for gaming, music, guitar, and singing alongside the code.
01Curiosity came first
Software moved from something I mainly interacted with into something I could study, break down, and gradually learn to build.
It was the beginning of a process, not an instant transformation. Computing gave that curiosity structure and a place to begin understanding what was happening beneath the interface.
InstitutionIslington College
ProgrammeBSc (Hons) Computing
StateLearning / Beginning
022024+ / Learning how systems connect
Frontend · Backend · APIs · Software engineering · Documentation
As the work became larger, software started looking less like separate tasks and more like one connected process with dependencies between every part.
Interfaces depended on APIs. APIs depended on backend logic and data. Planning, documentation, and software engineering thinking helped make the whole system easier to understand. The important shift was seeing how the parts related to one another.
Interfaces became one visible part of a larger application flow.
Application logic, data handling, and behaviour behind the UI.
The communication layer connecting different parts of a system.
Requirements, planning, and a more structured way of building.
Making systems clearer before and during implementation.
Model / Deeper
03Programming started to click
Working across different languages, stacks, and larger projects gradually changed how I understood software. I became less focused on isolated features and more aware of why the layers around them existed.
Different technologies gave the same questions more context. Responsibilities became clearer. Frontend, backend, APIs, and data started feeling like related parts of the same application instead of separate subjects. The shift was not mastery — it was a better mental model of how software fits together.
04Real work changed the context
August 2025 — November 2025
The internship was where software stopped being only an academic or personal project exercise and became a collaborative, real-world process.
A guided introduction to real-world software delivery: contributing alongside senior engineers, learning how requirements move through discussion, implementation, review, and client-facing work. The work also made the surrounding responsibilities visible: people, requirements, communication, existing systems, review, constraints, and shared ownership of the result.
05Outside / Person
Not hobbies in a sidebar.
Part of the actual story.
The work explains what I build. These interests explain more of the person doing the building.
Technology is more than a professional requirement. I genuinely enjoy exploring tools and understanding how systems work.
Open archive ↗A major personal interest and an evolving archive of play history, eras, favourites, and memories — catalogued without inventing the missing details.
Open archive ↗Songs and artists are part of everyday life, often tied to particular moods, memories, and periods of time.
Open archive ↗I play guitar, try to sing the songs I genuinely like, and enjoy making music something the people around me can share too.
This should never become a frozen biography. New work, learning, and interests need somewhere to go without the whole story pretending it was finished.
2026You are here ●
Next
Unwritten