Discussion about this post

User's avatar
Reid DeRamus's avatar

“The software engineering skill that's valuable is solving the problems—not writing the code.”

Awesome post, Logan! I’ve been thinking about this quote above, which I think is true for other functions as well: product, design, data, etc.

I’m wondering how all these functions change when, at their core, they’re all problem solvers, and a growing portion of the role is automated by AI. This is already true in many cases: a really great designer can pick up a lot of product work, a technical pm can straddle the eng / prod divide, and a great engineer can piece together a solid roadmap.

I’m really curious how these functions evolve over the next few years - would love to read a post on this topic.

Thanks again for sharing your thoughts, and especially grateful for the GitHub ML learning resource. 🙏

Expand full comment
Josh Brake's avatar

Enjoyed this post, Logan. I think you’re right on the money here. The thing that’s always mattered most is thinking and problem solving. Whether it’s programming or writing, that’s the skill we should be focusing on cultivating.

Expand full comment
12 more comments...

No posts