Red text is the default mechanic in UI design to indicate importance (which is why it's used for errors so often).
Asterisks are the default choice for indicating required input.
Avoid flashing, and other garish-looking visual mechanics.
If this extends beyond a one-time inquiry, you should look at reading some good GUI books, like Don't Make Me Think: A Common Sense Approach to Web Usability and Designing Web Usability, both seminal books in the field.
You should get yourself a copy of both Don't Make Me Think and The Non-Designer's Design Book for your base knowledge/insight.
From there, it's much easier for you to dissect and analyze the layouts you already know and like, and recreate them for your own amusement.
edit: To mitigate misunderstanding, the point I'm trying to make is that you probably don't need as many good examples of nice layouts, if you know what to look for. For example, I can be shown a thousand haute couture dresses, and I still couldn't make one myself, because I don't know what to look for.
As Steve Krug recommends in Don't Make Me Think, get rid of the question marks that pop in the user's head when they come to your site. If it is confusing it isn't likely to be helpful.
Although an interesting concept, in this context I think it is more confusing than useful. If I see "answered 18 mins ago" and "answered 17 mins ago" I have a perfect frame of reference. Also this is something I see on many other sites so it does not require me to learn anything new.
On the other hand if I see two comments that contain "5 mins later" and "6 mins later" I don't have a clear frame of reference. The first might be after the original question, but the other? Is it 6 minutes after that previous comment? Or 6 minutes after the original question, thus one minute after the other comment? Finally, this isn't what you typically see on a site so there will be a moment of "huh?" follow by either "wtf?" or "cool!". Not a reaction that should be left to chance.
This is going to sound cliched, but the best way is to start your own company or project from scratch and apply the concepts you learn from these resources.
Here are some "bestsellers", apart from http://www.amazon.com/Design-Everyday-Things-Donald-Norman/d...
* Don't make me Think: http://www.amazon.in/Dont-Make-Me-Think-Usability/dp/0321344...
* Objectified: http://www.amazon.com/The-Hard-Thing-About-Things/dp/0062273...
* The Startup of You: http://www.thestartupofyou.com/
* Build an audience before you launch the product - like 37Signals, Jeff Atwood and Joel Spolsky, Hubspot
* Traction Book: http://tractionbook.com/
* Be Creative - Each startup is different. There's no silver bullet
The sales course by Steli Efti: http://close.io/free-sales-course/
Dave McClure: https://www.youtube.com/results?search_query=dave+mcclure+st...
Founder Interviews, stories:
* PandoMonthly: https://www.youtube.com/results?search_query=pandomonthly
* Stanford ECorner: ecorner.stanford.edu
Also make wireframes before you code, when something is complicated -- or when you're starting out, for virtually any UI. Use Omnigraffle Pro, and you can also use Graffletopia's website to find stencils, e.g. Bootstrap Stencils. Or use Easel.io.