the engineers who will last are the ones with the best social skills, where they can translate from conversations, from the needs of the user, and be able to convert that into software, decide what's the best architecture or the best solution for that problem. And go back and let everyone know what you built and show them why you built it that way and how you built it. And I see that over and over.
Not because people care about how they built it, but because they are able to articulate the requirement back to the user and explain to them why they built it that way. Versus the classic engineer who would just get a PRD, write it down, execute and go back and say ticket done. Those engineers will die, I think, because the value now is the communication. And the closer you are to articulating, those are the engineers that will last.
And then you will probably have engineers who have better skills for something, like maybe those who like front end more, they have an eye for detail and they will build better UIs or better UXs, versus those who will do back end who maybe are better at architecting software. But going back with what you built, showing it and making it appealing for users to pay attention to it and use it, those are the engineers who are gonna last.
