What is the quality of a good tip?
-
TheArchitectmc∞ wrote:
Haha, it's 20% in the USA.
Now when did that actually happen? I came to the states about 13 years ago and the wisdom at the time was 15%. Now suddenly everybody seems to be insisting that it's 20% now. I think it's a conspiracy by waiters. :suss:
Yeah, 15% is the norm, but 20% if you think they are offering excellent service, and when you think they make less than minimum wage because of tips... I often just give out the 20....
"Make everything as simple as possible, but not simpler." -- Albert Einstein
-
The content looks good, but I did find a few type-os and spelling problems.
Software Zen:
delete this;Gary Wheeler wrote:
type-os and spelling problems
Darn Mozilla editor... I don't have a computer right now so I have to use these computers in a lab...
"Make everything as simple as possible, but not simpler." -- Albert Einstein
-
I'll just pummel them with my blackjack, or take a swipe at them with my poker. If we have to, we can put them in solitaire-y confinement.
Software Zen:
delete this; -
TheArchitectmc∞ wrote:
What makes a good tip?
No idea. Just post and pray !
Me, I'm dishonest. And a dishonest man you can always trust to be dishonest.
Honestly. It's the honest ones you want to watch out for...Yeah, but it's making my index go down. I thought I wrote a good tip and got a bad 2.67 rating I had a 4.67 rating before that tip and now it droped my overall rating to 3.67 or something.
"Make everything as simple as possible, but not simpler." -- Albert Einstein
-
Okay I don't think this one sucks, it has worth wile content: Building a Bridge...[^] Not even any spelling errors. I looked at yours, they look good. I'll use yours as a guideline. Are you a mentor here on CP John?
"Make everything as simple as possible, but not simpler." -- Albert Einstein
TheArchitectmc∞ wrote:
it has worth wile content:
More proof that any post talking about spelling errors will itself contain a spelling error. Including this one
Graham Librarians rule, Ook!
-
Don't take a knife to a gunfight.
-
Yeah, but it's making my index go down. I thought I wrote a good tip and got a bad 2.67 rating I had a 4.67 rating before that tip and now it droped my overall rating to 3.67 or something.
"Make everything as simple as possible, but not simpler." -- Albert Einstein
So who cares?
-
Don't eat yellow snow is a good tip.
-
So who cares?
Guess just my ego, and who ever I show off my technical writing skills to. I'm making the move to becoming a writer from a full time developer. :doh:
"Make everything as simple as possible, but not simpler." -- Albert Einstein
-
Haha, it's 20% in the USA. ;P
"Make everything as simple as possible, but not simpler." -- Albert Einstein
modified on Tuesday, January 26, 2010 11:41 AM
You're over tipping. It's still 15% for most of us.
-
Guess just my ego, and who ever I show off my technical writing skills to. I'm making the move to becoming a writer from a full time developer. :doh:
"Make everything as simple as possible, but not simpler." -- Albert Einstein
Just ignore the rating. Anyone seriously reading your work should be able to form his own opinion.
-
I'm thinking of writing a tip. My past tips have not gone so well, they don't get a lot of views or votes and the votes are not so great, I don't think the tip is all that bad. I think a tip should be be a short bit of experience you can offer, not a full article. What are your thoughts? What makes a good tip?
"Make everything as simple as possible, but not simpler." -- Albert Einstein
Well, looking at the tip you posted, while I like it and will look up Linq-pad, it's not exactly what people are probably looking for. I think people are more looking for specific tips/tricks for using an app like VS or one of the WPF designers, or maybe a small code snippet showing how to do something cool. For example, I've asked some simple algorithm questions in the past and people have responded with different solutions, including Linq, etc. For example, the follow who answered my question here[^], now that would make for a great tip/trick! Marc
-
Well, looking at the tip you posted, while I like it and will look up Linq-pad, it's not exactly what people are probably looking for. I think people are more looking for specific tips/tricks for using an app like VS or one of the WPF designers, or maybe a small code snippet showing how to do something cool. For example, I've asked some simple algorithm questions in the past and people have responded with different solutions, including Linq, etc. For example, the follow who answered my question here[^], now that would make for a great tip/trick! Marc
Yeah that Tip was not so good, the good one was: WPF: Simple Bridge between a FrameworkElement and a FramworkContentElement[^] This is a much better tip.
"Make everything as simple as possible, but not simpler." -- Albert Einstein
-
Yeah that Tip was not so good, the good one was: WPF: Simple Bridge between a FrameworkElement and a FramworkContentElement[^] This is a much better tip.
"Make everything as simple as possible, but not simpler." -- Albert Einstein
TheArchitectmc∞ wrote:
This is a much better tip.
I noticed that one second--I didn't realize it was in the tips/tricks section. Personally, I found it too long. It was like an article. That got me wondering how to decide whether something is a tip/trick or an article. Marc
-
I multiply the tax by 2 and round up to the nearest dollar.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001Thanks for the tip.
-
LabVIEWstuff wrote:
bridge
I'll trump that and switch to card games. You guys will need a rubber room or might even file suit before I'm done!
Software Zen:
delete this;I must be a dummy not being able to to come up with a Grand Slam
Steve _________________ I C(++) therefore I am
-
Yeah that Tip was not so good, the good one was: WPF: Simple Bridge between a FrameworkElement and a FramworkContentElement[^] This is a much better tip.
"Make everything as simple as possible, but not simpler." -- Albert Einstein
I don't really have any opinion about what makes a good tip/trick, but here are some things I noticed about that specific tip/trick.
Tip/Trick:
Here is the solution as it appears in MSDN for creating a bridge:
Where's the link to MSDN?
Tip/Trick:
FrameWorkElement
Uppercase W is incorrect.
Tip/Trick:
folloing
You must not like W's.
Tip/Trick:
FrameworkContnetElement
Is that related to a botnet?
Tip/Trick:
Here is the workaround in the help class
I didn't really see an explanation of what the workaround does. Self evident, you might say, but my maybe I don't want to try and interpret all that code. You explained what problem it solves, but not how it solves it.
-
I don't really have any opinion about what makes a good tip/trick, but here are some things I noticed about that specific tip/trick.
Tip/Trick:
Here is the solution as it appears in MSDN for creating a bridge:
Where's the link to MSDN?
Tip/Trick:
FrameWorkElement
Uppercase W is incorrect.
Tip/Trick:
folloing
You must not like W's.
Tip/Trick:
FrameworkContnetElement
Is that related to a botnet?
Tip/Trick:
Here is the workaround in the help class
I didn't really see an explanation of what the workaround does. Self evident, you might say, but my maybe I don't want to try and interpret all that code. You explained what problem it solves, but not how it solves it.
aspdotnetdev wrote:
Tip/Trick: Here is the solution as it appears in MSDN for creating a bridge: Where's the link to MSDN?
It's the blue link in the first paragraph: Code for "Create Flexible UIs with Flow Documents And Data Binding"[^]
aspdotnetdev wrote:
Tip/Trick: FrameWorkElement Uppercase W is incorrect.
yes, I am dyslexic, I alleyways goof this one up, the spell check is of no help of course.
aspdotnetdev wrote:
Tip/Trick: FrameworkContnetElement Is that related to a botnet?
Hmm, not sure what you mean, there are two types: FrameworkElements and FrameworkContnetElements. There is about a 20% split between the two types of classes, meaning 40% of the of the 100% that makes up WPF is split between these two base classes. ~err this could just be your idea of a joke, I don't know if I spelled it correctly.
aspdotnetdev wrote:
Tip/Trick: Here is the workaround in the help class I didn't really see an explanation of what the workaround does. Self evident, you might say, but my maybe I don't want to try and interpret all that code. You explained what problem it solves, but not how it solves it.
I thought I made it self evident. It's not possible to add FrameworkContentElements to a FrameworkElement. The article was about building a bridge between the two to allow for copy and paste of a ListItem widget that does not allow copy and paste as a FrameWorkElement, if you use this bridge you can then use the best of both worlds. The part where I write '...this does not work...' is the self evident part. :cool:
"Make everything as simple as possible, but not simpler." -- Albert Einstein
-
You're over tipping. It's still 15% for most of us.
-
Just ignore the rating. Anyone seriously reading your work should be able to form his own opinion.
PIEBALDconsult wrote:
Anyone seriously reading your work should be able to form his own opinion.
Excellent point.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
