Full-Stack Developer. Hive Software House. Egypt.

Every project was a new context with its own vocabulary. A dental clinic does not think about software the way a restaurant does. A retail brand does not think about software the way a clinic does. The same word means different things in different rooms. A visit to a dentist is the entire appointment plus the procedure plus the follow-up. A visit to a restaurant is the seating, the order, the bill. The first month on any new project, I learned the vocabulary.

The work itself was full-stack: React on the front, Node and Express on the back, MongoDB or SQL behind, Tailwind on top, MUI or Bootstrap when the client demanded it. I shipped features. I shipped bug fixes. I shipped UI work that had to look the same on a dentist's iPad and a teenage retail customer's phone. I worked with senior developers who taught me the small operational habits that make the difference between a developer who is mid-level and a developer who is approaching senior. Documentation. Conventional commits. Code that the next person can read.

What I noticed over the two years was that the contracts were a study in operator personalities. The dental clinic that asked for the wrong software (a heavier patient management system when what they needed was a simpler scheduling app). The restaurant that wanted every feature on the menu (and could not afford any of them). The retail brand that knew exactly what they wanted because the founder had built the previous version in a spreadsheet and was just looking for someone to make it scale. The job was as much reading the operator as writing the code.