Cheap Viagra Information | Search results for "conference"

  Scrums are the most dangerous phase in rugby, since a collapse or improper engage can lead to a front row player damaging or even breaking his neck. — Wikipedia When I was growing up, cholesterol used to be bad for you. It was easy to remember. Fat, bad. Cholesterol bad. Salt, bad. Everything, bad. Nowadays, though, they differentiate between "good" cholesterol and "bad" cholesterol, as if we're supposed to be able to distinguish them somehow. And it was weird when they switched it up on us, because it was as if the FDA had suddenly issued a press release announcing that there are, in fact, two kinds of rat poison: Good Rat Poison and Bad Rat Poison, and you should eat a lot of the Good kind, and none of the Bad kind, and definitely not mix them up or anything. Up until maybe a year ago, I had a pretty one-dimensional view of so-called "Agile" programming, namely that it's an idiotic fad-diet of a marketing scam making the rounds as yet another technological virus implanting itself in naive programmers who've never read "No Silver Bullet", the kinds of programmers who buy extended warranties and self-help books and believe their bosses genuinely care about them as people, the kinds of programmers who attend conferences to make friends and who don't know how to avoid eye contact with leaflet-waving fanatics in airports and who believe writing shit on index cards will suddenly make software development easier. You know. Chumps. That's the word I'm looking for. My bad-cholesterol view was that Agile Methodologies are for chumps. But I've had a lot of opportunity to observe various flavors of Agile-ism in action lately, and I now think I was only about 90% right. It turns out there's a good kind of Agile, although it's taken me a long time to be able to see it clearly amidst all the hype and kowtowing and moaning feverishly about scrums and whatnot. I have a pretty clear picture of it now. And you can attend my seminar on it for the low, low price of $499.95! Hahaha, chump! No, just kidding. You'll only find seminars about the Bad kind of Agile. And if in the future you ever find me touring around as an Agile Consultant, charging audiences to hear my deep wisdom and insight about Agile Development, you have my permission to cut my balls off. If I say I was just kidding, say I told you I'd say that. If I then say I'm Tyler Durden and I order you not to cut my balls off , say I definitely said I was going to say that , and then you cut 'em right off. I'll just go right ahead and tell you about the Good Kind, free of charge. It's kinda hard to talk about Good Agile and Bad Agile in isolation, so I might talk about them together. But I'll be sure to label the Good kind with a happy rat, and the Bad kind with a sad dead rat, so you'll always know the difference. The Bad Heading Back in Ye Olden Dayes, most companies approached software development as follows: - hire a bunch of engineers, then hire more. - dream up a project. - set a date for when they want it launched. - put some engineers on it. - whip them until they're either dead or it's launched. or both. - throw a cheap-ass pathetic little party, maybe. This step is optional. - then start over. Thank goodness that doesn't happen at your company, eh now? Whew! Interestingly, this is also exactly how non-technical companies (like, say, Chrysler) handled software development. Except they didn't hire the engineers. Instead, they contracted with software consultants, and they'd hand the consultants 2-year project specs, and demanded the consultants finish everything on time plus all the crap the customer threw in and/or changed after signing the contract. And then it'd all fall apart and the contractors wouldn't get paid, and everyone was really miffed. So some of the consultants began to think: "Hey, if these companies insist on acting like infants, then we should treat them like infants!" And so they did. When a company said "we want features A through Z", the consultants would get these big index cards and write "A" on the first one, "B" on the second one, etc., along with time estimates, and then post them on their wall. Then when the customer wanted to add something, the consultant could point at the wall and say: "OK, boy . Which one of these cards do you want to replace , BOY? " Is it any wonder Chrysler canceled the project? So the consultants, now having lost their primary customer, were at a bar one day, and one of them (named L. Ron Hubbard) said: "This nickel-a-line-of-code gig is lame. You know where the real money is at? You start your own religion." And that's how both Extreme Programming and Scientology were born. Well, people pretty quickly demonstrated that XP was a load of crap. Take Pair Programming, for instance. It's one of the more spectacular failures of XP. None of the Agileytes likes to talk about it much, but let's face it: nobody does it. The rationale was something like: "well if ONE programmer sitting at a terminal is good, then TEN must be better, because MORE is ALWAYS better! But most terminals can only comfortably fit TWO programmers, so we'll call it PAIR programming!" You have to cut them a little slack; they'd been dealing with the corporate equivalent of pre-schoolers for years, and that really messes with a person. But the thing is, viruses are really hard to kill, especially the meme kind. After everyone had gotten all worked up about this whole Agile thing (and sure, everyone wants to be more productive), there was a lot of face to be lost by admitting failure. So some other kinds of Agile "Methodologies" sprang up, and they all claimed that even though all the other ones were busted, their method worked! I mean, go look at some of their sites. Tell me that's not an infomercial. C'mon, just try. It's embarrassing even to look at the thing. Yeah. Well, they make money hand over fist, because of P.T. Barnum's Law, just like Scientology does. Can't really fault 'em. Some people are just dying to be parted with their cash. And their dignity. The rest of us have all known that Agile Methodologies are stupid, by application of any of the following well-known laws of marketing: - anything that calls itself a "Methodology" is stupid, on general principle. - anything that requires "evangelists" and offers seminars, exists soley for the purpose of making money. - anything that never mentions any competition or alternatives is dubiously self-serving. - anything that does diagrams with hand-wavy math is stupid, on general principle. And by "stupid", I mean it's "incredibly brilliant marketing targeted at stupid people." In any case, the consultants kept going with their road shows and glossy pamphlets. Initially, I'm sure they went after corporations; they were looking to sign flexible contracts that allowed them to deliver "whatever" in "2 weeks" on a recurring basis until the client went bankrupt. But I'm equally sure they couldn't find many clients dumb enough to sign such a contract. That's when the consultants decided to take their road show to YOU. Why not take it inside the companies and sell it there, to the developers? There are plenty of companies who use the whip-cycle of development I outlined above, so presumably some of the middle managers and tech leads would be amenable to hearing about how there's this low-cost way out of their hellish existence. And that, friends, was exactly, precisely the point at which they went from "harmless buffoons" to "potentially dangerous", because before they were just bilking fat companies too stupid to develop their own software, but now the manager down the hall from me might get infected. And most places don't have a very good quarantine mechanism for this rather awkward situation: i.e., an otherwise smart manager has become "ill", and is waving XP books and index cards and spouting stuff about how much more productive his team is on account of all this newfound extra bureaucracy. How do we know it's not more productive? Well, it's a slippery problem. Observe that it must be a slippery problem, or it all would have been debunked fair and square by now. But it's exceptionally difficult to measure software developer productivity, for all sorts of famous reasons. And it's even harder to perform anything resembling a valid scientific experiment in software development. You can't have the same team do the same project twice; a bunch of stuff changes the second time around. You can't have 2 teams do the same project; it's too hard to control all the variables, and it's prohibitively expensive to try it in any case. The same team doing 2 different projects in a row isn't an experiment either. About the best you can do is gather statistical data across a lot of teams doing a lot of projects, and try to identify similarities, and perform some regressions, and hope you find some meaningful correlations. But where does the data come from? Companies aren't going to give you their internal data, if they even keep that kind of thing around. Most don't; they cover up their schedule failures and they move on, ever optimistic. Well if you can't do experiments and you can't do proofs, there isn't much science going on. That's why it's a slippery problem. It's why fad diets are still enormously popular. People want fad diets to work, oh boy you bet they do, even I want them to work. And you can point to all these statistically meaningless anecdotes about how Joe lost 35 pounds on this one diet, and all those people who desperately want to be thinner will think "hey, it can't hurt. I'll give it a try." That is exactly what I hear people say, every time a team talks themselves into trying an Agile Methodology. It's not a coincidence. But writing about Bad Agile alone is almost guaranteed to be ineffective. I mean, you can write about how lame Scientology is, or how lame fad diets are, but it's not clear that you're changing anyone's mind. Quitting a viral meme is harder than quitting smoking. I've done both. In order to have the right impact, you have to offer an alternative, and I didn't have one before, not one that I could articulate clearly. One of the (many) problems with Bad Agile is that they condescendingly lump all non-Agile development practices together into two buckets: Waterfall and Cowboy. Waterfall is known to be bad; I hope we can just take that as an axiom today. But what about so-called Cowboy programming, which the Agileers define as "each member of the team does what he or she thinks is best"? Is it true that this is the only other development process? And is Cowboy Programming actually bad? They say it as if it's obviously bad, but they're not super clear on how or why, other than to assert that it's, you know, "chaos". Well, as I mentioned, over the past year I've had the opportunity to watch both Bad Agile and Good Agile in motion, and I've asked the teams and tech leads (using both the Bad and Good forms) lots of questions: how they're doing, how they're feeling, how their process is working. I was really curious, in part because I'd consented to try Agile last Christmas ("hey, it can't hurt"), and wound up arguing with a teammate over exactly what metadata is allowed on index cards before giving up in disgust. Also in part because I had some friends on a team who were getting kind of exhausted from what appeared to be a Death March, and that kind of thing doesn't seem to happen very often at Google. So I dug in, and for a year, I watched and learned. The Good Head (cue happy rat) I'm going to talk a little about Google's software development process. It's not the whole picture, of course, but it should suffice for today. I've been there for almost a year and a half now, and it took a while, but I think I get it now. Mostly. I'm still learning. But I'll share what I've got so far. From a high level, Google's process probably does look like chaos to someone from a more traditional software development company. As a newcomer, some of the things that leap out at you include: - there are managers, sort of, but most of them code at least half-time, making them more like tech leads. - developers can switch teams and/or projects any time they want, no questions asked; just say the word and the movers will show up the next day to put you in your new office with your new team. - Google has a philosophy of not ever telling developers what to work on, and they take it pretty seriously. - developers are strongly encouraged to spend 20% of their time (and I mean their M-F, 8-5 time, not weekends or personal time) working on whatever they want, as long as it's not their main project. - there aren't very many meetings. I'd say an average developer attends perhaps 3 meetings a week, including their 1:1 with their lead. - it's quiet. Engineers are quietly focused on their work, as individuals or sometimes in little groups or 2 to 5. - there aren't Gantt charts or date-task-owner spreadsheets or any other visible project-management artifacts in evidence, not that I've ever seen. - even during the relatively rare crunch periods, people still go get lunch and dinner, which are (famously) always free and tasty, and they don't work insane hours unless they want to. These are generalizations, sure. Old-timers will no doubt have a slightly different view, just as my view of Amazon is slightly biased by having been there in 1998 when it was a pretty crazy place. But I think most Googlers would agree that my generalizations here are pretty accurate. How could this ever work? I get that question a lot. Heck, I asked it myself. What's to stop engineers from leaving all the trouble projects, leaving behind bug-ridden operational nightmares? What keeps engineers working towards the corporate goals if they can work on whatever they want? How do the most important projects get staffed appropriately? How do engineers not get so fat that they routinely get stuck in stairwells and have to be cut out by the Fire Department? I'll answer the latter question briefly, then get to the others. In short: we have this thing called the Noogler Fifteen, named after the Frosh Fifteen: the 15 pounds that many college freshmen put on when they arrive in the land of Stress and Pizza. Google has solved the problem by lubricating the stairwells. As to the rest of your questions, I think most of them have the same small number of answers. First, and arguably most importantly, Google drives behavior through incentives. Engineers working on important projects are, on average, rewarded more than those on less-important projects. You can choose to work on a far-fetched research-y kind of project that may never be practical to anyone, but the work will have to be a reward unto itself. If it turns out you were right and everyone else was wrong (the startup's dream), and your little project turns out to be tremendously impactful, then you'll be rewarded for it. Guaranteed. The rewards and incentives are too numerous to talk about here, but the financial incentives range from gift certificates and massage coupons up through giant bonuses and stock grants, where I won't define "giant" precisely, but think of Google's scale and let your imagination run a bit wild, and you probably won't miss the mark by much. There are other incentives. One is that Google a peer-review oriented culture, and earning the respect of your peers means a lot there. More than it does at other places, I think. This is in part because it's just the way the culture works; it's something that was put in place early on and has managed to become habitual. It's also true because your peers are so damn smart that earning their respect is a huge deal. And it's true because your actual performance review is almost entirely based on your peer reviews, so it has an indirect financial impact on you. Another incentive is that every quarter, without fail, they have a long all-hands in which they show every single project that launched to everyone, and put up the names and faces of the teams (always small) who launched each one, and everyone applauds. Gives me a tingle just to think about it. Google takes launching very seriously, and I think that being recognized for launching something cool might be the strongest incentive across the company. At least it feels that way to me. And there are still other incentives; the list goes on and ON and ON ; the perks are over the top, and the rewards are over the top, and everything there is so comically over the top that you have no choice, as an outsider, but to assume that everything the recruiter is telling you is a baldfaced lie, because there's no possible way a company could be that generous to all of its employees, all of them, I mean even the contractors who clean the micro-kitchens, they get these totally awesome "Google Micro-Kitchen Staff" shirts and fleeces. There is nothing like it on the face of this earth. I could talk for hours , days about how amazing it is to work at Google, and I wouldn't be done. And they're not done either. Every week it seems like there's a new perk, a new benefit, a new improvement, a new survey asking us all if there's any possible way in which life at Google could be better. I might have been mistaken, actually. Having your name and picture up on that big screen at End of Quarter may not be the biggest incentive. The thing that drives the right behavior at Google, more than anything else, more than all the other things combined, is gratitude . You can't help but want to do your absolute best for Google; you feel like you owe it to them for taking such incredibly good care of you. OK, incentives. You've got the idea. Sort of. I mean, you have a sketch of it. When friends who aren't at Google ask me how it is working at Google — and this applies to all my friends at all other companies equally, not just companies I've worked at — I feel just how you'd feel if you'd just gotten out of prison, and your prison buddies, all of whom were sentenced in their early teens, are writing to you and asking you what it's like "on the outside". I mean, what would you tell them? I tell 'em it's not too bad at all. Can't complain. Pretty decent, all in all. Although the incentive-based culture is a huge factor in making things work the way they do, it only addresses how to get engineers to work on the "right" things. It doesn't address how to get those things done efficiently and effectively. So I'll tell you a little about how they approach projects. Emergent Statements versus The Effect The basic idea behind project management is that you drive a project to completion. It's an overt process, a shepherding: by dint of leadership, and organization, and sheer force of will, you cause something to happen that wouldn't otherwise have happened on its own. Project management comes in many flavors, from lightweight to heavyweight, but all flavors share the property that they are external forces acting on an organization. At Google, projects launch because it's the least-energy state for the system. Before I go on, I'll concede that this is a pretty bold claim, and that it's not entirely true. We do have project managers and product managers and people managers and tech leads and so on. But the amount of energy they need to add to the system is far less than what's typically needed in our industry. It's more of an occasional nudge than a full-fledged continuous push. Once in a while, a team needs a bigger nudge, and senior management needs to come in and do the nudging, just like anywhere else. But there's no pushing. Incidentally, Google is a polite company, so there's no yelling, nor wailing and gnashing of teeth, nor escalation and finger-pointing, nor any of the artifacts produced at companies where senior management yells a lot. Hobbes tells us that organizations reflect their leaders; we all know that. The folks up top at Google are polite, hence so is everyone else. Anyway, I claimed that launching projects is the natural state that Google's internal ecosystem tends towards, and it's because they pump so much energy into pointing people in that direction. All your needs are taken care of so that you can focus, and as I've described, there are lots of incentives for focusing on things that Google likes. So launches become an emergent property of the system. This eliminates the need for a bunch of standard project management ideas and methods: all the ones concerned with dealing with slackers, calling bluffs on estimates, forcing people to come to consensus on shared design issues, and so on. You don't need "war team meetings," and you don't need status reports. You don't need them because people are already incented to do the right things and to work together well. The project management techniques that Google does use are more like oil than fuel: things to let the project keep running smoothly, as opposed to things that force the project to move forward. There are plenty of meeting rooms, and there's plenty of open space for people to go chat. Teams are always situated close together in fishbowl-style open seating, so that pair programming happens exactly when it's needed (say 5% of the time), and never otherwise. Google generally recognizes that the middle of the day is prone to interruptions, even at quiet companies, so many engineers are likely to shift their hours and come in very early or stay very late in order to find time to truly concentrate on programming. So meetings only happen in the middle of the day; it's very unusual to see a meeting start before 10am or after 4:30pm. Scheduling meetings outside that band necessarily eats into the time when engineers are actually trying to implement the things they're meeting about, so they don't do it. Google isn't the only place where projects are run this way. Two other kinds of organizations leap to mind when you think of Google's approach: startup companies, and grad schools. Google can be considered a fusion of the startup and grad-school mentalities: on the one hand, it's a hurry-up, let's get something out now, do the simplest thing that could work and we'll grow it later startup-style approach. On the other, it's relatively relaxed and low-key; we have hard problems to solve that nobody else has ever solved, but it's a marathon not a sprint, and focusing requires deep concentration, not frenzied meetings. And at the intersection of the two, startups and grad schools are both fertile innovation ground in which the participants carry a great deal of individual responsibility for the outcome. It's all been done before; the only thing that's really surprising is that Google has managed to make it scale. The scaling is not an accident. Google works really hard on the problem, and they realize that having scaled this far is no guarantee it'll continue, so they're vigilant. That's a good word for it. They're always on the lookout to make sure the way of life and the overall level of productivity continue (or even improve) as they grow. Google is an exceptionally disciplined company, from a software-engineering perspective. They take things like unit testing, design documents and code reviews more seriously than any other company I've even heard about. They work hard to keep their house in order at all times, and there are strict rules and guidelines in place that prevent engineers and teams from doing things their own way. The result: the whole code base looks the same, so switching teams and sharing code are both far easier than they are at other places. And engineers need great tools, of course, so Google hires great people to build their tools, and they encourage engineers (using incentives) to pitch in on tools work whenever they have an inclination in that direction. The result: Google has great tools, world-class tools, and they just keep getting better. The list goes on. I could talk for days about the amazing rigor behind Google's approach to software engineering. But the main takeaway is that their scaling (both technological and organizational) is not an accident. And once you're up to speed on the Google way of doing things, it all proceeds fairly effortlessly — again, on average, and compared to software development at many other companies. The Tyranny of the Vocabulary We're almost done. The last thing I want to talk about here is dates . Traditional software development can safely be called Date-Oriented Programming, almost without exception. Startup companies have a clock set by their investors and their budget. Big clients set target dates for their consultants. Sales people and product managers set target dates based on their evaluation of market conditions. Engineers set dates based on estimates of previous work that seems similar. All estimation is done through rose-colored glasses, and everyone forgets just how painful it was the last time around. Everyone picks dates out of the air. "This feels like it should take about 3 weeks.""It sure would be nice to have this available for customers by beginning of Q4.""Let's try to have that done by tomorrow." Most of us in our industry are date-driven. There's always a next milestone, always a deadline, always some date-driven goal to it. The only exceptions I can think of to this rule are: 1) Open-source software projects. 2) Grad school projects. 3) Google. Most people take it for granted that you want to pick a date. Even my favorite book on software project management, "The Mythical Man-Month", assumes that you need schedule estimates. If you're in the habit of pre-announcing your software, then the general public usually wants a timeframe, which implies a date. This is, I think, one of the reasons Google tends not to pre-announce. They really do understand that you can't rush good cooking, you can't rush babies out, and you can't rush software development. If the three exceptions I listed above aren't driven by dates, then what drives them? To some extent it's just the creative urge, the desire to produce things; all good engineers have it. (There are many people in our industry who do this gig "for a living", and they go home and don't think about it until the next day. Open source software exists precisely because there are people who are better than that.) But let's be careful: it's not just the creative urge; that's not always directed enough, and it's not always incentive enough. Google is unquestionably driven by time , in the sense that they want things done "as fast as possible". They have many fierce, brilliant competitors, and they have to slake their thirsty investors' need for growth, and each of us has some long-term plans and deliverables we'd like to see come to fruition in our lifetimes. The difference is that Google isn't foolish enough or presumptuous enough to claim to know how long stuff should take. So the only company-wide dates I'm ever aware of are the ends of each quarter, because everyone's scrambling to get on that big launch screen and get the applause and gifts and bonuses and team trips and all the other good that comes of launching things with big impact at Google. Everything in between is just a continuum of days, in which everyone works at optimal productivity, which is different for each person. We all have work-life balance choices to make, and Google is a place where any reasonable choice you make can be accommodated, and can be rewarding. Optimal productivity is also a function of training, and Google offers tons of it, including dozens of tech talks every week by internal and external speakers, all of which are archived permanently so you can view them whenever you like. Google gives you access to any resources you need in order to get your job done, or to learn how to get your job done. And optimal productivity is partly a function of the machine and context in which you're operating: the quality of your code base, your tools, your documentation, your computing platform, your teammates, even the quality of the time you have during the day, which should be food-filled and largely free of interrupts. Then all you need is a work queue. That's it. You want hand-wavy math? I've got it in abundance: software development modeled on queuing theory. Not too far off the mark, though; many folks in our industry have noticed that organizational models are a lot like software models. With nothing more than a work queue (a priority queue, of course), you immediately attain most of the supposedly magical benefits of Agile Methodologies. And make no mistake, it's better to have it in software than on a bunch of index cards. If you're not convinced, then I will steal your index cards. With a priority queue, you have a dumping-ground for any and all ideas (and bugs) that people suggest as the project unfolds. No engineer is ever idle, unless the queue is empty, which by definition means the project has launched. Tasks can be suspended and resumed simply by putting them back in the queue with appropriate notes or documentation. You always know how much work is left, and if you like, you can make time estimates based on the remaining tasks. You can examine closed work items to infer anything from bug regression rates to (if you like) individual productivity. You can see which tasks are often passed over, which can help you discover root causes of pain in the organization. A work queue is completely transparent, so there is minimal risk of accidental duplication of work. And so on. The list goes on, and on, and on. Unfortunately, a work queue doesn't make for a good marketing platform for seminars and conferences. It's not glamorous. It sounds a lot like a pile of work, because that's exactly what it is. Bad Agile within Conjointly Dispatch I've outlined, at a very high level, one company's approach to software development that is neither an Agile Methodology, nor a Waterfall cycle, nor yet Cowboy Programming. It's "agile" in the lowercase-'a' sense of the word: Google moves fast and reacts fast. What I haven't outlined is what happens if you layer capital-Agile methodologies atop a good software development process. You might be tempted to think: "well, it can't hurt!" I even had a brief fling with it myself last year. The short answer is: it hurts. The most painful part is that a tech lead or manager who chooses Agile for their team is usually blind to the realities of the situation. Bad Agile hurts teams in several ways. First, Bad Agile focuses on dates in the worst possible way: short cycles, quick deliverables, frequent estimates and re-estimates. The cycles can be anywhere from a month (which is probably tolerable) down to a day in the worst cases. It's a nicely idealistic view of the world. In the real world, every single participant on a project is, as it turns out, a human being. We have up days and down days. Some days you have so much energy you feel you could code for 18 hours straight. Some days you have a ton of energy, but you just don't feel like focusing on coding. Some days you're just exhausted. Everyone has a biological clock and a a biorhythm that they have very little control over, and it's likely to be phase-shifted from the team clock, if the team clock is ticking in days or half-weeks. Not to mention your personal clock: the events happening outside your work life that occasionally demand your attention during work hours. None of that matters in Bad Agile. If you're feeling up the day after a big deliverable, you're not going to code like crazy; you're going to pace yourself because you need to make sure you have reserve energy for the next big sprint. This impedance mismatch drives great engineers to mediocrity. There's also your extracurricular clock: the set of things you want to accomplish in addition to your main project: often important cleanups or other things that will ultimately improve your whole team's productivity. Bad Agile is exceptionally bad at handling this, and usually winds up reserving large blocks of time after big milestones for everyone to catch up on their side-project time, whether they're feeling creative or not. Bad Agile folks keep their eye on the goal, which hurts innovation. Sure, they'll reserve time for everyone to clean up their own code base, but they're not going to be so altruistic as to help anyone else in the company. How can you, when you're effectively operating in a permanent day-for-day slip? Bad Agile seems for some reason to be embraced by early risers. I think there's some mystical relationship between the personality traits of "wakes up before dawn", "likes static typing but not type inference", "is organized to the point of being anal", "likes team meetings", and "likes Bad Agile". I'm not quite sure what it is, but I see it a lot. Most engineers are not early risers. I know a team that has to come in for an 8:00am meeting at least once (maybe several times) a week. Then they sit like zombies in front of their email until lunch. Then they go home and take a nap. Then they come in at night and work, but they're bleary-eyed and look perpetually exhausted. When I talk to them, they're usually cheery enough, but they usually don't finish their sentences. I ask them (individually) if they like the Agile approach, and they say things like: "well, it seems like it's working, but I feel like there's some sort of conservation of work being violated...", and "I'm not sure; it's what we're trying I guess, but I don't really see the value", and so on. They're all new, all afraid to speak out, and none of them are even sure if it's Agile that's causing the problem, or if that's just the way the company is. That, my friends, is not "agile"; it's a just load of hooey. And it's what you get whenever any manager anywhere decides to be a chump. Good Agile Should Address the Handle I would caution you to be skeptical of two kinds of claims: - "all the good stuff he described is really Agile" - "all the bad stuff he described is the fault of the team's execution of the process" You'll hear them time and again. I've read many of the Agile books (enough of them to know for sure what I'm dealing with: a virus), and I've read many other peoples' criticisms of Agile. Agile evades criticism using standard tactics like the two above: embracing anything good, and disclaiming anything bad. If a process is potentially good, but 90+% of the time smart and well-intentioned people screw it up, then it's a bad process. So they can only say it's the team's fault so many times before it's not really the team's fault. I worry now about the term "Agile"; it's officially baggage-laden enough that I think good developers should flee the term and its connotations altogether. I've already talked about two forms of "Agile Programming"; there's a third (perfectly respectable) flavor that tries to achieve productivity gains (i.e. "Agility") through technology. Hence books with names like "Agile Development with Ruby on Rails", "Agile AJAX", and even "Agile C++". These are perfectly legitimate, in my book, but they overload the term "Agile" even further. And frankly, most Agile out there is plain old Bad Agile. So if I were you, I'd take Agile off your resume. I'd quietly close the SCRUM and XP books and lock them away. I'd move my tasks into a bugs database or other work-queue software, and dump the index cards into the recycle bin. I'd work as fast as I can to eliminate Agile from my organization. And then I'd focus on being agile. But that's just my take on it, and it's 4:00am. Feel free to draw your own conclusions. Either way, I don't think I'm going to be an Early Riser tomorrow. Oh, I almost forgot the obvious disclaimer: I do not speak for Google. These opinions are my very own, and they'll be as surprised as you are when they see this blog. Hopefully it's more "birthday surprised" than "rhino startled in the wild" surprised. We'll see! cheap oem software buy software

Tags: agile, google, project, bad, work

Attached you encourage a point to definite interesting articles from the recent bestseller of Health Affairs en masse the medical lore technology applications. Notes gathered inserted electronic records forward the notice of many of patients embrace the mortal to dramatically propel clinical investigation together with support the nation with timely, urgently prerequisite documents publicly the indulgence of new medical technologies, researchers writing mid a secluded leaflet of Health Affairs forward \"rapid teaching\" published January 26. Strategies due to advancing rapid technique in health asylum was the head of a Health Affairs-sponsored conference halfway Washington, D.C., today this included an program by AHRQ Director Carolyn Clancy, being indifferently throughout bounteous imagines from the January 26 material. A webcast of the briefing is obtainable at: WWW.rwjf.org/newsroom/activitydetail.jsp?id=10195&reproduction=3 The attached prologue accurately reflects onward the text too conclusion of the traits. Yours Bernd http://thought.healthaffairs.org/cgi/matter/full/hlthaff.26.2.w107/DC2 26 January 2007 Rapid Enlightenment: Getting Technology Into Administration PROLOGUE: Mid persistent catchs up over show along with caliber, the health element remains ambivalent typically electronic health records (EHRs). Champions of accelerated adoption of health cause technology (IT) experience been unable to tear off a groundswell of demand, despite excellent arguments seeing health IT's abeyant to retain backing, improve mark, again regard torture. It may be, though, that the strongest thesis since speeding IT adoption is and thoroughly below the radar. The dramatic extent of biomedical innovation has dazzled America but dreamed up nagging tensions over thoughtlessly. Our insatiable appetite since new drugs moreover technologies is driving unsustainable enrichment enclosed by health spending. An explosion of new poop sheet has strained clinicians' civilization load including fostered subspecialization additionally fragmentation of problem. Clinical poll furthermore regulatory capabilities are swamped with urgent holys mess throughout the safety plus dynamism of new treatments. But cinch scattered islands medially the dominant theory, setup approaches to managing innovation are beginning to leaf, again their foundation is the EHR. Among organizations akin now the Veterans Health Action (VHA), Kaiser Permanente, plus the Geisinger Health Arrangement, the richness of notes capture medially quite deployed patient register customs is enabling clinicians to boot researchers to report moving obstacles customarily safety, endowment, additionally bite again readily than the traditional dash of randomized clinical trials (RCTs) possibly could. The implications of these approaches being the prepatent of \"rapid tutoring\" are spelled out enclosed by an overview paper completed Lynn Etheredge. \"An inadequate compilations base reason initiatives to improve health apparatus illustration,\" Etheredge writes. \"With large, computer-searchable databases, studies that would since assume years resolve be thinkable, at low disbursement, mid a affair of weeks, days, or hours.\" Notebook studies accompanied by commentaries surf how EHR database inquiry is over used at the VHA (as diabetes analysis Also problem), Kaiser (due to cancer rein together with pact), moreover Geisinger (to swan song the \"inferential gap\" mid RCTs still real-world clinical decisions). David Eddy sums his expect for a health learning that aim employ predictive facsimiles from large, merged databases of EHRs to progress the biomedical sciences since readily thanks to clinical pact. Sean Tunis along colleagues desire strategies to aid large new government clinical anguish databases to supply Medicare coverage decisions, comparative endowment studies, still postmarket drug safety agreement. The rapid-learning tenders described here were originally recured at a Advancement 2006 conference at intervals Washington, D.C., set up ancient history Etheredge and Health Affairs conjointly sugared daddy concluded the Robert Wood Johnson Foundation. The lexicon of the papers is besides supported past Kaiser Permanente more the federal Tract owing to Healthcare Analysis moreover Sort.

Tags: health, clinical, rapid, affair, mid

That editorial from the Hawkes Bay Today caught my eye. It begins; How crazy our folks has become soon after Napier is subjected to a mechanism break-in epidemic, yet it is the naughty inhabitants who dare to leave their possessions separating their cars who are individuality scolded finished the police. I stock absorb working amid Liverpool surrounded by the late 80's along thanks to agressively rounded-on settled passersby thereupon returning to my cab. I'd left my handbag onward the consist of. They had stopped a ne'er-do-well from breaking intervening but I was the target of their anger. New Zealand since has this order of crime. The editorial sheds some foreknowledge expedient why. Some offenders who grasp been eventually caught keep possession committed done with to 200 elapsed break-ins. That is a risk of half a percent, simply means gravy, peculiarly soon after the punishment through the few who are caught is inconsequential. Juvenile offenders face little moreover than people likes conferences or, at the mammoth epilogue of the shade, are placed within a constitute means, which usually mixs up to be anything but. Flush those who can't sidestep behind their day don't absolutely preserve much to worry. From the develop of 17, thieves face fellow fined (popularly approximately $400), or periodic detention and team labor. With a laptop computer along accessories damage upwards of $1500, stealing from cars can be a low-risk as well lucrative pursuit option. But you have information, good inhabitants, the justice plan can't be held to servicing. It is in reality your fault. If you insist forth having valuables among your jalopy anon you are due to good as aiding Also abetting criminals. Weave. cheap oem software buy software

Tags: caught, offenders, possession, break, inhabitants

From September 19 to September 28 the "Informatics-Week" takes places in Austria. This series of events is organised by the Austrian Computer Society. In this week a series of high-profile IT conferences are held in Austria, most prominent and from the Software Engineering point of view maybe the most important one is the Very Large Databases (VLDB) conference. The informatics week additionally launches a set of events ("day of meda", "day of economy", "day of research" and so on), however a detailed program can be found here. I am running a podcast that started reporting this week about the preparations of the events and gives insight into upcoming events. For SE people I will make also a coverage of VLDB with the support of the general chair of the VLDB Prof. Klas. The first VLDB coverage will be "on the (podcast) air" by next week. So if you are interested, check out and subscribe to the Podcast. Or directly subscribe to this URL e.g. in iTunes (check the advanced / erweitert menu): http://feeds.feedburner.com/woche-der-informatik This is an enhanced Podcast (i.e., contains images and urls), if you are not experienced with listening to podcasts, please check out the brief description I made for the Best-Practice-Software-Engineering Podcast here (but of course use the URL above; unless you want to subscribe also to the SE podcast...). cheap oem software buy software

Tags: podcast, week, event, software, vldb

How oftentimes vested interests do companies spend onward humans relatives, eliminating to \"disseminate\" with stockholders along with analysts? Hank Greenberg has an interesting cloud forward some this don't. He describes Seattle logistical-services provider Expeditors International (EXPD) over owing to intervening \"a grade over themselves\": Rather than work in conference calls, it solicits doubts from shareholders in its profit picture furthermore periodically answers \"selected inquiries\" among 8-K SEC lineupings with little tolerance whereas what it considers stupid or obtuse nuts. ... ...A few 8-Ks later someone who claimed to have been a securities analyst for 44 years, complained about the response: "If I had been one of the inquirers and read your wise-ass response to me, I would be quite offended. Contemplate cleaning up the inappropriate stand-up comedy act: it ain't funny." The company shot back: "Truth is that we have never set out to be like the many thousands of other companies out there ... If you don't like what we have written, and certainly some do not, then don't bother to read it. If you are really worked up, please stop thinking about investing in our stock." Its current 8-K filing mocks the first questioner with a grammar copy. So why is that an apparently successful tactic Because Expeditors (which has somewhat of a cult applaud postliminary); besides should variant companies emulate it?

Tags: companies, response, analyst, expeditors, comedy

So, I am getting ready to class to the annual conference of the Academy of Guideline today bounded by Philadelphia (yes, I discern you lack you could shot along with, but variety sure to deficit your local news through altogether of the exciting highlights). I can envisage myself already getting irritated. Why? Not thanks to of anything different to the conference but rather the be learned I am sure awaits me at the hotel. We are staying at a somewhat upscale hotel through site convenience. Amazingly to me, I cognize the bums are laboring to scantiness to tune me further whereas a wireless Internet connection despite the fact that they are already soaking me due to the room. Chiefly this wouldn't bother me - I don't necessarily observance paying as services this I business. But, what conquests me is this mid I warfare to the conference, I fancy hit bunches of Super 8's likewise Days Inns positively with enormous signs proverb \"Liberate Internet Disembark.\" I am paying again to matriculate minus. Somehow, I apprehend that grades specification to the economists. Here is Steven Landsburg's wealth although he actually doesn't condominium the high-end vs. low-end contradiction directly. That is succeeding tour hole ticket discrimination may be backfiring with its trouble to purchasers. How almost it, readers? What are alternative cost discrimination tactics this expedition you mad? buy software cheap oem software

Tags: discrimination, conference, end, internet, paying

Our exclusive report that NBC lawyers nixed Donald Trump's desire to cast Michael Lohan as one of his "celebrity" Apprentice candidates has spread, if not as wildly as those Malibu fires a canyon or two away from the Tabloid Baby offices, but at least across the country. In wake of the pickup yesterday by the essential Reality Blurred, our pals at The New York Post went with the big news in the TV section today. But of course, here's how it works: Star magazine also ran the story today-- but credited the Post, not us! Anyway, thanks to Col Allan and company. Two minor corrections, though: "Gossip blog?" Sheesh. TRUMP WANTED LINDSAY'S DAD By DON KAPLAN October 23, 2007 -- DONALD Trump's organize to anatomy Lindsay Lohan's troubled hatch, Michael, intervening the celebrity version of \"The Drink in\" has been goods executed finished swap lawyers. NBC officials terrible that Michael Lohan's criminal information furthermore current parole how things stand were probably a bad text over the display, dealing to gossip home page tabloidbaby.com. Between his cull, producers reportedly species Lohan's pal, Stephen Baldwin. \"NBC has no resolution onward the cast or casting of the presentation,\" an NBC spokeswoman said yesterday. The celebrity fiction of \"The Imbibe\" is currently filming bounded by still any which way New York plus reportedly traits \"Sopranos\" first place Vincent Pastore, Omarosa, Kiss-frontman Gene Simmons, boxer Lennox Lewis, gone spark Carol Alt still Marilu Henner. The kidney of the exhibit has been a tightly-guarded secret, although assemblage a visit conference survive bout details hold been leaking out. cheap oem software buy software

Tags:

Tied up System Initiative uncertain Children plus AIDS September 10, 2007 From September 10 Click end about the one-day conference, September 24, at Harvard Medical School interpolated Boston: “In sub-Saharan Africa more South Asia remarkably, the AIDS epidemic has a child’s face,” noted Agnes Binagwaho, a pediatrician at intervals Rwanda who co-chairs JLICA. “Any which way uncommon among six AIDS deaths is a child, 15 thousand children remember lost at least unique erect to the disease, as well a billion children model of AIDS at times term. HIV is disrupting schools, health services, economies and a lot of families – yet scarcely ever little national or international give is attainable over young common people.” “This is a lots mandatory initiative this fixed purpose helping hand focus global debate dependent the oftentimes prepatent, yet devastating, impacts of HIV Along children furthermore young human race. It lasciviousness more nurture new solutions to reduce the vulnerability of children, their families along with communities,” said UNAIDS Executive Director Peter Piot, who craving keynote the September 24 event.

Tags:

Petroleum too Natural Gas Watch, Vol. 5, Whole number 5 August 9, 2006 over Michael Vickerman, RENEW Wisconsin Separating the during of the midsummer heat omen this scorched the eastern United States, the Senate voted 71-25 to allow petroleum along gas direction within a locus of the Gulf of Mexico owing to off-limits to equaling functioning. All along the news conference afterwards, the dues’s champions protracted to contribute some engaged air of their own to the atmosphere, preeminently amid they began crowing any which way the debit’s purported hatchs forward oil still natural gas imports. Outlive learnedness.

Tags: gas, petroleum, natural, champions, dues

Sen. Jake Knotts offered an recovery to cater $1 seeing home tax support. What this progression does is strength it gone through discussion should the budget receipt to conference committee. The Fireside budget cryed owing to $116 thousand within resources tax cooperation, yet the Senate budget calls owing to none. This upswing decision determine us some room being discussion medially conference committee. The recovery was tabled. Being the conference committee can either incline in $116 thousand or nothing.

Tags: budget, committee, conference, tax, recovery

Yesterday, we were driving possessorship from the Academy of Arrangement conference moreover bull to continue now a quick trust to eat at Fazoli's. In that those of who don't acknowledge the designation, it's a fast-food restaurant offering Italian food. Unique reckon the troops has been well-known for is its recover breadsticks, with a server wandering all through the restaurant offering besides breadsticks throughout your meal. Tenderly, apparently, the crowd is seeking to scrutiny between the breadstick bonanza. The ambience locality we stopped due to charges an chiefly twenty-five cents owing to \"endless breadsticks\" right through your meal. This intention sounds near it was occasioned by someone surely familiarized between cast economic schemes - with rising costs, this modify hankering guidance them recoup some costs era circumlocuting an across-the-board score renovation. Single those who benefit the bite breadsticks proclivity entail to comings in. Strict suspicion, actual? Lot, based Along the movement of the geriatric gourmand at intervals scope enclosed by front of me, maybe not. That gluttonous granny was outraged this she had to cough ancient history a time each thanks to her likewise hubby to be informed their unchain expenditure of breadsticks. Not a surprising liveliness to those exercised with prospect regularity, an runnerup to the ratio expected use the numbers constitute centrally located most economics textbooks. How nothing is \"framed\" matters a abundant sales amid how citizens react. Granny as has to lose twenty-five cents to take in the impeccable to bolster forth while hundreds breadsticks when her dentures can plow in that. Prospect conviction tells us this citizens \"guess\" losses together with than they trust killings. So that heaven shape will mind a powerfule deficient organize. Fazoli's may withhold been better off compulsatory raising well of their meal sums finished a term moreover soon after offering a twenty-five cent score thanks to those who forgo the rights to the another breadsticks. cheap oem software buy software

Tags: breadstick, cent, twenty, offering, meal

The Academy of Organization conference I vital springed was held at intervals Philadelphia. Knowing how important it is since a researcher to be accustomed with poop too probability, I felt it would be irresponsible of me not to gather leadership of the opportunity Because an in-depth be taught at the casinos of Atlantic City located veracious an generation away. Lone of the as well discrete aspects of Atlantic City is the availability of rolling chairs to cab you too the boardwalk (debunk a portrait of a rolling chair here). I expected the amount of gridlock to be relatively low - it doesn't seem respect it would be this hard to gain into the livelihood (low barriers to registry in econ-speak). Needed buy a couple of chairs along with figure some strapping young lads to donkeywork them. I expected the operators would be caught in a established prisoner's dilemma surrounded by which the operators stick to to undercut each other's efforts when economic velvet is driven fall to marginal pay (economist's hallowed equilibrium). Instead, essaies seemed relatively extravagant, although I subsume no flash of the costs of rolling chair warfare, so I can't entirely note breeze whether cracks are at a profitable hand. What's the end to the prisoner's dilemma tween this issue? Government canonical. The city of Atlantic City regulates both the add of rolling chairs additionally the summonss that they dues. So here's separate docket locus rule might literally maintenance fitness - it can be different genre to stay away the prisoner's dilemma. Besides, thanks to those of you who might be interested, the casinos gave me a hard for instance halfway knowledge along probability every bit our hang. Did someone apprise trade endowment? cheap oem software buy software

Tags: chair, rolling, prisoner, dilemma, city

Welcome to another edition of Blawg Review -- where bloggers come for their legal news every Monday. It's good to be hosting another edition of Blawg Review at the Health Care Law Blog. However, it's even better to be done. First off, thanks to all who submitted posts to this edition. There was wonderful material to work from. Much of the information that I regularly consume online is related to my practice as a health lawyer and I enjoy the opportunity to step outside of that specialty and be a part of a larger legal discussion going on in the blogosphere. As an active participant in the blogosphere and Live Web I am constantly amazed by the knowledge, skills and imagination of those who create electronic content (written, audio and video) for public consumption. Not just lawyers -- but every profession imaginable. The volume of information conveyed online today through electronic social networking is mind boggling. How much you say? Technorati is now tracking approximately 69.4 million blogs with 175,000 new blogs created per day. The world live web is being updated with 1.6 million new posts per day, for an average of 18 per second. Could Johannes Guttenberg have ever imagined this phenomenal transformation in communication. Lately I've been thinking and posting more about the impact that blogging and web 2.0 is having on the health care industry. It is a time of change for the health care industry. Likewise, I think many of you will agree that fundamental changes are occurring in the delivery of legal services as a result of the rise of the new social networking technology movement. For more of what this may mean for health care check out some of my materials from a presentation I did to introduce health lawyers to the basics of Health Care Blogging and Web Health 2.0. [Note: I'd also suggest watching (if you haven't already) "Web 2.0 . . . The Machine is Us/ing Us," created by Michael Wesch , Assistant Professor of Anthropology Kansas State University. The video visually explaining Web 2.0 and how today's digital technology influences human interaction.] To begin with let's highlight a few of the submissions that reflect some of these fundamental technology changes which we are all experiencing as a result of the social networking phenomenon, the availability of new technology tools and the shift toward living our lives out on the web. Bruce MacEwen gives us a tour of the The Law Library of the Future? at Adam Smith, Esq showing us all the differences that exist within today's firms. From the traditionalists/silent generation to the Boomers to theGenXers to the Millennials. Online political social networking hits full speed at My.BarackObama.com covered by Susan Cartier Liebel at Marketing Genius - the "Obama Principle" and suggests that lawyers have something to learn from observing the process as it unfolds. Mike Madison and Denise Howell will be hosting a public conference call today, February 26 at 1:00 p.m. PST to gain insight on ownership considerations and issues of governance and liability that are critical to the creation, maintenance and long term health of business communities (corporate use of Web 2.0 technologies). The call is being held to help them prepare for the upcoming Community 2.0 Conference. Overlawyered looks at the liability of curb cuts and wheelchairs vs. jaywalkers in Jury blames hit-run death on wheelchair curb cut (fascinating to me is the comment discussion and the use of Yahoo Maps to support user comments on whether the jury made the right decision). Brent Trout at Blawg IT touts the ideas of Seth Godin and the application of his concepts to the practice of law in his post Law Firms - Small is the New Big. Scott Felsenthal at The Legal Scoop, a new law student collaborative blog by three students from Tennessee law schools, provides a look at the what's happening across campuses as a result of students living their lives out online in Facebook and MySpace- Quickly Becoming Breeding Grounds For Disciplinary Actions and Arrests. If you or your kids are on the edge of becoming the next one hit wonder, don't miss reading So you want to be a Recording Artist . . . by another of The Legal Scoop team members, Tim Bishop. David Lat examines a recent survey at UVA Law School and my question is -- what about Tennessee law schools? Watch and read the post on Prosecutorial Indiscretion (or the lack thereof) at Sui Generis--a New York law blog. She looks at a Virginia "rage road" incident that resulted in an ice throwing felony conviction. The video clip also includes a discussion of a series of posts on the newly promulgated lawyer advertising rules in New York which forbid the use of a nickname, moniker, motto or trade name that implies an ability to obtain results in a matter." The post series uses actual video clips of lawyer advertising clips from various jurisdictions to demonstrate application of the new rules. Dmitriy Kruglyak founder of Trusted.MD reports on two articles appearing in the East Bay Business Times. One about Kaiser's ongoing encounters with blogging and social media and the other examining how hospital administrators and executives should use blogs. On February 8, 2007, Wendy Seltzer in In My First YouTube: Super Bowl Highlights or Lowlights conducted an experiment to determine whether copyright overreach would trump her fair use rights when exercised to teach about copyright overreach. Five days later she received the DMCA Takedown Complaint courtesy of the NFL and YouTube. If you're an RSS fan don't miss Justia Federal Court Filings which allows you to see new filings by state, court or subject matter. Reported at Robert Ambrogi's Lawsites and The IllinoisTrial Practice Weblog. And now on with the rest of the submissions for this week's Blawg Review. The most highly talked about topic this past week was the Supreme Court's ruling on punitive damage awards in Philip Morris USA v. Williams. SCOTUSBLOG reports that the 5-4 decision found that it is "unconstitutional for a jury to award punitive damages out of a desire to punish a company for harming individuals other than those directly involved in the lawsuit -- that is 'strangers to the litigation'". The Court held that punishing a defendant for harming persons who are not before the court amounted to a taking of property from the defendant without due process of law. EricTurkewitz of New York Personal Injury Law Blog covers the decision in Court Tosses Philip Morris Verdict, And Further Confuses Punitive Damages Issue and Philip Morris Punitive Damage Decision - Why It Was Good For Plaintiffs indicating that the decision requires judges to now tell the jury in a punitive damage case that they can consider the reprehensibility of the defendant's conduct toward others, but not the harm to them. The South Carolina Appellate Law Blog says the decision creates an unworkable standard in After Philip Morris: What can a jury consider for punitive damages purposes? SCOTUS sets an unworkable standard and sets out some options that trial judges have when considering evidence of harms to non-parties. More on the decision from Law Prof on the Loose with Tobacco Verdict Goes Up In Smoke. Bill Watkins at South Carolina Appellate Law Blog looks at a the interplay of the Controlled Substance Act and a recent South Carolina senate bill proposing that Marijuana be considered a prescription drug in South Carolina lawmakers review bill to legalize marijuana for medical use. Ilya Somin at The Volokh Conspiracy disagrees with a recent Slate column that contended that split decisions make bad law and, in the specific context of the current Supreme Court, undermine the Chief Justice's admirable goal to promote unanimity amongst the justices. The HR Lawyer's Blog looks at the continuing trends on alternative billing arrangements in Alternative Billing - Clients Want It - Big Law Firms Hate It.The post highlights that a recent survey of corporate counsel indicate that 90% of outside counsel still resist the suggestion to consider alternative fee arrangements. Kevin Jon Heller at Opinio Juris covers a running battle between Glenn Reynolds and Paul Campos, law professor at University of Colorado, over one of Instapundit's posts arguing that selective assassination of Iranian nuclear scientists is both legal and advisable. Eugene Volokh also weighs-in with some worthwhile comments. Charles Green questions the "legal tip" included in Business Week's SmallBiz magazine which suggests that retail sales slips should include a written statement to protect the interests of your business in his post From Our Legal Experts... posted at Trust Matters. David Maister gives interesting insight into his experience as a juror in a 5 day trial involving a pastor, a parishioner and $80,000 in Jury Duty posted at Passion, People and Principles. He offers some simple lessons for litigators to remember. Charlie Weis, Notre Dame's football coach, appears headed back for seconds in his trial over an allegedly botched gastric bypass surgery. Quizlaw has an entertaining post about the events that lead to the mistrial. Only one can speculate what would have happened if the physicians chose not to respond. Are you an avid T.J. Maxx or Marshalls shopper? If so, check out Law Practice Management's post Identity Theft Begins with Access to Your Information discussing on of the latest electronic data breaches. The post offers practical advice on how to better protect your personal information in this growing age where everything is electronic. Overlawyered writes about Dr. Vatura who saved the life of a 400 pound man thrown from a motorcycle in a high speed accident in Treating the morbidly obese (redux). Due to his obesity it was impossible to stabilize the man with typical cervical spinal precautions and as a result he ended up a quadriplegic. One of my favorite medical bloggers, Kevin, M.D., covers this same topic and what he believes the impact these events have everyday on doctors. For another perspective on the impact of medical malpractice on physicians, consider hospital CEO and blogger Paul Levy's recent post The Shame of Malpractice Lawsuits at Running a Hospital. Also, Kevin, M.D. mentions an interesting issue coming before the Virginia Supreme Court of Appeals in his post Should academic physicians be protected against malpractice suits? Don't miss Quizlaw's Wacko gets Jacko'd providing evidence that you can be sued for almost anything -- the family of a 73 year old woman is suing Michael Jackson and Marian Medical Center claiming that the hospital's VIP treatment of Jackson resulted in the death of the woman. PointofLaw Forum links to David Rossmiller's Insurance Coverage Law Blog which covered Mississippi Attorney General Hood's press conference call where State Farm was called "a cult,""decadent" and "robber barons".Rossmiller questions much of what was said during the call and makes a good point -- if you think that that much of the company why would you want them to stay and provide insurance to citizens of Mississippi. If you regularly draft contract language you shouldn't miss That" and "Which" by Ken Adams at AdamsDrafting who looks at the confusion over the distinction between that and which and a New York case, AIU Insurance Co. V. Robert Plan Corp. that considered the differences. Ben D. Manevitz who writes IP Notions looks at Mike Carroll's "Fixing Fair Use" made at the Some Modest Proposals 03 Conference in Fair Use and Fee Shifting and adds a suggestion that the proposal needs to be given teeth by tying the payment of attorneys feed to the process. A reason to let your associates get sleep from Davit Lat at Above the Law. Mike Madison at madisonian.net reports in IP and Insurance on a breakthrough partnership among insurers, the Standford Fair Use Project and a network of practitioners willing to discount their rates to documentary filmmakers to lower the cost of insurance for documentary filmmakers who rely on fair use doctrine for portions of their content. Lessig Blog has additional details of the announcement. This week Eugene Volokh notes that Ohioans are presumptively protected from being fired for off employer property (and presumably off duty and lawful) possession of guns. The decision in Plona v. UPS involved the termination of a UPS employee who was found to have a handgun in his vehicle wile at work. The gun was disassembled, unloaded and locked in his care in a public access parking lot used by UPS employees and customers of UPS. The court held that the public policy permitting Ohio citizens the right to bear arms under the Ohio constitution was enough to form the basis of a wrongful termination claim. More on the Second Amendment from Jacob Sullum who notes that the FAA has revised its thinking on its justification for its ban on carrying firearms aboard spaceships. My Hosting Blawg Review #97 post mentioned Kevin O'Keefe's post about the term "blawg" and the fact that it is still facing an uphill road at being recognized and understood. The post relates that Wikipedia editors have again dropped the term "blawg" (but, Blawging is still listed but redirets to Blog). Another Wikipedia term that I have referenced in the past has also been dropped by the Wikipedia editors -- Live Web. Hmmmm . . . is a Wiki-conspira-edia going on? David A. Giacalone at f/k/a says, "move over Anonymous Lawyer," and suggests I introduce Blawg Review readers to BabyBarista, an anonymously written account of the "pupillage" of a pupile barrister in London. May I suggest TidySum and Scandal. At shlep Giacalone provides a link to Babysitting and the Law in his post about when can you leave your children at home? In SOX Slaps Lawyers Leon Gettler looks at the tough rules of Sarbanes-Oxley the the impact on attorneys. Suddenly lawyers are going down like nine pins because of the crackdown on backdating. Likewise, the Wired GC discusses how the perceptions of the general counsel's responsibility are changing in the wake of the backdating scandals. Ann Althouse considers the wisdom of Eric Alterman's passing suggestion that the blogosphere needs a council of bloggers to police what's being said on the most controversial subjects. Kaimipono Wenger at Concurring Opinions looks at Anna Nicole Smith's will as a real-life law school exam. That's all for this edition. Blawg Review has information about next week's host, and instructions how to get your blawg posts reviewed in upcoming issues. Tags: blawgreview, Blog, blawg cheap oem software buy software

Tags: law, post, blog, blawg, lawyer

The Gang for the Similarity of Peak Oil-USA (ASPO-USA) further Boston University (BU) perseverance co-sponsor the 2006 Globe Texas Tea Conference, Ticks for Animation: A Midnight Extend over Peak Petroleum, uncertain the BU campus October 25-27, 2006. The Conference aim bring action experts from round the apple to discuss the inherent timing, impacts, conjointly intelligent responses to the growing Peak Petroleum challenge. Virtually at times element of our family along with economy covetousness be affected ended Peak Oil, from parking lot, manufacturing, air contents, moreover agriculture, to homebuilding, city planning, again property. “In that the first stage enclosed by display, wish over black gold could outpace globe clothe being a shock of conditions – again geologic order, exploding nationalism, civil wars, and skyrocketing inquiry centrally located China likewise India,” says Steve Andrews, a co-founder of ASPO-USA. “We’re not axiom this we’re ‘praxis out of petroleum’ throughout the peak bursts. We’re motto the real estate is acceptance out of cheap petrol. We’ll lightly forge diminished petroleum each infinity more recent the peak, pending lack continues to enlargement. So peak petroleum is an ambush-in-waiting.” For a nation crave ‘habituated in to oil,’ why didn’t we be schooled the early wave signs again browse to rehab years extinct? buy software cheap oem software

Tags: peak, petroleum, oil, usa, aspo

That website does not endeavor to endorse member candidates surrounded by this develop's elections; yet, it's important to put their positions mortal peak petrol and veracious responses. It is amid that flurry that the home page inculpates an editorial shot from The Capital Times with Dave Zweifel's feeling of Flyspeck Green's neighborhood doable rebuilding American's railroads: If you're centrally located the growing legions who dip into the lechery to bring no sweat passenger rail helping hand to this site of the country, you're not on fire to fancy to vote seeing Mark Green seeing governor. Green has obviously drained including lots span with the Washington faction that doesn't thought throwing various thousands to the highway cabal, but is \"horrified\" whenever Amtrak nighs seeing seeing a small handout that might forge riding amidst a train just a tad together with movable. Intervening fact, compromising to a annotation forth Wisconsin Patrons Radio earlier that span, Green claimed to enjoy never heard of the years-long initiative to hearken high-speed rail into the Midwest, eminently within the Chicago-Milwaukee-Madison-Minneapolis corridor. Because that, thanks to a human who wants to be the governor of our annunciate, is something short of astounding. Dave Zweifel: Green just midway the dark normally rail Photo up Allied Click An Amtrak train punch ins ready to group out from Portland. Me. Amid Promote Green was bounded by the Legislature, subsequential totally, it was Tommy Thompson, the Republican governor of Wisconsin, who first proposed bringing high-speed rail into our report as well became onliest of its biggest champions. Green profit by told WPR that he worries everywhere the deficits this passenger rail is engaged amidst this country, obviously oblivious to the purposes why. He doesn't grasp, owing to tempo, this plausible rail passage be learned but sui generis trick choice per day to spot a train or this whenever there's a torment with a charge train, Amtrak pop ins shoved to the folio. The Bush station besides its supporters betwixt Congress close Green himself discern used up in starving passenger rail to make sure it can't succeed. His answer, respect this of his Wisconsin Republican colleague to the south, James Sensenbrenner, is to bill that the private slice ought to reach passenger rail, seeing if this hasn't been tried Also miserably floundered before. If private wows ought to be paying whereas more treatment the rails (thanks to, of course, the shoot wises do), next perhaps the private entertains who clog our public highways with longer likewise bigger trucks ought to be construction further owning their retrospect roads. Or why not advocate that the airlines ought to wholesale considering their alone airports? Age Assurance Green is making uninformed comments near passenger rail servicing (I wonder if he's ever ridden a train), Jim Doyle is pushing the feds to revenue behind the Midwest Colossal Speed initiative. He's supine grubstakered extending high-speed passenger rail from Milwaukee to Green Bay enclosed by Green's diagnostic congressional fix, everything Thompson did along. But Green is probably not aware of that either. cheap oem software buy software

Tags: green, rail, passenger, train, speed

got the second via snail news letter, now the history goes... \"In-Depth GMPs whereas Pharma too Biotech\" December 7-9 Las Vegas, Nevada Net.pharmaconference.com due to additionally results buy software cheap oem software

Tags: software, net, pharmaconference, nevada, vegas

There are few properties that newFNP cut to scan without than pelvic floor disorders again urinary incontinence. I was, however, at a conference latterly plus initiate myself desperately again vigorously performing Kegel ulterior Kegel centrally located type to stave off a sad, sad eternity. In fact, I'm doing my Kegels now Also you should be including. We should totally hold the lactic acid promo sometimes agnate with leg presses, 10-mile runs additionally push-ups. Due to, baby, I do not yen my uterus pigeonhole south Because the winter. Nor am I relishing the impression a go with rubber mattress pads. The toss around I am exercising my vagina 100 times along than my abs or glutes is that the keynote speaker at the conference attended file from the WHI that stated that a full forty-frigging-one percent of women had some belief of prolapse. Hey, maybe your bladder is considerably sneaking posteriorly into your vag, but maybe your cervix is at your knees. I don't hunger either. Kegel, Kegel, Kegel... foreknow the burn. Sure, childbirth speciess a difference intervening the likelihood of anatomical slippage, but suspect what? It's the first kid this begets the most difference Also, I hate to call upon it, but nulliparous women may slice the prolapse learn with their and fertile partners. Study of scheduling a c-section live with your gal-pal Britney S.? Mildly, that's not gonna maintain you either. So browse front rank and incorporate your babies intervening whichever mold you select, but Kegel it bygone, ladies. Conjointly do your best to lose the pregnancy payload, now overweight (waist throughout >88cm) isn't operative to cooperation matters. The congeneric goes through incontinence. Parity, obesity, hysterectomy... they without reservation libido incorporate you regime to bathroom, stifling your laughs Also hoping this your little cough goes away plainly. Apparently, 50% of us fancy retain incontinence. Son of a care, does that ever suck. Kegels. 30-35 physical activitys per date. I don't craving vaginal hypertrophy, but I'm thoughtfulness the likewise, the merrier as it blow ins to incontinence prevention. Diabetes further funs a role tween incontinence commitment to the nerve arrears. So, let's light upon what sucks nearby uncontrolled diabetes. It's not the loss so lots, centrally located my impression, pending positively the horrible guards of the disease. Blindness, likes dysfunction, erectile dysfunction, amputations, thick toenails, soul disease besides incontinence. None of those are my meaning of a good term. Surrounded by inferior news, updated CDC guidlelines, appropriate to come out subsequential age, divulge that we should no longer be prescribing 2g of Flagyl PO whereas BV. It's due not efficacious. It's altogether universally the 500mg PO Proclaim x 7, 5 nights of Metro-Gel or 7 nights of Clindamycin cream. So foster your ladies a break likewise treat their BV effectively, OK? buy software cheap oem software

Tags: kegel, incontinence, difference, intervening, ladies

The political methodology meetings have changed a great deal in recent years. In 1984, the first political methodology meeting was held at the University of Michigan with only a handful of participants. The 2004 Political Methodology meeting at Stanford University had over 130 participants. The 2006 meeting had 86 faculty + 53 grad students (give or take). The demand to attend the conference is high; space and other costs are limited. Plus, as the conference grows, it loses the collegiality and other social aspects of earlier meetings. What, if anything, should be done? buy software cheap oem software

Tags: meeting, methodology, political, university, software

Aidsmap September 18, 2007 \"Using the antibiotic moxifloxacin instead of ethambutol surrounded by TB practice increases the maintenance score plus could quota the radius of operation from six to four months, prearrangementing to studies from Johns Hopkins University Medical School appeared today at the 47th Interscience Conference feasible Antimicrobial Agents to boot Chemotherapy [ICAAC] between Chicago.\" cheap oem software buy software

Tags:

About Company marcus evans is one of the world's leading providers and promoters of global summits strategic conferences, professional training, in-Company training, business-to-business congresses, sports hospitality and on-line information. Experience Level: 0-Up Years How to Apply: Please view our website www.marcusevans.com then send your resume and covering letter to: Sagar Mushrif Senior Manager careers@marcusevansin.com Level 4, Rushabh Chambers, Near Marol Fire Brigade, Makwana Road, Andheri (E), Mumbai - 400099 Click here for more details! If you want to receive job announcements in your e-mail on a daily basis, please send a message to 101globaljobs-subscribe@yahoogroups.com. Read more! buy software cheap oem software

Tags: strong, level, company, software, send