Education on Antoine Boucher

Compiler pipeline, language genealogy, and why grammars matter

Mon, 13 Apr 2026 15:40:00 -0400

These figures come from a programming languages / compiler design textbook I was reading for a course. I kept the photos as a single reference page: how compilation is staged, how today’s languages relate historically, and where syntax stops being enough — you need precedence rules, disambiguation for things like else, and attributes for semantics such as types.

Compiler pipeline

The usual story: source program → lexical analyzer (tokens) → syntax analyzer (parse trees) → intermediate code (with semantic analysis) → optional optimization → code generator → machine code on a computer, plus input data and results. A symbol table sits beside the front phases and feeds the back end.

From BMC to pitch — QcES journey notes (Spring 2024)

Mon, 13 Apr 2026 10:00:00 -0400

Full article in French — same slug; you can also switch to FR in the header.

At a glance

The Business Model Canvas (BMC) describes how an organization creates, delivers, and captures value; it answers three questions: desirability, feasibility, and viability.
You usually start with customer segments and value proposition, then iterate—the model evolves with the market.
Segmentation makes the market concrete (B2B vs B2C, crisp criteria) instead of vague labels (“doctors”, “parents”).
Interviews are for discovery: the goal is to learn, not to sell; connect, don’t convince—and stay attached to the problem, not your first idea of the solution.
Structured feedback (strengths + one growth angle) and a short spoken pitch (no slides) clarify the idea early.
A product roadmap is a strategic view over time, not a detailed project plan; it aligns vision, audience, horizon, metrics, and resources.
PoC, prototype, and MVP play different roles: technology check, user interaction learning, then a first market version you can stress-test with real users or buyers.
Market and value proposition: account for external forces (macro, industry, trends) and express value as offer + customer benefit.
A solid pitch often follows Hook → Believe → Join: lead with the problem, show credibility and differentiation, then make a specific ask.

This is a personal write-up based on QcES materials (Spring 2024 cohort) and facilitators; it is not an official program document.

Software lifecycle notes — GOALS, waterfall, and verification vs validation

Mon, 13 Apr 2026 08:00:00 -0400

These pages are from a software engineering textbook I used in coursework. I grouped the figures here as a single reference: goal-oriented planning, how the waterfall model sequences activities (with verification and validation paired to each phase), an incremental variant, the textbook’s list of life-cycle subgoals, a reminder that method advice depends on context, and a short ethics passage about impact on people.

GOALS approach (Figure 3-1)

The GOALS flowchart is a top-down pattern: set overall life-cycle goals (functions, constraints, schedule, usability, maintainability), analyze the problem and sketch solution structure, separate concerns into subgoals, develop solutions for each subgoal in parallel where possible, then validate those solutions against the other goals and iterate until the decision “all goals satisfied?” is yes.

Byzantium’s first workshop — Solidity and an ERC-20 token on Ethereum

Mon, 11 Mar 2024 18:30:00 -0400

Byzantium ran its first Ethereum workshop: a hands-on session where attendees went from a Solidity / ERC-20 starter (via OpenZeppelin) to deploying a token and swapping transfers with each other. Khalil Anis Zabat led the session.

Full article in French (same slug — you can also switch to FR in the header).

Links: LinkedIn thread / Byzantium recap · Deployed contract (short link)

Thanks to the facilitator and everyone who joined.