02About / Person

Personal archive
Record / Open

There's moreto methan the stack.

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.

File / RP-PERSON-02State / EvolvingNext / Development record ↓

01Curiosity came first

Started computing.

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

Learning how
systems connect.

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.

System viewConnected
01

Frontend

Interfaces became one visible part of a larger application flow.

02

Backend

Application logic, data handling, and behaviour behind the UI.

03

APIs

The communication layer connecting different parts of a system.

04

Software Engineering

Requirements, planning, and a more structured way of building.

05

Documentation

Making systems clearer before and during implementation.

2025

Model / Deeper

03Programming started to click

The piecesstarted makingsense.

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.

01Languages02Stacks03Application layers04System thinking

04Real work changed the context

August 2025November 2025

The code wasn't
the whole job.

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.

  1. 01Assisted and worked alongside senior developers and engineers across active project work.
  2. 02Participated in sprint discussions, task planning, code review, and Git-based team workflows.
  3. 03Helped understand and break down requirements into practical implementation tasks.
  4. 04Contributed ideas around UI structure and translated design and content requirements into implementation.
  5. 05Worked across frontend development, reusable components, CMS-managed content, UI updates, and bug fixes.
  6. 06Gained exposure to backend and broader application workflows where relevant.

06Current / Still building

Biography state / Mutable

This page should
change as I do.

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

Next chapter / 02Projects