Fortran\u2019s return to the top 10 in Tiobe\u2019s monthly index of language popularity<\/a> is being attributed to the growing importance of numerical or mathematical computing.<\/p> Fortran returned to the top 10 in the index for April 2024 and retains the 10th place in the index for May 2024. The rating for Fortran did slip a bit, from 1.47% last month to 1.24% this month. But before April, Fortran\u2019s last appearance in the Tiobe top 10 was April 2002.<\/p> Paul Jansen, CEO of Tiobe, a provider of tools for measuring software quality, attributed Fortran\u2019s recent rise to the language\u2019s advantages for numerical\/mathematical computing. \u201cDespite lots of competitors in this field, Fortran has its reason for existence,\u201d Jansen said. He noted shortcomings in the competition: Python, while the top choice, is slow; MATLAB comes with expensive licensing; C\/C++, while mainstream and fast, has no native computation support; R is slow; Julia, while rising, is not mature yet. \u201cAnd in this jungle of languages, Fortran appears to be fast, having native mathematical computation support, mature, and free of charge. Silently, slowly but surely, Fortran gains ground. It is surprising but undeniable.\u201d<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li> About a decade ago, I was a CIO evaluating a technology solution and I shared our primary requirements with a prospective vendor\u2019s rep. He demoed at least three products from the company\u2019s portfolio. Each tool had its own user experience, development approach, and learning requirements, but all three were needed to solve our business requirements. As CIO, I recognized that different parts of my team would either need to collaborate using these different tools, or I would have to hire more advanced developers capable of mastering them all. I decided not to invest in this technology solution because of the complexities of development involved.<\/p> The concept of developer experience (DX or DevEx) was not a primary or measurable objective back then. Few business leaders were thinking about the value of improving developer satisfaction, productivity, and happiness. But leading CTOs, digital trailblazers<\/a>, delivery managers, and technical leads understood its importance. It\u2019s why we bought large, multi-monitor workspaces, upgraded desktops to use the most powerful devices, brought in foosball tables to encourage work breaks, and celebrated major releases with our developer teams.<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li> When we set out to rebuild the engine at the heart of our managed Apache Kafka<\/a> service, we knew we needed to address several unique requirements that characterize successful cloud-native<\/a> platforms. These systems must be multi-tenant from the ground up, scale easily to serve thousands of customers, and be managed largely by data-driven software rather than human operators. They should also provide strong isolation and security across customers with unpredictable workloads, in an environment in which engineers can continue to innovate rapidly.<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li> No one thinks software development is easy, but who would have thought it could be hard in so many different ways? Evans Data estimates there are 26.9 million software developers globally. Recently more than 100 of those developers weighed in on Ali Spittel\u2019s question<\/a>, \u201cWhat\u2019s the most difficult part of your job as a developer?\u201d<\/p> I expected the answers to mostly coalesce around a few key themes, but the responses were highly varied. It\u2019s worth digging into them to see how your company can improve life for your developers.<\/p> Sometimes we love our developers too much. We rely on them (the new kingmakers and queenmakers) to innovate and to keep innovating. As Kyle Shevlin notes<\/a>, \u201cThe constant threat of scope creep from product and design\u201d makes life difficult for developers. This stems from a healthy confidence in developers\u2019 talents, but scope creep translates into bloated software, which is hard to maintain, something Sofiene Salem highlights<\/a>. Couple this with \u201cunrealistic deadlines set by non-developers,\u201d as Brian Shimkus stresses<\/a>, and you end up in double trouble.<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li> Visual Studio Code 1.89, the April 2024 release of Microsoft\u2019s popular code editor<\/a>, has arrived with capabilities including enhanced branch switching and middle-click paste support.<\/p> The update, downloadable from the project website<\/a>, was announced May 2<\/a>. Enhanced branch switching addressed a long-standing feature request to save and restore editors when switching between source control branches. Developers can use the To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li><\/ul>[\/et_pb_code][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":" Fortran\u2019s return to the top 10 in Tiobe\u2019s monthly index of language popularity<\/a> is being attributed to the growing importance of numerical or mathematical computing.<\/p> Fortran returned to the top 10 in the index for April 2024 and retains the 10th place in the index for May 2024. The rating for Fortran did slip a bit, from 1.47% last month to 1.24% this month. But before April, Fortran\u2019s last appearance in the Tiobe top 10 was April 2002.<\/p> Paul Jansen, CEO of Tiobe, a provider of tools for measuring software quality, attributed Fortran\u2019s recent rise to the language\u2019s advantages for numerical\/mathematical computing. \u201cDespite lots of competitors in this field, Fortran has its reason for existence,\u201d Jansen said. He noted shortcomings in the competition: Python, while the top choice, is slow; MATLAB comes with expensive licensing; C\/C++, while mainstream and fast, has no native computation support; R is slow; Julia, while rising, is not mature yet. \u201cAnd in this jungle of languages, Fortran appears to be fast, having native mathematical computation support, mature, and free of charge. Silently, slowly but surely, Fortran gains ground. It is surprising but undeniable.\u201d<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li> About a decade ago, I was a CIO evaluating a technology solution and I shared our primary requirements with a prospective vendor\u2019s rep. He demoed at least three products from the company\u2019s portfolio. Each tool had its own user experience, development approach, and learning requirements, but all three were needed to solve our business requirements. As CIO, I recognized that different parts of my team would either need to collaborate using these different tools, or I would have to hire more advanced developers capable of mastering them all. I decided not to invest in this technology solution because of the complexities of development involved.<\/p> The concept of developer experience (DX or DevEx) was not a primary or measurable objective back then. Few business leaders were thinking about the value of improving developer satisfaction, productivity, and happiness. But leading CTOs, digital trailblazers<\/a>, delivery managers, and technical leads understood its importance. It\u2019s why we bought large, multi-monitor workspaces, upgraded desktops to use the most powerful devices, brought in foosball tables to encourage work breaks, and celebrated major releases with our developer teams.<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li> When we set out to rebuild the engine at the heart of our managed Apache Kafka<\/a> service, we knew we needed to address several unique requirements that characterize successful cloud-native<\/a> platforms. These systems must be multi-tenant from the ground up, scale easily to serve thousands of customers, and be managed largely by data-driven software rather than human operators. They should also provide strong isolation and security across customers with unpredictable workloads, in an environment in which engineers can continue to innovate rapidly.<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li> No one thinks software development is easy, but who would have thought it could be hard in so many different ways? Evans Data estimates there are 26.9 million software developers globally. Recently more than 100 of those developers weighed in on Ali Spittel\u2019s question<\/a>, \u201cWhat\u2019s the most difficult part of your job as a developer?\u201d<\/p> I expected the answers to mostly coalesce around a few key themes, but the responses were highly varied. It\u2019s worth digging into them to see how your company can improve life for your developers.<\/p> Sometimes we love our developers too much. We rely on them (the new kingmakers and queenmakers) to innovate and to keep innovating. As Kyle Shevlin notes<\/a>, \u201cThe constant threat of scope creep from product and design\u201d makes life difficult for developers. This stems from a healthy confidence in developers\u2019 talents, but scope creep translates into bloated software, which is hard to maintain, something Sofiene Salem highlights<\/a>. Couple this with \u201cunrealistic deadlines set by non-developers,\u201d as Brian Shimkus stresses<\/a>, and you end up in double trouble.<\/p> To read this article in full, please click here<\/a><\/p><\/section><\/article><\/li> Visual Studio Code 1.89, the April 2024 release of Microsoft\u2019s popular code editor<\/a>, has arrived with capabilities including enhanced branch switching and middle-click paste support.<\/p> The update, downloadable from the project website<\/a>, was announced May 2<\/a>. Enhanced branch switching addressed a long-standing feature request to save and restore editors when switching between source control branches. Developers can use the Scope creep<\/h2>\n
scm.workingSets.enabled<\/code> setting to enable this capability.<\/p>Scope creep<\/h2>\n
scm.workingSets.enabled<\/code> setting to enable this capability.<\/p>