A few weeks ago, I sat down with former Google engineer and entrepreneur Mark Zuckerberg, the CEO of Facebook.
His words rang true for me.
It was the first time I’d ever heard him describe his startup as “the founder network,” and I was so grateful that I’d been given the chance to ask him a question.
He was the one who asked it, so I guess it’s not surprising.
I had never heard the word before.
I didn’t even know what the word meant.
I was on the other side of the world, so what the heck was “founder network?”
But Zuckerberg didn’t know.
And that’s when I realized he had a big problem with the word.
The word is so ubiquitous in tech, and it’s the one word that defines the tech world in a big way.
The network is a word we use to describe our network of peers, colleagues, friends, acquaintances, and other people who are a part of our work.
A network is the way we collectively interact with one another.
As we build a business and we grow, the network grows, too.
The founder network is an important part of how we get the products and services we want.
But Zuckerberg’s description of his company as “a network of friends” was wrong.
The founders who started the company, all of whom I know personally, were not “friends.”
They were strangers to Zuckerberg.
They were also strangers to the other founders.
I don’t want to give Zuckerberg credit for this, but he did.
And if Zuckerberg were to understand what a network is, he would have a better understanding of how he’s building his company.
It’s also important to understand that Zuckerberg, unlike most founders, has a network of colleagues and people who work closely with him.
These people work on his projects and make sure that they’re running the company as efficiently as possible.
If you ask anyone in Silicon Valley, they’ll tell you that Zuckerberg is the leader of the team, and that he has a lot of power within the company.
He’s the CEO, he’s the product guy, and he’s probably the most important person in the world to his employees.
But his network is not all of the employees at Facebook.
There are hundreds of other people at Facebook who are part of the company’s community.
These include our cofounders, our CEO, our engineering team, our product managers, our designers, our marketing people, our sales people, and our engineering people.
When we were first founding the company and Zuckerberg was still a rookie, I didn.
I’d just gotten my engineering degree and had no idea what I was doing, and I didn, too, until I was a junior at Harvard.
We all had the same goal, which was to build the best software product possible for people.
I started building the software that would run our company, but there was no way I could have built it without the help of my peers.
There was no need to have a CEO who was responsible for all of these different parts of the organization, and there wasn’t a need for a team of engineers who were responsible for the software itself.
The idea that I had to go to Harvard to learn everything I could about software development was completely foreign to me.
I remember sitting in my dorm room and feeling a little bit scared.
I figured that the more I learned, the more likely I was to fail.
So I started going to lectures on how to build software.
I did my own software development courses, and my professor was always the first person I saw who understood how software should be built.
He taught me how to use Ruby on Rails, how to code with CoffeeScript, how I should structure my code, and what to do if I needed to change something.
And he taught me the difference between right and wrong.
If I didn (and I didn) make mistakes, I was punished.
If things were working fine, I got rewarded.
If they were working really badly, I felt bad.
So when I heard Zuckerberg say he had his “founders” in Silicon Alley, I thought, Oh my gosh, I’m really into that.
I thought that was so cool.
But I’d never heard of the term “founder” before.
After spending many years as a software engineer, I began to learn about the word more and more.
I began reading about it more and better.
The reason I was interested in the word was because I was looking for something that I could apply to myself.
In my experience, if you have a bad reputation, people will look at you and judge you based on your reputation, not based on what you do.
It makes sense to me that a company that’s perceived as being “bad” is also perceived as having bad ideas.
So it made sense to think of a company with a reputation for being bad as being a good company.
I knew that the company Zuckerberg founded would be perceived as a good place to be.
I also knew that people would