Understand before adding
Reading the context and observing current behaviour helps me ask better questions and define a useful change.
ABOUT
What makes me want to go further.
I like computing because an idea can become something people use. Classes, teamwork and my projects each give me a different way to explore that.
I’m a Computer Science Technology student at Cégep Saint-Jean-sur-Richelieu and a part-time software developer at Laxson Solutions Inc. After my internship, I stayed on to contribute to Conexgo. Working on an existing application teaches me to understand changes and collaborate around a product.
I’m passionate about artificial intelligence and would like to work in this field. I want to understand how these tools work, their possibilities and their limits. It’s a direction I want to pursue while continuing to build my software development foundations.
DevFlow Studio and Practicora let me explore ideas at my own pace. One gathers tasks and the context of development work; the other connects internship days to objectives and reports. Both make me think about how data fits together and the effort each workflow asks of someone.
I often come back to interfaces: where information sits, whether an action is clear, whether a screen stays readable. I enjoy working on those details because they turn technical choices into an everyday experience.
Keep a critical eye
A solution can seem right in one case and cause problems in another. I try to understand the assumptions behind a decision.
Check it in use
I look at user flows and their different states. A good screen also needs to work when the data or actions change.
Keep learning
Classes, work and personal projects bring different problems. I try to take more precise questions from each into the next.
HOW I WORK
Understand, try, revisit.
My personal projects give me somewhere to put ideas to the test. I choose a first workflow, follow the data and try its different states to understand changes and check how they fit the project.
Start with the need
I look at what the person needs to do, which information is missing and what makes the workflow difficult. Describing that helps me notice where my idea is still vague.
Try, then adjust
An initial screen or short workflow gives me something to observe. I can then revisit an action, simplify a step or shape what comes next around the result.
Return to the details
I read changes and try the different states of a workflow. An unclear label, an error or a crowded screen can lead me to reconsider a choice that seemed settled.
An article about choosing a first workflow and what trying it can teach us.
From an idea to a first screen