Home Blog

Survey: AI, cyber threats, distributed workforces problem IT groups most



Key elements behind insufficient difficulty prevention and mitigation embrace:

  • Inefficient workflows sluggish difficulty response: 53%
  • Understaffing as a key problem: 36%
  • Lack the appropriate instruments: 13%

“Corporations usually default to fixing issues with know-how first. But when they don’t get the outcomes they have been anticipating, they’re left questioning why. So whereas they might purchase the best-in-class device to resolve all their issues, they have a tendency to neglect about how folks leverage the instruments. They purchase seats however neglect the folks sitting in them.” Gazarek said within the report.

Important points result in poor buyer expertise

Penalties of poor operational resilience usually fall on prospects, in response to the report.

The survey discovered that 71% of respondents word buyer expertise as a core concern stemming from vital points and programs outages. About one-third (32%) of these surveyed stated they misplaced income from outages and different vital points, and greater than one-quarter (28%) cited model harm on account of poor efficiency and buyer expertise.

Greater than half (55%) of organizations measure efficiency metrics equivalent to imply time to detect, acknowledge, or restore (MTTx), however 45% of these surveyed reported they don’t monitor MTTx metrics. Among the many most typical the explanation why respondents don’t use MTTx embrace:

  • Lack of expertise: 38%
  • Difficultly measuring precisely: 16%
  • Favor different efficiency metrics: 16%
  • Not related to operational targets: 14%
  • Useful resource constraints stopping implementation: 8%
  • Would spotlight deficiencies: 6%

Of these respondents measuring efficiency metrics, practically one-quarter (73%) say that instruments have the best influence on decreasing MTTx, workflows are available an in depth second (67%), and groups land in third place, with 44% saying folks play the most important function in decreasing MTTx metrics.

Flutter native notifications not firing after midnight on each iOS and Android till app is opened


Вот переформулированный вопрос без упоминания лекарств:


Title: Flutter native notifications not firing after midnight on each iOS and Android till app is opened

Physique:

I am experiencing a problem the place scheduled native notifications cease working after midnight on each iOS and Android, however provided that the app hasn’t been opened because the notifications have been scheduled.

State of affairs:

  1. Consumer interacts with the app in the course of the day and completes a number of duties
  2. Every accomplished job schedules a notification for a similar time subsequent day
  3. Consumer closes the app within the night (e.g., 21:00) and would not open it once more
  4. Subsequent morning, NO notifications arrive at scheduled occasions
  5. BUT if consumer opens the app even briefly after midnight, all subsequent notifications for that day work completely

Present implementation:

  • Utilizing flutter_local_notifications package deal
  • Scheduling with flutterLocalNotificationsPlugin.zonedSchedule()
  • Utilizing AndroidScheduleMode.alarmClock for Android
  • Notifications are scheduled accurately (verified with debug logs)

Testing outcomes:

  • Works completely in emulator even when altering system time
  • Works on bodily gadget when manually altering time
  • Fails solely in real-world situation when gadget sleeps in a single day
  • Similar conduct on each iOS and Android

Code snippet:

await flutterLocalNotificationsPlugin.zonedSchedule(
  notificationId,
  title,
  physique,
  tzDateTime,
  notificationDetails,
  payload: payload,
  uiLocalNotificationDateInterpretation:
      UILocalNotificationDateInterpretation.absoluteTime,
  androidScheduleMode: AndroidScheduleMode.alarmClock,
);

It looks as if the OS is killing scheduled notifications in the course of the evening. Has anybody skilled this? What is the correct manner to make sure notifications survive in a single day with out opening the app?

Stack Overflow: Builders’ belief in AI outputs is worsening 12 months over 12 months


An increasing number of builders are adopting AI, however the belief they’ve in its outputs is getting worse and worse over time.

That is in accordance with Stack Overflow’s 2025 Developer Survey, which gathered responses from 49,000 builders throughout 177 international locations.

This 12 months, 84% of respondents say they’re utilizing or plan to make use of AI instruments for growth (up from 76% final 12 months), however 46% say they don’t belief the output of these AI instruments (up from 31% final 12 months).

Extra particularly, 75.3% stated they don’t belief AI-generated solutions, 61.7% had moral or safety issues about AI-generated code, and 61.3% stated they need to have the ability to absolutely perceive their code.

“The rising lack of belief in AI instruments stood out to us as the important thing information level on this 12 months’s survey, particularly given the elevated tempo of development and adoption of those AI instruments. AI is a robust software, but it surely has vital dangers of misinformation or can lack complexity or relevance,” stated Prashanth Chandrasekar, CEO of Stack Overflow. 

The survey discovered that for 45% of respondents, debugging AI-generation code is time consuming, which is likely one of the key frustrations with coping with AI-generated code.

Stack Overflow additionally discovered that solely 31% of respondents are at present utilizing AI brokers, and of these, 69% stated they’ve seen a rise in productiveness. Seventeen % are planning to make use of them sooner or later, whereas 38% don’t plan to ever use them. 

Moreover, 64% of builders don’t understand AI as a menace to their jobs, a slight lower from final 12 months (68%). 

The report additionally discovered that 69% of builders have hung out studying new coding methods or languages up to now 12 months, and 44% used AI instruments for studying (up from 37%) final 12 months. 

Lastly, whereas builders are utilizing AI to help with their work, a majority (77%) aren’t partaking in vibe coding for his or her skilled work. 

Different fascinating findings from the survey are:

  • 24% of builders are completely happy at their present job—a slight enhance from final 12 months’s 20%, doubtless associated to pay raises
  • 32% of builders work remotely and 45% of US builders work remotely
  • GitHub surpassed Jira as essentially the most fascinating collaboration software

For extra insights, the total survey findings can be found right here

RNA-seq outperforms DNA strategies in detecting actionable most cancers mutations – NanoApps Medical – Official web site


Hospital for Sick Kids in Toronto researchers are reporting that focused RNA sequencing can detect clinically actionable alterations in 87% of tumors and supply decisive findings the place DNA-seq both fails, returns no variant, or just isn’t informative.

Most cancers remedies have seen super enhancements lately, partially on account of extremely particular concentrating on and .

DNA-based strategies dominate molecular most cancers diagnostics however battle to detect  and assess splice web site penalties. RNA sequencing permits delicate fusion detection and direct evaluation of transcript-level disruption attributable to splicing mutations.

Within the examine, “Medical utility of focused RNA sequencing in most cancers molecular diagnostics,” printed in Nature Drugs, researchers applied a focused RNA-seq assay to judge 2,310 tumors throughout , stable, and hematopoietic cancers.

Of the two,310 tumors submitted for evaluation, 110 (4.8%) failed , primarily on account of inadequate RNA. Amongst samples assembly high quality thresholds, sequencing was profitable in 99.6%.

Oncogenic variants have been recognized in 74% of tumors, with a further 13% categorised as pertinent negatives—bringing complete scientific utility to 87%.

Amongst constructive instances, 40% carried single nucleotide variants (SNVs) or indels, 32% fusions, 2.5% different structural variants, and 5% confirmed a number of lessons. Fusions have been 1.8 instances extra frequent in youngsters, whereas SNVs have been 1.6 instances extra frequent in adults.

Amongst 103 samples with matched DNA sequencing, RNA-seq detected 93.3% of oncogenic variants. Variant allele frequencies between RNA-seq and DNA-seq confirmed sturdy correlations.

Amongst tumors sequenced with diagnostic intent, 37 obtained new diagnoses, representing 1.9% of evaluable instances. A further 11 tumors have been reclassified based mostly on the presence or absence of diagnostic alterations, bringing the entire to 48 revised diagnoses.

Central nervous system tumors accounted for 30 of the 48 revised diagnoses. In 13 instances, RNA-seq reclassified ependymoma as glioma, astroblastoma, or paraganglioma. Seven low-grade gliomas have been re-diagnosed as diffuse midline glioma, H3 K27-altered, based mostly on identification of H3K27M mutations.

 have been reclassified, together with one initially recognized as metastatic Wilms tumor, re-identified as clear cell sarcoma of the kidney following detection of a BCOR inside tandem duplication. One other case, beforehand examined with destructive fusion outcomes, was revised to dermatofibrosarcoma protuberans after RNA-seq recognized a canonical COL1A1::PDGFB fusion.

Eight tumors have been reclassified not by detection of a brand new alteration however by ruling out anticipated diagnostic options. In every case, RNA-seq excluded defining molecular markers of the histologic prognosis, resulting in re-evaluation of tumor classification.

In complete, 94 of 104 sufferers thought of for focused remedy obtained remedy based mostly on RNA-seq findings. MAPK pathway inhibitors, , and immune checkpoint therapies have been mostly used.

Fusions alone defined oncogenesis in 86% of fusion-driven tumors, lots of which lacked extra alterations. RNA-seq succeeded throughout all tumor sorts and tissue codecs, together with degraded FFPE samples.

Researchers conclude that focused RNA-seq can function a stand-alone molecular diagnostic with excessive yield, minimized price, and broad scientific applicability.

Written for you by our writer Justin Jackson, edited by Sadie Harley, and fact-checked and reviewed by Robert Egan—this text is the results of cautious human work. We depend on readers such as you to maintain impartial science journalism alive. If this reporting issues to you, please think about a donation (particularly month-to-month). You’ll get an ad-free account as a thank-you.

Extra info: Robert Siddaway et al, Medical utility of focused RNA sequencing in most cancers molecular diagnostics, Nature Drugs (2025). DOI: 10.1038/s41591-025-03848-8

Debian shifts to 64-bit time storage to go off Epochalypse



The Y2K38 bug presents an analogous difficulty. Unix (and Linux) clocks depend time in seconds, ranging from January 1, 1970, which was dubbed the Unix Epoch, and a few techniques retailer that quantity in a signed 32-bit integer which is able to overflow at (brace your self) exactly 03:14:07 UTC on January 19, 2038. When it does so, clocks will revert to December 1901.

Epochalypse now?

Actually, it’s already an actual mess that’s hitting techniques, comparable to pension fund projections, that look into the long run past that magic second in 2038.

Mentioned mess received’t have an effect on fashionable 64-bit techniques, in fact — their dates are saved in 64-bit variables, good for greater than 292 billion years. However legacy and embedded techniques are in danger, therefore the work by Debian and different distros. Every part from plant management techniques and constructing monitoring techniques to routers and safety cameras are operating some kind of embedded working system, and for a lot of, it’s 32-bit Linux. These techniques typically stay in service for many years with out substitute, making a software program repair a necessity. It’s one other instance how the failure to take {hardware} and software program longevity under consideration can come again to chunk us.

The remedy: altering date storage to 64-bit variables. It was a huge job for Debian maintainers, involving nearly 6,500 packages, and all of it needed to occur at one time as a result of it additionally concerned a change to the applying binary interface (ABI). However Debian says the work is full, or no less than, as full because it’s going to get for now. To make sure compatibility with x86 binaries, it’s leaving dates on i386 techniques as 32-bit, though it’s contemplating choices if there’s sufficient demand for 64-bit dates on these techniques.

It might appear that the overflow continues to be a far-off drawback however, “As of 2025, that is much less that 13 years away, and loads of techniques that can have issues have already been shipped,” Debian stated in a publish in regards to the difficulty. “We should always cease including to the issue. Most computing, particularly computing utilizing Debian or its derivatives, is now executed on 64-bit {hardware} the place this difficulty doesn’t come up. Nevertheless there’s various cost-sensitive 32-bit computing nonetheless on the market, and nonetheless delivery in new gadgets (automotive, IoT, TVs, routers, plant management, constructing monitoring/management, low-cost Android telephones and many others.), with a few of that {hardware} most likely operating Debian or its derivatives.”

That is notably necessary as a result of many different Linux distros, together with RedHat and Fedora, have already dropped 32-bit help, and SUSE’s help is unofficial, leaving the Debian ecosystem to hold a big a part of  the 32-bit load.