I enjoy dissent and debate among commenters, and criticism of my views is also always welcome; you are even free to call me an assclown, a dupe, a partisan ignoramus — whatever you like, as long as you don't insult other commenters.

I've been meaning to remind readers that I do read the comments. Some time ago, one disappointed commenter mused that others' reflections seemed to go (as I recall) "into a void," because I remained silent to each. Perhaps I was ignoring readers' remarks? I assure you that is not the case. I read them all — although on this site, for some reason, "all" means somewhat sparse — and I find them nearly all remarkable in their perceptiveness. I especially welcome, and enjoy, intelligent disagreement. I choose not to respond, however, only because of my editorial philosophy, which holds that the comment section is, rightfully, for commenters — and commenters alone. I've already had my say, and it seems to me rather rude to take another whack in reply. Whenever I'm so substantively shaky or incoherent as to make my case unpersuasively the first time around, I figure I should live with the consequences. And whenever I find criticism flawed, I figure readers — perceptive as they are — will see the flaw as well, therefore there's no need for me to rub it in. So, I beg you not to take my silence personally.

We believe great companies sound negative because they focus on what they can improve, not on what is working. Our first question in every conversation with someone outside the company should be: what do you think we can improve?

Yes, traditional scenario load tests are naturally in the risk zone of being axed in the name of this-step-is-taking-too-long as load tests need time to ramp-up and execute the user journeys with the simulated traffic to gain enough measurements that can be acted on. This is why we don’t recommend load tests to be run on every commit for scenario type load tests, but rather in the frequency range of “daily” for performance regression type tests. When merging code into a release branch or as a nightly build perhaps, so that you can have your snazzy load test report with your morning coffee before you’ve settled into your zone!

An ssh public key in a ~/.ssh/authorized_keys file can have a command="" option which forces a particular command to be executed when the key is used to authenticate an ssh connection. This is a security control that mitigates against private key compromise. This is great when you only need to execute a single command. But if you need to perform multiple tasks, you would normally need to create and install a separate key pair for each command, or just not bother making use of forced commands and allow the key to be used to execute any command.

from="<ip>",command="/usr/local/sbin/validate-rsync" ssh-dss AAAAZ5Hbl......

echo "from="${MYIP%% *}",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty,command="rsync ${SSH_ORIGINAL_COMMAND#* }" $(ssh-keygen -yf ~/.ssh/rsync_rsa)" | ssh targetserver "cat - >>~/.ssh/authorized_keys" Note that the ‘command=’ restriction (http://larstobi.blogspot.ch/2011/01/restrict-ssh-access-to-one-command-but.html) will not apply if ‘/etc/sshd_config’ has already a ‘ForceCommand’ directive.

No backup regimen would be complete without testing. You should regularly test recovery of random files or entire directory structures to ensure not only that the backups are working, but that the data in the backups can be recovered for use after a disaster. I have seen too many instances where a backup could not be restored for one reason or another and valuable data was lost because the lack of testing prevented discovery of the problem.

The x mark is also sometimes used for this purpose (most notably on election ballot papers, e.g. in the United Kingdom), but otherwise usually indicates "no", incorrectness, or failure.

PortfolioWhat you can learn from me.

Managing and maintaining the privacy and security of your digital identity through behaviors and digital tool settings

But I can write when she is out, and see her a long way off from these windows.

The better a designer understands his or her audience and the unique needs of that particular audience, the more efficiently and effectively he or she will be able to develop, design, implement, and evaluate instructional materials in a rapid format. 

There are no audits matching your search

In conformity with the principles of our constitution, which places all sects of religion on an equal footing, with the jealousies of the different sects in guarding that equality from encroachment & surprise, and with the sentiments of the legislature in favor of freedom of religion manifested on former occasions, we have proposed no professor of Divinity

The objects of this primary education determine its character & limits. These objects would be, To give to every citizen the information he needs for the transaction of his own business. To enable him to calculate for himself, and to express & preserve his ideas, his contracts & accounts in writing. To improve by reading, his morals and faculties. To understand his duties to his neighbours, & country, and to discharge with competence the functions confided to him by either. To know his rights; to exercise with order & justice those he retains; to choose with discretion the fiduciaries of those he delegates; and to notice their conduct with diligence with candor & judgment. And, in general, to observe with intelligence & faithfulness all the social relations under which he shall be placed.

This doctrine is the genuine fruit of the alliance between church and State

Some of these have rendered the elements themselves subservient to the purposes of man

an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.