I went to the Central Region graduation today. Word was out in the puppy community, thanks to a face book post by daughter Jenn. The puppy raisers who know I am headed to team training were as excited as I am. These marvelous people never cease to amaze me.
The Kings turned in Roscoe today. He'll be missed. The same Roscoe who tried to steal the Thanksgiving Turkey carcass out of the kitchen trash. "Well the lid was up and it was there and I was there and......." ROSCO NO!!! "But I was getting it for Ella" Yea right.
Design Automation Grump
A hangout for those of us involved in design automation in all of it's flavors. Why Grump? Just ask some of my former co-workers. 'Sides he is my favorite character.
Friday, February 15, 2013
Design Automation is going to the dogs
Well, DA Grump has retired(mostly) effective January 2013. I'll still keep my hand in Solidworks and design automation but I'm looking forward to lounging in comfy clothes or so I thought. More on that in a bit. I was thinking about taking down this blog but I have decided to re-purpose it instead.
Awhile back I was convinced by my daughter Jennifer, who has been a puppy raiser for Canine Companions, to apply for a hearing dog. So I did and was evaluated, accepted and placed on the waiting list. Wednesday 13 Feb(Ash Wednesday) I received the e-mail inviting me to team training starting on the 25th of March. I accepted( like I was going to say no). So I have decided to blog about my experience while going through the preparation and training process.
The first irony: Nathan (aka Nashville) raised by Marty Cavour will be in that class. I worked with Nathan in puppy class. Nathan won that round. I wanted a rematch but he turned in before that could happen. Looks like I have to go to California for the rematch.
Plane & car rental reservations made. Waiting for more information from Northwest. 34 day and a wake up but who's counting.
Awhile back I was convinced by my daughter Jennifer, who has been a puppy raiser for Canine Companions, to apply for a hearing dog. So I did and was evaluated, accepted and placed on the waiting list. Wednesday 13 Feb(Ash Wednesday) I received the e-mail inviting me to team training starting on the 25th of March. I accepted( like I was going to say no). So I have decided to blog about my experience while going through the preparation and training process.
The first irony: Nathan (aka Nashville) raised by Marty Cavour will be in that class. I worked with Nathan in puppy class. Nathan won that round. I wanted a rematch but he turned in before that could happen. Looks like I have to go to California for the rematch.
Plane & car rental reservations made. Waiting for more information from Northwest. 34 day and a wake up but who's counting.
Wednesday, January 26, 2011
Solid Works World 2011 is over :-(
This has been a fast 4 days. Saw a lot, learned a lot and am ready to head home. The swag is in the suitcase and I'm going to have to use one of the backpacks for the over flow. I had a session today with the product development group on the new equation interface that previewed today and that is all I can say for now. Next task is to get the presentation posted and wait for the results of the critiques.
Saturday, January 22, 2011
San Antonio
I'm HERE @ Solidworks World. Settled in the hotel, saw some of San Antonio, getting excited about tomorrow.
Tuesday, January 18, 2011
Solidworks World 2011
SWW 2011 in 3 days. I've been asked to participate in round table discussions all day Sunday and product testing on Wednesday. First round table is on Design Automation. ;-}}} I'm starting to get excited.
Wednesday, December 8, 2010
Soildworks World
DA Grump has had the good fortune to be selected as a presenter at SWW 2011. The presentation currently scheduled for 1:30 on Monday. It compares 4 different automation methods, 2 for personal use (macros & Driveworks Express) and two enterprise tools (KBMax & Rulestream). If you are at SWW2011, stop by and say hi!
Tuesday, September 21, 2010
My pointy haired boss is too cheap to buy software. He wants me to write an Automation tool
Give him this
14 Reasons to write my own product configurator.
1. I am a masochist any enjoy abuse.
2. I wish to spend the rest of my life living and breathing macro code and bask in the knowledge that the company is paying me big $ and benefits to do this instead of spending a couple of $k for a piece of software.
3. Job security, no single person will be able to understand my code.
4. I can quit here and get more money from some other stupid company for doing the exact same thing.
5. I will be unable to be an engineer.
6. I will create the results that where specified in the documentation only to discover that was not the result that was desired.
7. I am prepared to assume responsibility for the correct functioning of my code after any or all of the following events
a. The IT department change network software ( including anti-virus)
b. The IT department moves network drives.
c. IT decides to migrate from 32bit to 64 bit.
d. Microsoft changes operating systems
e. Solidworks/Autocad release an update
f. Visual basic changes format
8. The company releases new product designs before the old ones are configured and want them available for the next advertising campaign
9. I will spend days writing code just to prove that what somebody wants what can’t be done. Like automation of drawing cleanup.
10. Someone will want to combine two extremely different product configurators. ( reference Item 9)
11. Everybody will leave an automation planning meeting agreeing to the same thing but already planning the strategy that will get them what they want, not what they agreed to. I will enjoy the abuse this creates(ref Item 1)
12. I will thank my company for putting me in this position, because I used to drink for no particular reason, now I have a reason.
13. Support the drug companies Prozac, valium, cymbalta etc.sale are down.
Stress tests and heart caths are fun
Subscribe to:
Posts (Atom)