Antichesse (o ^ω^ o)
Why are there is so many terms like SR, MR, CR, XL, etc., for the same sustained release medications? Is there regulatory reasons?
La réponse :
MR (modified Release) is the general term for all the drug delivery systems that are deviating from the conventional release pattern, these include all the preparations known as SR, CR, XL. SR (Sustained Release) are those which sustain the release of drug for a specified time period or region of administration these include delivery systems that generally tries to mimics zero order but follows pseudo first order and also those which sustain the delivery in Gastric environment. XL (Extended Release) is delivery systems that extend the release rate of drug for longer period of time without or with generating constant plasma level and follows pseudo first order release mechanism. CR (Controlled Release) are ideal in achieving constant plasma level for longer period of time as these follow zero order kinetic model. So are so many factors that actually correlates with each other so these are mistakenly used in the same manner and also regulatory agencies do not have any of such definition that separates them apart.
Je cite :
Culture
DevOps is mostly about breaking down barriers between teams. An enormous amount of time is wasted with tickets sitting in queues, or individuals writing handoff documentation for the person sitting right next to them. In pathological organizations it is unsafe to ask other people questions or to look for help outside of official channels. In healthy organizations, such behavior is rewarded and supported with inquiry into why existing processes fail. Fostering a safe environment for innovation and productivity is a key challenge for leadership and directly opposes our tribal managerial instincts.
AutomationPerhaps the most visible aspect of DevOps. Many people focus on the productivity gains (output per worker per hour) as the main reason to adopt DevOps. But automation is used not just to save time, but also prevent defects, create consistency, and enable self-service.
MeasurementHow can you have continuous improvement without the ability to measure improvement? How do you know if an automation task is worthwhile? Basing decisions on data, rather than instinct, leads to an objective, blameless path of improvement. Data should be transparent, accessible to all, meaningful, and able to be visualized in an ad hoc manner.
SharingKey the success of DevOps at any organization is sharing the tools, discoveries, and lessons. By finding people with similar needs across the organization, new opportunities to collaborate can be discovered, duplicate work can be eliminated, and a powerful sense of engagement can be created among the staff. Outside the organization, sharing tools and code with people in the community helps get new features implemented in open source software quickly. Conference participation leaves staff feeling energized and informed about new ways to innovate.