What-s-up: building and checking a chat application
What-s-up is a chat software project. My contributions covered backend communication, functional testing, and debugging, as described in my October 2026 CV.
My contributions
| Area | Contribution |
|---|---|
| Backend communication | Worked on the communication behavior behind the chat software. |
| Functional testing | Checked application functionality as part of development. |
| Debugging | Investigated and corrected issues in the software. |
These areas connect implementation with observable behavior: a feature needs a working communication path, and testing and debugging help establish whether it behaves as intended.
A way to explain the work
For a future technical walkthrough, I would organize a communication feature around a simple sequence:
- Interaction: describe the action a person takes in the application.
- Communication: trace the backend behavior involved in that action.
- Verification: state the expected result and show how it is checked.
- Diagnosis: preserve the observation that explains a failure and motivates a fix.
This is a writing structure, not a claim about the project’s network architecture or an account of a particular bug. Protocols, deployment details and performance measurements are outside this CV-based overview. The repository is the place to inspect the implementation.
Connecting software development and research
The same habit is useful in both settings: make the question concrete, inspect the behavior, and keep enough evidence to explain the next decision. That is the thread connecting this software project with the research and development notes on this blog.
Explore LucidGPT for a different kind of tooling, the AI4Game notebook for an evolving project outline, or my background.