Understanding SQL Stored Procedure Dependencies with CodeLogic Twitter Youtube Twitter Youtube Introduction SQL stored procedures have long been a critical architectural component in many complex …
Understanding SQL Stored Procedure Dependencies with CodeLogic Read More »
In this blog, we will discuss the benefits and downsides of AI coding tools, propose strategies to mitigate the risks, and provide a practical example of integrating CodeLogic with AI-assisted development to maximize productivity while maintaining safety and reliability.
NYDFS is proposing a new amendment that compliance, security, and development teams should be particularly concerned about one of the areas covered in the new amendment – the requirement to maintain an inventory of all software API endpoints. This is a tall order since most organizations have APIs they don’t even know about. And you can’t inventory what you don’t know is there.
The New York State Department of Financial Services (DFS) has proposed an amendment to its 2017 Cybersecurity Regulation (also known as 23 NYCRR Part 500). The 2017 regulation was one of the first of its kind and served as the model for many other regulations nationally and internationally. The proposed amendment would significantly expand the requirements that covered entities need to follow.
At JavaOne 2022 our VP of Product, Eric Minick, delivered an urgent message to Java devs in need of order amidst inherited and compounded code chaos. Watch his 15-minute session to get a glimpse of the biggest blind spots facing software development teams today.
“If we double the team size, we’ll go twice as fast, right?” If this sounds familiar, you’re not alone. Every day, organizations must make decisions to help them move faster and keep up with their competition.
Tool fatigue is a common affliction in many software development environments and is characterized by an overwhelming sense of weariness that sets in as more and more tools get added to the developer toolkit.
Software engineers can now begin to remove their blindfolds, surface what-if scenarios with accurate information, and stop the fear of breaking changes. Here’s how.
When it comes to software intelligence and dependency mapping, how does it compare and work with APM tools? How exactly do application performance monitoring tools and dependency maps differ? And can they be used together?
While deprecated code is common in development cycles, how does it impact software engineers? And how can dependency mapping alleviate the complications inherent with deprecated code?
