Blog

New Idea: Post Release Improvements (Web Development)


Sections-of-Website-Solutions-icon[1]This is my idea about a "task category" I termed as "Post Release Improvements" or PRI for short, some already used this term so I won't claim I invented it. I define this as tasks that improves the system, but, without accomplishing such tasks, the system will still work, but with lower quality. Such tasks can be done later, after the release/launch of the application. This will enable development to succeed or "fail faster"; Meaning you would be on the right direction faster.

Examples

Performance: caching, priority based selection, performance based selection, trimming unnecessarily fetched data. Security : login requirements, password validation, IP restriction, content encryption. Update oriented: xml sitemaps, data backup auto-saving. Randomness:  random proxies, random ad Usability: canonicalization of URLs by redirection, additional navigations You might even consider having static pages first; This will allow early seo indexing of the page; Enabling preparation of the design layout, while developing the dynamic nature of the pages. On ADD Framework, a PHP framework I'm working on, static pages can be done with controller-less resources (view only)

Warnings

This calls for wisdom: developers must be careful to discern which of the deprioritizing will actually save time; as it may slow down the overall development like if resulting to unbearable loading speed of a web page, which will make testing a bad experience. For public websites:
  • on-page SEO probably should not be categorized as such, because it may affect future search ranking
  • security features like logins probably shouldn't be skipped.

Identification: Hashtag comments

To identify PRI on the code, I have this another related idea (so I won't go in depth with it) I call hashtag comments; like #todo and #PRI e.g.
#todo #PRI make this is really return random;
random_string() {
   return "yuioiuytuiopbvbnm,lkjfguiop";
}

Conclusion

On every system development we indeed have things that we skip, but what do we call them? Maybe we could have an official term for it, like "Post Release Improvement" as this article suggests. I hope this idea helped on this matter. Happy developing. Shalom.

Comments (0)


Add a Comment





Allowed tags: <b><i><br>Add a new comment:


A Few Accomplishments

Integer eu ante ornare amet commetus vestibulum blandit integer in curae ac faucibus integer non. Adipiscing cubilia elementum integer. Integer eu ante ornare amet commetus.

Possibly broke spacetime

Integer eu ante ornare amet commetus vestibulum blandit integer in curae ac faucibus integer adipiscing ornare amet.

Terraformed a small moon

Integer eu ante ornare amet commetus vestibulum blandit integer in curae ac faucibus integer adipiscing ornare amet.

Snapped dark matter in the wild

Integer eu ante ornare amet commetus vestibulum blandit integer in curae ac faucibus integer adipiscing ornare amet.

Contact Me

Integer eu ante ornare amet commetus vestibulum blandit integer in curae ac faucibus integer non. Adipiscing cubilia elementum integer. Integer eu ante ornare amet commetus.