text:
St.Paul, TX, Allen TX, Community TX, Copeville TX, Dallas TX, Fairview TX, Farmersville TX, Fate TX, Garland TX, Highland Park TX, Josephine TX, Lavon TX, Lucas TX, Murphy TX, Nevada TX, Parker TX, Plano TX,Richardson TX, Rockwall TX, Rowlett TX, Royse City TX, Sachse TX, University Parks TX
75002, 75023, 75024, 75025, 75040, 75041, 75042, 75043, 75044, 75048, 75074, 75075, 75080, 75081,75082, 75087, 75088, 75089, 75093, 75094, 75098, 75121, 75164, 75166, 75173, 75189, 75218, 75225, 75230,75231, 75238, 75240, 75243, 75248, 75251, 75252, 75254, 75442
"Pamela, I wanted to personally write to you regarding the unbelievable and spectacular Christmas arrangement that Christine and her partner put together. This went way beyond my expectations. I can't even put it in words. My wife has not seen it yet and she may just fall to her knees when she gets home. The collaboration and the thought that went into this - and the fact that your team was able to put this together in less than 24 is beyond commitment. What freaking awesome staff members you have. I have over 100 employees and I will be sending this out to all the dudes to encourage them to go stop buy and get their wives and girlfriends something special from Wylie flowers. I'm going to send a picture of this to everyone. I copied Christine into this email and Pamela you should be extremely pleased that she is on your team. Happy Holidays…Thanks again Christine!!!!!!!!!!!!!!!!!!!! Scott" December 19, 2013 - Scott F.
"Hi Pam! The shoe arrived safe and sound today! Thanks so much - I really appreciate it! I'm still interested in getting the Shoe Love Ya Shoe La La, if you come across another one. That's the only one I don't have now! Happy Holidays to you ! Sydney" December 9, 2013 - Sydney B.
"I wanted to tell you Thanks for the great job. It was a special birthday for my wife and you really sent a special and beautiful flower arrangement. Thank You very much. You helped me make it a special day for her and that is what I wanted to do. Thanks Again Roy" December 5, 2013 - Roy
"Hi, I just wanted to send a quick note to tell you THANK YOU from the bottom of my heart for the beautiful arrangement that was made for my Grandfathers service (William D. V.). It was breathtaking! Warmest Regards, Lorrie S." - Novemver 25, 2013
Facebook - Hi Wylie Flower, Rose tagged you in a post. Rose wrote: "I Would like to say THANK YOU to Wylie Flower Shop for the Beautiful flowers that was sent to my Mom's Funeral Service." - November 17, 2013
Facebook - Best Flower shop in the world Hands down" November 14, 2013 - A.B.S.
Facebook - Hi Wylie Flower, Martha tagged you in a post. Martha wrote: "Wylie Flower Shop. Pam, thanks for doing such a beautiful job on my mother-in-laws casket flowers. I could have never imagined they would be so beautiful. Thanks again Martha." - November 10, 2013 - Martha
Facebook - Marjie wrote: "Thank you sweet Pam and my amazing Flower shop Wylie Flower Shop" - October 26, 2013
"thank you so much, she loves them !!" October 18, 2013 - John P.
"Thank you very much! They look amazing as always, y'all have yet to disappoint! Ill place my next order Friday and pick up Saturday. We won't be here for the entire week next week so a Monday deliver will be out. Thank you all again very much! Best Regards, - James" James H.- September 23,2013
"Thank you so much!" September 23, 2013 - Ann S.
"Thank you so much. Y'all made me a hero!" September 16, 2013 - John P.
"Thank you, another wonderful arrangement of dazzling roses." September 16, 2013 - Marvin F.
"Thanks Danny I live in Wylie . But I am working in Hong Kong for 2 years while my family is still in Wylie . So will be using you're service every month and more . You're past service has been great when I've sent flowers or my wife debbie has sent flowers in the past Thank you Chris" September 14, 2013 - Chris T.
"Thank you very much. My step mom just called and said it was absolutely beautiful. I will definitely be back. Thanks again. Kimberly" August 8, 2013 - Kimberly P.
"Thank you, you always provide such good service." July 30, 2013 - Teresa W.
"Thank you so very much for delivering the beautiful flowers to her today. Your service was excellent and the arrangement was perfect, made her very happy. I very much appreciate your customer service and will recommend your store to everyone I know. I look forward to buying from you again. Tony" July 29, 2013 - Tony W.
"Pam, you rock, girl!!!!!! Thanks, Marvin" July 23, 2013 - Marvin F.
"Thank you, my friend loves that arrangement. Nili" July 16, 2013 - Nili K.
"I just wanted to say Thank You for delivering my sister's flowers so promptly today. She called me and said they were beautiful. It made her have a better day and I am truly appreciative for your help. Thank you, Judy" July 12, 2013 - Judy S.
"Thank you so much! She absolutely loved her gift and appreciated the kindness of the person delivering! Diane" May 15, 2013 - Diane G.
"Once again, she loved the flowers and was very ecstatic! Delivery was perfect. Thank you so much" May 11, 2013 - Shelby C.
"Thank you very much. Kerry sent a pix of the beautiful arrangement. I will be calling on you again." May 11, 2013 - Douglass T.
Facebook - Courtney wrote: "Thank you for your "artistic license"...loved the arrangement you put together." May 11, 2013 - Courtney B.
Facebook - Tricia wrote: "I was surprised at work by a beautiful bouquet of flowers yesterday. So beautiful and they made the whole office smell so good!!! Thank you!!!!!" May 11, 2013 - Tricia Y.J.
"Judy and Wanda were greatly impressed by your Marvelous Arrangement. Thank you, Marvin" May 10, 2013 - Marvin F.
"Thank you y'all are awesome!" May 9, 2013 - Myrna P.
"My sister just received her candy basket and loved it! She said it looked very nice, and the man who delivered it was so genuine. Thank you and appreciate your customer service!!" April 30, 2013 - Starr P.
"Thank you! They loved em!" April 24, 2013 - Kyle K.
"Thank you so much! My son just sent pictures and they are beautiful! And besides, my son said that the person that delivered them was so nice! We are so happy to have found you! My other son is Exec. VP of Warner Brothers Pictures and very hard to buy for. Do you have a branch out there that is as good? Thanks again for everything - you are the best and I would be happy to do an ad for you! Penny, Colorado Springs, CO" March 29, 2013 - Penny K
"Got them! Beautiful!" March 22, 2013 - Cindy A.
"Oh my, yes she did!!! It was gorgeous! Thank you so much!! We will. Thanks for making his last day beautiful. Shanna" February 20, 2013 - Shanna M.
"Thank you for your service. Becky sent me a picture of the flowers. They were beautiful. She really enjoyed them. Thank you for making it a morning delivery also. Thank you again, Diane" February 17, 2013 - Diane H.
Facebook - Richard wrote: "Pam, you guys did it again! You guys are fantastic! Thank you!" February 15, 2013 - Richard E.
"Pam Rocks!" February 15, 2013 - Marvin F.
"I can't thank you enough! The flowers were beautiful, the teddy bear was perfect, and it meant so much to my sister on this day that is so hard for her. I am so grateful!!! Thank you! Wendi Baltimore, MD" February 14, 2013 - Wendi S.
"Beautiful as usual." February 12, 2013 - Shirley W.
"Thank you do much for such fast delivery and the phone call confirming and telling me my cousin was delighted! :) on my florist list from now on! Melissa" February 5, 2013 - Melissa G.
"Hello, I want to thank you for your GREAT service! Our niece loved the plant you delivered yesterday. She sent us a photo, BEAUTIFUL! Just what I had in mind. Carol V. Castro Valley, Ca." January 17, 2013 - Carol V.
"The bride's bouquet -- and all the flowers -- were simply beautiful! Thank you so very much, Pam:):):) Karen" Jaunary 3, 2013 - Karen
"Thank you so much. She really loved her delivery." December 29, 2012 - Mark D.
"Cool, thank you! ~Ted, sent from mobile. Please pardon typos and brevity." December 21, 2012 - Ted S.
"I wanted to thank you for the flowers that you're shop delivered to my Grandmother. She loved them!!! ." December 12, 2012 - Tim G.
"Thank you for taking care of this! She loved the flowers." December 7, 2012 - Christine M.
"Thank you so much Pam! I love it!! Thank you & have a great day!" November 8, 2012 - Wendi H.
"Much appreciated! The flowers were delivered within hours of ordering and looked outstanding. I will happily pass along your name to anyone I know in need of a great local florist. Thank you, -Matt" October 3, 2012 - Matt W.
"Dear Pam, Wow, it's BEAUTIFUL...thank you so much! Bev " September 26, 2012 - Bev
"Very lovely. Thank you. " September 22, 2012 - Rose F.
"Thank you he loved loved them. Warm regards, Javier M.
March 24, 2012 - Javier M.
"Thank you. She sent me a picture and they were lovely. I appreciate knowing there is a dependable florist in Wylie that I can use when the occassion calls for flowers.
March 10, 2012 - Geannie N.
THANK YOU for taking the time to explain the situation. My intention was to use a local florist, so I am glad that you filled the order, as the flower cake looks beautiful -- from what I can see on the photo that was sent to me. Thank you!
Thanks for filling the order quickly, and making the delivery right away, too. I will use your florist again for ocassions in your delivery area. God bless, G. Clymire"
March 10, 2012 - G. Clymire
"Thank you for delivering the beautiful flowers today. Timing was PERFECT! Appreciate it."
August 26, 2011 - Staci R.
"Thanks so much for getting the order there early! I really appreciate all the extra effort and great customer service!"
August 14, 2011 - Mary K.
"Pam, Beautiful flowers (as always)! Thanks,Ronni :)"
July 19, 2011 - Ronni F.
"Thank you and she loved it!!! Marilyn"
June 30, 2011 - Marilyn G.
"The funeral arrangements were outstanding. I am never disappointed when I use you. Thank you soo much. Linda"
June 30, 2011 - Linda G.
"thank you. the flowers were just beautiful!"
June 25, 2011 - Jane S.
"Wanted to thank you again. The actual arrangement you sent was beautiful. The one in on the web page doesn't do it justice. Regards, Fred M."
May 18, 2011 - Fred M.
"Pam, The arrangement is beautiful. Thank you for your assistance and for sending the picture. Regards, Frank "
May 12, 2011 - Frank L.
"thanks a lot guys. good job"
May 10, 2011 - Dejon M.
"Dear Pam, Thanks so much! My mom and daughter are both living in Wylie now, but I'm in Arizona. It's so nice to find a local florist who is so easy to deal with -- and your prices are MUCH more reasonable than most others I've found on the internet. Thanks again and I hope you have a happy Mother's day (whether you are a mother or just have one!). Joy, Larry F."
May 7, 2011 - Larry F.
"Thank you so much for taking care of my Mom from afar! Happy Mother's Day to all of you! Have a Blessed Day! "
May 6, 2011 - Angie R.
"Just wanted to advise that the above referenced flower arrangement was received; and my wife was very pleased. Thank You Very Much. Have A Great Weekend. "
May 6, 2011 - Morand H.
"Thank you!! She was soooo impressed. She knew it was from me when the delivery man came to her door, because she knows wylie florist has the best arrangements in town. Her words. Thank you for another great delivery and stellar service. Much appreciated.
May 5, 2011 - Wendy R.
"Hi All at the Wylie Flower Shop! I spoke to Mom last night. She says her flower arrangement is just magnificant! I knew they would be, coming from your shop. Thanks so much for ALWAYS providing the best! It's great to know I can count on you. Sincerely, Judy P."
May 5, 2011 - Judy P.
"Thank you, the flowers were very nice and thank you for putting a star gazer lily in the arrangement.:-D"
May 4, 2011 - Drema S.
"Thank you so much for the excellent customer service. I was really surprised by the level of personal attention given to my order.Thank you!"
April 20, 2011 - Donna M.
"It's me again. Steph sent photos of the Easter baskets and they are fabulous!! Love the bunnies and all the rest you put in for each girl. :) thank you again!"
April 18, 2011 - Susan L.
"Thank yawl very much & looking forword to sending more soon"
April 14, 2011 - David M.
"Thank you for delivering those perfect flowers to my mom. They really lifted her spirits. You all did a wonderful job."
April 10, 2011 - Aaron S.
"Hi!!! Thank you for a beautiful Birthday Arrangement for Ms. R T....she loved it!!! CINDY & Fred."
April 9, 2011 - Cindy G.
"They are absolutely beautiful."
April 5, 2011 - Cynthia R.
"You all are awesome... thanks for making my sister's day SPECIAL... GOD
March 23, 2011 - Linda F.
"Thank you Pam for the delivery confirmation. The birthday gal was thrilled with the arrangement!"
March 21, 2011 - Suzanne M.
"Thank you!!! Everyone thinks you did a wonderful job!!!"
March 11, 2011 - Wendy S.
"Thanks, she loved them"
March 2, 2011 - Russell A.
"Thanks very much for all your help. The flowers were loved :)"
February 24, 2011 - Nathan W.
"Just wanted to thank you for the quick turnaround. They said the flowers were beautiful!"
February 24, 2011 - Sandi S.
"To all at the Wylie Flower Shop, I just want to say Thank You for the amazing job you did on my fathers flowers last Thursday. When I walked into the funeral home Thurday evening, I cried when I saw my flowers/easel spray. They were beautiful and so bright. Many complimented on the wonderful job. My only regret is that I did not get a picture of them. I took a few flowers from the arrangement to have as a keepsake, and the rest were donatee to the battered womens shelter. Thank you again and I will use you when times are better!"
February 21, 2011 - Kristyn R.
"The flowers and arrangement are beautiful!!! Very colorful and cheery. There were used near the on the display table at the funeral services. THANKS!!!"
February 11, 2011 - Debie S.
"Thanks...she sent me a picture of them and they were BEAUTIFUL! I'm so glad I was able to shop "local" for them! I prefer to support local merchants and hope she liked them well enough to order her next flowers for someone from you guys! Kindest Regards,"
February 8, 2011 - Linda F.
"Dear Pam, Once again thanks so much for all you have done over the years for my family. The arrangements for Maxine were perfect. It was so nice to see you again, you are as lovely as ever. Be sure and give your mom another hug for me. I'll be sure and stop by some time and buy you lunch again. You never know when I might be down that way. Don't hesitate to drop me an e-mail once in a while, and I will include my cell number. Take care."
January 23, 2011 - Don B.
"Pam my aunt Janet went by Restland and said Deb;s flowers were beautiful, thank you so much for making them so pretty."
December 29, 2010 - Helen M.
Hi - this is Kathy M. I wanted to tell you how beautiful the basket was that you made for Alma's service. Barbara especially loved the book. Everyone thought that is was really beautiful. Thank you so very much for your personalized service. That also made it very special to know that we were in good hands. God bless you and your family!"
December 28, 2010 - Kathy M.
"Pam, I just wanted to thank you again for making such a beautiful arrangement for my Mom. She went on and on about how beautiful the flowers were and how much she's still enjoying them. Thank you ever so much."
December 28, 2010 - Kim T.
Copyright © 2018 Wylie Flower and Gift Shop
Powered by osCommerce

subset: commoncrawl


text:
January 13, 1958 - March 15, 2013
Campbell Hall, NY
Arthur A. Fenty, Jr. of Campbell Hall, NY, an Oil Burner Technician for Carpenter & Smith of Monroe and a 23-year resident of the area, died March 15, 2013 at Westchester Medical Center, Mt. Pleasant, NY. He was 55 years of age.
The son of the late Arthur A. and Helen Hallahan Fenty, Sr., he was born in New York on January 13, 1958.
He is survived by his wife, Lillian Fenty, at home and her children: Paula Zito of Campbell Hall, NY and Michael Zito of Monroe, NY, along with his grandchildren: Michael, Cole, Michael and Dixie Pearl; his brother, David Fenty of Washingtonville, NY, along with his nieces and nephews.
Visitation will be held on Wednesday, March 27th, during the hours of 5 to 7 p.m. at Flynn Funeral & Cremation Memorial Centers, Inc., 139 Stage Road, Monroe, NY 10950. Services will be held at the funeral home with the Rev. Lisa Worthington officiating. Interment will follow at St. Mary's Cemetery, 2 Fr. Tierney Circle, Washingtonville, NY 10992 on Thursday, March 28th,.
Funeral and Cremation Services are under the direction of Thomas F. Flynn and the staff of Flynn Funeral & Cremation Memorial Centers, Inc., 139 Stage Road, Monroe, NY 10950; for directions to the funeral home or to share an online memorial, please visit www.flynnfh.com .


text:
HARTSVILLE, S.C. – The Coker women's soccer team defeated the Mount Olive Trojans 2-0 on Wednesday (Oct. 16) night at the Coker Soccer Field, in a nonconference meeting.
Freshman Salina Maynard got the scoring started after she received a long cross from Jalynn Fortt, and tapped the pass into the right corner of the Trojan net to give Coker the 1-0 lead. The two teams would battle to end the first half, but the Cobras would head into the break with a one goal advantage.
Mount Olive had a chance to tie the game in the 57th minute of the second half on a breakaway, but a diving save from goalkeeper Lizz Morris prevented the goal to keep the Trojans off the scoreboard. Morris would finish the game with six saves.
The duo of Fortt to Maynard would strike again late in the second half, when Fortt sent a free kick into the box where Maynard was waiting to head the ball into the back of the net to put Coker up 2-0 and preserve the win.
Coker will be back in action this Saturday (Oct. 19) to host Carson Newman in a SAC competition. Kick-off is set for 4:30 p.m.
McDonalds Player of the Game: Salina Maynard.


text:
Spotza Directory « Shopping « Autos
Spot is a free onine business directory offering links to websites across South Africa and the World. Feel free to add your website for FREE by doing a reciprocal link or add your site by paying a monthly listing fee via Paypal. Spot FREE online business directory offers quality links to website and blogs that have great content and valuable information to our users and we only accept the best websites in South Africa and the World.
Copyright © 2018 - Spotza Directory |
Powered by PHP weby software


text:
Fender Mustang Guitars @ Dolphin Music!
The new Fender '65 Mustang guitars are now available here at Dolphin Music. The Mustangs are one of the most legendary and well-loved guitars Fender ever made, being popularized in the early 90's by "alternative rock" bands such as Nirvana (the Mustang was Kurt Cobain's favourite guitar) and Britpop icons such as Graham Coxon (Blur).
But fact is the Mustangs have been quite popular since Fender started making them in the mid-60's, and this new reissue, which is faithful to its original design, serves as a proof of that.
The Mustang features two single coil pickups with an unusual switching configuration, and a unique tremolo arm shared with only its derivative the Jag-Stang. It was originally available in two scale lengths, but the reissue opted for teh most popular of them, the 22 fret 24-inch neck.
24 inches is a relatively short neck, the same as the Fender Jaguar but a full inch and a half shorter than the Stratocaster and three-quarters of an inch shorter than the Gibson Les Paul. The short scale neck makes this guitar perfect for people with small hands, and also enhances the ability to use the tremolo arm for upbends.
This short scale, combined with a unique and extremely direct tremolo arm would make the Mustang a cult guitar in the 1990s. Before that, its relatively low cost and marketing as a student guitar made it an obvious candidate for aftermarket upgrades, particularly pickup changes and also amateur finishes. Its wiring with the original pickups also led itself to custom modifications.
The Mustang has two angled single-coil pickups, each with an adjacent on-off-on switch, and a master tone and volume control.
The Mustang is unusual in having neither a pickup selector nor a circuit selector switch, instead just using the two pickup switches to allow the pickups to be used either singly or in parallel. The second on position reverses the phase of the selected pickup, allowing the pickups to be either in or out of phase when in parallel. This phasing option was also unusual for 1964/65 when they were originally made.
The Mustang introduced the Fender Dynamic Vibrato tailpiece, which together with a floating bridge forms the Mustang trem or 'stang trem system. The floating bridge concept is common to the Fender floating tremolo developed for the Jazzmaster, but on the Mustang the saddles have only a single string slot, while on other Fender guitars there are multiple slots to allow limited adjustment of the string spacing.
The tailpiece was unique when introduced and remains the most unusual feature of the Mustang.
- Model Name '65 Mustang®
- Model Number 027-3706-(Color#)
- Series Classic Series
- Colors (504) Daphne Blue, (505) Olympic White, (554) Dakota Red, (Polyurethane Finish)
- Body Poplar
- Neck Maple, "C" Shape, (Gloss Polyurethane Finish)
- Fingerboard Rosewood, 7.25" Radius (184mm)
- No. of Frets 22 Vintage
- Pickups 2 Mustang Single-Coil Pickups (Neck & Bridge)
- Controls Master Volume, Master Tone
- Pickup Switching On/Off Slider, In/Out Phase Switch for Each Pickup
- Bridge Floating Bridge with "Dynamic" Vibrato Tail-piece
- Machine Heads Fender/Gotoh® Vintage Style Tuning Machines with White Buttons
- Hardware Chrome
- Pickguard 3-Ply White Pearloid on (504) Daphne Blue (554) Dakota Red, 4-Ply Tortoise Shell on (505) Olympic White
- Scale Length 24" (610 mm)
- Width at Nut 1.625" (41 mm)
- Unique Features Vintage Correct Styling that Includes: '65 Mustang Headstock and Bridge Plate Logos, White Tipped Vintage Tuning Machines, Vintage Appropriate Gap Between the Control Plate and the Pickguard
- Strings Super 250R, NPS, #073-0250-006, (.010, .013, .017, .026, .036, .046)
- Accessories None
- Case None


text:
Difference between revisions of "Students for Global Sustainability Wiki"
From OpenWetWare
|Line 1:
|Line 1:
'''*[[SfGS ecoexpo|Submit for EcoExpo now!]]'''
'''*[[SfGS ecoexpo|Submit for EcoExpo now !]]'''
Revision as of 15:04, 9 March 2007
*Submit for EcoExpo now by clicking here!
SfGS Mission Statement
Students for Global Sustainability (SfGS) is a student organization commited to sustainable development and conservation projects on both the global and local levels. SfGS is a chapter of the World Student Community for Sustainable Development (WSC-SD), which is an international partnership of six student communities seeking to promote sustainable development in research, education, and day-to-day collaborations among tomorrow's scientists, engineers and policy-makers.
- 2007 Student Summit for Sustainability: "Taking Action for Global Sustainability"
- Earth Day and EcoExpo - Coming soon in April 2007
- SfGS: Studio!Sus
- How do I use this wikipedia anyway?
More about us
Upcoming events (and other ways to get involved)


text:
Nobody wrote:So Rifraf, is the bolt busted or what?
Ok I've spent hours reading on the subject and the best I can come up with is that most issues are related to tension.
Bearing this in mind and the suggestions here and from wiggle I decided to dig a little deeper into the saddle.
I'm sorry but I didnt take photos but the links I'll add will hopefully add some clarity.
This link:
http://2.bp.blogspot.com/_VY9lef3Ripw/S ... Grease.jpg
shows whats described/labelled "tension shakle".
This link :
http://4.bp.blogspot.com/_VY9lef3Ripw/S ... nParts.jpg
Shows whats described/labelled "nose piece"
This link;
shows their relationship with the "tension bolt"
http://4.bp.blogspot.com/_VY9lef3Ripw/S ... G_1574.JPG
In my saddle for an unknown reason the "shackle" had twisted inside the "nose piece" despite feeling like it was of a decent
amount of preload (tension).
Rather than sitting on the two edges/sides of the "nose piece" the "shackle" was down on one side and into the "nose piece"
twisting the "tension bolt" to one side as per my photos.
I've released all tension and removed the "tension bolt" to examine for damage (none I can see).
I carefully put everything back together taking care to make sure the "shackle" mounts both edges of the nose piece (sitting on the edges) and I've added up what I feel to be an appropriate amount of "tension".
Shame there's not some torque figures to go by curtesy of Brooks but perhaps there's too much variance in the types of leather used.
Hope this all makes sense
Links for pics curtesy of :
http://pedaldamnit.blogspot.com.au/2010 ... anium.html


text:
Adm. Robert J. Papp Jr. leaves an imprint at Coast Guard Academy
New London — The paws were everywhere.
That is what irked Adm. Robert J. Papp Jr. when he stepped aboard the Coast Guard Cutter Papaw in Charleston, S.C., as the ship's new commanding officer in 1986.
The crew had adopted the paw print as an unofficial emblem. Paws were spray painted on the deck, on lockers and on buoys the crew worked on. The ship was once asked to leave a port in Florida after the Navy found paw prints down the side of a destroyer, Papp said.
The previous commander ignored Coast Guard instructions and policies and had been fired, work was behind schedule, standards were low and the crew looked ragged, Papp told the corps of cadets at the Coast Guard Academy Wednesday.
"The first thing I did after taking command is I said, 'I want every damn paw print removed from the ship,' " said Papp, the commandant of the Coast Guard. "And we set about the business of doing that. What I didn't realize was that they liked that, they had become accustomed to that. They took offense to the fact that this new guy they didn't know was coming in and unilaterally giving directions to change what they had been doing for two years."
Papp said he had been arrogant, and even though it was for the right reason — to change the climate on the ship — he encountered tremendous resistance. He said he should have made changes more slowly, set goals, and engaged the chiefs and other officers on board. He said he should have kept the big picture in mind and not have worried so much about the paw prints.
He eventually did do that, and he said he was proud of the ship by the time he left in 1989.
Leadership, at its most basic definition, is accomplishing tasks through other people, Papp said. The hard part, he said, is making them feel happy about what they are doing and inspiring them.
This year's annual leadership address at the academy was Papp's last as the head of the Coast Guard, and unlike any of his previous addresses.
Papp did not have a formal speech prepared. He spoke candidly about the practical lessons he has learned and mistakes he has made during his 39-year career so the cadets will not make the same errors. He showed pictures of his wife, Linda, and three daughters, Lindsay, Caitlin and Jillian, through the years. His family is his greatest success, he said.
"We've had 39 good years. And we have enjoyed every moment of it," he said. "… I've never had a job in my life because I've been able to come and do something that I enjoy, that I love, and that has provided me with all kinds of adventures and thrills and excitement."
Before he retires, Papp hinted he may try to better address alcohol abuse and its role in misconduct because, he said, his previous efforts to do so have failed. He said the issue has been "weighing very heavily" on him, particularly because of the number of sexual assaults that involve alcohol.
"A lot of my admirals right now are encouraging me to do something very significant before I leave," he said. "I don't want to leave as commandant and be remembered as the guy who did away with drinking, or I don't know what it is. I don't know exactly what they want me to institute. I don't want that to be my legacy. But maybe I do. Maybe it's important enough to do that."
He has not decided on any policy changes at this point.
After May 30, when he is relieved as commandant, Papp said he will cheer from the sidelines.
"I love this organization. I love the academy and I love all of you, and that's why I take the time to do this," he said to end his talk.
Several cadets said after it was the best talk Papp has given at the academy.
"You always picture these leaders as perfect at this point in their career, they've never made a mistake," said Zach Kearney, a second-class, or junior, cadet from Virginia. "… He was mentioning the mistakes he made with his crew and with those higher above him. It's good to see someone admit to these mistakes and figure out what he learned from them and tell us this now. If this happens to us, when it happens to us, we know we're not alone."
Sarah Kukich said she liked seeing how someone can balance a successful career and family life.
"He was being so candid and so lively about it," said Kukich, a third-class, or sophomore, cadet from East Lyme.
Jon Heller, who is in charge of instructor development at the Leadership Development Center in New London, said the center uses a series of videos in which Papp talks about his leadership tenets in classes for officers, enlisted members and civilians who work for the Coast Guard. In one, Papp explains the challenges he faced commanding ships.
"It's nice for the commandant to be able to say, 'I thought I knew it all. I had been a successful leader in the past and here's someplace where I hiccupped, took a step back and learned from it,'" he said. "He is a model that way … leaders are always learning and growing."
Papp also visited Norwich Free Academy and the U.S. Naval War College in Newport, R.I., last week. Papp graduated from NFA in 1970, from the Coast Guard Academy in 1975, and from the war college in 1990 with a master's degree in national security and strategic studies.
At NFA, it was a homecoming for Papp, who grew up in Norwich. He had never addressed the students before and could not recall ever visiting.
John Tedeschi, who was an athletic trainer, returned to the school to welcome his former student back. He said tears came to his eyes when he first saw Papp walk into the auditorium Tuesday.
Papp encouraged about 500 11th-graders to give back to their community or to the country by working for the government, serving in the military or finding some other way.
At times, Papp said he wishes he could be a cadet again, so he could do it all over.
Critics pile on after Trump cancels visit to U.S. military cemetery outside Paris
Trump opens WWI armistice visit to France with jab at Macron


text:
Hi-Rel/COTS Oscillator
Delivers industry's highest frequency in smallest package for reliability amid extreme conditions.
HOPKINTON, MA & BALTIMORE, MD – June 7, 2011 – Valpey Fisher Corporation (NASDAQ: VPF) a leading provider of high performance integrated products for timing and frequency control today announced its latest product offering: the VFH3225, the industry's smallest size High Reliability/Commercial off the shelf (COTS) oscillator which offers outstanding performance for military applications. The device delivers frequency stability of ±50ppm over -55°C to +125°C in a miniature 3.2 x 2.5 mm SMD package meeting the military requirements for Group A, B, or C testing in a small form factor for a wide range of military communications applications.
Introduced today and showcased at the Valpey Fisher booth (#1633) at the IEEE IMS 2011 Conference, the VFH3225 offers output frequencies up to 160 MHz in the low-power CMOS output with supply voltages of 3.3V, 2.8V, 2.5V or 1.8V. Typical current consumption is as low as 8 mA and to minimize battery drain the device also has an output enable/disable option. Its miniature size, 3.2 x 2.5 mm, allows for efficient use of board space and product designs expansion.
"Today's demanding military applications require higher frequencies and smaller package sizes," says John Fortune, Director of Sales and Marketing for Valpey Fisher. "The VFH3225 is the only part in the industry with frequencies up to 160MHz in a miniature package that can withstand tough environmental conditions like high temperature, vibration and shock."
Valpey Fisher: Eight Decades of Innovation in Oscillators
Hi-Rel/COTS oscillators are quartz oscillators that work in tough, environmentally challenging applications typically associated with mission-critical military uses.
Valpey Fisher offers a complete line of Hi-Rel/COTS oscillators (XO and VCXO) available in industry standard packages including the latest 3.2 x 2.5mm design. By supporting wide temperature ranges and high frequencies, Valpey Fisher's Hi-Rel/COTS products offer a competitive advantage to our customers when confronted with extreme conditions. Customers worldwide use Valpey Fisher Hi-Rel/COTS products to enable a wide range of applications for military communications, munitions and guidance systems.
Please visit Valpey Fisher's website for more information on our Military and Hi-Rel/COTS products by clicking the link below our logo on this page. Samples are available upon request. Please contact your local representative or email firstname.lastname@example.com for datasheets, samples and pricing.


text:
Talkback: Should Chris Nolan Direct The Twilight Zone?
According to Variety, Christopher Nolan tops the shortlist to helm Warner Bros.' Twilight Zone reboot, but he's not alone on the list of potential candidates; Michael Bay, Alfonso Cuaron, and Rupert Wyatt are also in the mix to direct the big-budget, single-story version based on Rod Serling's original sci-fi television series. Nolan may have an in with producer Leonardo DiCaprio and the studio that released his last five films, not to mention the upcoming The Dark Knight Rises. But should he get the gig?
It might all be much simpler if each director was given a portion of the film to shoot, a la 1983's Twilight Zone: The Movie, which split duties between John Landis, Steven Spielberg, Joe Dante, and George Miller. Then again, probably not; could you see Nolan, Bay, Cuaron, and Wyatt sharing the same bill, let alone working together to create a balanced omnibus film?
Meanwhile, there's the question of each director's upcoming schedule. Nolan and Bay already have other projects on deck, and it'd certainly be refreshing to see Bay go the small-scale route with his Pain & Gain crime pic than take on another huge franchise. Wyatt earned a bump with Rise of the Planet of the Apes, which earned critical acclaim, but would he just go straight into prepping its inevitable sequel?
Which leaves Cuaron. He's certainly got the sci-fi/fantasy chops, with Children of Men, Harry Potter, and the upcoming Gravity under his belt. But is he the right guy for The Twilight Zone?
Chime in below.
• Nolan, others may be slipping into 'THE TWILIGHT ZONE' [Variety's Showblitz]


text:
Reviewed By Tom K (Plainwell, MI) Reviewed for a 2005 Saturn Vue —9/21/2007 2:44 AM
I mounted the mirror on a Saturn Vue with no problems and it worked well. There is a whistling effect caused by wind through the tie-down straps which I stopped by wrapping with electrical tape. Also the plastic clips fall off easily when the mirror is not mounted on the car.


text:
posted by Thom Holwerda on Mon 23rd Apr 2007 22:27 UTC, submitted by linuxbeta
"Stephan Binner, a well-known KDE and openSUSE developer, has released a set of live CDs featuring the latest development snapshot of KDE 4 (screenshots). Unlike the SLAX-based live CD called KLAX, which he used to develop in order to demonstrate new KDE releases, his 'KDE Four Live' images are based on openSUSE. After a large, uncompressed live DVD released earlier in the week, a set of smaller live CDs (compressed with Squashfs) is now also available for download. Don't expect trouble-free computing with these early KDE 4 snapshots, but as demonstration tools designed to give KDE users an early taste of things to come, they aren't too bad. The first alpha build of KDE 4 is scheduled for release early next week."


text:
Search our database of handpicked sites
Looking for a great physics site? We've tracked down the very best and checked them for accuracy. Just fill out the fields below and we'll do the rest.
You searched for "explore-results-all.asp?q=explore-results-all.asp?q=explore-results-all.asp?q=quantum", type: Video
We found 16 results on physics.org and 7 results in our database of sites
(of which 0 are Websites, 7 are Videos, and 0 are Experiments)
Search results on physics.org
Time Twins
Inside Story
Physics Life
Inside Story
What does the 5 sigma mean?
Wanted: Your computer's spare time
What does it take to build, run and interpret results from the LHC
How weird is quantum?
Alien spotting comes down to Earth
Who is Stephen Hawking?
Science Places
Lab in a lorry
The physics of Santa
Recreating the Big Bang
Three alternative ways to charge your iPod
Search results from our links database
Showing 1 - 7 of 7
Showing 1 - 7 of 7
Quantum levitation video
Amazing demonstration of quantum levitation by Tel Aviv University's quantum levitation group.
Quantum Computers Animated
A PhD Comics animation explaining the the principle behind quantum computers that relies on superposition and entanglement.
What is Quantum Mechanical Superposition?
A great explanation video about quantum superposition
Particles and waves: The central mystery of quantum mechanics
A short video from TED-Ed about wave-particle duality.
Doing The Impossible - PHD Animation
A PhD Comics animation explaining the weirdness of the quantum world by examining one experiment.
Richard Feynman - The Douglas Robb Memorial Lectures
Series of video lectures by nobel prize winner Richard Feynman on quantum electrodynamics.
What is the Heisenberg uncertainty principle?
A short TED-Ed video about the Heisenberg uncertainty principle, a major component of the quantum mechanics.
Showing 1 - 7 of 7


text:
If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user
Notice To Airmen (NOTAM)
From SKYbrary Wiki
Revision as of 09:52, 16 June 2009 by Validator1 (Talk | contribs)
|Article Information
|Content source:
|Content control:
A notice to airmen (NOTAM)
A notice to airmen (NOTAM) is a notice containing information concerning the establishment, condition or change in any aeronautical facility, service, procedure or hazard, the timely knowledge of which is essential to personnel concerned with flight operations. (ICAO Annex 11: Air Traffic Services)
NOTAMs are issued by national authorities for a number of reasons, such as:
- Hazards such as air-shows, parachute jumps and glider or micro-light flying;
- Flights by important people such as heads of state;
- Closed runways, taxiways, etc;
- Unserviceable radio navigational aids;
- Military exercises with resulting airspace restrictions;
- Unserviceable lights on tall obstructions;
- Temporary erection of obstacles near airfields (e.g. cranes).
For reasons of conciseness and precision, NOTAMs are encoded, although the code is usually sufficiently self-evident to allow the user to identify a hazard. In aerodrome briefing facilities, NOTAMs are usually posted alongside a map to enable the location of hazards to be easily identified.
NOTAMs are distributed to addressees to whom the information is of direct operational significance, and who would not otherwise have at least seven days' prior notification.
Flight Crew Access to current NOTAMS during pre flight planning may be via an airport flight briefing facility or via an alternative 'tailored access' system provided by their Company which will provide access only to NOTAMS relebant to their intended flight.
Snow conditions are notified, not by NOTAM but by a special message called SNOWTAM. Similarly, volcanic ash is notified as a special message known as an ASHTAM.
Full details concerning the content and distribution of NOTAMs, SNOWTAMs and ASHTAMs are contained in ICAO Annex 15.
Digital NOTAM
The EUROCONTROL Digital NOTAM (xNOTAM) Project, run in cooperation with US FAA, has as an objective the provision of NOTAM information in a format that would make it suitable for automatic processing. This will enable automated systems that support ATC and air navigation to have a more actual view of the aeronautical environment, thus increasing the safety and efficiency of the ATM system.
Related Articles
Further Reading
- ICAO Annex 15: Aeronautical Information Services, Chapter 5 and Appendices 2, 3 & 6.
- EUROCONTROL Digital NOTAM Web site: [1]


text:
Agile Team Meets a Fixed Price Contract
- Share
- |
Read later
Reading List
Fixed price contracts are evil - this is what can often be heard from agilists. On the other hand those contracts are reality which many agile teams have to face. But what if we try to tame it instead of fighting against it? How can a company execute this kind of contract using agile practices to achieve better results with lower risk? This article will try to answer those questions.
So let's start with the contract itself.
Fixed Price, Time and Scope
Fixed price contracts freeze all three magical factors at once – money, time and scope. Are the price and time a problem for agile teams? Well they shouldn't be. In fact, time boxing is common agile practice. Limiting money simply makes time boxing work better.
A real problem with fixed price contracts is the scope, which is fixed in terms of what should exactly be built instead of how much should we build.
Why are clients so obsessed with fixing the scope? We understand that they want to know how much they will pay (who does not want to know that) and when they will get it. The only thing they don't know is what exactly they want to get (even if they insist they do know).
The problem of fixing the scope has its roots in:
- Lack of trust between the contractors
- Lack of understanding about how software development processes work
- Misunderstanding what the scope means
Every fixed price contract has a companion document, the "Requirements Specification" or something similar. This document tries to reduce the risk of forgetting something important and tries to set a common understanding of what should be done to provide an illusion of predictability.
Key wrong assumptions in fixing the scope are:
- The more detail we include in the scope definition up front, the better we understand each other
- Well-defined scope will prevent changes
- A fixed scope is needed to better estimate price and time
Moving from Fixed Scope to Fixed Budget
Now, when we understand that the main conflict between application of agile mindset and a fixed price contract lies in the fixed scope, we can focus on converting the fixed scope into the fixed budget.
This means that instead of providing detailed specification of requirements we need to focus on catching as many of them as possible in the form of user stories. We need to build an initial product backlog which we will try to estimate using the story points technique along with whole-team estimation techniques like planning poker.
First, we need to understand that a higher level of detail in software requirements specification means two completely different things for both sides of a contract. Software companies will usually focus on technical details while the other side is more business oriented. Specifications are usually created by a software company and are usually very protective. This is the place where the three key players come to play.
User stories as a way of expressing requirements are understandable for both clients and vendors. The understanding builds trust and a sense of common vision. User stories are quick to write and quick to destroy, especially written on an index card. They are also feature oriented, so they can provide a good view on the real scope of a project and we can compare them with each other in terms of size or effort.
Story points as a way of estimating stories are harder to explain to the client in the beginning because they are not a common way of expressing the effort. But in return they lower the risk of underestimating the scope. How does this happen? Story points in their nature are relative and focus either on the whole scope or on the groups of stories, while traditional estimation (usually done in man-hours) tries to analyze each end every feature in isolation.
Definition of done is another way of building trust and common understanding about the process and all the future plans for the project. It's usually the first time Clients see user stories and while they may like the way the stories are written, it may be not so obvious what it means to implement a story. Teams who discuss their definition of done with the client know better what are the client's expectations. They also estimate better. In addition, on the client side, the definition of done creates high level criteria for user story acceptance.
For example the definition of done for stories in the newly created web application may introduce such criteria as:
- Tested under IE 7/8, Firefox 3.x and Chrome
- Corresponding section in the "Users Guide" created
Later on the team can put some other, more internal elements of the definition of done, but at the stage of building a contract those general guidelines give an understanding between the Client and the team about what we all want to build within a defined scope.
Hopefully, having our definition of done in mind we will come up with some value defining our scope budget in points. And this value, not the stories that are behind it, is the first thing that should be fixed in the contract. This opens the door for change.
While we have the scope fixed (in terms of points) we still want to embrace the change the agile way. We have the tools (user stories and points) which we can use to compare one requirement with another. This allows us to exchange requirements along the way within a defined scope limit. And if we can stay within that limit, we can also stay within the fixed price and time.
Initial Estimation
The hardest part in preparing a fixed price contract is to define the price and schedule that will be fixed based on the well-defined scope. Let's look how can the team contribute to such a contract with initial project estimation done the agile way.
First, educate. Meet with your client and describe the way you're going to work. We need to tell what the stories are all about, how we are going to estimate them and what is the definition of done. Often we need to do that even earlier when preparing an offer for the client's Request For Proposal (RFP).
The next step is to gather user stories. This can be arranged as a time-boxed session taking no more than 1 or 2 days. This is long enough to find most of the stories forming the product vision without falling into feature creep. At this point it is also very important to discuss the definition of done for stories, iterations and releases with the client.
We need to know:
- The environment in which stories should be tested (like the number of browsers or mobile platforms, or operating systems)
- What kind of documentation is required
- Where should finished stories be deployed so that the client can take a look at them
- What should the client do (i.e. take part in demo session)
- How often do we meet and who participates
- etc.
This and probably many more factors specific to your project will affect the estimation and will set a common understanding about the expectations and quality on both sides. They will also make the estimation less optimistic as it often happens when only the technical aspects of story implementation are considered by the team.
Having discussed with the client a set of stories and a definition of done, we can now start the estimation. This is a quite well-known part of the process. The most important activity here is to engage as many future team members as possible so that the estimation is done collectively. Techniques like planning poker are known to lower the risk of underestimation because of some particular team member's point of view, especially if this team member is also the most experienced-one, which is usually the case when estimations are done be one person. It is also important that the stories are estimated by the people who will actually implement the system.
The Fibonacci-like scale (1, 2, 3, 5, 8, 13, 20, 40, 100) comes in handy for estimating stories in points. Relative estimation starts with finding a set of easiest or smallest stories. They will get 1 or 2 points as a base level for further estimation.
In fact during the initial estimation it is often hard to estimate stories using the lowest values like 1 or 2. The point is, the higher the estimation, the less we know about the story. This is also why estimating in points is easier at this early stage, because it is far easier to tell that a story A is 2x as complicated as story B than to tell that story A will take 25 man-hours to get it Done (remember the definition of done?) and the story B will take 54 hours.
This works well even If we choose 3 or 5 point stories as the base level and if we do that, then it will be easier to break them down into smaller stories later during the development phase. Beware however the stories of 20, 40 or 100 points. This kind of estimation suggests that we know nothing about what is to be implemented, so it should be discussed with the client here and now in a little more detail instead of just happily putting it in the contract.
The result of the estimation is a total number of story points describing the initial scope for a product to be built. This is the number that should be fixed in terms of scope for the contract, not the particular stories themselves.
Fixing the Price and Time
Total number of points estimated based on the initial set of stories does not give us the price and time directly. So how to get them? We need some magic numbers.
We should not be surprised by this as in fixed price contracts there have always been the magic numbers. All estimated values have always been such numbers. Right now we are changing the way we estimate but at the end we also need to predict the future based on the knowledge we have of the past. So what do we need to know? It's the predicted team's velocity.
Lets assume we estimated our stories for a total of 300 points. We need to determine the velocity that our team may have based on:
- The team's velocity on earlier projects
- The number of activities we need to do in our iteration (see the definition of done)
- The ease of communication with a client (of course the ideal and hard to achieve goal is to have a client on site as a part of the team, but usually this is not what we have and clients have different amounts of their time that they are willing to spend with our team) – the less time our clients have for us, the lower our velocity
- Just a feeling we have when looking at the scope (yes, good ol' wishful thinking)
Let's say we have a team of 5 people -- 3 programmers, 1 tester and 1 team leader -- who will communicate with clients and stakeholders as well as any other people outside of the team (like a Scrum Master in a Scrum methodology).
We may now decide that our team will try to achieve a velocity of 20 story points per 2 week iteration. This is our main magic number in the contract. Many factors during the project may affect the velocity, however if the team we're working with is not new, and the project we're doing is not a great unknown for us, then this number might be actually given based on some evidence and observations of the past.
Now we may be facing one of the two constraints that the client could want to impose on us in the contract:
- The client wants the software as fast as we can do it (and preferably even faster)
- The client wants as much as we can do by the date X (which is our business deadline)
Scenario 1
In the first scenario we can determine the predicted time to finish using the formula:
time = (<points> / <velocity>) * <iteration length>
So in our example it would be:
time = (300 pts / 20 pts) * 2 weeks = 30 weeks (or 15 iterations)
If the calculated time is not acceptable then the only factor we can change is the team's velocity. To do that we need to extend the team, however this is not working in a linear way. So doubling the team size will never double its velocity.
Scenario 2
We know that the deadline comes in the next 20 weeks, which are only 10 of our iterations, so we can do only 200 points from the scope. Now it is up to the client to decide what can be removed from the scope without losing the ability to deliver something with the required business value.
Here also (to some extent) we can change the size of the required team to be able to expect higher velocity.
Knowing required team size and target finish time we can finally calculate the main part of the price for the contract – the working time cost:
money = <hrs per iterations> * <no. of iterations> * <people> * <hour price>
In our example we would have:
money = 80 hours * 15 iterations * 4 people * $100= $480,000
So now we have fixed price contract values:
- price - $480,000
- time - 15 iterations (30 weeks)
- scope - 300 story points
Those simplistic calculations are of course just a part of the cost that will eventually get into the contract, but they are also the part that usually is the hardest to define. What we were trying to show here is that the way we work in agile projects can be transferred also to the contract negotiations environment.
There is one more question to deal with. The client asks "why is it so expensive?" This is where negotiations actually start and one thing we want to mention here is that the only factor a software company is able to change is its man-hour cost rate. It is those $100 that we are negotiating. Not the length of our iteration, not even the number of iterations. Our team has no superhero powers and will not start working twice as fast just because we negotiate it this way.
It is the money that we are willing to lose. If we say we can be cheaper it is because we will earn less not because we will work faster.
Tracking Progress and Budget
Now that we have our contract signed (that was easy right?), it is time to actually build the software within the agreed limits. You might have already heard that agile will not solve your problems but it will make them visible. That is why we want to know early how we are doing so that we take proper actions. There is a chance that the magic number (our velocity) from the fixed price contract was a mistake.
Burndown charts are a very common way of tracking progress in many agile projects.
Figure 1 – Planned scope burndown vs. real progress.
They are good to visualize planned progress versus the reality. For example the burndown chart from Figure 1 looks quite good:
We are a little above the planned trend but it does not mean that we made a huge mistake when determining our velocity during the contract negotiations. Probably many teams would like their own chart to look like this. But the problem is that this chart shows only two out of three contract factors – scope and time. So what about money?
Figure 2 – Scope burndown vs budget burndown.
The chart on Figure 2 shows two burndowns – scope and budget. Those two trends are expressed here in percent for the purpose. There is no other way to compare those two quantities calculated (one in story points and the other in man-hours or money spent).
The second chart does not look promising. We are spending more money to stay on track than we expected. This is probably because of using some extra resources to actually achieve the expected team's velocity. So having all three factors on one chart makes problems visible and iteration 4 in this example is where we start to talk with the client before it is too late.
To track the scope and budget this way we need to:
- Track the story points completed (done) in each iteration
- Track the real time spent (in man-hours) in each iteration
- Recalculate the total points in your project into 100% of our scope and draw a burndown based on percentage of the total scope
- Recalculate the budget fixed in the contract (or its part) into a total available man-hours – this is our 100% of a budget – and draw a budget burndown based on percentage of the total budget used so far
In our previous examples we had:
- The scope of 300 story points
- The budget of 30 weeks * 4 people * 40 hours a week = 4,800 man-hours
Those would be our totals. So spending 120 hours to burn 6 story points would mean that we have burned 2% of our scope using 2.5% of our budget.
Embracing Change
We need to get back one more time to the point where we changed fixed scope into fixed budget. The 300 story points from the previous examples allows us to exchange the contents of the initial user story list. This is one of the most important aspects that we want to achieve with a fixed price contract done the agile way.
Agile embraces change, and what we want to do is to streamline change management within the fixed price contract. This has always been the hard part and it still is, but with a little help through changing the focus from the requirements analysis into some boundary limits early in the process, we want to welcome change at any stage of the project.
The difficulty here is to convince the client that stories can be exchanged because they should be comparable in the terms of effort required to complete them. So if at any point client has a new great idea that we can express as some new set of stories (worth for example 20 points) then it is again up to the client if we are going to remove stories worth 20 points from the end of our initial backlog to make a place for the new ones.
Or maybe the client wants to add another iteration (remember the velocity of 20 points per iteration?). It is quite easy to calculate the price of introducing those new stories, as:
money = 1 iteration * 80 man-hours * 4 people * $100 = $24,000
What still is the most difficult in this kind of contracts is when we find out during the project that some stories will take longer than expected because they were estimated as epics and now we know more about them than we did at the beginning. But still this might not always be the case, because at the same time some stories will actually take less. So again tracking during the contract execution will provide valuable information. Talking about the problems earlier helps negotiating as we can talk about actions that need to be taken to prevent them instead of talking about the rescue plans after the huge and irreversible disaster.
Earning Trust
All those techniques require one thing so that they can actually be used with the fixed price contract - trust. But as we know, we cannot earn it just by describing what a great job our team is going to do for our clients.
Agile principles bring one good idea for solving this problem. With every iteration we want to build value for the client. But what is more important, we focus on delivering the most valuable features first. So, the best way to build the trust of a client might be to divide the contract.
Start small, with some pilot of 2 or 3 iterations (which will also be fixed price, but shorter). The software delivered must bring an expected value to the client. In fact it must contain some working parts of the key functionalities. The working software proves that you can build the rest. It also gives you the opportunity to verify the first assumptions about the velocity and eventually renegotiate the next part.
The time spent on the pilot should also be relatively small when compared to the scope left to be done. This way if our clients are not satisfied with the results, they can go away before it is to late and they no longer need to continue the contract and eventually fail the project.
Fixed price contracts are often considered very harmful and many agile adopters say that we should simply avoid them. But most of the time they cannot be avoided, so we need to find ways to make them work for the goal we have, which is building valuable quality software.
Actually, some aspects of fixed factors are even better for agile teams since we are used to working within time boxes and that is exactly what the fixed date in the contract (and also fixed price) are -- just time boxes and boundaries. The only thing that actually bothers us is the scope and with this article we tried to gather together ideas on how to deal with that limit.
The intention of this article was not to suggest that agile is some ultimate remedy for solving the problem of fixed price contracts but to show that there are ways to work in this context the agile way.
About the author
Marcin Niebudek is an entrepreneur and co-owner at Agilers, and creator of tinyPM, a lightweight agile project management tool. Marcin is insanely idealistic about software development and strongly believes in it as a craft. He enjoys experimenting with all flavors of Agile and Lean Development techniques. He also loves to write software, read about software, think about it, and blog about it. Author of an agile blog, "Battle for Agility", which describes agile movement in Polish IT, he is a mostly-Java developer with 8 years of experience in building enterprise systems leveraging all kinds of technologies from a Java EE stack.
Rate this Article
Hello stranger!You need to Register an InfoQ account or Login or login to post comments. But there's so much more behind being registered.
Get the most out of the InfoQ experience.
Tell us what you think
magic numbers
Jay Dub
My experience is that clients not used to working in this manner are very contract-specific - to the point of even putting the features and estimates inside the contract.
Have you used techniques where is movement in the contract for fluctuations in the velocity?
I heard of one organization who wrote a clause that if the team came in over estimate on an iteration, the client would only have to pay 50% of the extra cost, and if they came in under then the client would get 50% of the savings back. I am not sure how this worked in practice but is an interesting approach.
Re: magic numbers
Marcin Niebudek
Of course we can add some restrictions on high velocity changes, but I thing the most important is to keep the contract as simple as possible without to many strict rules which can be gamed later by the team (If I pay a penalty for the velocity loss I'll make it stable anyway, not necessarily due to better planning).
About difficulty of estimating user stories
Tarik Fdil
1 - I think it is very difficult to find the building blocks to the baseline estimates (user story with 1 or 2 points) and then make the relative comparisons. This can be very risky and prone to errors. So we haven't solved the main problem of fixed price contract : wrong estimate of time/price.
2 - Using Fibonnacci numbers seems a little magic for me. We may as well use an increasing sequence of (prime) numbers. The underlying problem doesn't change.
3 - Choosing story points instead of hours x men or functional points does not change the problem of estimation. Moving from one measure to another is a simple matter of conversion.
Re: About difficulty of estimating user stories
Marcin Niebudek
Rusell Pannone posted a very good recipe (at least I like it very much) for estimating seto of stories when you have a low confidence in your velocity. You will find it at Ask About Projects.
As for Fibbonaci numbers or story points in general the actual values do not matter, but their relative nature does. So prime number would be as good for me.
What is important for me in the story points/planning poker tandem is the relativity of points and collaborative way of estimation using poker which represents the teams point of view on the problem complexity, while function points will rather focus on the raw complexity of the problem treating the team as an "average team of N developers".
But of course the method you will choose is up to you. The point is to agree on some total budget (if it's in function points, let it be) and be able keep estimating easily any changes the same way after the project launch, so you can change requirements withing that agreed budget.
Re: About difficulty of estimating user stories
Tarik Fdil
Furthermore, I totally agree on your last paragraph!
Re: magic numbers
C Curl
Where I work we commonly use this approach to agile projects. It works better for clients who really want to know how much the software they want is going to cost them. With a fixed-price contract you end up loading on risk factors to the price, and trying to nail down the details of scope at the contract stage. With target price, or incentive contracts you share the risks and rewards with the clients. You do go into overall scope of the solution in sufficient detail to allow you to estimate it. Both parties have incentives to meet the price, but neither party are unduly punished if it doesn't, and you can avoid much of the blame game should it miss the target. Also, the client has the opportunity to work out the details and change their mind later on (usually on a like-for-like basis - e.g. swapping one 3-point story for another), without incurring hefty fees for raising change requests.
If it's a government procurement project, there are some sure obstacles to derive the "magic number" (a.k.a velocity) using the approaches described in the article. It's unlikely you'll have many meetings with client until the final negotiation stages, the team you're putting to the task will probably not have worked together before (unless you're a very small one client company), and you won't know it's velocity from earlier. Also, although it's a great practice, it may be difficult to get time for the (planned) team to get together to do the estimates if they are working on other projects or for different clients.
Maintenance projects are much simpler in this regard - it's easier to use the existing team's experience with the system to plan the effort and project the velocity.
Fixed price contracts is fixing time, scope, money?
Yves Hanoulle
For me the best explaination of how fixed priced contract could be don in agiel was writing by Pascal Van cauwenberghe
Re: Fixed price contracts is fixing time, scope, money?
Marcin Niebudek
As for fixing all three variables... well it's not something that I can also agree with, but in the other hand (at least in my experience) it's the most common approach to that kind of contracts. So here I also wanted to focus on loosening the "scope" variable and have only two of them fixed.
Re: Fixed price contracts is fixing time, scope, money?
Yves Hanoulle
yes loosening the scope is also what Pascal wrote.
If it is the most common approach, I think that is because people don't know any better.
I still have to meet the first customer that does not agree with what Pascal wrote.
Usually the customers are well aware that fixing all three variables is a disaster waiting to happen.
Re: About difficulty of estimating user stories
David Peterson
Outcomes over features
Kevlin Henney
Contracts comparison
Dandik M
Re: Contracts comparison
Chris Ch
* price - $480,000
* time - 15 iterations (30 weeks)
* scope - 300 story points
be very careful of including the 300 story points as part of the contract because
1) Story Points can be gamed by estimating work to be larger and therefore the team can appear to have increased their velocity;
2) Stories are often re-estimated as we learn more and hence may change and
3) the client (or even worse, management) may start anchoring story points to a dollar figure which is not what you want - according to the values above, 1 story point costs $1,600.
These can have unwanted side effects to the project.
Fix time or scope?
Wes McClure
Doesn't really answer the question
Jim Strange
The article immediately dodges the issue by saying, "don't fix the scope, fix the budget." So you're now dealing with a different type of contract. Nice if you can do it, but it's not really what the article purports to help with.
We all know the problems with operating in an Agile manner under a fixed price contract. Arbitrarily changing the terms of the contract doesn't address the problem, it just changes it to a different problem that we *can* address.
Agile and fixed price
Patrycja Kiełkowicz


text:
WikipediaRead full entry
Ilex /ˈaɪlɛks/, or holly,[1] is a genus of 400 to 600 species of flowering plants in the family Aquifoliaceae, and the only living genus in that family. The species are evergreen and deciduous trees, shrubs, and climbers from tropics to temperate zones worldwide.
The genus Ilex is widespread throughout the temperate and subtropical regions of the world. It includes species of trees, shrubs, and climbers, with evergreen or deciduous foliage and inconspicuous flowers. Its range was more extended in the Tertiary period and many species are adapted to laurel forest habitat. It occurs from sea level to more than 2,000 metres (6,600 ft) with high mountain species. It is a genus of small, evergreen trees with smooth, glabrous, or pubescent branchlets. The plants are generally slow-growing with some species growing to 25 m (82 ft) tall. The type species is the European holly Ilex aquifolium described by Linnaeus.[2]
Plants in this genus have simple, alternate glossy leaves, typically with a spiny toothed, or serrated leaf margin. The inconspicuous flower is greenish white, with four petals. They are generally dioecious, with male and female flowers on different plants.
The small fruits of Ilex, although often referred to as berries, are technically drupes.[3] They range in color from red to brown to black, and rarely green or yellow. The "bones" contain up to ten seeds each. Some species produce fruits parthenogenetically, such as the cultivar 'Nellie R. Stevens'. The fruits ripen in winter and thus provide winter colour contrast between the bright red of the fruits and the glossy green evergreen leaves. Hence the cut branches, especially of I. aquifolium, are widely used in Christmas decoration. The fruits are generally slightly toxic to humans, and can cause vomiting and diarrhea when ingested. However, they are an important food source for birds and other animals, which help disperse the seeds.
Ilex in Latin means the holm-oak or evergreen oak (Quercus ilex). Despite the Linnaean classification of Ilex as holly, as late as the 19th century in Britain, the term Ilex was still being applied to the oak as well as the holly – possibly due to the superficial similarity of the leaves.[4][5] The name "holly" in common speech refers to Ilex aquifolium, specifically stems with berries used in Christmas decoration. By extension, "holly" is also applied to the whole genus. The origin of the word "holly" is considered a reduced form of Old English hole(ġ)n,[6] Middle English Holin, later Hollen.[7] [8] The French word for holly, houx, derives from the Old Low Franconian *hulis (Middle Dutch huls).[9] Both are related to Old High German hulis, huls,[10] as are Low German/Low Franconian terms like Hülse or hulst. These Germanic words appear to be related to words for holly in Celtic languages, such as Welsh celyn, Breton kelen(n) and Irish cuileann. [11]
Several romance languages use the Latin word acrifolium (turned into aquifolium in modern time), so Italian agrifoglio, Occitan grefuèlh, etc. [12]
The phylogeography of this group provides examples of various speciation mechanisms at work. In this scenario ancestors of this group became isolated from the remaining Ilex when the Earth mass broke away into Gondwana and Laurasia about 82 million years ago, resulting in a physical separation of the groups and beginning a process of change to adapt to new conditions. This mechanism is called allopatric speciation. Over time survivor species of the holly genus adapted to different ecological niches. This led to reproductive isolation, an example of ecological speciation. In the Pliocene, around five million years ago, mountain formation diversified the landscape and provided new opportunities for speciation within the genus.
The fossil record indicates that the Ilex lineage was already widespread prior to the end of the Cretaceous period. Based on the molecular clock the common ancestor of most of the extant species probably appeared during the Eocene, about 50 million years ago, suggesting that older representatives of the genus belong to now extinct branches.[13] The laurel forest covered great areas of the Earth during the Paleogene, when the genus was more prosperous. This type of forest extended during the Neogene, more than 20 million years ago. Most of the last remaining temperate evergreen forests are believed to have disappeared about 10,000 years ago at the end of the Pleistocene. Many of the then existing species with the strictest ecological requirements became extinct because they could not cross the barriers imposed by the geography, but others found refuge as a species relict in coastal enclaves, archipelagos, and coastal mountains sufficiently far from the extreme cold and aridity and protected by the oceanic influence.
The genus includes about 400 to 600 species, divided into three subgenera:
- Ilex subg. Byronia, with the type species Ilex polypyrena
- Ilex subg. Prinos, with 12 species
- Ilex subg. Ilex, with the rest of the over 400 species
The genus is distributed throughout the world's different climates. Most species make their home in the tropics and subtropics, with a worldwide distribution in temperate zones. The greatest diversity of species is found in the Americas and in Southeast Asia.
Ilex mucronata, formerly the type species of Nemopanthus, is native to eastern North America.[14] Nemopanthus was treated as a monotypic genus with eight species.[15] of the family Aquifoliaceae, now transferred to Ilex on molecular data;[16] it is closely related to Ilex amelanchier.[17]
In Europe the genus is represented by a single species, the classically named holly Ilex aquifolium, and in continental Africa by this species and (Ilex mitis). Ilex canariensis, from Macaronesia, and Ilex aquifolium arose from a common ancestor in the laurel forests of the Mediterranean. Australia, isolated at an early period, has (Ilex arnhemensis). Of 204 species growing in China, 149 species are endemic. A species which stands out for its economic importance in Spanish-speaking countries is Ilex paraguariensis or Yerba mate. Having evolved numerous species that are endemic to islands and small mountain ranges, and being highly useful plants, many hollies are now becoming rare.
Often the tropical species are especially threatened by habitat destruction and overexploitation. At least two species of Ilex have become extinct recently, and many others are barely surviving.[18]
They are extremely important food for numerous species of birds, and also are eaten by other wild animals. In the autumn and early winter the fruits are hard and apparently unpalatable. After being frozen or frosted several times, the fruits soften, and become milder in taste. During winter storms, birds often take refuge in hollies, which provide shelter, protection from predators (by the spiny leaves), and food. The flowers are sometimes eaten by the larva of the Double-striped Pug moth (Gymnoscelis rufifasciata). Other Lepidoptera whose larvae feed on holly include Bucculatrix ilecella, which feeds exclusively on hollies, and The Engrailed (Ectropis crepuscularia).
Holly can contain caffeic acid, caffeoyl derivatives, caffeoylshikimic acid, chlorogenic acid, feruloylquinic acid, quercetin, quinic acid, kaempferol, tannins, rutin, caffeine, and theobromine.[17][19]
Holly berries can cause vomiting and diarrhea. They are especially dangerous in cases involving accidental consumption by children attracted to the bright red berries.[20] Ingestion of over 20 berries may be fatal to children.[19][20]
Holly leaves if eaten might cause diarrhea, nausea, vomiting, and stomach and intestinal problems.[20]
Holly plants might be toxic to pets and livestock.[21]
Leaves of some holly species are (or were) used by some cultures to make daily tea. Leaves of other species, such as gallberry (I. glabra) are bitter and emetic. [22] In general little is known about inter-species variation in constituents or toxicity of hollies.
Ornamental use[edit]
Many of the holly species are widely used as ornamental plants in temperate/European gardens and parks, notably:
- I. aquifolium (common European holly)
- I. crenata (box-leaved holly)
- I. verticillata (winterberry)[23]
Moreover, many hundreds of hybrids and cultivars have been developed for garden use, among them the very popular "Highclere holly", Ilex × altaclerensis (I. aquifolium × I. perado) and the "blue holly", Ilex × meserveae (I. aquifolium × I. rugosa).[24] Hollies are often used for hedges; the spiny leaves make them difficult to penetrate, and they take well to pruning and shaping.[25]
|This section does not cite any references or sources. (February 2014)
Holly – more specifically the European holly, Ilex aquifolium – is commonly referenced at Christmas time. In many western cultures, holly is a traditional Christmas decoration, used especially in wreaths and illustrations, for instance on Christmas cards. Since medieval times the plant has carried a Christian symbolism, as expressed in the well-known carol "The Holly and the Ivy". However, the association of holly with winter celebrations almost certainly pre-dates Christianity. Druids wore holly wreaths on their heads.
In heraldry, holly is used to symbolize truth.
The Norwegian municipality of Stord has a yellow twig of holly in its Coat-of-arms.
In the Harry Potter novels, holly is used as the wood in the titular character's wand.
Selected species[edit]
- Ilex abscondita
- Ilex acutidenticulata
- Ilex affinis
- Ilex × altaclarensis
- Ilex altiplana
- Ilex amara – Caachira
- Ilex ambigua – Sand Holly
- Ilex amelanchier – Swamp Holly
- Ilex anomala Hook. & Arn. – Kāwaʻu (Hawaiʻi)[26]
- Ilex anonoides
- Ilex aquifolium – European Holly, English Holly, Christ's Thorn
- Ilex aquifolium 'Ferox' – Hedgehog holly
- Ilex aracamuniana
- Ilex argentina
- Ilex arisanensis
- Ilex arnhemensis – Northern Holly (Northern Australia)
- Ilex bioritsensis
- Ilex brachyphylla
- Ilex brasiliensis
- Ilex brevicuspis
- Ilex brevipedicellata
- Ilex buergeri
- Ilex canariensis – Small-leaved Holly, Acebino
- Ilex caniensis
- Ilex cassine – Dahoon Holly, Cassena
- Ilex centrochinensis
- Ilex cerasifolia
- Ilex chamaedryfolia
- Ilex chapaensis
- Ilex chengkouensis
- Ilex chinensis
- Ilex chuniana
- Ilex ciliolata
- Ilex ciliospinosa
- Ilex cognata
- Ilex colchica
- Ilex collina
- Ilex conocarpa
- Ilex cookii – Cook's Holly (Puerto Rico)
- Ilex corallina
- Ilex coriacea – Gallberry
- Ilex cornuta – Chinese Holly, Horned Holly
- Ilex costaricensis
- Ilex cowanii
- Ilex crenata – Japanese Holly, Box-leaved Holly, inutsuge (Japanese)
- Ilex crepitans
- Ilex cyrtura
- Ilex dabieshanensis
- Ilex davidsei
- Ilex decidua Walter – Possumhaw (Eastern United States, Northeastern Mexico)
- Ilex dehongensis
- Ilex dimorphophylla
- Ilex diospyroides
- Ilex dipyrena – Himalayan Holly
- Ilex dumosa
- Ilex ericoides
- Ilex euryoides
- Ilex fargesii
- Ilex fengqingensis
- Ilex fertilis
- Ilex florifera
- Ilex gardneriana (extinct: 20th century?)
- Ilex geniculata
- Ilex georgei
- Ilex gigantea
- Ilex glabella
- Ilex glabra L. A.Gray – Evergreen Winterberry, Bitter Gallberry, Inkberry (Eastern North America)
- Ilex gleasoniana
- Ilex glomerata
- Ilex goshiensis
- Ilex graciliflora
- Ilex grandiflora
- Ilex guaiquinimae
- Ilex guayusa – Guayusa
- Ilex guianensis
- Ilex harrisii
- Ilex hemiepiphytica
- Ilex holstii
- Ilex huachamacariana
- Ilex humboldtiana
- Ilex ignicola
- Ilex illustris
- Ilex integerrima
- Ilex integra – Mochi Tree, Nepal Holly
- Ilex intricata
- Ilex jamaicana Proctor (Jamaica)
- Ilex jauaensis
- Ilex jelskii
- Ilex karuaiana
- Ilex khasiana
- Ilex kingiana
- Ilex kudingcha
- Ilex kusanoi
- Ilex laevigata – Smooth Winterberry
- Ilex lasseri
- Ilex latifolia – Tarajo Holly, tarayō (Japanese)
- Ilex lechleri
- Ilex leucoclada
- Ilex longipes
- Ilex longzhouensis
- Ilex machilifolia
- Ilex maclurei
- Ilex macoucoua
- Ilex macrocarpa
- Ilex macropoda
- Ilex magnifructa
- Ilex maingayi
- Ilex marahuacae
- Ilex marginata
- Ilex margratesavage
- Ilex mathewsii
- Ilex × meserveae
- Ilex microdonta
- Ilex mitis
- Ilex montana Torrey & A.Gray – Mountain Winterberry (Eastern United States)
- Ilex mucronata (L.) M.Powell, Savol., & S.Andrews – Mountain Holly, Catberry (Eastern North America)
- Ilex myrtifolia – Myrtle Holly, Myrtle Dahoon
- Ilex neblinensis
- Ilex nothofagifolia
- Ilex oblonga
- Ilex occulta
- Ilex opaca – American Holly (Eastern United States)
- Ilex ovalifolia
- Ilex palawanica
- Ilex pallida
- Ilex paraguariensis – Yerba mate (mate, erva-mate)
- Ilex parvifructa
- Ilex patens
- Ilex pauciflora
- Ilex paujiensis
- Ilex pedunculosa – Longstalked holly
- Ilex peiradena
- Ilex perado – Madeiran Holly
- Ilex perlata
- Ilex pernyi – Perny's Holly
- Ilex polita
- Ilex praetermissa
- Ilex pringlei
- Ilex pseudobuxus
- Ilex puberula
- Ilex pubescens
- Ilex pubiflora
- Ilex purpurea
- Ilex qianlingshanensis
- Ilex quercetorum
- Ilex quercifolia
- Ilex rarasanensis
- Ilex reticulata
- Ilex rotunda
- Ilex rugosa
- Ilex sclerophylla
- Ilex serrata – Japanese Winterberry
- Ilex sessilifructa
- Ilex shimeica
- Ilex sikkimensis
- Ilex sintenisii (Urban) Britt. – Sintenis' Holly (Puerto Rico)
- Ilex sipapoana
- Ilex socorroensis
- Ilex spinigera
- Ilex spruceana
- Ilex steyermarkii
- Ilex subrotundifolia
- Ilex subtriflora
- Ilex sugerokii
- Ilex sulcata
- Ilex syzygiophylla
- Ilex tahanensis
- Ilex tarapotina
- Ilex tateana
- Ilex taubertiana
- Ilex ternatiflora (extinct: 20th century?)
- Ilex theezans
- Ilex tiricae
- Ilex tolucana
- Ilex trachyphylla
- Ilex trichocarpa
- Ilex tugitakayamensis
- Ilex uraiensis
- Ilex urbaniana – Urban's holly
- Ilex vaccinoides
- Ilex venezuelensis
- Ilex venulosa
- Ilex verticillata (L.) A.Gray American Winterberry (Eastern North America)
- Ilex vomitoria – Yaupon Holly, casseena (Spanish)
- Ilex vulcanicola
- Ilex wenchowensis
- Ilex williamsii
- Ilex wilsonii
- Ilex yunnanensis
- Ilex wugonshanensis
- Ilex yuiana[27]
A contorted hedgehog holly Ilex aquifolium 'Ferox'
Ilex pernyi from west China.
- ^ Sunset Western Garden Book 1995:606–607
- ^ "Index Nominum Genericorum". 2009-02-05.
- ^ "Kew Plants and Fungi". 2012-04-11.
- ^ Shorter Oxford English dictionary, 6th ed. United Kingdom: Oxford University Press. 2007. p. 3804. ISBN 0199206872.
- ^ Abbe, Elfriede Martha (1965). The plants of Virgil's Georgics. Cornell University Press. p. 88.
- ^ Middle English Holin, later Hollen. Skeat, Walter William (1887). Principles of English etymology, Volume 1. London, U.K.: Clarendon Press. p. 371.
- ^ T. F. Hoad, English Etymology, Oxford University Press, 1993 (ISBN 0-19-283098-8), p. 218b.
- ^ Skeat, Walter William (2005). A Concise Etymological Dictionary of the English Language. Cosimo, Inc. p. 244. ISBN 978-1-59605-092-1.
- ^ etymology of "houx" (French)
- ^ Pick, Edward (1869). An etymological dictionary of the French language. Murray. p. 106.
- ^ Skeat, Walter William (1882). An etymological dictionary of the English language. Clarendon Press. p. 269.
- ^ Nettleship, Henry (1889). Contributions to Latin lexicography. Clarendon Press. p. 27.
- ^ Loizeau, P.-A.; Barriera G., Manen J.-F. & Broennimann O. (2005). "Towards an understanding of Ilex L. (Aquifoliaceae) on a World-wide scale". In Friis I., Balslev H.,. Plant diversity and complexity patterns: local, regional, and global dimensions : proceedings of an international symposium held at the Royal Danish Academy of Sciences and Letters in Copenhagen, Denmark, 25–28 May 2003. Biologiske skrifter 55. Kongelige Danske videnskabernes selskab. pp. 507–517. ISBN 978-87-7304-304-2. Retrieved 9 April 2012.
- ^ Germplasm Resources Information Network: Ilex mucronata
- ^ Species PPP-index
- ^ Powell, M., Savolainen, V., Cuénod, P., Manen, J. F., & Andrews, S. (2000). The mountain holly (Nemopanthus mucronatus: Aquifoliaceae) revisited with molecular data. Kew Bulletin 55: 341–347.
- ^ a b Alexandra M. Gottlieb, Gustavo C. Giberti & Lidia Poggio (2005). "Molecular analyses of the genus Ilex (Aquifoliaceae) in southern South America, evidence from AFLP and ITS sequence data". American Journal of Botany 92 (2): 352–369. doi:10.3732/ajb.92.2.352. JSTOR 4123880. PMID 21652411.
- ^ International Union for Conservation of Nature and Natural Resources (IUCN) (2007): 2007IUCN Red List of Threatened Species:Ilex]
- ^ a b "Toxicity of Holly". Retrieved 3 March 2014.
- ^ a b c "HOLLY". webmd.com. Retrieved 3 March 2014.
- ^ "American Holly". aspca. Retrieved 3 March 2014.
- ^ Austin, Daniel F. (2004). Florida Ethnobotany. CRC Press. p. 363.
- ^ RHS A-Z encyclopedia of garden plants. United Kingdom: Dorling Kindersley. 2008. p. 1136. ISBN 1405332964.
- ^ Huxley, A., ed. (1992). New RHS Dictionary of Gardening. Macmillan ISBN 0-333-47494-5.
- ^ Northumbria Police: Security starts at the Garden Gate
- ^ Little Jr., Elbert L.; Roger G. Skolmen (1989). "Kāwaʻu, Hawaiian holly" (PDF). United States Forest Service.
- ^ Ulloa Ulloa & Jørgensen (1993), eFloras.org (2007a, b), IUCN (2007), RBGE (2007), USDA (2007a, b)


text:
Living Rooms with Zones
The living room in my old apartment was small. Upon a recent move, I found myself with a larger living room but the same furniture. The old seating arrangement is staying, but there's now room for something more in the room. Here are a few different living rooms that put to use a little extra space beyond the seating area:
• 1 The living room in Young House Love combines with dining table, chairs, and bench.
• 2 A desk behind the sofa adds a little work space to the main room of the home, via 5 Things to Put Behind a Sofa (Besides a Sofa Table).
• 3 A comfy reading nook in the corner of the living room at Brooklyn Limestone.
• 4 A television and sideboard beyond the seating area of this living room, via Our Best Hide The TV In Plain Sight Tricks.
• 5 A settee behind the sofa provides a little place to relax without being in the main part of this living room from Southern Living.


text:
Neri&Hu Design and Research Office
Rossana Hu is a Founding Partner of Neri&Hu Design and Research Office, a multi-disciplinary international architectural design practice based in Shanghai, China, which won AR Awards for Emerging Architecture 2010 by Architectural Review, UK and was selected as one of the ten firms for Design Vanguard 2009 by Architectural Record, USA. Ms. Hu received a Master of Architecture and Urban Planning from Princeton University, and a Bachelor of Arts in Architecture and Music from the University of California at Berkeley. Before establishing Neri&Hu with her partner Lyndon Neri, Ms. Hu worked for Michael Graves & Associates, Ralph Lerner Architect in Princeton, Skidmore, Owings and Merrill in New York City, and The Architects Collaborative (TAC) in San Francisco.
Rossana Hu received the Perspective Award as one of the '40 under 40' prominent designers shaping Hong Kong and Greater China. Ms. Hu is also a Founding Partner and Creative Executive for Design Republic, a Founding Panel Member of 100% Design Shanghai, and the Regional Advisor for The Atlas of 21st Century Architecture, published by Phaidon Press.
Aside from Architecture and Interiors, together with her partner Mr. Lyndon Neri, Ms. Hu is actively working on a number of industrial design products for various brands in Europe including MOOOI, LEMA, BD Barcelona Design and Meritalia, the latter two were in collaboration with Swarovski's "SWAROVSKI ELEMENTS at Work" project, and Shanghai based brand Stellar Works. They are developing their own product line under the monicker brand 'neri&hu', which was honored to receive the Perspective Awards, the Red Dot Award and I.D. magazine's Annual Design Review Awards. Mr. Neri and Ms. Hu were invited to guest edited the October issue of DI magazine in 2009, which is one of the vanguard architectural publications in China, they also published and edited a book called 'Persistence of Vision'. The book is a beginning of a series of exploration on architecture and urban issues in major cities in China.


text:
Budd Christman with large sedated polar bear - Ursus maritimus.
Bears were measured and tagged for future study.
Image ID: anim0037, NOAA's Ark - Animals Collection
Location: Alaska, Beaufort Sea
Photo Date: 1982 May
Photographer: Captain Budd Christman, NOAA Corps
Category: Mammals/Bear/Polar/
• High Resolution Photo Available
of the U.S. Department of Commerce, National Oceanic & Atmospheric
Adminstration (NOAA),
NOAA Central Library
NOAA Privacy Policy
| NOAA Disclaimer
Last Updated:
November 10, 2017


text:
Project Description
The particulate deposition model developed by The Ohio State University (OSU) in prior University Turbine Systems Research (UTSR) work will be modified to better account for the fundamental physics of particle impact and sticking, including particle and surface properties. Experimental data from OSU's Turbine Reacting Flow Facility (TuRFR) deposition cascade facility will be used to validate the revised model.
The TuRFR facility will be modified to provide for the generation of inlet temperature profile non-uniformities (hot streaks), which will be tracked through the turbine nozzle passage using surface temperature infrared imagery and exit plane temperature measurements. Hot streak evolution and the effect of the hot streaks on deposition will be evaluated. Film cooling will then be added to both the experiments and the computation to evaluate its effect on hot streak migration and deposition. Finally, the model's ability to track hot streak migration will be exercised on a full turbine stage (vane and rotor) using data acquired in the OSU Gas Turbine Laboratory transient turbine test rig. The model will also be used to predict deposition in the rotating configuration, although there will be no experimental validation of deposition in the rotating frame.
Project Benefits
This project will modify the particulate deposition model developed in prior work to better account for the fundamental physics of particle impact and sticking. Turbine aerodynamics and heat transfer research will develop advanced cooling technology that will allow for higher firing temperatures which translate into increased cycle efficiency. Specifically, this project will refine the deposition model to include the evolution and migration of hot streaks and the effects of film cooling on hot streaks and deposition, and validate the data using the Turbine Reacting Flow Facility.
Contact Information
Click to view Presentations, Papers, and Publications


text:
Tune in to ESPN 97.5 FM tonight for a new episode of Soccer Matters with Glenn Davis. The Dynamo broadcaster will chat with Dynamo midfielder Brad Davis and forward Giles Barnes as well as Mexican national team head coach Chepo de la Torre, LA Galaxy analyst Cobi Jones and former Dynamo and current Stoke City defender Geoff Cameron.
Tonight's episode airs from 7-9 p.m. and can be heard on the radio on 97.5 FM or online at www.espn975.com.
The call-in number for the show is 713-780-3776.


text:
2013 Fall Registration for Junior Football
Although its not even Summer yet, its already time to start thinking about football and more specifically for your kids, the 2013 South Dakota Junior Football League.
South Dakota Junior Football is an instructional participation tackle football program for area youth in 2nd though 8th grade. This organization was established in 1969 by a number of Sioux Falls business leaders and parents who wanted their children to better learn and understand the game of football before entering high school.
The Sign-ups begin Friday April 26th, 2013.
Teams are aligned into four divisions: Rookie Division is made up of 2nd graders, Pee Wee Division is made up of 3rd and 4th graders, Junior Division is made up of 5th and 6th graders, and Senior Division is made up of 7th and 8th graders. All players are placed on teams by address with other players from the same neighborhood.
All teams play a 6 game regular season schedule and are guaranteed 2 playoff games. Games are played on the 9 South Dakota Junior Football fields in the new Sanford Youth Sports Complex in NW Sioux Falls and on the 2 fields at the Yankton High School.
For more information and to sign your child up, visit sdjuniorfootball.com for more information.


text:
At Dayton Superior, we're serious about concrete construction supplies. To us, they're not just what we sell, they're a reflection of who we are. Our 17,000+ products are tough, tested and high performing, just like the people who stand behind them. Today, we are one of the leading suppliers to the global non-residential concrete construction industry. Accessories…chemicals…forming…paving. All the concrete solutions you need, all in one place.
At our new Innovation Center, we develop, test and market products at an industry-leading pace. We invent new products as market and construction needs evolve. Our engineering and sales teams are the most experienced in the industry. Even our customer support is a step ahead, offering mobile apps, online support and 70+ customer service advisors ready to serve you.
自1924年成立以来, 作为家族拥有的代顿控股 & 海岸公司, 我们从来没有停止发展。我们购买了西蒙斯 ® 由代顿高级 — 现在一个100年的旧品牌 — 在1997年和收购16家公司在整个二十世纪九十年代, 以扩大我们的服务线。尽管2008-09 的经济低迷受挫, 代顿比以往任何时候都更加强大, 重新致力于了我们创立的企业素质。
The new World Trade Center Towers. The Tappan Zee Bridge. The Panama Canal. Trump Ocean Club. The Amazon.com Fulfillment Center. Our story is indelibly linked with these and more than a million other structures around the world, thanks to a quality standard that we believe in so strongly, it's part of our name. Dayton Superior.


text:
What's Your Skeletal System IQ?
Taken 896 times44 Comments Share
This Quiz has 12 questions.0% complete
The human body's amazing architecture is built around our unique skeletal system. How much do you really know much about the bones and joints that make up our internal infrastructure? Take the quiz and find out!


text:
: Science
Sell your diamonds now.
View Single Post
Join Date: Aug 2011
Casino cash: $100
Originally Posted by
yeah, it is.
that's why I laugh at idiots who spend 6 months salary on an engagement ring or any other diamond for that matter. One of the biggest scams of all time and people still fall for it.
I got my wife an engagement ring that cost 2 euros. We were on the beach in Italy, and this dude was making jewelry. So I gave him a couple coins, bought the ring, and proposed.
Any woman who needs you to spend $5,000 on a piece of shit rock isn't worth marrying. I'm not saying that any girl who wants a diamond ring isn't worth it, but if it's a deal breaker for her, then that should be a deal breaker for you.
I have argued soooo much with my friends about this, but why the **** would you give one of the worst companies on earth any more money? What does it prove? You love her so much you'll spend money on nothing? How about donating $5,000 to cancer research in her name? Oh, I'm sorry... she can't trot that around at happy hour?
How about spending that money on furniture for your house? Because guess what? Nothing says "I plan on spending all of my time with you" like a giant comfy couch and 50 inch plasma. Your man ain't goin NOWHERE, honey.
But no... let's give some more money to a company that is only thinly differentiated from slavery to honor a "tradition" that is only decades old, and created by that same company.
What a racket.
Posts: 9,547
View Public Profile
Find More Posts by saphojunkie


text:
*Offer valid online only at www.volcom.co.uk or www.volcom.eu for the purchase of any Men's or Women's jacket from
the Fall-Winter 2018 collection and while stock lasts.
Limited to one beanie per order
(excluding of Good deals category and Snow collection).
Sweep Beanie - Navy
Sweep Beanie - Navy
Belgium, Italy, Luxembourg, Netherlands and Portugal
9€ Standard Shipping
12€ Express Shipping
Denmark, Finland, Ireland and Sweden
15€ Standard Shipping
20€ Express Shipping
- Machine Knit Acrylic
Full Specs
- Machine Knit Acrylic