So we've boiled it down for you. Regard your soldiers as your children, and they will follow you into the deepest valleys; look upon them as your own beloved sons, and they will stand by you even unto death.
If, however, you are indulgent, but unable to make your authority felt; kind-hearted, but unable to enforce your commands; and incapable, moreover, of quelling disorder: then your soldiers must be likened to spoilt children; they are useless for any practical purpose. When the general is weak and without authority; when his orders are not clear and distinct; when there are no fixed duties assigned to officers and men, and the ranks are formed in a slovenly haphazard manner, the result is utter disorganization.
When the common soldiers are too strong and their officers too weak, the result is insubordination. When the officers are too strong and the common soldiers too weak, the result is collapse.
When the higher officers are angry and insubordinate, and on meeting the enemy give battle on their own account from a feeling of resentment, before the commander-in-chief can tell whether or not he is in a position to fight, the result is ruin. If we know that our own men are in a condition to attack, but are unaware that the enemy is not open to attack, we have gone only halfway towards victory.
blacksmithsurgical.com/t3-assets/in/vixo-matthew-as-story.php In your deliberations, when seeking to determine the military conditions, let them be made the basis of a comparison, in this wise Move not unless you see an advantage; use not your troops unless there is something to be gained; fight not unless the position is critical. Hold out baits to entice the enemy. Feign disorder, and crush him. Though we have heard of stupid haste in war, cleverness has never been seen associated with long delays.
There is no instance of a country having benefited from prolonged warfare. The quality of decision is like the well-timed swoop of a falcon which enables it to strike and destroy its victim. Therefore the good fighter will be terrible in his onset, and prompt in his decision.
Whoever is first in the field and awaits the coming of the enemy, will be fresh for the fight; whoever is second in the field and has to hasten to battle will arrive exhausted Rapidity is the essence of war: take advantage of the enemy's unreadiness, make your way by unexpected routes, and attack unguarded spots. If your opponent is of choleric temper, seek to irritate him. Pretend to be weak, that he may grow arrogant.
Attack him where he is unprepared, appear where you are not expected. If we wish to fight, the enemy can be forced to an engagement even though he be sheltered behind a high rampart and a deep ditch. All we need do is attack some other place that he will be obliged to relieve. So in war, the way is to avoid what is strong and to strike at what is weak. Carefully study the well-being of your men, and do not overtax them.
Concentrate your energy and hoard your strength. Keep your army continually on the move, and devise unfathomable plans. The skillful tactician may be likened to the shuai-jan. Now the shuai-jan is a snake that is found in the Ch'ang mountains. Strike at its head, and you will be attacked by its tail; strike at its tail, and you will be attacked by its head; strike at its middle, and you will be attacked by head and tail both. We cannot enter into alliance with neighbouring princes until we are acquainted with their designs. We are not fit to lead an army on the march unless we are familiar with the face of the country - its mountains and forests, its pitfalls and precipices, its marshes and swamps.
We shall be unable to turn natural advantages to account unless we make use of local guides. Hence the saying: The enlightened ruler lays his plans well ahead; the good general cultivates his resources. No ruler should put troops into the field merely to gratify his own spleen; no general should fight a battle simply out of pique. What enables the wise sovereign and the good general to strike and conquer, and achieve things beyond the reach of ordinary men, is foreknowledge. Now this foreknowledge cannot be elicited from spirits; it cannot be obtained inductively from experience, nor by any deductive calculation.
Knowledge of the enemy's dispositions can only be obtained from other men. They [spies] cannot be properly managed without benevolence and straightforwardness. Without subtle ingenuity of mind, one cannot make certain of the truth of their reports. However, the divide and conquer rule is not the only political strategy that can be applied to software development.
Although politics and warfare have little to do with software development, just like politicians and generals, developers must lead subordinates, coordinate efforts between teams, find the best strategies to resolve problems, and administer resources. The Art of War is an ancient military treatise written in the fifth century B. The text is divided into 13 chapters, each one devoted to a different aspect of warfare. In fact, you might just be applying some of these principles in your daily routine, without even knowing their origins.
Detailed below, you will a find a brief list of basic tactics and tips explained in the Art of War. They can probably be applied to your job in the software industry, or any of a number of other industries.
If a group of developers work on the same projects for months, with no clear goals or end in sight, they may become frustrated and their productivity may decline. Software development is an intellectual endeavour, so motivation is the main fuel for productivity. Working every day without perceiving that your work is generating real results can be very demotivating. As indicated in some agile methodologies , the development roadmap should be divided into several goals and milestones, which the team might be able to achieve in short timeframes, and they are going to give them a sense of progress and achievement.
First, it can be seen as a precursor of the UNIX philosophy: Write programs that do one thing and do it well. When developing software, you must always keep in mind the main objective of the program, the key feature that it provides, or the biggest problem that it solves, and ensure proper implementation.
Sometimes you might get inspired and think of a really cool feature to add, but do not forget that applications that have lot of infrequently used features have a disparaging name: bloatware. Second, the statement may also be considered as a precursor for one of the lean software development principles: Deliver as fast as possible. The sooner you deliver software without major defects, the sooner you will get feedback from the client, and you will be able to incorporate the changes into the next iteration.
This will make the next stage of development more difficult, or impossible in situations where your next iteration depends on customer feedback. Now the general is the bulwark of the State; if the bulwark is complete at all points, the State will be strong; if the bulwark is defective, the State will be weak.
This quote describes the importance of the role of the manager in a development team: the success of a project depends on the strength of all people involved, and the manager is the bulwark of the project. Responsibility starts at the top. Project managers are in charge of keeping the team on track, ensuring effective communication and dispute resolution, and leaders, obviously, define the priorities of the project among other tasks , so their role should not be underestimated. Neither should their responsibility if something goes wrong. Imagine what would happen to a military leader whose unit failed to perform its duty in the field of battle?
Do not repeat the tactics which have gained you one victory, but let your methods be regulated by the infinite variety of circumstances. However, unless the requirements of the new projects are exactly the same as previous ones, this might be the wrong approach. In programming, as in most domains, the panacea a supposed remedy capable of curing all diseases does not exist.
There is no single combination of technologies that you can use for solving all problems; each technology has its upsides and downsides. Of course, learning a new programming language or using an unknown API might initially be expensive but in the long term, the quality of the software will be superior and you will become a better developer. Hence it is only the enlightened ruler and the wise general who will use the highest intelligence of the army for purposes of spying, and thereby they achieve great results. This phrase may be interpreted as the importance of using monitoring tools and logging libraries during the maintenance phase.
Although sometimes clients might not think so, development does not end when you get a stable and fully tested release. Software is always evolving, either by fixing bugs, adding new features or improving efficiency. And there is no better source of information for knowing what changes to make than having spies monitoring the software in production environments, checking which features are used the most, the most common errors and the lengthiest operations.
Error reports, logging entries and usage data are fundamental for detecting bugs, identifying bottlenecks and other issues since it is not always possible to reproduce the same conditions in controlled testing environments. He who advances without seeking fame, Who retreats without escaping blame, He whose one aim is to protect his people and serve his lord, The man is a jewel of the Realm.
It is more important to work together with others rather than to pursue personal gain. Software development is a complex activity that requires developers to work effectively as a team. A good developer is not the one who fixes the most bugs, implements the most features or finishes assignments ahead of schedule; a good developer is the one who helps the team reach its goals. This phrase indicates the importance of team development meetings, such as those proposed by agile methodologies. When working on a team, it is important to discuss any major changes before implementing them.
Remember that other developers could give you insights into unfamiliar parts the software. This means they could start implementing the changes faster than expected, because they could be fully aware of the effects of said changes. Regard your soldiers as your children, and they will follow you into the deepest valleys; look upon them as your own beloved sons, and they will stand by you even unto death.