- Elisabeth_The_Third
- There is nothing more powerful as an idea whose time has come
- Los Angeles, United States
- Offline
Business Blog
December 2, 2008
Trust
It is a greater compliment to be trusted than to be loved.
George Mac Donald
Character Wisdom Competence
Integrity Judgement Technical
Maturity Conceptual
Abundance Interdependence
Mentality
Almost all the work is done through relationship with people and in organizations. But what is communication like when there is no trust? It is impossible. It is like walking through the minefield. What if your communication is clear and precise, yet there is no trust? You will always be looking for hidden agenda. A lack of trust is the very definition of bad relationship.
The Speed of Trust
What is communication like when there is high trust? It is easy, it is effortless, it is instantaneous. There is nothing as fast as the speed of trust. It is faster then anything you can think about. Trust is the glue of life. It is the glue that holds organizations, cultures and relationship together.
Making and Keeping Promises
Nothing destroys trust faster then making and breaking a promise. Nothing builds and strengthen your trust more than keeping a promise you make.
Never use word promise until you are totally prepared to pay whatever price is to keep it.
Honesty and Integrity
Basketball coach legend Rick Pitino captured the principle of honesty: “Lying makes a problem part of the future; truth makes a problem part of the past.”
Trust is a highs form of motivation. Trust people, and when you do, you give a priceless gift and opportunity to others. The greatest risk of all is the risk of risk-less living.
November 24, 2008
The Laws Of Web Design
A great article - MUST READ - can be found at http://ejoh.zmolklife.com/fs/lowd.html
"A small list of laws concerning web design"
Mitch ’s observation
95 percent of the functionality will take 5% of the time to program, and the other 5 % - that which we call �the exceptions� - takes 95%.
Outline
First Law On System Planning
The Law of Detail
The Laws On Your Client’s Behavior
Hofstadter's Law
Murphy’s Law On Web Design
Wienberg’s Law (general law but applies to web design too)
Emil’s Principles
Emsz' Law of Self Criticism
Golub’s Laws of Computerdom
Glaser’s Law
November 24, 2008
Does-not-exist-in-reality News
Broken banker continues to insist on the reliability of a burned-out bank
translation from http://davydov.blogspot.com/2008/11/blog-post_17.html
Alexei Semonin, the former owner SeverInvestBank, that declared bankrupt last week, convened a press conference «to stop rumors about the reliability of the bank».
«I know that you, journalists, like sensations. However, while not distort the facts. The facts are that SeverInvestBank is one of the most reliable and innovative banks in Russia. We go from the crisis stronger than entered it all the enemies of spite. So make yourself a note. »
November 19, 2008
Painless Functional Specifications - Part 4: Tips
http://www.joelonsoftware.com/articles/fog0000000033.html
The biggest complaint you'll hear from teams that do write specs is that "nobody reads them." When nobody reads specs, the people who write them tend to get a little bit cynical.
The fact that the spec was shelved (unread and unloved) when it was completed makes people feel like it was all a bunch of work for naught.
So. Specs are good, but not if nobody reads them. As a spec-writer, you have to trick people into reading your stuff, and you should also probably make an effort not to cause any already-too-small brains to leak out through eye-sockets.
Tricking people into reading your stuff is usually just a matter of good writing. But it's not fair of me to just say "be a good writer" and leave it at that. Here are four easy rules that you absolutely must follow to make specs that get read.
Rule 1: Be Funny
Rule 2: Writing a spec is like writing code for a brain to execute
Rule 3: Write as simply as possible
Rule 4: Review and reread several times
R ule 5: Templates considered harmful
November 19, 2008
Who writes specs? Things to avoid
Here are three things to avoid
Don't let the marketing people be program managers. No offense, but I think my readers will agree that good marketing people rarely have a good enough grasp of the technology issues to design products.
Basically, program management is a separate career path. All program managers need to be very technical, but they don't have to be good coders. Program managers study UI, meet customers, and write specs. They need to get along with a wide variety of people -- from "moron" customers, to irritating hermit programmers who come to work in Star Trek uniforms, to pompous sales guys in $2000 suits. In some ways, program managers are the glue of software teams. Charisma is crucial.
November 19, 2008
Painless Functional Specifications - Part 3: Who should writ...
http://www.joelonsoftware.com/articles/fog0000000034.html
When Microsoft started growing seriously in the 1980s, everybody there had read The Mythical Man-Month, one of the classics of software management. The main point of that book was that when you add more programmers to a late project, it gets even later. That's because when you have n programmers on a team, the number of communication paths is n(n-1)/2, which grows at O(n2).
Program manager (project manager) would own the design and the spec for products. Since then, program managers (project managers) gather requirements, figure out what the code is supposed to do, and write the specs. There are usually about 5 programmers for every program manager (project manager); these programmers are responsible for implementing in code what the program manager (project manager) has implemented in the form of a spec.
A program manager (project manager) also needs to coordinate marketing, documentation, testing, localization, and all the other annoying details that programmers shouldn't spend time on. Finally, program managers are supposed to have the "big picture" of the company in mind, while programmers are free to concentrate on getting their bits of code exactly right.
November 19, 2008
Painless Functional Specifications - Part 2: What's a Spec?
From http://www.sharenow.com/blog/elisabeth_the_third/post/add/
A functional specification describes how a product will work entirely from the user's perspective. It doesn't care how the thing is implemented. It talks about features. It specifies screens, menus, dialogs, and so on.
A technical specification describes the internal implementation of the program. It talks about data structures, relational database models, choice of programming languages and tools, algorithms, etc.
When you design a product, inside and out, the most important thing is to nail down the user experience. What are the screens, how do they work, what do they do. Later, you worry about how to get from here to there.
Sample of function specification
http://www.joelonsoftware.com/articles/WhatTimeIsIt.html
Here are some of the things I put in every spec.
A disclaimer.
An author. One author.
Scenarios.
Nongoals.
An Overview.
Details, details, details.
Open Issues.
Side notes.
Specs Need To Stay Alive.
Views: 144
Subscribers: 6
Archive
Tags
- 8th
- actionscript
- bank
- bitchology
- business development
- business valuation
- cooking
- design
- ecommerce integration
- fish
- flash
- free software now
- fun
- fun design
- functional specifications
- habit
- heroes
- hr
- ideology
- international business
- investment capital
- iphone applications
- joint ventures
- leadership
- liquidation preference
- lost
- management
- networking
- news
- nickels and dimes
- obama
- organization
- politics
- preferred shares
- programming
- project management
- psd to xhtml
- psd to xhtml services
- ratchet
- requirements
- selling business
- social
- stress management
- sturgeon
- talent
- term sheet
- top executives
- tranches
- trust
- ui
- valuation
- vc process
- web
- weight
- widget development
- women









