this post was submitted on 25 Sep 2023
13 points (69.7% liked)
Programming
17362 readers
203 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's a decimal floating point specifier with a precision sub-specifier.
https://cplusplus.com/reference/cstdio/printf/
Example with pi.
This answer makes me so angry like revisiting trauma from learning programming. I just remember asking questions early on and getting answers more confusing that are even harder to parse
If you bothered to read the documentation, which exists in abundance on the web, in many books, in the built-in manuals of various operating systems and dev tools, and which I also linked in my answer, you would see a full explanation with clear examples.
But you can't be bothered with any of that, and instead expect other people to spend their time writing custom tutorials just for you?
Your anger is misplaced. Please consider taking a walk.
When you ask people questions about their field of knowledge, and they don't know you, it's reasonable for their answers to assume you know the rudimentary basics. (Just as it would be reasonable for a fourth-year group to assume a that a stranger asking them questions has at least taken the first-year class.) Asking beyond your level of experience is not necessarily bad, but you should be ready to describe what you don't understand about the answer, so that people can either elaborate with a helpful level of detail or send you to a forum more appropriate for your needs. For example:
!learn_programming@programming.dev
Nobody asked you to spend your time helping people out on Lemmy, if you don't want to do it, then don't do it. There's plenty of people here who are happy to do that.
And I don't think it is reasonable to expect people to understand the basics. If they did, then they wouldn't have asked.
If we assumed everyone asking a question knows nothing at all of the surrounding topic, and responded at length addressing every related detail instead of what was asked, our answers would be tedious, and often annoying. It's called overexplaining (among other things). It's usually better to tailor the answer to the cues given by the person asking, and let them ask more questions if necessary.
OP didn't ask about the basics. They clearly know them already, as we can see from the language and specificity of their question. I was happy to answer and provide a link for deeper detail.
But then someone else came along who apparently knew less than OP did, and decided express anger at me for not preemptively guessing and catering to their unstated special needs, in an answer that wasn't intended for them in the first place. That was incredibly entitled and rude.
I'm even angrier now.
Go touch some gr... Oh, you are touching grass already??
Just touching some Poaceae
Which part of that is confusing to you? We can help make it easier to understand.
Edit: Oh, this isn't even OP.
The confusion is you just provided sample code showing how
"%.2f"
works - you didn't answer the question which was what does that sequence of characters actually mean? What does the%
do. What does the.
do. What does the2
do. What does thef
do.OP needs to know the answer to all of those.
OP got the answer to those in another comment, I'm asking what part they need help understanding in this link. Also, I didn't provide the link.
Edit: Nevermind, I mistook the comment for being OP.
Its not confusion to me, I get what it is. Its the style of answer. Its like if you see a dog, ask what it is and someone answers Canis lupus familiaris.
There's no grokking that. You either know or you don't. If they're asking what .2f then lots of answers here do a good job describing that it formats the value to two decimal places. We can all do something with that at any level.
Saying its a crombopulater sub cablator is much harder to process. It just seems like an answer thats likely to make the person to have to ask more questions or frustrated
...and gives you a link to the Wikipedia page about dogs.
It's not a good answer in the sense that they did not do the work of copying and rephrasing the content of the website they linked, you have to do some of the work yourself. But it's a very thorough answer that gives you all the information you need about formatting. Including examples of pretty much exactly the question OP asked.
I'm not looking for meta level criticism of this style of advice, I'm trying to ask OP what was confusing on this page and help them learn how to read this page specifically. I'm not saying OP should be able to understand this page. I'm not saying this style of advice is acceptable or not.
Edit: Nevermind, I thought OP posted that comment.