Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
 Your new post is loading...
Your new post is loading...
Scoop.it!
Change is an inevitable consequence of development process. During development: new insights surface, requirements change and feature requests arise. All of it has one consequence — we need to change… 
No comment yet.
Sign up to comment
Scoop.it!
A comment on a recent Community blog post raised a question about whether a planned change for the constituent API was a breaking change. This question prompted us to review our definition of breaking... - Blackbaud Community
|
Scoop.it!
Gestion des changements - WikipédiaUn changement a pour objectif de modifier, créer ou supprimer un des composants de l'infrastructure du système d'information, donc un ou plusieurs éléments de configuration. Ce changement doit être réalisé dans le respect des méthodes, procédures et processus standardisés. Il est aussi nécessaire de planifier et approuver la faisabilité avant la mise en œuvre.
Scoop.it!
If you are in the business of creating Quality Software, every day can throw up a surprise or two. How one overcomes these day-to-day challenges often defines the course of your success. Here’s one such challenge we recently faced, we thought of sharing with you. We would love to hear your feedback. Like any good software developer, we tend to treat breaking backward compatibility as a crime and work hard to protect our end-users from facing any consequences resulting from unexpected changes. That said, we live in a world where change is the only constant! It’s always a challenge to absorb the changes.
|
