Aug 31, 2009 (CIDRAP News) – Egyptian authorities have reported two more H5N1 avian influenza cases, both in children, raising the country’s total for this year to 34, the World Health Organization (WHO) reported today.Both patients have been treated with oseltamivir (Tamiflu) and are in stable condition, the WHO said.One is a 14-year-old girl from Damitta governorate who fell ill on Aug 21 and was hospitalized 2 days later. The other patient is 2-year-old girl from Menofyia governorate. She became ill Aug 23 and was admitted to a fever hospital Aug 26, the agency said.The WHO said investigations indicated that both girls had contact with dead and/or sick poultry.Meanwhile, the Egypt-based Web site Strengthening Avian Influenza Detection and Response (SAIDR) reported that sampling triggered by the human case in Menofyia detected the virus yesterday in some household chickens. SAIDR said two other poultry outbreaks were also found yesterday, in Fayoum and Beheira governorates.Of the 34 human H5N1 cases in Egypt this year, 4 have been fatal. The country has had a total of 85 cases and 27 deaths since the avian flu virus arrived in 2006, according to the WHO.With the latest cases, the WHO’s global H5N1 count reached 440 cases with 262 deaths.See also:Aug 31 WHO report on Egypt H5N1 caseshttp://www.who.int/csr/don/2009_08_31/en/index.html
Topics : Google Jambi BRG PeatlandRestorationAgency peatland peatland-restoration forest-fires-2019 forest-fires forest-fires-in-Indonesia Log in with your social account Facebook Forgot Password ? LOG INDon’t have an account? Register here The Peatland Restoration Agency (BRG) has called on the public to support its efforts to restore peatland areas in the province of Jambi, where land clearing and fires cause trillions of rupiah in environmental damage and impact people’s livelihoods.BRG official Myrna A. Safitri said the agency needed help from locals for its program to gradually restore peatlands amid limited funding provided by the government.“Peat areas that have been damaged over the past few decades cannot be repaired in one or two years. But, with the support of the local community, we are optimistic that the damaged areas can be restored,” she said on Wednesday.Since 2017, the agency had been focusing on the regencies of West Tanjung Jabung, East Tanjung Jabung and Muarojambi in Jambi, as those three were particularly prone to forest and land fires. Those regencies also saw lots of lan… Linkedin
Take into consideration the recent realization of missteps by the U.S. Department of Corrections, which accidentally released more than 3,200 prisoners over a span of 12 years in Washington state due to an unaddressed software glitch. Considering the U.S. keeps a detailed record on the 2.2 million individuals incarcerated, that’s a lot of data to manage, and this was just in one state. In this situation, some officials knew it was happening but failed to take some practical steps to eliminate the core problem. This resulted in a complete breakdown of the system and the release of potentially dangerous criminals back into society.While it does take some elbow grease, IT managers must take the appropriate steps to measure not just the output of the data in systems, but also the structural quality of systems. Uncovering vulnerabilities in critical systems unveils possible issues that will disrupt services, impact customer satisfaction, and negatively impact the company’s brand before they take hold. By establishing an application reliability benchmark, managers can see if systems have stability and data integrity issues before they’re deployed into production, meaning secure data, 24×7 uptime, and happy customers.Identify technical debtTechnical debt refers to the accumulated costs and effort required to fix problems that remain in code after an application has been released. CAST Research Lab estimates the technical debt of an average-sized application is $1 million, and according to Deloitte, more CIOs are turning their attention to technical debt to build business cases for core renewal projects, prevent business disruption, and prioritize maintenance work.Despite the heightened awareness of technical debt, many businesses still struggle to correctly estimate it and make the use case to business decision makers. When it comes to Big Data, technical debt can be exacerbated by the enthusiasm and urgency that often comes with closing a deal and merging two companies together.To overcome this, IT mangers should task development teams to configure structural quality tools to measure the cost of remediation and improvement of core systems. This includes the code quality and structural quality of both buy-side and sell-side applications.Structural quality measures can identify code and architectural defects that pose risks to the business when not fixed prior to a system release. These represent carry-forward defects whose remediation will require effort charged to future releases. Code quality addresses coding practices that can sometimes make software more complex, harder to understand and more difficult to modify—a major source of technical debt.Equipped with real-world estimates of technical debt (including the remediation and validation of code defects), businesses can accurately work this into their M&A strategy, reducing profits lost on fixing problems by tacking them on the front end.Understanding that an objective view of technology assets plays a key role in driving value is the first step to a successful merger or acquisition. It’s not enough to simply slap on a fresh coat of paint; real success can only be achieved by taking care to ensure the support beams are as solid as the foundation. Software is like a house: It must be adequately maintained, or peeled-up wallpaper might reveal the foundation underneath isn’t as stable as you thought. This metaphor brings new meaning to mergers and acquisitions as companies on the buy side and the sell side attempt to patch up rough edges that might ruin a deal.When buying a house in a seller’s market, one might forego the due diligence of an engineering inspection of the electric, plumbing, roof, and ceiling joists. If it’s not clearly a seller’s market, doing a thorough inspection is a good idea. It can remove some of the information asymmetry and help with the purchase decision, or at least the price negotiation.What does this have to do with software development and IT management?When companies enter into an acquisition, they are also taking on the technology assets of the selling company, including all the buggy software and hodge-podge applications that have been put together to support operational needs. More often than not, these technology assets are not considered as part of the M&A due diligence process. This results in a lack of objective understanding by the buy side when it comes to application portfolios. Put bluntly, a buyer could be acquiring a system that fully does not work without knowing it.(Related: Docker introduces Docker Security Scanning)So for CIOs and IT managers who don’t have a chance to vet this new set of technology before a company merger, there are two key things to measure: reliability and technical debt.According to the latest data from CAST Research Labs, there are more than 550 million lines of code in today’s average application. That’s a lot to get through, and ideally, IT should go through acquired applications within the first three to six weeks after a merger to set benchmarks and prepare for a successful integration.Check the reliability status of your assetsU.S. companies are losing up to US$26 billion in revenue due to downtime every year. That’s a big number, even for big business, and implementing routine application benchmarking tests can eliminate much of it.
SQL databases seem to be very frustrating when you have to convert SQL data constantly into an object-oriented language — whether it’s Python on your server or Java on your app. So maybe we can simply get rid of SQL-based databases altogether. The easiest solution would be to just use a NoSQL database on your backend, so that you can drop JSON documents right into it without any serialization code.But you could also free yourself of the pain of SQL and its related ORMs on the mobile end app if you use an object database. That way, you simply define your schema in a class, and the data you create exists as instances of that class. You work with native objects the whole time on the app, and serialize them only when you have to communicate with the server.Ultimately, the problem is that you have to move from SQLite in your app, to a native model class, to JSON that you can send to your server, into another model class, and finally into SQL again, before your data finally comes to rest on your server. That’s a long trek, and we owe it to our users and our developers to cut out the unnecessary steps that our data takes.Beyond limiting the number of endpoints or serialization and deserialization steps, you can move away from the request-response cycle and towards seeing data as soon as it’s available by adopting reactive principles. Mobile apps bring with them an expectation of constant connectivity, but realizing that with constant HTTP requests can introduce a lot of overhead. Also, you’re making these requests blindly — you don’t actually know if there’s any new data on the other side. A modern reactive app starts by moving to streaming, so that data gets to your device whenever it’s available. Data is pushed to you, instead of pulled from your server.With a guarantee of fresh data, reactivity means that you can let data do the hard work of telling your app what to do next. Instead of refreshing your UI in a callback of a successful request, reactive programming means tying your UI to your data. Whenever new data comes in, the UI automatically adapts to those underlying changes — no need to call an update method. Now, you’ve got fresher data, and much less code meant to wrangle and display it.RESTful APIs give you a predictable, well-defined way to exchange information between your client devices and your servers. But doing it in a way that’s likely to result in the best experience for your users isn’t as simple as getting your app and your server to talk. It involves making sure the right data is being sent as economically as possible, as soon as it’s available, and being displayed to your users the moment it shows up. I started building REST APIs a few years ago because I was desperately in need of a back-end engineer, and it seemed easier for me to just do it myself. That, of course, is how all classic software engineering problems begin and where many startups end, but I thought: How hard could it really be? After all, I’d already finished my mobile app, and I’d designed the necessary algorithms already. I just needed them to run on a server.Predictably, that’s where things got tough. Because for every action you take in an app, you need a corresponding endpoint on the server — and usually multiple methods for each endpoint — so that your app can communicate what it’s doing with the server. And for every bit of data you generate beyond a simple button press, you also need a structured way to communicate that data back to your server, which you usually accomplish by converting data that starts in SQL or as properties on an object into JSON. So, you end up with many endpoints, much serialization code, and many more lines of code for every time you changed your mind about what you want to send or receive from the server.In short, making your mobile app talk to your server is never an easy thing. And the greater your ambitions, the more complex and fragile this dance becomes.In principle, this doesn’t seem like a necessary state of affairs. Often, we take technologies and accept their limitations as fundamental, when really we’re just using the wrong technologies in the wrong contexts. When it comes to building modern mobile apps, it’s high time we accept that we’re victims of server-side and mobile technologies that simply do not like speaking to another. It’s not just development time that gets eaten up by these incompatibilities, either. It’s also the performance of our apps. Every time our apps have to translate another bit of data from JSON to something useful, we slow down the app. Users don’t like that. We also have an opportunity cost: Every joule of energy used to communicate with the server means you can no longer use that joule to do something that the user will actually notice and appreciate.But there’s hope. If code complexity and data incommensurability are the fundamental problems that mean mobile apps suffer under the weight of the RESTful APIs on which they rely, then that points to our solution, too. Let’s make things simpler — by speaking the same language.