While content is there, it reads like marketing text.
> Near-term trends and innovations that people can grapple with or adopt today in hopes of being well-positioned tomorrow
> Medium-term rumblings...
> Long-term visions of the future that contextualize today's fashions within the broader strokes...
As someone who is presenting at his first national conference soon, I was hoping to read through this article and get some good insight. Your list of 4 items amounts to advice that can be summed up as:
1. Old lessons applied to new technology.
2. Future-proofing your skill-set.
3. Analyze today's hard problems and share new solutions.
4. Bold, new ideas that we otherwise wouldn't make the time for.
And this can be summed up in 3 steps:
1. Present a problem.
2. Present solutions to the problem.
3. Solve the problem with the solutions.
Or, more concisely:
1. Solve a problem.
Whether the problem is an old or new problem is irrelevant. And whether the solution is old or new is irrelevant. This is essentially covered in the Angular example.
The result of solving a problem is having to describe the problem. And usually that's best done with a story.
1. Tell a story about solving a problem.
This provides context. And, everyone loves a good war story. This helps you connect (as mentioned in the connect portion of the article). Also, by telling a story, and solving a specific or specific problems, you avoid that general overview. You have to dig into specifics, because your problem was specific.
So, the shortest advice I can sum up is: Tell a problem solving story.
> Near-term trends and innovations that people can grapple with or adopt today in hopes of being well-positioned tomorrow > Medium-term rumblings... > Long-term visions of the future that contextualize today's fashions within the broader strokes...
As someone who is presenting at his first national conference soon, I was hoping to read through this article and get some good insight. Your list of 4 items amounts to advice that can be summed up as:
1. Old lessons applied to new technology. 2. Future-proofing your skill-set. 3. Analyze today's hard problems and share new solutions. 4. Bold, new ideas that we otherwise wouldn't make the time for.
And this can be summed up in 3 steps:
1. Present a problem. 2. Present solutions to the problem. 3. Solve the problem with the solutions.
Or, more concisely:
1. Solve a problem.
Whether the problem is an old or new problem is irrelevant. And whether the solution is old or new is irrelevant. This is essentially covered in the Angular example.
The result of solving a problem is having to describe the problem. And usually that's best done with a story.
1. Tell a story about solving a problem.
This provides context. And, everyone loves a good war story. This helps you connect (as mentioned in the connect portion of the article). Also, by telling a story, and solving a specific or specific problems, you avoid that general overview. You have to dig into specifics, because your problem was specific.
So, the shortest advice I can sum up is: Tell a problem solving story.