At some point during the development lifecycle someone, be it a developer, QA, or a business owner, asks for "real" data to test against. Typically this is for two reasons, they want the volume of data to match production, or the "fake" data doesn't make any sense. A request such
The tooling necessary to incorporate DevOps practices is already out there. There are many different flavors of build tools, Jenkins, TeamCity, VSTS, AppVeyor, and Bamboo. Release management is covered by Octopus Deploy, Release Management, and Bamboo. And finally, database automation tooling provided by Redgate SQL Toolbelt and Microsoft SSDT. The
Back in the article How Redgate Helped Define our Process, there was this small blurb about SSDT:
Microsoft SSDT Tooling Considered - the increased cost of licenses forced us to take a hard look at Microsoft's SSDT tooling. Could it do what Redgate did? Could we build additional functionality around
Thanks to the Visual Studio 2017, creating .NET Standard Class Libraries is easier than ever. While it is easy, there are few tips and tricks to help make the process as smooth as possible.
This is the first in a series of posts to generate a class library for a
Code reuse is near the top, if not at the top, of my priority list. In the .NET world, that can mean only one thing, .NET Standard. Until a few months ago, the chance to experiment with it for the enterprise had not yet presented itself to me. Now that
In my late twenties, I was hired to work on a project for a new client. The project was to add a lot of new features to a SaaS application. The client was the largest player in its particular industry and wanted a lot of customizations. After several months of
Redgate's ANTS Memory Profiler is a fantastic tool to help track potential memory leaks. But, it is important to have realistic expectations when getting started using the tool. When used properly, the tool can be very helpful in tracking down memory leaks. By no means is it a silver bullet.
A major passion of mine is readable code. When the code is easy to read, it is easy to maintain. It is easy to test. In a lot of the projects we work on, the code we write ends up living for over ten years.
One area I've noticed developers
My team has a New Relic Insights dashboard up in our area on a large screen. As I was talking to someone, I noticed the error count jump from 10 to 20 to 40 and 80 in a manner of minutes. Something was not right. That is very abnormal. We
A few weeks ago a key component the loan origination system my team is responsible for at Farm Credit Services of America had a problem. The loan origination system's main REST API calls this component when a user performs a certain action. Concerning overall usage, this key component is used