A 58k text-only version is available for download. Apology Translated by Benjamin Jowett Socrates' Defense How you have felt, O men of Athens, at hearing the speeches of my accusers, I cannot tell; but I know that their persuasive words almost made me forget who I was - such was the effect of them; and yet they have hardly spoken a word of truth. But many as their falsehoods were, there was one of them which quite amazed me; - I mean when they told you to be upon your guard, and not to let yourselves be deceived by the force of my eloquence. They ought to have been ashamed of saying this, because they were sure to be detected as soon as I opened my lips and displayed my deficiency; they certainly did appear to be most shameless in saying this, unless by the force of eloquence they mean the force of truth; for then I do indeed admit that I am eloquent.
Further Reading I vividly remember one of my first sightings of a large software project. I was taking a summer internship at a large English electronics company. My manager, part of the QA group, gave me a tour of a site and we entered a huge depressing warehouse stacked full with cubes.
I was told that this project had been in development for a couple of years and was currently integrating, and had been integrating for several months. My guide told me that nobody really knew how long it would take to finish integrating.
From this I learned a common story of software projects: But this needn't be the way. Most projects done by my colleagues at ThoughtWorks, and by many others around the world, treat integration as a non-event. Any individual developer's work is only a few hours away from a shared project state and can be integrated back into that state in minutes.
Any integration errors are found rapidly and can be fixed rapidly. This contrast isn't the result of an expensive and complex tool. The essence of it lies in the simple practice of everyone on the team integrating frequently, usually daily, against a controlled source code repository.
The original article on Continuous Integration describes our experiences as Matt helped put together continuous integration on a ThoughtWorks project in When I've described this practice to people, I commonly find two reactions: What people find out as they try it is that it's much easier than it sounds, and that it makes a huge difference to development.
Thus the third common reaction is "yes we do that - how could you live without it?
When I started at ThoughtWorks, as a consultant, I encouraged the project I was working with to use the technique. Matthew Foemmel turned my vague exhortations into solid action and we saw the project go from rare and complex integrations to the non-event I described. Matthew and I wrote up our experience in the original version of this paper, which has been one of the most popular papers on my site.
Although Continuous Integration is a practice that requires no particular tooling to deploy, we've found that it is useful to use a Continuous Integration server. The best known such server is CruiseControl, an open source tool originally built by several people at ThoughtWorks and now maintained by a wide community.
Since then several other CI servers have appeared, both open source and commercial - including Cruise from ThoughtWorks Studios. Building a Feature with Continuous Integration The easiest way for me to explain what CI is and how it works is to show a quick example of how it works with the development of a small feature.
Let's assume I have to do something to a piece of software, it doesn't really matter what the task is, for the moment I'll assume it's small and can be done in a few hours.
We'll explore longer tasks, and other issues later on. I begin by taking a copy of the current integrated source onto my local development machine.
I do this by using a source code management system by checking out a working copy from the mainline. The above paragraph will make sense to people who use source code control systems, but be gibberish to those who don't.
So let me quickly explain that for the latter. A source code control system keeps all of a project's source code in a repository. The current state of the system is usually referred to as the 'mainline'.
At any time a developer can make a controlled copy of the mainline onto their own machine, this is called 'checking out'. The copy on the developer's machine is called a 'working copy'. Most of the time you actually update your working copy to the mainline - in practice it's the same thing. Now I take my working copy and do whatever I need to do to complete my task.In religion, ethics, philosophy, and psychology "good and evil" is a very common rutadeltambor.com cultures with Manichaean and Abrahamic religious influence, evil is usually perceived as the dualistic antagonistic opposite of good, in which good should prevail and evil should be defeated.
In cultures with Buddhist spiritual influence, both good and evil are perceived as part of an antagonistic. Students strive hard to get good grades at colleges and universities. They spent immense time on the strenuous task of finding proper authentic sources and references for completing their coursework paper.
Sep 06, · Expert Reviewed. How to Introduce Yourself. Five Methods: Introduction Help Introducing Yourself in Any Social Situation Introducing Yourself to an Individual Introducing Yourself Before Giving a Speech Introducing Yourself at a Professional Event Community Q&A Introducing yourself is much more than saying your name; it’s a way to connect with someone new by exchanging 75%(41).
The Part 1 question will be an essay on a given topic. A set of notes on the topic will be provided, and will include three bullet points. Candidates will be asked to select two of the bullet points and to base their essay on those two points.
Be Able to Introduce Yourself By Lindsey Pollak “So, tell me about yourself.” This may just be the most common, and the most intimidating, phrase you’ll hear during your job. May (This essay was originally published in Hackers & Painters.) If you wanted to get rich, how would you do it?
I think your best bet would be to start or join a startup.