What is the quality of a good tip?
-
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
-
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
I agree with Marc...
Marc Clifton wrote:
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.
I would say make it more along the lines of an article with a bit more meat to it.
TheArchitectmc∞ wrote:
my ego
I told my ego to shove it when I saw some people voted down my article (it is a book review and could probably have more to it, but hey, it's just my personal thought/opinion of a book). I am not really into the immature voting game some people play, and look more towards making myself happy that I contributed to the community.
"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
-
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
TheArchitectmc∞ wrote:
It's the blue link in the first paragraph
Gotcha.
TheArchitectmc∞ wrote:
this could just be your idea of a joke
Which of these does not belong? FrameworkElement FrameworkContnetElement FrameworkContentElement
TheArchitectmc∞ wrote:
The part where I write '...this does not work...' is the self evident part
Yeah, you explain the problem, but not the solution. But I could be incorrect... I just thought I'd run that by you. I have no intention of voting on your tip/trick as it doesn't really relate to me at this time so I'm not going to read it in-depth (and I don't rate articles I don't read in-depth). Just letting you know my initial impression in case you want to adjust your tip/trick accordingly.
-
I agree with Marc...
Marc Clifton wrote:
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.
I would say make it more along the lines of an article with a bit more meat to it.
TheArchitectmc∞ wrote:
my ego
I told my ego to shove it when I saw some people voted down my article (it is a book review and could probably have more to it, but hey, it's just my personal thought/opinion of a book). I am not really into the immature voting game some people play, and look more towards making myself happy that I contributed to the community.
"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
Paul Conrad wrote:
I agree with Marc...
Yeah, I really wanted to write an article, but I don't have visual Studio set up so I can't compile the demo. I read the MSDN article and understood that this was a good idea for other things other than just a simple copy paste list. I'm also with out computer, can't wait to get a new one. Have to do with what I have access to right now.
Paul Conrad wrote:
I told my ego to shove it when I saw some people voted down my article (it is a book review and could probably have more to it, but hey, it's just my personal thought/opinion of a book). I am not really into the immature voting game some people play, and look more towards making myself happy that I contributed to the community.
Yeah, I wrote a book review also: Writing Great Code Vol 2: Thinking Low-Level, Writing High-Level[^] funny it's my most popular article, I think my 'Big O analyzer' is much better tool / article. I also got a bunch of down votes on it, seemed they either loved it or hated it. Not much in between. As for my ego, well I have given up on being a professional developer in the business world and would like to be an author, I'm starting to write articles here and getting some training on Microsoft .NET to make my writing better. I could probably write a novel better than a technical book, I spend 90% writing and perfecting the code and about 10% writing the article. I should spend more time perfecting the article, that is what will gain the readers interest in what it is I am talking about. Thanks for your candor! ~TheArch :thumbsup:
"Make everything as simple as possible, but not simpler." -- Albert Einstein
-
TheArchitectmc∞ wrote:
It's the blue link in the first paragraph
Gotcha.
TheArchitectmc∞ wrote:
this could just be your idea of a joke
Which of these does not belong? FrameworkElement FrameworkContnetElement FrameworkContentElement
TheArchitectmc∞ wrote:
The part where I write '...this does not work...' is the self evident part
Yeah, you explain the problem, but not the solution. But I could be incorrect... I just thought I'd run that by you. I have no intention of voting on your tip/trick as it doesn't really relate to me at this time so I'm not going to read it in-depth (and I don't rate articles I don't read in-depth). Just letting you know my initial impression in case you want to adjust your tip/trick accordingly.
aspdotnetdev wrote:
TheArchitectmc∞ wrote: this could just be your idea of a joke Which of these does not belong? FrameworkElement FrameworkContnetElement FrameworkContentElement
:laugh: Well being dyslexic and having them all toghether I can see the problem, I'll fix it if possible.
aspdotnetdev wrote:
Yeah, you explain the problem, but not the solution. But I could be incorrect... I just thought I'd run that by you. I have no intention of voting on your tip/trick as it doesn't really relate to me at this time so I'm not going to read it in-depth (and I don't rate articles I don't read in-depth). Just letting you know my initial impression in case you want to adjust your tip/trick accordingly.
Your honesty is well respected... ~TheArch :thumbsup:
"Make everything as simple as possible, but not simpler." -- Albert Einstein
-
Paul Conrad wrote:
I agree with Marc...
Yeah, I really wanted to write an article, but I don't have visual Studio set up so I can't compile the demo. I read the MSDN article and understood that this was a good idea for other things other than just a simple copy paste list. I'm also with out computer, can't wait to get a new one. Have to do with what I have access to right now.
Paul Conrad wrote:
I told my ego to shove it when I saw some people voted down my article (it is a book review and could probably have more to it, but hey, it's just my personal thought/opinion of a book). I am not really into the immature voting game some people play, and look more towards making myself happy that I contributed to the community.
Yeah, I wrote a book review also: Writing Great Code Vol 2: Thinking Low-Level, Writing High-Level[^] funny it's my most popular article, I think my 'Big O analyzer' is much better tool / article. I also got a bunch of down votes on it, seemed they either loved it or hated it. Not much in between. As for my ego, well I have given up on being a professional developer in the business world and would like to be an author, I'm starting to write articles here and getting some training on Microsoft .NET to make my writing better. I could probably write a novel better than a technical book, I spend 90% writing and perfecting the code and about 10% writing the article. I should spend more time perfecting the article, that is what will gain the readers interest in what it is I am talking about. Thanks for your candor! ~TheArch :thumbsup:
"Make everything as simple as possible, but not simpler." -- Albert Einstein
TheArchitectmc∞ wrote:
book review also: Writing Great Code Vol 2: Thinking Low-Level, Writing High-Level
Read it, looks good, voted it good, and ripped into one of the guys who down voted it :-\
"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
-
TheArchitectmc∞ wrote:
book review also: Writing Great Code Vol 2: Thinking Low-Level, Writing High-Level
Read it, looks good, voted it good, and ripped into one of the guys who down voted it :-\
"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
Thanks Guy! :cool:
"Make everything as simple as possible, but not simpler." -- Albert Einstein
-
Never play pool with a guy named after a city.
.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, 2001Wow! I wonder where that comes from because I distinctly remember saying that to someone about 25 years ago but can't for the life of me remember where I heard it. Still an excellent tip though! :)
"I made this letter longer than usual because I lack the time to make it shorter." — Blaise Pascal
-
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
Who cares? If you found it valuable, someone else might also. If a few people who fancy themselves critics want to down-vote your post, it doesn't matter. Someone out here may have learned a lot from your tip and just moved on without voting. That's more of a valuable contribution to the site than many of those who post negative votes ever make. We're running a community here, not an election.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
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
In my experience, only the foremost inch or two count as a tip. The rest is merely supporting structure. A quality tip should be well formed, and be presented in a professional, goal-oriented manner, addressing directly the core issue. It should provide ultimate satisfaction to the recipient with minimum introductory comments, but sufficient commentary to place the recipient in a receptive frame of mind. Repetition can be important, especially for newbies, so the point should be hammered home, so to speak, in order to acheive the desired goal. Feedback from recipients can be effectively utilized to fine tune the presentation for the consumers of your tip.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
In my experience, only the foremost inch or two count as a tip. The rest is merely supporting structure. A quality tip should be well formed, and be presented in a professional, goal-oriented manner, addressing directly the core issue. It should provide ultimate satisfaction to the recipient with minimum introductory comments, but sufficient commentary to place the recipient in a receptive frame of mind. Repetition can be important, especially for newbies, so the point should be hammered home, so to speak, in order to acheive the desired goal. Feedback from recipients can be effectively utilized to fine tune the presentation for the consumers of your tip.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
I think this should be interesting. You may want to know why they call it the "minimal" code site.
Najeeb Shaikh
-
Don't eat yellow snow is a good tip.
-
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
<blockquote class="FQ"><div class="FQA">TheArchitectmc∞ wrote:</div>Not even any spelling errors.</blockquote> I see a few errors. Two missing words, one spelling error, one missing comma, a missing hyphen (I'd let that one slide, maybe CP ate it or there is a difference in norms between where I was taught and where you were). As far as why the tip got low marks, I don't know. It seems decent enough, but maybe it feels more like just presenting facts than really giving a "tip". To me a tip would be more of a unique way of doing something than just regurgitating something you read somewhere. I'm not sure how anyone else would rate it though, so take that for what it's worth.
-
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
Depends on how cute she is, if she's not, or its a dude, then i usually do 20-25 depending on the service. ;) Also depends on how much the meal was, but generally no less that a couple of bucks. And never less that 20%, unless the service was horrible. But I've been known to do up to 50% on some meals. And we are talking about meals right? I can think of other services that you tip.
I like dead people. They are quiet and happy with what you give them.
-
Depends on how cute she is, if she's not, or its a dude, then i usually do 20-25 depending on the service. ;) Also depends on how much the meal was, but generally no less that a couple of bucks. And never less that 20%, unless the service was horrible. But I've been known to do up to 50% on some meals. And we are talking about meals right? I can think of other services that you tip.
I like dead people. They are quiet and happy with what you give them.
When I was a drinker, I would tip very well; sometimes they would come back and tell me it was way too much, I'd say no, go home and take care of your kids and have a nice night. Me an the booze don't mix anymore so I'm going to stick with the 20%.
ecooke wrote:
And we are talking about meals right?
No this was suppose to be a thread about writing tips/tricks here at CP. :laugh:
"Make everything as simple as possible, but not simpler." -- Albert Einstein
-
You're over tipping. It's still 15% for most of us.
There is no such thing as overtipping (IMHO) for good service. I love to eat/drink/be merry and nothing brings down the experience than someone who doesn't care that I'm there to enjoy myself and my company. I say 20% + for good service or better, average service will get them 20% on the nose and when I'm unhappy I'll go 10% to make the point. Regardless of the service I'll never leave no tip at all as I think this is just bad form. So... what was the OP asking again? :~
Mike Devenney
