Archive for March, 2007

links for 2007-03-29



links for 2007-03-27



Rough week, rough year

When I last updated about fitblogging/fatblogging, I was way under. I let that go to my head and I managed not to lose a single pound, or half pound, or tenth of a pound. I am still at the same weight and while I’m a little disappointed, I’m not too upset as a whole.

The thing that was weird about today was that we lost our cat today. Not in the “oh no, he got outside and ran away”, but in the way where he has joined the great scratching post in the sky. Floyd has been sick for a while, three months now, and while he showed some improvement over the course, on the whole it was really just a steady decline. He had lost over 40% of his body weight, consisting of little more than flesh and bones, he could eat or drink with bringing it up shortly after consumption and the vets were no where closer to finding out what was wrong with him.

Esther and I were faced with a choice, costly test that may or may not get us answers to what’s wrong, or take away Floyd’s suffering, which there was plenty of.

So on the whole, the past year has been one of loss. First we lost Esther’s dad, then my pet rat, and now our first pet together, Floyd. It has been very hard to maintain my Buddhist outlook on life, partly because there is no god to be angry with, partly because it all come back to attachment, which leads to suffering; how can you perceive death with out attachment? Apparently, that means I should meditate more.

Floyd, I miss you.

Floyd

Kelly Johnson’s 14 Rules of Management

I recently read a blog posting which linked over to Kelly Johnson’s 14 Rules of Management and I was intrigued by his principles of management and how they can relate to a design shop. I have been interested in Skunk Works ever since I had read a Popular Mechanics article on the organization just after the first Gulf War and learning of Kelly’s rules of management, I immediately been can to co-relate them to running a design shop. Below are Kelly’s rules of management with my thoughts on each and how they relate to design management immediately below. They are numbered SWD: Skunk Works Design.
  1. The Skunk Works manager must be delegated practically complete control of his program in all aspects. He should report to a division president or higher.
    SWD 1. If the project manager must have control of the project.
  2. Strong but small project offices must be provided both by the military and industry.
    SWD 2. Small, competent teams should be provided by all parts of the project (web, print, programming, etc.)
  3. The number of people having any connection with the project must be restricted in an almost vicious manner. Use a small number of good people (10% to 25% compared to the so-called normal systems).
    SWD 3. A project does not need everyone’s input, especially on the client side.
  4. A very simple drawing and drawing release system with great flexibility for making changes must be provided.
    SWD 4. The project system should facilitate that changes be made easily.
  5. There must be a minimum number of reports required, but important work must be recorded thoroughly.
    SWD 5. The project system should not get in the way of the design process, although client documentation of approval must be recorded.
  6. There must be a monthly cost review covering not only what has been spent and committed but also projected costs to the conclusion of the program. Don’t have the books ninety days late and don’t surprise the customer with sudden overruns.
    SWD 6. Project costs should be reviewed regularly by the team, any changes or projected changes in costs should be reported to the client immediately.
  7. The contractor must be delegated and must assume more than normal responsibility to get good vendor bids for subcontract on the project. Commercial bid procedures are very often better than military ones.
    SWD 7. If you have to subcontract out, make it for less than you charge but that you are willing to take responsibility for the results
  8. The inspection system as currently used by the Skunk Works, which has been approved by both the Air Force and Navy, meets the intent of existing military requirements and should be used on new projects. Push more basic inspection responsibility back to subcontractors and vendors. Don’t duplicate so much inspection.
    SWD 8. Basic proofing should be done well before the client sees the project. Proofing should be done by those who will directly approve the project.
  9. The contractor must be delegated the authority to test his final product in flight. He can and must test it in the initial stages. If he doesn’t, he rapidly loses his competency to design other vehicles.
    SWD 9. The client should be kept up to date with thumbnails, sketches and rough ideas initially, if not you are designing it wrong.
  10. The specifications applying to the hardware must be agreed to well in advance of contracting. The Skunk Works practice of having a specification section stating clearly which important military specification items will not knowingly be complied with and reasons therefore is highly recommended.
    SWD 10. Specifications for the project must be spelled out well in advance.
  11. Funding a program must be timely so that the contractor doesn’t have to keep running to the bank to support government projects.
    SWD 11. Billing, invoicing or charging should be quick. Don’t leave the client guessing what the bill will be.
  12. There must be mutual trust between the military project organization and the contractor with very close cooperation and liaison on a day-to-day basis. This cuts down misunderstanding and correspondence to an absolute minimum.
    SWD 12. There must be trust between the project manager and the client. If daily updates are needed, they should be given to cut down on misunderstandings. If they are not needed, don’t do them.
  13. Access by outsiders to the project and its personnel must be strictly controlled by appropriate security measures.
    SWD 13. Clients should not interact with the design team, they should interact with project managers. Maintain a sense of team security.
  14. Because only a few people will be used in engineering and most other areas, ways must be provided to reward good performance by pay not based on the number of personnel supervised.
    SWD 14. Rewards should be based on performance, those who consistently hit the mark should be rewarded more.

What do think about these Skunk Work Design rules?



Mid-week Weigh-in 176.8 1

Um. I didn’t lose a limb, but apparently I lost almost 10 pounds lighter than last week. I stepped on the scale this morning and I said to Esther, I lost a little weight.

“How much?”

“A little, it says 176.8″

“A little! That’s almost 10 pounds!

“Oh yeah… I guess it is

It’s probably due to the stress I’ve been under at work, I haven’t been eating my lunches, I’ve been drinking a _lot_ of coffee, which has probably shot my metabolism into high gear. Now it’s all about maintaining that phenomenal drop in poundage!



links for 2007-03-22



Fat blogging weigh-in: 184.9 1

Today was the weigh-in after a week of not really following the Weight Watchers super strict. I was not the best Weight Watchers dieter. The great thing was I was only up half of a pound. Pretty good for not exercising or really following the plan. I kind of needed a week off to regain my focus. Esther went on a big long walk this morning to re-enforce the fact that we are back on “the wagon”. With the motivation of losing that additional half pound, I will be doing regular midweek updates again.

links for 2007-03-16



Haiku Tuesday: Welcome to the suck

Heartburn, I’m feeling depressed. No motivation, “Welcome to the suck.”

Updates, updates… 1

So based on yesterday’s weigh-in, I’m now up to 36% of my weight loss goal! I’m really pumped now

Also, if you’ve been watching the site closely, you will have noticed a yellow fade-out in the top bar. I have been continually updating my tumblelog (RSS), and the above is the link. A tumblelog is

… is a variation of a blog, that favors short-form, mixed-media posts over the longer editorial posts frequently associated with blogging. Common post formats found on tumblelogs include links, photos, quotes, dialogues, and video. Unlike blogs, this format is frequently used to share the author’s creations, discoveries, or experiences without providing a commentary.
via - Wikipedia

Here is a better definition of a tumblelog as proffered by Leo Laporte on Net@Nite:

Twitter is what you are doing right now, a Tumblelog is a low threshold blog, you post what you find and a blog is something you work on writing and crafting. There are three levels of web engagement
I can’t agree more. In case you don’t know, I do have a twitter account. You can check me out at http://twitter.com/jeredb (RSS), add me as a friend to keep up to date on what I’m doing.



Next Page »

Blog Information Profile for jeredb