Loading content…
Jonathan Blanchard
I build complete applications for concrete problems, from the idea to the interface, from the backend through to deployment.
I am looking for a full-stack apprenticeship to grow alongside a team and contribute to useful products.
I like to start from a situation that resists: files that are hard to organize, secrets scattered everywhere, job offers impossible to follow. Before picking a technology, I try to understand what actually gets in the user's way.
I then turn that understanding into a complete product. I treat the interface, the business rules, the data and the deployment as parts of one system — with particular attention to ambiguous cases, to security, and to recovering from mistakes.
My personal projects are my exploration ground. They let me build beyond an isolated exercise, test my decisions against real usage, and learn to finish properly what I start.
Jonathan connects usage, interface, business rules and operations so the solution stays coherent from the first screen to deployment.
Watch the errors, the hesitations and the risks before designing a feature.
Prefer understandable behavior over opaque automation, especially when the action is sensitive.
Evolve the interface, the API, the data and the infrastructure as one product.
Test, log, containerize and prepare the deployment instead of stopping at the demo.
A professional transition built around the urge to understand systems and to build useful tools. Precise education and experience details will be filled in by Jonathan.
Journey details still to be filled inFrom first web applications to desktop ones, Jonathan grows his projects to practice interface, backend, data, security and operations within a single context.
Join a team as an apprentice, contribute to a real product, get demanding feedback, and keep progressing across the whole development chain.
Every case study starts from the need, then shows the solution, the choices, and what is left to learn.
Organize and rename a media library before importing it into Plex.
Organizing a large media library becomes hard once files are badly named, mixed together, or matched to the wrong episode order.
Role: Product design, architecture, Java/JavaFX development, and the safety strategy for file operations.
Centralize, control, and hand out access to API keys.
API keys tend to be scattered across projects, rotated poorly, and exposed directly to the applications that use them.
Role: Product design, permission modeling, and development of both the backend service and the panel.
Building readable, accessible flows that stay connected to the business rules.
React · TypeScript · JavaScript · JavaFX
Put into practice in: Episort, Overkill, mini social network
Modeling access, permissions and exchanges between applications.
Java · Spring Boot · Spring Security · REST API · PHP · Laravel · Symfony
Put into practice in: Janus, Overkill, mini social network
Structuring persistence around what the product needs.
PostgreSQL · MySQL · MongoDB
Put into practice in: Janus, Overkill, mini social network
Preparing reproducible environments and going all the way to deployment.
Docker · Git · Linux
Put into practice in: Janus, Overkill
Starting from the problem, framing sensitive actions and planning for ambiguous cases.
Requirements analysis · Modeling · Security by design
Put into practice in: Episort, Janus
An apprenticeship, a product to move forward, or simply a conversation about a useful application: Jonathan is open to professional exchanges.
Contact address still to be filled in.