What distinguishes computer enthusiasts from programmers

Excellent computer enthusiasts have a priceless skill. Can a programmer be the same as a computer enthusiast? are programmers less creative than computer enthusiasts who don't know how to encode them?

The following story makes me see the difference between them.

I have recently been invited to do a weekend business coaching. In the evening of Friday, we called together to eat pizza, set ideas, LDTX teams and discuss start-up plans. At the end of the week, everyone was very satisfied with what was going to be done this weekend.

On the weekend morning I came to the scene and found that people were working hard. Some people stayed up all night in a hurry to realize their ideas. This is the entrepreneurial spirit!

But I was surprised to find that so many teams have already started coding! The feeling is that they are rushing to get things developed and running by the Sunday night, which makes most teams think about fulfilling their original ideas, instead of exploring different ideas and choosing a better one.

Doesn't that sound different?

There is a team that stands out because there is no programming in the team. So they spend their time using PowerPoint to make prototypes, visit rooms and other people to communicate their ideas, get feedback, and then go back to their desks and discuss and refine their ideas. They are the most noisy, the most angry, the most enthusiastic and good group, they seem to get a lot of fun from the activity. Most importantly, they move forward a lot faster than the others because they are not lost in the details of how to get things running with rails or PHP.

In the morning of Sunday, they had a flash of light, abandoned all previous prototypes and returned to work before the drawing board. I saw them making a new prototype in a few hours. Because they don't write code, they don't worry about abandoning yesterday's work (after all, prototypes are used for this). Because they use PowerPoint to model their ideas, they can quickly make their ideas concrete.

In the evening of Sunday, they did not hand over an application that could be run, but they used all of the viewers with the click-Effect prototype that was produced based on their final ideas. Not only did they present the final idea, they also took the audience through the change generation process of the whole idea.

What's the result?

They are not winning over the idea of how good or the other group contains more features. This weekend produced a lot of ideas. But when other groups spend their limited time on implementation details, the group is focused on the high level of their ideas and spends more time improving it rather than coding it.

They are not programmers, but they are computer enthusiasts. This identity finally let them benefit!

Many entrepreneurs think they are at a disadvantage compared to those who encode. They think they are not computer enthusiasts because they don't program. The reality is that they have a creative advantage because they don't rush into coding work. Instead, they are forced to "trim" their ideas, test them with upper-level tools and platforms, and are constrained to not care about the details. This will force them to focus on solving the user problem rather than solving the implementation problem.

Making software is not just a coding technique. It is a thought habit that focuses on the most important things at each stage at different stages rather than getting bogged down in details prematurely.