![\"\"](\"https:\/\/sdtimes.com\/wp-content\/uploads\/2025\/12\/pexels-digitalbuggu-167538-490x327.jpg\")
<\/p>\nArticles about AI dominated media protection in 2025, as the flexibility to carry out extra than simply rudimentary duties grew into making software program growth life cycle processes autonomous. The widespread piloting and implementation of generative AI, brokers and MCP servers have been among the many matters that produced the highest trending articles on sdtimes.com this yr. However AI wasn\u2019t the one factor on the minds of builders and their managers. Right here\u2019s a have a look at the highest trending tales on sdtimes.com for 2025.<\/p>\n
Essentially the most-viewed article this yr requested the query: \u201cIs Agile Lifeless within the Age of AI?<\/a>\u201d Creator Adam Sandman, CEO of Inflectra, posited that Agile processes are in truth not useless, however are evolving. \u201cThe way forward for software program growth isn\u2019t Agile vs. <\/i><\/b>AI, it\u2019s Agile with <\/i><\/b>AI. Strategic alignment, mentorship, and good governance guarantee that AI\u2019s energy enhances security, maintainability, and long-term product worth.,\u201d he wrote.<\/p>\n No. 2: 88% of firms are considering leaving Oracle Java<\/b><\/a><\/p>\n SD Instances editor Jenna Barron dug right into a January report by Java platform supplier Azul Programs that confirmed Oracle modified<\/a> its licensing mannequin to base the price on the variety of staff a company has, as an alternative of charging by the Java occasion in use. \u201cSince then,\u201d Barron wrote, \u201corganizations have been considering alternate options, and 72% of respondents have been already fascinated about it when surveyed in 2023.\u201d<\/p>\n The report reveals that the highest 5 causes for wanting to maneuver on from Oracle embody price (42%), desire for open-source (40%), Oracle\u2019s gross sales ways (37%), uncertainty round altering licenses and pricing (36%), and restrictive Oracle insurance policies (33%).<\/p>\n No. 3: AI coding productiveness positive factors cancelled out by different friction factors that gradual builders down<\/b><\/a><\/p>\n \u201cAI adoption is saving builders a major period of time, however a number of friction factors nonetheless exist all through the software program growth life cycle that builders are nonetheless dropping time to,\u201d Barron wrote from August research of developer expertise and engineering administration.<\/p>\n Atlassian\u2019s 2025 State of Developer Expertise report confirmed, \u201cSo we\u2019re proper again the place we began, with builders saving 10 hours every week utilizing AI and dropping 10 hours every week to inefficiencies. Enhancing the developer expertise requires a scientific method to understanding and resolving developer friction factors.\u201d<\/p>\n No. 4: AI received\u2019t exchange builders, however it is going to go away some behind<\/b><\/a><\/p>\n Dan Faulkner, CEO of Sensible Bear, wrote: When execs ask, \u201cWhat number of builders can we lower if we embrace AI?\u201d\u2014 They\u2019re asking the mistaken query.<\/p>\n The fitting query is: How can we evolve our whole software program lifecycle to match the rate AI makes doable with out breaking belief or burning down high quality?<\/p>\n \u201cThe longer term doesn\u2019t belong to groups that write probably the most code. It belongs to those that ship probably the most resilient, reliable, and scalable <\/i>software program,\u201d he wrote. \u201cThat future wants growth groups. But it surely wants a unique mindset and a unique type of management.\u201d<\/p>\n No. 5: Why AI brokers want a protocol like MCP to achieve their potential<\/b><\/a><\/p>\n MCP can do for AI brokers what USB does for computer systems, Lin Solar, senior director of open supply at cloud native connectivity firm Solo.io<\/a>, defined.<\/p>\n As an illustration, a pc wants a means to hook up with peripherals like a mouse, keyboard, or exterior storage, and USB is a typical that gives that connectivity. Equally, MCP permits AI brokers to hook up with totally different instruments and information sources, like Google Calendar. It gives \u201ca typical strategy to declare the instruments so the instruments may be simply found and may be simply reused by totally different AI purposes,\u201d she mentioned.<\/p>\n No. 6: Google goes all in on agent growth, Gemini at Google Cloud Subsequent 25<\/b><\/a><\/p>\n At its Google Cloud Subsequent 25 occasion in April, Google introduced plenty of new bulletins, primarily associated to enhancing Gemini choices and making it simpler to construct and undertake brokers.<\/p>\n Among the many bulletins have been the discharge of ADK, Google\u2019s Agent Improvement Package; an Agentspace platform on which builders can construct brokers combining Gemini fashions, Google-quality search performance, and enterprise information; and launched Google Workspace Flows<\/a>, enabling customers to create agentic workflows to streamline processes and automate repetitive duties throughout Workspace.<\/p>\n No. 7: Containers in 2025: Bridging the hole between software program and {hardware}<\/b><\/a><\/p>\n Containers have lengthy been a well-liked means of packaging up and delivering software program, however many builders have additionally begun to discover utilizing containers in additional methods than initially meant.<\/p>\n In a latest episode of the SD Instances podcast<\/a>, What the Dev, Scott McCarty, senior principal product supervisor for Pink Hat Enterprise Linux, sat down with us to debate the developments he\u2019s been seeing and in addition make predictions for what\u2019s to return.<\/p>\n No. 8: tRPC vs GraphQL vs REST: Selecting the best API design for contemporary net purposes<\/b><\/a><\/p>\n Software program engineer Kacper Mihalik contributed this information to SD Instances evaluating these applied sciences from a sensible engineering standpoint, after a number of years of constructing manufacturing methods with React and TypeScript.<\/p>\n \u201cI\u2019ve shipped REST, GraphQL, and tRPC APIs,\u201d he wrote.\u00a0 \u201cEvery choice presents distinct strengths, with real-world tradeoffs builders and engineering leaders ought to perceive. \u2026 specializing in structure, kind security, toolchains, and developer expertise.<\/p>\n