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.

Transcript

1. @lilobase – TECH POUR L’EMPLOI #3 From Code to Consequence You write code. But what do you really build?
2. 1. Scaling A multi-dimensional problem
3. 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.
4. Scale by Unscaling
5. — 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
6. — 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
7. 1. Ownership You’re Not (Only) Shipping Code
8. Full Stack Ownership at code level
10. — Jackie Stewart « You don’t have to be an engineer to be a racing driver, but you do have to have mechanical sympathy »
12. • 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)
17. Full Cycle End-to-End Delivery Ownership
32. — The Phoenix Project « DevOps requires shared goals and shared pains throughout the IT value stream »
33. Ownership is something you take, not something you are given.
34. Sta ff Engineer Ownership at System Level
45. Alignement Because Ownership is Not Enough
47. Autonomy Alignement
48. Autonomy Alignement
49. Autonomy requires Alignement Autonomy Alignement Micromanagement & Mindless execution Confusion & Inaction Misdirected Actions (Chaos)
50. Autonomy Alignement Micromanagement & Mindless execution Confusion & Inaction Misdirected Actions (Chaos) Autonomy Autonomy requires Alignement
51. Autonomy Alignement Clarity (Vision & shared understanding) Competency (Mastery) Cohesion (Trust) The 3 C model
52. Scale Autonomy Ownership & Accountability Alignement & Clarity
53. You The One Thing AI Can’t Replace
54. — 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. »
55. Ownership
56. Alignement
57. Arnaud LEMAIRE CTPO @ sundayapp.com Merci