Just Do It Efficiency - Revision history

ThePlaz: write some more

2009-09-02T04:09:10Z

write some more

ThePlaz: add some more

2009-09-02T03:55:18Z

add some more

ThePlaz: fix template

2009-09-02T03:43:09Z

fix template

ThePlaz: put together more random thoughts

2009-09-02T03:42:25Z

put together more random thoughts

ThePlaz: moved Living the W3Life to Just Do It Efficiency: reflects broader topic

2009-09-02T03:36:41Z

moved Living the W3Life to Just Do It Efficiency: reflects broader topic

ThePlaz: from original revision: some of the parts written a few years ago and some now; cleaning it up now and added a bunch

2009-09-02T03:35:55Z

from original revision: some of the parts written a few years ago and some now; cleaning it up now and added a bunch

ThePlaz: write some more and clean up

2009-09-02T02:23:56Z

write some more and clean up

ThePlaz: very rough draft

2009-08-22T05:15:52Z

very rough draft

New page

Living the w3 life

Doing not talking about

Sometimes it's important to just do. Not talk about over and over. Do the

purpose. Orgizational structure is sometimes a nessessity - but many times

the paperwork gets in the way of doing things. The paperwork should be

proportional to the size of the job. Otherwise you will spend too much

time doing paperwork and not getting stuff done.

My friend Mike Gdovin ran a "company" called w3life. Throughout their 3

year lifespan they put out about 10 content pieces, but they changed their

logo 3 times and their content style 3 times.

It's not the company structure that is important. Having a CEo role,

arguing about shares, trying to get the best logo. You must do something.

From working with profesiopnalias in this insustry, I've learned that they

do this. There is a discrete way to talk about ownership, but this does

not get in the way. They recognize that 60% of 0 is 0. Formal structures

are added later, as needed.

Logo
W3Life changed their logo many times. Write the progression - can't

research now.

With my experience with big business in 2009, I've seen that this type of

foot dragging happens in big business. It's really fustrating to me. I

particularly dislike foot dragging or anything that is not effiencet.

Efficency is good

I always strive for effiencey in my life, because that is how I get the

most done. I realize much of my life goes tro perpehy "living and

relaxing" but when I am working I try to be effiencent. I heard this

somewhere and I think its particlarly true: People want to keep their jobs

(want to remain part of the process and look busy) But in my business I

would fire them. Second, people don't want to rock the boat.

I think the best teams work with a small group of motivated, first class

workers who are given the room to work. They need to be willing to talk

out about the structure and rock the boat.

Problbly the biggest problem is communication. Part of the issue probabley

is that people don't want to put themsleves out of a job. But also, teams

that are too big don't share stuff. Wikis are a large part of the solution

if people take the time to contribute.

I want to always bring more value to a job that I should not play into

these tricks - and in high school I didn't by tring to sneak by without

doing HW - don't always get recongized like Chris Denny - I am bad at BSing

In programming, you can do a lot of nothing if you spend a lot of time of

planning out specs. Now this is needed sometimes. But I think most of the

time rapid prototyping or agile progamming would get stuff done. Just try

it. Again, this works best with small, close-knit teams, who really know

what they are doing.

← Older revision		Revision as of 04:09, 2 September 2009
Line 34:		Line 34:

	Forcing yourself to do something, even if it is hard. No matter how hard. That's what you have to aspire to.		Forcing yourself to do something, even if it is hard. No matter how hard. That's what you have to aspire to.
		+
		+	===Working===
		+	Young people who are successful always seem to be busy. They are always on their iPhone. That's there their secretary. They are always connected and can work in any portion of the organization. You send them an email and then they send you a terse reply which fixes the problem. They are always on the run, being busy.

	==How I Would Run My Business==		==How I Would Run My Business==

@@ Line 32: / Line 32: @@
 ===Living and Relaxing===
 People do need periphery time for "living and relaxing."  I find that when I am busy I finish things in a much shorter amount a time.  You must find the right balance of time for yourself.  You need to schedule it in, enjoy the time you have, and get back to work.
 ==How I Would Run My Business==

← Older revision		Revision as of 03:43, 2 September 2009
Line 46:		Line 46:
	In programming, you can do a lot of nothing if you spend a lot of time of planning out specs. Now this is needed sometimes. But I think most of the time rapid prototyping or agile programming would get stuff done. Just try it. Again, this works best with small, close-knit teams, who really know what they are doing.		In programming, you can do a lot of nothing if you spend a lot of time of planning out specs. Now this is needed sometimes. But I think most of the time rapid prototyping or agile programming would get stuff done. Just try it. Again, this works best with small, close-knit teams, who really know what they are doing.

−	{{Personal ~~Philosophy~~}}	+	{{Personal Philosophies}}

@@ Line 1: / Line 1: @@
-My friend, Mike Gdovin ran a "company" called [[W3life]] during high school.  It was a perfect learning experience to show what the power of "doing stuff" is and to talk about my drive for it.  It kinda veers off course.  This was started in Oct 2008 and finished Sept 2009.
+My friend, Mike Gdovin ran a "company" called [[W3life]] during high school.  It was a perfect learning experience to show what the power of "doing stuff" is and to talk about my drive for it.  It's a bunch of random thoughts.  This was started in Oct 2008 and finished Sept 2009.
 ==Do Stuff Philosophy==
@@ Line 8: / Line 8: @@
 Organizational structure is sometimes a necessity - but many times the paperwork gets in the way of doing things.  The paperwork should be proportional to the size of the job.  Otherwise you will spend too much time doing paperwork and not getting stuff done.
-==W3life==
+==Living the W3life==
 My friend Mike Gdovin ran a "company" called w3life.  Throughout their 3 year lifespan they put out about 10 content pieces, but they changed their logo 3 times and their content style 3 times.  You can read the history on the [[W3life]] page.
@@ Line 27: / Line 27: @@
 Plus if you are always worrying how to do the least bit possible it is simply a big distraction.  It's the same with lying.  You spend so much energy trying to be different things for different people that you get less done.  I find its far better not to worry about and just try the hardest.
 ===Living and Relaxing===
 People do need periphery time for "living and relaxing."  I find that when I am busy I finish things in a much shorter amount a time.  You must find the right balance of time for yourself.  You need to schedule it in, enjoy the time you have, and get back to work.
-==How I would Run My Business==
+==How I Would Run My Business==
 I want people who are not afraid of standing up and rocking the boat to call attention to something.  No none works in just departments anymore.  Everyone needs to respectfully voice their opinion about everything.  Nothing can be written off as "not my job".  It's about a life long of learning.
@@ Line 37: / Line 39: @@
 ==Problems: Communication==
-Probably the biggest problem is communication.  Part of the issue probably is that people don't want to put themselves out of a job.  But also, teams that are too big don't share stuff.  Wikis are a large part of the solution if people take the time to contribute.
+Probably the biggest problem is communication.  Teams that are too big don't share stuff.  Wikis are a large part of the solution if people take the time to contribute.  They need to be managed well.
 ==Rapid/agile==
 In some ways, this might be related to the philosophies of rapid or agile programming.  In many cases, its faster just to try something.  This way you will know all of the issues and might think of things that you would have never guessed.

@@ Line 1: / Line 1: @@
-My friend, Mike Gdovin ran a "company" called [[W3life]] during high school.  It was a perfect learning experience to show what the power of "doing stuff" is.
+My friend, Mike Gdovin ran a "company" called [[W3life]] during high school.  It was a perfect learning experience to show what the power of "doing stuff" is and to talk about my drive for it.  It kinda veers off course.  This was started in Oct 2008 and finished Sept 2009.
 ==Do Stuff Philosophy==
-I am strongly a proponent of doing something.  Instead of planning, and talking, just do it.  Now perhaps in software that is easy.  Building a building requires lots of planning not only to make the building stand up, but to make sure that no workers are standing around doing nothing.  Some enterprise software is also all about integration.  However, even in big projects, people need to stand up and take the lead,  make a decision on something or just push to get stuff done.  (I always try to get stuff done as fast as possible, because then it is not sitting around and I can switch to doing whatever is most efficient at the moment.)  The moment anything lags, you are losing something.  You can not lose the focus on getting stuff done.
+I am strongly a proponent of doing something.  Instead of planning, and talking, just do it.
-==Doing not talking about (from a few years ago)==
+Now perhaps in software that is easy.  Building a building requires lots of planning not only to make the building stand up, but to make sure that no workers are standing around doing nothing.  Some enterprise software is also all about integration.  However, even in big projects, people need to stand up and take the lead,  make a decision on something or just push to get stuff done.  (I always try to get stuff done as fast as possible, because then it is not sitting around and I can switch to doing whatever is most efficient at the moment.)  The moment anything lags, you are losing something.  You can not lose the focus on getting stuff done.
-Sometimes it's important to just do.  Not talk about over and over.  Do the purpose.  Orgizational structure is sometimes a nessessity - but many times the paperwork gets in the way of doing things.  The paperwork should be proportional to the size of the job.  Otherwise you will spend too much time doing paperwork and not getting stuff done.
-My friend Mike Gdovin ran a "company" called w3life.  Throughout their 3 year lifespan they put out about 10 content pieces, but they changed their logo 3 times and their content style 3 times.
+Organizational structure is sometimes a necessity - but many times the paperwork gets in the way of doing things.  The paperwork should be proportional to the size of the job.  Otherwise you will spend too much time doing paperwork and not getting stuff done.
 It's not the company structure that is important.  Having a CEO role, arguing about shares, trying to get the best logo.  You must do something.
-From working with profesiopnalias in this insustry, I've learned that they do this.  There is a discrete way to talk about ownership, but this does not get in the way.  They recognize that 60% of 0 is 0.  Formal structures are added later, as needed.
+==Pros==
-==Logo==
+Plus if you are always worrying how to do the least bit possible it is simply a big distraction.  It's the same with lying.  You spend so much energy trying to be different things for different people that you get less done.  I find its far better not to worry about and just try the hardest.
-W3Life changed their logo many times.  Write the progression - can't research now.
-With my experience with big business in 2009, I've seen that this type of foot dragging happens in big business.  It's really fustrating to me.  I particularly dislike foot dragging or anything that is not effiencet.
+===Living and Relaxing===
-==Efficency is good==
+==How I would Run My Business==
-I always strive for effiencey in my life, because that is how I get the most done.  I realize much of my life goes tro perpehy "living and relaxing" but when I am working I try to be effiencent.  I heard this somewhere and I think its particlarly true: People want to keep their jobs (want to remain part of the process and look busy)  But in my business I would fire them.  Second, people don't want to rock the boat.
+I want people who are not afraid of standing up and rocking the boat to call attention to something.  No none works in just departments anymore.  Everyone needs to respectfully voice their opinion about everything.  Nothing can be written off as "not my job".  It's about a life long of learning.
 I think the best teams work with a small group of motivated, first class workers who are given the room to work.  They need to be willing to talk out about the structure and rock the boat.
-Problbly the biggest problem is communication.  Part of the issue probabley is that people don't want to put themsleves out of a job.  But also, teams that are too big don't share stuff.  Wikis are a large part of the solution if people take the time to contribute.
+==Problems: Communication==
-I want to always bring more value to a job that I should not play into these tricks - and in high school I didn't by tring to sneak by without doing HW - don't always get recongized like Chris Denny - I am bad at BSing
+I want to always bring more value to a job that I should not play into these tricks - and in high school I didn't by tring to sneak by without doing HW - don't always get recognized like Chris Denny - I am bad at BSing
 In programming, you can do a lot of nothing if you spend a lot of time of planning out specs.  Now this is needed sometimes.  But I think most of the time rapid prototyping or agile progamming  would get stuff done.  Just try it.  Again, this works best with small, close-knit teams, who really know what they are doing.