Upgrade to Pro — share decks privately, control downloads, hide ads and more …

From code to consequences — Tech Pour l'Emploi #3

Sponsored · Your Podcast. Everywhere. Effortlessly. Share. Educate. Inspire. Entertain. You do you. We'll handle the rest. →

From code to consequences — Tech Pour l'Emploi #3

Qu’est-ce que ça veut dire aujourd’hui être fullstack, staff, product engineer ?
À quel moment on arrête d’écrire du code… et où s'arrête notre responsabilité ?

Et qu’est-ce que l’IA change — ou pas — dans tout ça ?

👉 J’ai essayé de prendre un peu de recul sur notre métier, nos trajectoires, nos angles morts aussi.

Arnaud LEMAIRE

November 25, 2025

Transcript

57 slides
  1. @lilobase – TECH POUR L’EMPLOI #3 From Code to Consequence

    You write code. But what do you really build?
  2. A Multi-Dimensional Problem • Load: Ability to handle more users,

    more transactions, and more data without degrading performance. • Complexity: Managing more fl ows, more integrations, more edge cases, and more dependencies. • Organization: Moving from a few teams to multiple units.
  3. — AWS Executive Insights « No team should be big

    enough that it would take more than two pizzas to feed them.[…] This is a team of less than 10 people: smaller teams minimize lines of communication and decrease the overhead of bureaucracy and decision-making. » The Two Pizzas Team Model
  4. — AWS Executive Insights « Two-pizza team isn’t solely about

    size as much as it is about fostering and pushing ownership and independence down to the team level. » The Two Pizzas Team Model
  5. — Jackie Stewart « You don’t have to be an

    engineer to be a racing driver, but you do have to have mechanical sympathy »
  6. • HTML & CSS mastery (Including semantic markup, accessibility (a11y),

    and responsive design) • Localization & Internationalization (Handling multiple locales, date/number formatting, plurals, RTL support, and dynamic language switching) • Component Architecture & Rendering Framework (Design systems, reusable UI components, framework- speci fi c patterns (e.g., React, Vue, etc.)) • State Management (Local/global state, lazy loading, prefetching, and hydration strategies) • Async Flow Management (Fetching, error handling, retries, caching, and suspense-like patterns) • Rendering Performance (Virtual DOM ef fi ciency, avoiding unnecessary re-renders, memoization, prioritizing TTI, and improving LCP). • SSR / SSG Expertise (Familiarity with server-side rendering and static site generation) • Animations & Transitions (Motion design for UX, accessibility-aware transitions, and performance-safe animations) • Front-end Security (XSS prevention, safe DOM manipulations, CSP usage, and secure cookie handling) • Testing & Validation (E2E testing (Playwright, Cypress), visual regression testing, and test coverage for UI behavior) • Build Pipeline & Tooling (Linting, dependency management, tree-shaking, and bundle size optimization (e.g., via Vite, Webpack)) • Analytics & Instrumentation (Event tracking, tagging plans, performance monitoring, cookie consent, and GDPR- compliant data collection)
  7. — The Phoenix Project « DevOps requires shared goals and

    shared pains throughout the IT value stream »
  8. — Kent Beck « The value of 90% of my

    skills just dropped to $0. The leverage for the remaining 10% went up 1000x. I need to recalibrate. »

More Decks by Arnaud LEMAIRE

Other Decks in Technology