|
9 | 9 | - event: '[React Summit US](https://reactsummit.us/)' |
10 | 10 | date: 2026-11-17 |
11 | 11 |
|
| 12 | +- title: 'The Last Software Engineer' |
| 13 | + resources: |
| 14 | + - '[article](https://www.epicproduct.engineer/the-last-software-engineer)' |
| 15 | + deliveries: |
| 16 | + - event: |
| 17 | + '[WeAreDevelopers World |
| 18 | + Congress](https://www.wearedevelopers.com/world-congress)' |
| 19 | + date: 2026-07-09 |
| 20 | + tags: |
| 21 | + - ai |
| 22 | + - product engineering |
| 23 | + - software development |
| 24 | + - career |
| 25 | + description: >- |
| 26 | + I'm not here to tell you software engineering is ending soon. Nobody can put |
| 27 | + a reliable date on that, and pretending otherwise is a distraction. But we |
| 28 | + also have to admit something humbling: a year ago, most of us would not have |
| 29 | + predicted coding agents would be this good. That should make us less |
| 30 | + confident about predicting what they'll be able to do one year, or five |
| 31 | + years, from now. |
| 32 | +
|
| 33 | +
|
| 34 | + So let's use "The Last Software Engineer" as a thought exercise. If AI keeps |
| 35 | + taking over more of the implementation work, what remains most human and |
| 36 | + valuable for us to do? In this talk, we'll take one step back from the |
| 37 | + hypothetical end and focus on the durable skill that has always separated |
| 38 | + great engineers from merely productive ones: judgment. |
| 39 | +
|
| 40 | +
|
| 41 | + The future belongs not to people who only know how to build, but to people |
| 42 | + who know what should be built. We'll talk about product engineering, |
| 43 | + accountability, trade-offs, constraints, evaluation, and how to keep making |
| 44 | + software worth having in an AI era. |
| 45 | +
|
12 | 46 | - title: 'Building with Remix 3' |
13 | 47 | resources: |
14 | 48 | - '[Remix](https://remix.run)' |
|
0 commit comments