Fault Vs Responsibility Quotes

on. “No matter how obstructive the Republicans may be, Obama has the responsibility of leadership. I’m worried that he’s overplaying his hand in saying that it’s all the Republicans’ fault.

Secure Man VS Vulnerable Man A secure man is someone who can identify their own weaknesses and improve. He can accept his flaws and maintain his self esteem. He knows his journey is never over, so he always strives for more. He lends strength to others needing a helping hand. He prefers to take the hard right over the easy wrong. He can handle constructive criticism without bitterness. He can provide for himself and his family. He can set goals for himself knowing one day he can achieve them. He is a multitasker. He doesn't make decisions just for the moment; He makes decisions that he knows will benefit and effect his whole life. If this man makes a mistake he will hold himself responsible and correct his mistake. He has confidence in himself and holds no one else accountable for his happiness and/or peace of mind. A sincere understanding of empathy for others, a sense of humility, and humbleness are reinforcing characteristics of this man. A secure man has faith in the Lord. A vulnerable man is someone who depends on others. He can not accomplish routine tasks or deliver on his own. He is always asking for a helping hand and has little or no self esteem. He lives for the moment without a life plan. He doesn't set lifetime goals. A vulnerable man is either too arrogant and ignorant to notice when somebody is trying to help him, so he rebels against those closest to him. A vulnerable man gets angry when things doesn't go his way. He doesn't only complain, he also complains about what others aren't doing for him. He can't provide for himself or others. You can never go to him for advice or will he extend a hand of help to others without wanting something in return. A vulnerable man can not make a decision and lives a reactive life instead of a proactive one. He knows right from wrong...but still decides to go the wrong way because it's the easiest. A vulnerable man seeks an enabler one who will bail them out time and time again. Others notices his individual weaknesses...However he chooses a life of denial and deflection. This man believes it is always someone else's fault and feels entitled to others hard work and efforts. A vulnerable man has no faith in a higher power and thinks he'll never have to answer for the choices made in their life.-27 September 2012-

As a Marketer (specifically a Digital Marketer) your job is not to prove the operational or fulfillment side of your company wrong by providing so much activity it proves fundamental flaws in the systems, but rather to ensure the activity you are creating is educated, nurtured and that the internal operational systems are in place to support the operational side of your organization so that it can quickly pivot and learn from the data your activity creates. A marketer has to be able to market externally, but also systematically utilize that data to change strategies when and if needed internally. How and what to do with the activity's data is a responsibility that falls with production\fulfillment AND marketing\sales. "I brought you 1,000 inbound leads it's not my fault we couldn't fulfill them" is no longer acceptable.

Specific Architectural Topics Is the overall organization of the program clear, including a good architectural overview and justification? Are major building blocks well defined, including their areas of responsibility and their interfaces to other building blocks? Are all the functions listed in the requirements covered sensibly, by neither too many nor too few building blocks? Are the most critical classes described and justified? Is the data design described and justified? Is the database organization and content specified? Are all key business rules identified and their impact on the system described? Is a strategy for the user interface design described? Is the user interface modularized so that changes in it won’t affect the rest of the program? Is a strategy for handling I/O described and justified? Are resource-use estimates and a strategy for resource management described and justified for scarce resources like threads, database connections, handles, network bandwidth, and so on? Are the architecture’s security requirements described? Does the architecture set space and speed budgets for each class, subsystem, or functionality area? Does the architecture describe how scalability will be achieved? Does the architecture address interoperability? Is a strategy for internationalization/localization described? Is a coherent error-handling strategy provided? Is the approach to fault tolerance defined (if any is needed)? Has technical feasibility of all parts of the system been established? Is an approach to overengineering specified? Are necessary buy-vs.-build decisions included? Does the architecture describe how reused code will be made to conform to other architectural objectives? Is the architecture designed to accommodate likely changes? General Architectural Quality Does the architecture account for all the requirements? Is any part overarchitected or underarchitected? Are expectations in this area set out explicitly? Does the whole architecture hang together conceptually? Is the top-level design independent of the machine and language that will be used to implement it? Are the motivations for all major decisions provided? Are you, as a programmer who will implement the system, comfortable with the architecture?