Note that there are some explanatory texts on larger screens.

plurals
  1. POFeatures/functions that make your app more professional? Coding hobbyhorses
    primarykey
    data
    text
    <p>What <strong>features</strong> do you implement (how) in your PHP web applications because you deem it "<em>more professional</em>" in some way? Or do you have personal nitpicks and code hobbyhorses, specifically small things that might count? Which unsavoured code or minor functionality do you spend an inordinate amount of time on to get <em>right</em>?</p> <p>.</p> <blockquote> <p>Example coding hobbyhorses for Q&amp;A illustration:</p> <p><strong>Configuration data not in database</strong>: Application data != configuration data, which is also a matter of necessity and efficiency.</p> <p><strong>URL fixing</strong>: Normalize all web addresses by appending the trailing slash, even if it's technically not required.</p> <p><strong>Human-readable cookies</strong>: For <em>data privacy</em> I try to avoid opaque session/database handles (for user options, not authorization usage).</p> <p><strong>Content negotiation</strong>: Makes sense for simple variations between e.g. RSS and Atom formats. But I see it infrequently used.</p> <p><strong>No database IDs in UI</strong>: Avoid leaking database internal surrogate keys into URLs. And with ORMs db-internal keys don't even had to leak into business logic.</p> </blockquote> <p>.</p> <h2>Hints (not rules)</h2> <ul> <li>So, which functionality do you believe puts your web application above average?</li> <li>Why is it uncommon?</li> <li>Does it benefit users, but is likewise easy to overlook?</li> <li>More professional and secure coding suggestions are very much on topic. They always are.</li> <li>But the intended <strong>scope of this Q&amp;A</strong> is actually <em>uncommon/unique features</em>, and possibly non-standard and controversial functionality. Big bonus for fascinating.</li> <li>It's also about coding preferences and nitpicks that just happen to materialize in PHP.</li> <li>Don't think too big or too high level. Small functionality counts too. </li> <li>Show code if feasible.</li> <li>Syntax and coding style / paradigms are however mostly off-topic.</li> <li>And let's not argue about usefulness or code quality. <strong>It's purely a featuritis &amp; code survey.</strong></li> </ul> <p><strong>First featuritis research bounty round</strong>: It was difficult to decide on one of the many good ideas. Truth be told, I could only narrow it down to five favorites and left the decision to <code>rand()</code>. And the topic is definitely interesting enough to warrant a second bounty round. After a break. And maybe someone else takes over to refine the scope.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload