Where do savvy BC readers find the best shopping values, both online and overall? Nominate your favorite stores and online retailers in the form below. I'll sum up the responses in a Readers Choice Cheepie Awards post on New Years' Eve. I had no idea what the man could do, but he terrified me, and had crazy eyes that were just so filled with Wrong. I wasn't actually in the dream this time, just perceiving what happened, so w00t for not getting killed or hunted in my dreams for a change.
"Buttons!"
"No, C."
Her finger keeps moving towards the keys... as the distance closes, her grin widens.
"BUTTONS!"
"No, C! Don't push my buttons!"
Heh. Hehe. Sound advice for life with a happy Mama, wouldn't you say?
The Chief Development Manager was originally published on April 4, 2007.
"Wait a sec," whispered Chris’s coworker David, "he can’t possibly think this will solve the Build Problem? His idea is completely absurd!"
Chris nodded slightly, clearly uncomfortable to be part of a conversation taking place in the middle of a meeting. Especially a meeting being held by the Chief Development Manager. While some managers like to lead by example, and others like to lead by befriending, the Chief Development Manager liked to lead by fear.
"I mean, seriously," David continued, "this will only make the problem much –"
"Oh I’m sorry," the Chief Development Manager barked, callously, "were you guys trying to have a meeting in here? Because, if I was interrupting you two, I can stop. And I’m sure all the fifty-three other developers sitting here have nothing better to do than wait for your little meeting to end."
David and Chris stared blankly, mouths agape.
"Oh. You’re done? Great! Let’s continue, then. That okay with you?"
That was exactly what Chris was trying to avoid. The Chief Development Manager was known to act condescendingly like that. In fact, Chris had witnessed similar outbursts like that in the past. He wasn’t too thrilled to be at the center of one this time around.
I wish it could be said that, deep down inside, the Chief Development Manager was a nice guy and just liked to dish out tough love. But he wasn’t. He was a cantankerous, spiteful little man who wielded a lot of power and used that power to make everyone around him miserable. And his latest idea – the new Build & Deploy Process – was just another step in that direction.
David was right, the new Build & Deploy Process was ridiculous and, with the hundreds of developers spread across four offices around the world, it could never work. But the Chief Development Manager had staked his reputation on it and had sold it to his higher-ups as The Solution to all of their build problems. It didn’t matter what anyone said, they were using his process.
The new plan was to have a fixed build schedule with strict deadlines. If a developer didn’t get his change in by 3PM Tuesday, then that change wasn’t going. No excuses, no exceptions. And to manage all of these changes, there would be a single Excel spreadsheet on a network share drive that each developer would be responsible for updating. They’d have to add a row for every file changed and include its path, the issue number, and the reason behind the change.
To almost no one’s surprise, the first build using this new process was a complete disaster. Most developers spent all of Tuesday fighting over the change spreadsheet, desperately clicking it and cursing the "this file is currently in use by..." dialogs. With all the haphazard updates, the build wouldn’t even compile.
The second build, the third build, the fourth build – all suffered the same problems. 200+ developers trying to a share a single spreadsheet around a hectic build schedule just didn’t work. The Business was getting a bit fed up with the lack of working builds on their test environments and went straight to the Chief Development Manager for an explanation. As you may have guessed, the Chief Development Manager passed the blame right on down to the development managers and even the developers themselves. He expressed concerns that they might even be trying to sabotage his system.
"This is complete bullshit," David complained to Chris, as they sat in another developers cube, "does executive management actually believe that? I’ve put in a helluva lot of hours this year, and this is just going to kill our bonuses! I’m going to say something. This just isn’t right!"
Chris agreed, but cautioned his coworker about raising a stink. Everyone knew that the Chief Development Manager was not one to be messed with. But David ignored Chris’s advice and started gathering a small group of developers. Together, they would set up a meeting about the Build Process, invite executive management, and directly confront the Chief Development Manager. They would not put up with his blame-passing laying down.
As you also may have guessed, the Chief Development Manager covertly told executive management that their attendance at a meeting about the Build Process was a waste of their time, and that he’d distill the results to them later. David and his fellow developers waltzed into the conference room expecting a big confrontation, only to find the Chief Development Manager calmly sitting down, feigning eagerness to listen to their complaints.
Before he even let David finish his first sentence, the Chief Development Manager snapped that the meeting was a complete waste of his time, as well as everyone else’s. He forcefully declared that there was nothing wrong with his system and that he didn’t appreciate lowly developers telling him how to do his job. The meeting was officially adjourned when the Chief Development Manager stormed out of the conference room.
A week later, the Chief Development Manager approached David and each of the other developers from the Build Process meeting and apologized to them.
I’m kidding. He fired them on the spot. As security led them away, one at a time, every developer knew why they were let go and who made it happen.
The next day, the Chief Development Manager sent an email to all developers letting them know that, effective immediately, a third-party build management system will be used to manage changes. A slightly different email went to the executives, informing them that the problems behind the new build process – i.e., the developers he just fired – were now solved.
While this may seem like a rather depressing ending, I will share with you an email that Chris received a few weeks later. It was from David. "Chris, my new job is fantastic. And best of all, there’s no Chief Development Manager."
While looking for something entirely-unrelated, I came across this old post from 2006. I read the entire post that it's excerpted from on Radio Free Burrito 17, but this part made me smile, so it gets its own spot right here on my bloggy-blog-blog:
Though I've been there for several auditions, I haven't been on the Universal Studio Tour since A-Team and Knight Rider were in prime time.
I can mark that particular period of time with this degree of certainty, because I clearly recall talking with KITT, and wanting to ask it if it ever raced the A-Team van around the back lot, but actually asking something stupid about how fast it could go.
I also recall taking a scratch off game with me on the tour tram, where we were supposed to look for A-Team characters in various places, and scratch off the appropriate image on the map, with the promise of a prize for kids who turned in correctly completed games. I can't remember all of them, but Mr. T -- well, a model of Mr. T's head, anyway -- was in this out of control train that was supposed to come within inches of crashing into the tram, and I was so busy trying to figure out how they did it, I forgot to scratch him off . . . until the tour guide reminded all us kids to scratch off that circle on our map.
"That's stupid," I told my mom, "if they're just going to tell everyone where the A-Team is, why should we even look?"
"Maybe you can just enjoy the tour," she said.
2006 was a fantastic year for me as a writer. When I go through the 2005-2006 archives, I see a lot of creative writing and narrative non-fiction that I recall having a lot of fun writing, which remains a lot of fun for me to read today. I'm not entirely sure why that is, but I suspect a lot of it has to do with how much I was allowing myself to simply enjoy the tour.
1 pound cream cheese
1 cupish confectioner's sugar
1 pintish sweetened condensed milk
2 tsp vanilla extract
Mix all of the above in a big ol' bowl.
Melt some Nutella and ice/frost/ganache/whatever the pie crusts with the molten Nutella. Stick it in the freezer for a bit to solidify before pouring in pie filling. One 13 oz jar should get you two well-glazed 9" crusts and plenty of finger lickin'.
Lightly sprinkle the top of the pie with nutmeg and allspice.
I have two of these pies. One of them is coming with me to my NYE party of choice.
What shall I do with the other one?
Get a value box of Pampers Cruisers for $24.81 at Amazon when you use Subscribe and Save (it's easy to cancel your subscription online after one delivery). That's .214 each for size 3 (the "Stockupportunity" price is .22 each). Free shipping, too! Thanks to BC reader "The Bookworm" for the tip!That combo makes it easy to forgive him when he grabs my face with his two meaty little hands and chews.
Well, come to think of it, that's pretty cute too.
Slobbery, but cute.
Because our last Advent service was snowed out, we looked at Isaiah 9:6 this week:
For unto us a Child is born
Unto us a Son is given
And the government will be upon His shoulder
And His name will be called Wonderful, Counselor, Mighty God
Everlasting Father, Prince of Peace.
Save 30% on LeapFrog Tag Reader Storybooks at LeapFrog.com with code LEAP30. Plus, get free shipping on orders of $30 or more. I just picked up a few "Classic" storybooks for $6.99 each. Great prices on the "Learn to Read" series, too. Ends 1/7.Edited: Just found out that the same coupon code is good for Tag Junior books, too!
Memories of the Future got a nice write up in the Toledo Free Press:
There’s one thing that Wil Wheaton wants to make very clear: “Memories of the Future” is not, repeat, NOT a “tell-all” book about his time working on “Star Trek: The Next Generation.”
“It was extraordinarily important to me that this was not some kind of stupid, gossipy book,” Wheaton said. “I despise that kind of thing. I just hate it. It’s the reality television of literature, and I absolutely cannot stand it.”
Indeed, “Memories of the Future” is instead a funny review of, and a loving tribute to, the first season of “Next Generation,” which began its television run in 1987.
I also saw that Happiest Days of Our Lives was used as an example of one of those new-fangled paper-style books:
Today I picked up a paper book to read just for fun — The Happiest Days of Our Lives by Wil Wheaton. Long-time (since this spring!) Kindle user that I am, I immediately noticed the dashing use of color on its front cover, but when I opened it, I was disappointed that I couldn’t scale the font size down from the default. It seems that paper books have only one font option — what are all these Kindle forum posters complaining about with its six sizes of a single font?
On the very first page, I encountered a word I wasn’t familiar with (Namaste). I thought I knew what it meant from the context clues, and even had the thought that on the Kindle, I could just highlight it and confirm my guess. But my paper dictionary was in the basement, so I didn’t bother looking it up until I wrote this post. (My hunch was reasonably correct.)
Interface-wise, the paper book is solid, and crashes, lockups, or other malfunctions are rare. I have, however, noted severe stability problems when attempting to read outdoors, especially when it’s windy (which, since I live in Kansas, is pretty much always). Pages start turning themselves, even without me making the “turn page” gesture. Sometimes the book will even lose its memory of my last page read. This is rather annoying, and might even involve a lengthy search for a suitable temporary replacement bookmark. Also, I haven’t tried it, but I suspect that the trick of putting a Kindle in a ziplock bag to read at the beach or in the tub without risk of getting it wet would be impractical with a paper book.
That entire post is really funny and clever, and I think you should read the whole thing. Go ahead, I'll wait.
See? Wasn't it funny? I like clever writing that is funny.
Speaking of The Happiest Days Of Our Lives, I know a non-zero number of people have been waiting very patiently for the special edition to be released by Subterranean Press. I wanted to explain, again, why it's been a year: After the book was announced, I spent almost two months digging through published and unpublished material for the expanded parts of the book, then I spent another month or so rewriting and polishing the stuff that made the cut. After that, I wrote additional introductions and notes to go with each chapter. That was the first delay (and, honestly, I thought it was entirely reasonable, since the book was announced as a pre-order) The biggest delay, and the first serious problem, though, was a software compatibility issue between me and the copy editor. OpenOffice and Word don't track notes the same way, but neither of us knew this until we'd both spent a lot of time working in our respective suites, completely oblivious to the work of the other. Finally, we realized what was wrong, and had to go all the way back to the beginning of the copy editing process the old way, printing the entire manuscript out on paper and making notes in the margins. It had a certain nostalgic value, but it took forever to get all that shit straightened out.
So that process, which should have taken a couple weeks, took close to three months. Then, once we got that all squared away, I had to get a bunch of pictures together, caption them, fact-check the captions with my parents and siblings, then get all that stuff to Subterranean Press. I also held up this part of the process for a couple more weeks while I looked for even more unpublished pictures that neither me nor my mom could find.
Finally, I asked my son Ryan (who is a creative writing student) if he wanted to write an afterword. He said he would, but it would take some time because he's in college and has his own responsibilities. I was willing to wait, because I thought it would be awesome to have his contribution to in the book, and I figured at this point (August) another couple weeks didn't make that big a difference. It ended up taking about 6 or 8 weeks, but I think it will ultimately be worth the delay (please note that I am not an objective source of information in this regard.)
Finally, the manuscript was turned in, the pictures were approved, the layout was all set ... and then the signature pages arrived. I had to sign something like 2500 pages, and it was important to me that each one looked like it was the only one I'd signed. I could have blown through it, of course, and gotten it done in a couple of days, but that would have guaranteed disappointment to everyone who bought the book and waited almost a year to get it. So I limited myself to between 50 and 75 pages at a "session," and it took several weeks to work my way through them all.
Oh, also, keep in mind that during all of these months, I was working on other projects, including several television shows that took me away from the Happiest Days project for weeks at a time.
So all of those delays stacked up on top of each other, until everything was finally finished about six or eight weeks ago. I realize that this is a very long time to wait for something, and I also realize that I've probably killed any chance of doing other special editions with Subterranean Press because this one took so long, but I sincerely believe that it will be worth the wait, because I've seen it, and it's something very special.
Amazon has reduced many of their Fisher Price toys for preschoolers by 37% off or more:- Little People Fairy Treehouse: was $29.99, now $18.99 (37% off)
- Magical Tea For Two was $14.99, now $8.99 (40% off)
- Laugh and Learn Learning Vacuum Cleaner was $23.99, now $14.99 (38% off)
- Learning Mower was $23.99, now $14.99 (38% off)
- Little People Stack 'n Sort Train was $18.99, now $11.99 (37% off)
- Grow With Me Trike (silver and purple) was $34.99, now $19.99 (43% off)
- Amazing Animals Press and Go Animal Parade was $29.99, now $18.99 (37% off)
- Brilliant Basics Musical Roll-Along Pony was $39.99, now $24.99 (38% off)
There are a few interesting things in software development that you’ll generally only learn about by working on “certain” types of applications. Take, for example, the HTTP 414 “Way Too F#%&ing Long” response: there’s no standardized upper limit and many web servers don’t even document how long GET requests may be.
While working with his company's service desk application, Ben noticed a similar type of error message come from SQL Server.
Incorrect syntax near '('.
Some part of your SQL statement is nested too deeply.
Rewrite the query or break it up into smaller queries.
It was Error 191 — another error with no (seemingly) documented upper limit — and was triggered by the following query.
SELECT DISTINCT COUNT(Task.RecId)
FROM Task
WHERE (Task.TaskType = @P514)
AND (Task.Status = @P1)
AND (Task.RecId is not null)
AND ((((((((((((((((((((((((((((((((((((((((((((((((((((
((((((((((((((((((((((((((((((((((((((((((((((((((((
((((((((((((((((((((((((((((((((((((((((((((((((((((
((((((((((((((((((((((((((((((((((((((((((((((((((((
((((((((((((((((((((((((((((((((((((((((((((((((((((
((((((((((((((((((((((((((((((((((((((((((((((((((((
((((((((((((((((((((((((((((((((((((((((((((((((((((
((((((((((((((((((((((((((((((((((((((((((((((((((((
((((((((((((((((((((((((((((((((((((((((((((((((((((
(((((((((((((((((((((((((((((((((((((((((((
(Task.OwnerTeam = @P2)
AND (Task.OwnerTeam = @P3))
AND (Task.OwnerTeam = @P4))
AND (Task.OwnerTeam = @P5))
AND (Task.OwnerTeam = @P6))
AND (Task.OwnerTeam = @P7))
AND (Task.OwnerTeam = @P8))
AND (Task.OwnerTeam = @P9))
AND (Task.OwnerTeam = @P10))
AND (Task.OwnerTeam = @P11))
AND (Task.OwnerTeam = @P12))
AND (Task.OwnerTeam = @P13))
AND (Task.OwnerTeam = @P14))
AND (Task.OwnerTeam = @P15))
AND (Task.OwnerTeam = @P16))
AND (Task.OwnerTeam = @P17))
AND (Task.OwnerTeam = @P18))
AND (Task.OwnerTeam = @P19))
AND (Task.OwnerTeam = @P20))
AND (Task.OwnerTeam = @P21))
AND (Task.OwnerTeam = @P22))
AND (Task.OwnerTeam = @P23))
AND (Task.OwnerTeam = @P24))
AND (Task.OwnerTeam = @P25))
AND (Task.OwnerTeam = @P26))
AND (Task.OwnerTeam = @P27))
AND (Task.OwnerTeam = @P28))
AND (Task.OwnerTeam = @P29))
AND (Task.OwnerTeam = @P30))
AND (Task.OwnerTeam = @P31))
AND (Task.OwnerTeam = @P32))
AND (Task.OwnerTeam = @P33))
AND (Task.OwnerTeam = @P34))
AND (Task.OwnerTeam = @P35))
AND (Task.OwnerTeam = @P36))
AND (Task.OwnerTeam = @P37))
AND (Task.OwnerTeam = @P38))
AND (Task.OwnerTeam = @P39))
AND (Task.OwnerTeam = @P40))
AND (Task.OwnerTeam = @P41))
AND (Task.OwnerTeam = @P42))
AND (Task.OwnerTeam = @P43))
AND (Task.OwnerTeam = @P44))
AND (Task.OwnerTeam = @P45))
AND (Task.OwnerTeam = @P46))
AND (Task.OwnerTeam = @P47))
AND (Task.OwnerTeam = @P48))
AND (Task.OwnerTeam = @P49))
AND (Task.OwnerTeam = @P50))
AND (Task.OwnerTeam = @P51))
AND (Task.OwnerTeam = @P52))
AND (Task.OwnerTeam = @P53))
AND (Task.OwnerTeam = @P54))
AND (Task.OwnerTeam = @P55))
AND (Task.OwnerTeam = @P56))
AND (Task.OwnerTeam = @P57))
AND (Task.OwnerTeam = @P58))
AND (Task.OwnerTeam = @P59))
AND (Task.OwnerTeam = @P60))
AND (Task.OwnerTeam = @P61))
AND (Task.OwnerTeam = @P62))
AND (Task.OwnerTeam = @P63))
AND (Task.OwnerTeam = @P64))
AND (Task.OwnerTeam = @P65))
AND (Task.OwnerTeam = @P66))
AND (Task.OwnerTeam = @P67))
AND (Task.OwnerTeam = @P68))
AND (Task.OwnerTeam = @P69))
AND (Task.OwnerTeam = @P70))
AND (Task.OwnerTeam = @P71))
AND (Task.OwnerTeam = @P72))
AND (Task.OwnerTeam = @P73))
AND (Task.OwnerTeam = @P74))
AND (Task.OwnerTeam = @P75))
AND (Task.OwnerTeam = @P76))
AND (Task.OwnerTeam = @P77))
AND (Task.OwnerTeam = @P78))
AND (Task.OwnerTeam = @P79))
AND (Task.OwnerTeam = @P80))
AND (Task.OwnerTeam = @P81))
AND (Task.OwnerTeam = @P82))
AND (Task.OwnerTeam = @P83))
AND (Task.OwnerTeam = @P84))
AND (Task.OwnerTeam = @P85))
AND (Task.OwnerTeam = @P86))
AND (Task.OwnerTeam = @P87))
AND (Task.OwnerTeam = @P88))
AND (Task.OwnerTeam = @P89))
AND (Task.OwnerTeam = @P90))
AND (Task.OwnerTeam = @P91))
AND (Task.OwnerTeam = @P92))
AND (Task.OwnerTeam = @P93))
AND (Task.OwnerTeam = @P94))
AND (Task.OwnerTeam = @P95))
AND (Task.OwnerTeam = @P96))
AND (Task.OwnerTeam = @P97))
AND (Task.OwnerTeam = @P98))
AND (Task.OwnerTeam = @P99))
AND (Task.OwnerTeam = @P100))
AND (Task.OwnerTeam = @P101))
AND (Task.OwnerTeam = @P102))
AND (Task.OwnerTeam = @P103))
AND (Task.OwnerTeam = @P104))
AND (Task.OwnerTeam = @P105))
AND (Task.OwnerTeam = @P106))
AND (Task.OwnerTeam = @P107))
AND (Task.OwnerTeam = @P108))
AND (Task.OwnerTeam = @P109))
AND (Task.OwnerTeam = @P110))
AND (Task.OwnerTeam = @P111))
AND (Task.OwnerTeam = @P112))
AND (Task.OwnerTeam = @P113))
AND (Task.OwnerTeam = @P114))
AND (Task.OwnerTeam = @P115))
AND (Task.OwnerTeam = @P116))
AND (Task.OwnerTeam = @P117))
AND (Task.OwnerTeam = @P118))
AND (Task.OwnerTeam = @P119))
AND (Task.OwnerTeam = @P120))
AND (Task.OwnerTeam = @P121))
AND (Task.OwnerTeam = @P122))
AND (Task.OwnerTeam = @P123))
AND (Task.OwnerTeam = @P124))
AND (Task.OwnerTeam = @P125))
AND (Task.OwnerTeam = @P126))
AND (Task.OwnerTeam = @P127))
AND (Task.OwnerTeam = @P128))
AND (Task.OwnerTeam = @P129))
AND (Task.OwnerTeam = @P130))
AND (Task.OwnerTeam = @P131))
AND (Task.OwnerTeam = @P132))
AND (Task.OwnerTeam = @P133))
AND (Task.OwnerTeam = @P134))
AND (Task.OwnerTeam = @P135))
AND (Task.OwnerTeam = @P136))
AND (Task.OwnerTeam = @P137))
AND (Task.OwnerTeam = @P138))
AND (Task.OwnerTeam = @P139))
AND (Task.OwnerTeam = @P140))
AND (Task.OwnerTeam = @P141))
AND (Task.OwnerTeam = @P142))
AND (Task.OwnerTeam = @P143))
AND (Task.OwnerTeam = @P144))
AND (Task.OwnerTeam = @P145))
AND (Task.OwnerTeam = @P146))
AND (Task.OwnerTeam = @P147))
AND (Task.OwnerTeam = @P148))
AND (Task.OwnerTeam = @P149))
AND (Task.OwnerTeam = @P150))
AND (Task.OwnerTeam = @P151))
AND (Task.OwnerTeam = @P152))
AND (Task.OwnerTeam = @P153))
AND (Task.OwnerTeam = @P154))
AND (Task.OwnerTeam = @P155))
AND (Task.OwnerTeam = @P156))
AND (Task.OwnerTeam = @P157))
AND (Task.OwnerTeam = @P158))
AND (Task.OwnerTeam = @P159))
AND (Task.OwnerTeam = @P160))
AND (Task.OwnerTeam = @P161))
AND (Task.OwnerTeam = @P162))
AND (Task.OwnerTeam = @P163))
AND (Task.OwnerTeam = @P164))
AND (Task.OwnerTeam = @P165))
AND (Task.OwnerTeam = @P166))
AND (Task.OwnerTeam = @P167))
AND (Task.OwnerTeam = @P168))
AND (Task.OwnerTeam = @P169))
AND (Task.OwnerTeam = @P170))
AND (Task.OwnerTeam = @P171))
AND (Task.OwnerTeam = @P172))
AND (Task.OwnerTeam = @P173))
AND (Task.OwnerTeam = @P174))
AND (Task.OwnerTeam = @P175))
AND (Task.OwnerTeam = @P176))
AND (Task.OwnerTeam = @P177))
AND (Task.OwnerTeam = @P178))
AND (Task.OwnerTeam = @P179))
AND (Task.OwnerTeam = @P180))
AND (Task.OwnerTeam = @P181))
AND (Task.OwnerTeam = @P182))
AND (Task.OwnerTeam = @P183))
AND (Task.OwnerTeam = @P184))
AND (Task.OwnerTeam = @P185))
AND (Task.OwnerTeam = @P186))
AND (Task.OwnerTeam = @P187))
AND (Task.OwnerTeam = @P188))
AND (Task.OwnerTeam = @P189))
AND (Task.OwnerTeam = @P190))
AND (Task.OwnerTeam = @P191))
AND (Task.OwnerTeam = @P192))
AND (Task.OwnerTeam = @P193))
AND (Task.OwnerTeam = @P194))
AND (Task.OwnerTeam = @P195))
AND (Task.OwnerTeam = @P196))
AND (Task.OwnerTeam = @P197))
AND (Task.OwnerTeam = @P198))
AND (Task.OwnerTeam = @P199))
AND (Task.OwnerTeam = @P200))
AND (Task.OwnerTeam = @P201))
AND (Task.OwnerTeam = @P202))
AND (Task.OwnerTeam = @P203))
AND (Task.OwnerTeam = @P204))
AND (Task.OwnerTeam = @P205))
AND (Task.OwnerTeam = @P206))
AND (Task.OwnerTeam = @P207))
AND (Task.OwnerTeam = @P208))
AND (Task.OwnerTeam = @P209))
AND (Task.OwnerTeam = @P210))
AND (Task.OwnerTeam = @P211))
AND (Task.OwnerTeam = @P212))
AND (Task.OwnerTeam = @P213))
AND (Task.OwnerTeam = @P214))
AND (Task.OwnerTeam = @P215))
AND (Task.OwnerTeam = @P216))
AND (Task.OwnerTeam = @P217))
AND (Task.OwnerTeam = @P218))
AND (Task.OwnerTeam = @P219))
AND (Task.OwnerTeam = @P220))
AND (Task.OwnerTeam = @P221))
AND (Task.OwnerTeam = @P222))
AND (Task.OwnerTeam = @P223))
AND (Task.OwnerTeam = @P224))
AND (Task.OwnerTeam = @P225))
AND (Task.OwnerTeam = @P226))
AND (Task.OwnerTeam = @P227))
AND (Task.OwnerTeam = @P228))
AND (Task.OwnerTeam = @P229))
AND (Task.OwnerTeam = @P230))
AND (Task.OwnerTeam = @P231))
AND (Task.OwnerTeam = @P232))
AND (Task.OwnerTeam = @P233))
AND (Task.OwnerTeam = @P234))
AND (Task.OwnerTeam = @P235))
AND (Task.OwnerTeam = @P236))
AND (Task.OwnerTeam = @P237))
AND (Task.OwnerTeam = @P238))
AND (Task.OwnerTeam = @P239))
AND (Task.OwnerTeam = @P240))
AND (Task.OwnerTeam = @P241))
AND (Task.OwnerTeam = @P242))
AND (Task.OwnerTeam = @P243))
AND (Task.OwnerTeam = @P244))
AND (Task.OwnerTeam = @P245))
AND (Task.OwnerTeam = @P246))
AND (Task.OwnerTeam = @P247))
AND (Task.OwnerTeam = @P248))
AND (Task.OwnerTeam = @P249))
AND (Task.OwnerTeam = @P250))
AND (Task.OwnerTeam = @P251))
AND (Task.OwnerTeam = @P252))
AND (Task.OwnerTeam = @P253))
AND (Task.OwnerTeam = @P254))
AND (Task.OwnerTeam = @P255))
AND (Task.OwnerTeam = @P256))
AND (Task.OwnerTeam = @P257))
AND (Task.OwnerTeam = @P258))
AND (Task.OwnerTeam = @P259))
AND (Task.OwnerTeam = @P260))
AND (Task.OwnerTeam = @P261))
AND (Task.OwnerTeam = @P262))
AND (Task.OwnerTeam = @P263))
AND (Task.OwnerTeam = @P264))
AND (Task.OwnerTeam = @P265))
AND (Task.OwnerTeam = @P266))
AND (Task.OwnerTeam = @P267))
AND (Task.OwnerTeam = @P268))
AND (Task.OwnerTeam = @P269))
AND (Task.OwnerTeam = @P270))
AND (Task.OwnerTeam = @P271))
AND (Task.OwnerTeam = @P272))
AND (Task.OwnerTeam = @P273))
AND (Task.OwnerTeam = @P274))
AND (Task.OwnerTeam = @P275))
AND (Task.OwnerTeam = @P276))
AND (Task.OwnerTeam = @P277))
AND (Task.OwnerTeam = @P278))
AND (Task.OwnerTeam = @P279))
AND (Task.OwnerTeam = @P280))
AND (Task.OwnerTeam = @P281))
AND (Task.OwnerTeam = @P282))
AND (Task.OwnerTeam = @P283))
AND (Task.OwnerTeam = @P284))
AND (Task.OwnerTeam = @P285))
AND (Task.OwnerTeam = @P286))
AND (Task.OwnerTeam = @P287))
AND (Task.OwnerTeam = @P288))
AND (Task.OwnerTeam = @P289))
AND (Task.OwnerTeam = @P290))
AND (Task.OwnerTeam = @P291))
AND (Task.OwnerTeam = @P292))
AND (Task.OwnerTeam = @P293))
AND (Task.OwnerTeam = @P294))
AND (Task.OwnerTeam = @P295))
AND (Task.OwnerTeam = @P296))
AND (Task.OwnerTeam = @P297))
AND (Task.OwnerTeam = @P298))
AND (Task.OwnerTeam = @P299))
AND (Task.OwnerTeam = @P300))
AND (Task.OwnerTeam = @P301))
AND (Task.OwnerTeam = @P302))
AND (Task.OwnerTeam = @P303))
AND (Task.OwnerTeam = @P304))
AND (Task.OwnerTeam = @P305))
AND (Task.OwnerTeam = @P306))
AND (Task.OwnerTeam = @P307))
AND (Task.OwnerTeam = @P308))
AND (Task.OwnerTeam = @P309))
AND (Task.OwnerTeam = @P310))
AND (Task.OwnerTeam = @P311))
AND (Task.OwnerTeam = @P312))
AND (Task.OwnerTeam = @P313))
AND (Task.OwnerTeam = @P314))
AND (Task.OwnerTeam = @P315))
AND (Task.OwnerTeam = @P316))
AND (Task.OwnerTeam = @P317))
AND (Task.OwnerTeam = @P318))
AND (Task.OwnerTeam = @P319))
AND (Task.OwnerTeam = @P320))
AND (Task.OwnerTeam = @P321))
AND (Task.OwnerTeam = @P322))
AND (Task.OwnerTeam = @P323))
AND (Task.OwnerTeam = @P324))
AND (Task.OwnerTeam = @P325))
AND (Task.OwnerTeam = @P326))
AND (Task.OwnerTeam = @P327))
AND (Task.OwnerTeam = @P328))
AND (Task.OwnerTeam = @P329))
AND (Task.OwnerTeam = @P330))
AND (Task.OwnerTeam = @P331))
AND (Task.OwnerTeam = @P332))
AND (Task.OwnerTeam = @P333))
AND (Task.OwnerTeam = @P334))
AND (Task.OwnerTeam = @P335))
AND (Task.OwnerTeam = @P336))
AND (Task.OwnerTeam = @P337))
AND (Task.OwnerTeam = @P338))
AND (Task.OwnerTeam = @P339))
AND (Task.OwnerTeam = @P340))
AND (Task.OwnerTeam = @P341))
AND (Task.OwnerTeam = @P342))
AND (Task.OwnerTeam = @P343))
AND (Task.OwnerTeam = @P344))
AND (Task.OwnerTeam = @P345))
AND (Task.OwnerTeam = @P346))
AND (Task.OwnerTeam = @P347))
AND (Task.OwnerTeam = @P348))
AND (Task.OwnerTeam = @P349))
AND (Task.OwnerTeam = @P350))
AND (Task.OwnerTeam = @P351))
AND (Task.OwnerTeam = @P352))
AND (Task.OwnerTeam = @P353))
AND (Task.OwnerTeam = @P354))
AND (Task.OwnerTeam = @P355))
AND (Task.OwnerTeam = @P356))
AND (Task.OwnerTeam = @P357))
AND (Task.OwnerTeam = @P358))
AND (Task.OwnerTeam = @P359))
AND (Task.OwnerTeam = @P360))
AND (Task.OwnerTeam = @P361))
AND (Task.OwnerTeam = @P362))
AND (Task.OwnerTeam = @P363))
AND (Task.OwnerTeam = @P364))
AND (Task.OwnerTeam = @P365))
AND (Task.OwnerTeam = @P366))
AND (Task.OwnerTeam = @P367))
AND (Task.OwnerTeam = @P368))
AND (Task.OwnerTeam = @P369))
AND (Task.OwnerTeam = @P370))
AND (Task.OwnerTeam = @P371))
AND (Task.OwnerTeam = @P372))
AND (Task.OwnerTeam = @P373))
AND (Task.OwnerTeam = @P374))
AND (Task.OwnerTeam = @P375))
AND (Task.OwnerTeam = @P376))
AND (Task.OwnerTeam = @P377))
AND (Task.OwnerTeam = @P378))
AND (Task.OwnerTeam = @P379))
AND (Task.OwnerTeam = @P380))
AND (Task.OwnerTeam = @P381))
AND (Task.OwnerTeam = @P382))
AND (Task.OwnerTeam = @P383))
AND (Task.OwnerTeam = @P384))
AND (Task.OwnerTeam = @P385))
AND (Task.OwnerTeam = @P386))
AND (Task.OwnerTeam = @P387))
AND (Task.OwnerTeam = @P388))
AND (Task.OwnerTeam = @P389))
AND (Task.OwnerTeam = @P390))
AND (Task.OwnerTeam = @P391))
AND (Task.OwnerTeam = @P392))
AND (Task.OwnerTeam = @P393))
AND (Task.OwnerTeam = @P394))
AND (Task.OwnerTeam = @P395))
AND (Task.OwnerTeam = @P396))
AND (Task.OwnerTeam = @P397))
AND (Task.OwnerTeam = @P398))
AND (Task.OwnerTeam = @P399))
AND (Task.OwnerTeam = @P400))
AND (Task.OwnerTeam = @P401))
AND (Task.OwnerTeam = @P402))
AND (Task.OwnerTeam = @P403))
AND (Task.OwnerTeam = @P404))
AND (Task.OwnerTeam = @P405))
AND (Task.OwnerTeam = @P406))
AND (Task.OwnerTeam = @P407))
AND (Task.OwnerTeam = @P408))
AND (Task.OwnerTeam = @P409))
AND (Task.OwnerTeam = @P410))
AND (Task.OwnerTeam = @P411))
AND (Task.OwnerTeam = @P412))
AND (Task.OwnerTeam = @P413))
AND (Task.OwnerTeam = @P414))
AND (Task.OwnerTeam = @P415))
AND (Task.OwnerTeam = @P416))
AND (Task.OwnerTeam = @P417))
AND (Task.OwnerTeam = @P418))
AND (Task.OwnerTeam = @P419))
AND (Task.OwnerTeam = @P420))
AND (Task.OwnerTeam = @P421))
AND (Task.OwnerTeam = @P422))
AND (Task.OwnerTeam = @P423))
AND (Task.OwnerTeam = @P424))
AND (Task.OwnerTeam = @P425))
AND (Task.OwnerTeam = @P426))
AND (Task.OwnerTeam = @P427))
AND (Task.OwnerTeam = @P428))
AND (Task.OwnerTeam = @P429))
AND (Task.OwnerTeam = @P430))
AND (Task.OwnerTeam = @P431))
AND (Task.OwnerTeam = @P432))
AND (Task.OwnerTeam = @P433))
AND (Task.OwnerTeam = @P434))
AND (Task.OwnerTeam = @P435))
AND (Task.OwnerTeam = @P436))
AND (Task.OwnerTeam = @P437))
AND (Task.OwnerTeam = @P438))
AND (Task.OwnerTeam = @P439))
AND (Task.OwnerTeam = @P440))
AND (Task.OwnerTeam = @P441))
AND (Task.OwnerTeam = @P442))
AND (Task.OwnerTeam = @P443))
AND (Task.OwnerTeam = @P444))
AND (Task.OwnerTeam = @P445))
AND (Task.OwnerTeam = @P446))
AND (Task.OwnerTeam = @P447))
AND (Task.OwnerTeam = @P448))
AND (Task.OwnerTeam = @P449))
AND (Task.OwnerTeam = @P450))
AND (Task.OwnerTeam = @P451))
AND (Task.OwnerTeam = @P452))
AND (Task.OwnerTeam = @P453))
AND (Task.OwnerTeam = @P454))
AND (Task.OwnerTeam = @P455))
AND (Task.OwnerTeam = @P456))
AND (Task.OwnerTeam = @P457))
AND (Task.OwnerTeam = @P458))
AND (Task.OwnerTeam = @P459))
AND (Task.OwnerTeam = @P460))
AND (Task.OwnerTeam = @P461))
AND (Task.OwnerTeam = @P462))
AND (Task.OwnerTeam = @P463))
AND (Task.OwnerTeam = @P464))
AND (Task.OwnerTeam = @P465))
AND (Task.OwnerTeam = @P466))
AND (Task.OwnerTeam = @P467))
AND (Task.OwnerTeam = @P468))
AND (Task.OwnerTeam = @P469))
AND (Task.OwnerTeam = @P470))
AND (Task.OwnerTeam = @P471))
AND (Task.OwnerTeam = @P472))
AND (Task.OwnerTeam = @P473))
AND (Task.OwnerTeam = @P474))
AND (Task.OwnerTeam = @P475))
AND (Task.OwnerTeam = @P476))
AND (Task.OwnerTeam = @P477))
AND (Task.OwnerTeam = @P478))
AND (Task.OwnerTeam = @P479))
AND (Task.OwnerTeam = @P480))
AND (Task.OwnerTeam = @P481))
AND (Task.OwnerTeam = @P482))
AND (Task.OwnerTeam = @P483))
AND (Task.OwnerTeam = @P484))
AND (Task.OwnerTeam = @P485))
AND (Task.OwnerTeam = @P486))
AND (Task.OwnerTeam = @P487))
AND (Task.OwnerTeam = @P488))
AND (Task.OwnerTeam = @P489))
AND (Task.OwnerTeam = @P490))
AND (Task.OwnerTeam = @P491))
AND (Task.OwnerTeam = @P492))
AND (Task.OwnerTeam = @P493))
AND (Task.OwnerTeam = @P494))
AND (Task.OwnerTeam = @P495))
AND (Task.OwnerTeam = @P496))
AND (Task.OwnerTeam = @P497))
AND (Task.OwnerTeam = @P498))
AND (Task.OwnerTeam = @P499))
AND (Task.OwnerTeam = @P500))
AND (Task.OwnerTeam = @P501))
AND (Task.OwnerTeam = @P502))
AND (Task.OwnerTeam = @P503))
AND (Task.OwnerTeam = @P504))
AND (Task.OwnerTeam = @P505))
AND (Task.OwnerTeam = @P506))
AND (Task.OwnerTeam = @P507))
AND (Task.OwnerTeam = @P508))
AND (Task.OwnerTeam = @P509))
AND (Task.OwnerTeam = @P510))
AND (Task.OwnerTeam = @P511))
AND (Task.OwnerTeam = @P512))
AND (Task.OwnerTeam = @P513)))
And I’d have to agree. That is nested way too f#%&ing deeply.
Needless to say, Bean didn't want to give it up. "But I don't want to share my baby Jesus!"
"JEEEESUS! BABY JEEESUS!"
And so on... and so on... It got a little crazy.
Anyway, after lunch, I was trying to hurry Bean into her car seat so I could help her buckle up and she was being a trifle difficult. "Mama, I can't buckle the top buckle. I can't reach it." "Mama, my arms are tired." "Mama, I want YOU to do it." Etc., etc., etc.
Finally, my patience were shot and I snapped at her,
"BEAN! If you don't get your arms into those car seat straps right now, I'M GOING TO TAKE BABY JESUS AWAY!"
She got her arms into the straps.
C piped up, "BABY JEEEEEESUS! HAB IT!!!"
Oh good glory.
And, now, I will insert a hammer into my wall.



