Put an idea to the test
Programming attracted me through the possibility of building something, running it and seeing what happens. An idea becomes more than a description when it meets data, rules and use. If the result differs from what I imagined, there is a concrete question to investigate. I can examine the gap and try a different response.
I like that feedback, including when it reveals a problem. It asks me to make an intention precise: what should the program do, and which assumption led to this choice? Changing the code offers a way to test an answer. That connection between reasoning and a visible result explains my interest better than an expectation of already knowing everything.
Study how the pieces fit together
I started the Computer Science Technology DEC at Cégep de Saint-Jean-sur-Richelieu in 2025, with graduation expected in May 2028. Programming sits within a wider field that includes databases, web development, networks and systems. That variety interests me because an application rarely depends on a single isolated piece of code. Its parts need to agree about the same work.
An interface needs meaningful data. A business rule needs to remain understandable beyond the screen using it. Systems and testing introduce further questions. I am not claiming mastery of each area. I want to understand enough of the connections to know where to look when a result does not make sense.
Projects give the tools a purpose
React and TypeScript have an important place in my projects. DevFlow Studio connects tasks, projects, focus and a technical journal around local data. Practicora starts with internship days to build tracking and prepare reports. Those different needs make me consider data and workflows before deciding how a feature should appear on the screen.
That shift matters to me: a technology becomes a response to a constraint rather than a name to display in a list. DevFlow raises storage and recovery questions. Practicora raises questions about daily entry and permissions. Both remain in development, and part of their value lies in the decisions that still need to be made clearer.
What work has added since the first publication
When this article was first published in January 2026, my internship had not started. The October update can add that perspective: from May to August, I worked on Conexgo at Laxson Solutions Inc., then continued part-time. C#/.NET, Blazor and MudBlazor are part of that working environment, alongside the context of an existing application and team.
A production application changes the learning situation. Understanding existing code, connecting an issue to its workflow and examining a fix’s consequences all become part of the work. Playwright checks, logs and Git diffs provide concrete evidence for that process. A feature appearing correct in one case does not settle every relevant question about the change.
A direction with plenty left to learn
I want to keep progressing in these environments and explore architecture, testing and systems through real needs. That involves noticing gaps in my reasoning, asking precise questions and revisiting choices with more context. Being in training leaves space for that progress without requiring every intermediate step to be presented as a finished answer.
My choice of Computer Science Technology still comes back to the same movement: understand a situation, build a response and observe what it makes possible. I now add attention to the code other people will read and the people who will use the result. That meeting of reasoning, product and shared work is where I want to continue.