Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>That's why an application needs to be easy to expand, and you should be able to easily add-in all the buzzwords.</p> <p>If you have a solid base code, most of the buzzwords are related to the UI (Vista Controls, Ajax, .net, ASP.net 3.5)...</p> <p>You could be running COBOL in the back-end ( I wouldn't).</p> <ol> <li>A new major system is implemented - There's nothing you can do.</li> <li>current IT policies have changed, - The app should be adaptable.</li> <li>users don't like/hate the existing app - why? cosmetic changes in the UI can fix this most of the time.</li> <li>The company you acquired the basic app from, to customize it for your needs has disappeared. - I wouldn't do that, I'd prefer to write it myself.</li> <li>The technology for the existing app is "obsolete" (according to the framework vendor/Microsoft/consultant/industry expert/new IT manager who has management's ear.) - same as the above, if the back-end is solid, you should follow these in the front-end.</li> <li>"We're phasing out (Windows 95/Windows 98/Windows 2000/Windows XP/NT) and we need matching technology in our apps". - a simple compatibility test and minor UI elements solve this.</li> </ol> <p>I'll also say that this is different when you compare in-house to commercial apps, if you're doing an in-house app, change guarantees your job (if you know what you're doing). If you're doing a commercial app, change is an opportunity to make more money, new features would get you upgrades from existing clients and new clients who are looking for the buzzwords, these buzzword could become your advantage when compared to a competitor.</p>
 

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