Skip to content
All work
02Professional experienceApprenticeship

Web applications at SYSOPS

Software engineering · Business applications

Building and evolving web applications for concrete business use: starting from user needs, improving features, testing, and folding feedback back in.

Context
Apprenticeship at SYSOPS
Scope
Features, data, testing
Stack
Next.js · React · PHP · SQL · Supabase
Confidentiality
No client data published
↳ change1Need2Build3Test4FeedbackInterfaceNext.js · ReactDataPHP · SQL · Supabase
Illustration — Principle diagram — no client interface or data is reproduced.

01Context

SYSOPS works with client companies, notably in the construction sector, on their IT and software. As an apprentice, I contribute to web applications built for concrete business use.

02The problem

A business application is only valuable if it fits the way people actually work. The challenge isn't just adding features: it's evolving the tool without breaking what works, while taking the feedback of the people who use it into account.

03Constraints

  • Business users, not technical ones: the interface has to stay obvious.
  • Applications in daily use: every change must be tested before it ships.
  • Company data: confidentiality and rigour about what is handled.

04My responsibilities

  • Building features with Next.js and React.
  • Back-end and database work with PHP, SQL and Supabase.
  • Testing changes before they are made available.
  • Incorporating user feedback into improvements.
  • Translating stated needs into concrete technical changes.

05Approach

  • Understand the usage before touching the code: who uses this screen, and to do what.
  • State the expected change in a way that can be checked.
  • Implement in small, individually tested increments.
  • Go back to users and adjust.

06Technical implementation

Front end: Next.js and React. Data: PHP, SQL and Supabase, depending on the application. The technical work always stays tied to a need expressed by a user or a client.

07Business relevance

This work teaches me to judge a feature by its real use: a successful change is one that saves someone time or prevents a mistake in their daily work.

08Results

The applications and their data belong to SYSOPS and its clients: no screenshots, code or metrics are published here. I'm happy to discuss the work in an interview, within the limits of confidentiality.

09Lessons learned

  • The best specification is still watching how the tool is really used.
  • Testing before shipping protects users' trust, not just the code.
  • A small, well-aimed change is often worth more than a rewrite.

Working on something similar?

If you're tackling a related problem, I'd be glad to talk it through.

Get in touch

Next project

03Business software & operational workflows

IT consulting · Business analysis · Process