Search this blog
The Current Book – The Phoenix Project (re-reading)

-

18 Year MVP Awardee

Tags
- administration
- AI
- AIExperiments
- auditing
- Azure
- backup
- Backup/Recovery
- blogging
- business
- career
- career2
- car update
- Cloud Computing
- conferences
- containers
- continuous integration
- coping
- data
- data analysis
- database design
- databases
- Database Weekly
- data privacy
- dbatools
- DevOps
- disaster recovery
- encryption
- Flyway
- Friday Poll
- FWTips
- GDPR
- Git
- goals
- hardware
- high availability
- Humor
- life
- Linux
- Microsoft
- misc
- monitoring
- networking
- PASS
- Performance
- powershell
- presentations
- Redgate
- Redgate Monitor
- republish
- sabbatical
- security
- software development
- software development
- speaking
- SQL Compare
- SQL in the City
- SQLNewBlogger
- SQL Prompt
- SQL Saturday
- sql server
- SQLServerCentral
- SSMS
- syndicated
- T-SQL
- T-SQL Tuesday
- Tesla
- testing
- travel
- tsqlt
- vacation
- version control
- webinar
- windows
- words
- work
Search this blog
Steve’s Tweets
Tweets by way0utwestOlder Posts
Meta
Tag Archives: software development
Avoiding Development Taxes
When I first worked in an environment where multiple developers needed to release software, I found too many rules and constraints for smooth development. The process was developed by one person, or for one application, and somehow expanded to encompass … Continue reading
Don’t Use Code Coverage
I got asked in a seminar recently how to perform code coverage for T-SQL. There aren’t a lot of options, but there is a project from Ed Elliot called SQLCover that looks to examine how much of your code gets called from … Continue reading
Posted in Editorial
Tagged software development, software testing
Comments Off on Don’t Use Code Coverage
Rewrite Your Code Tomorrow
One of the things that many developers learn over time is that they write better code with practice. In fact, some of the time a developer will find that if they write a bit of code to solve a problem, … Continue reading
I Will Write Bad Code
I’ll write bad code. I know it will happen. I’ll produce a bad query, incorrect logic, or the wrong data transformation being returned. This won’t be a malicious act. It might be because of ignorance, or perhaps just a simple … Continue reading