The NATO Science Committee report on Software Engineering from 1968 (available here) is a fantastic read and shows that perhaps not as much has changed in the world of software development as you might think!
What does it mean to be a great software engineer at Redgate? Read on to find out!
At Redgate, we try to guide our work using Objectives and key results (OKRs).
I wanted to start this article by posing an important question and one we’ve circled a number of times at Redgate: Is domain knowledge (or a lack of) a fundamental and pervasive barrier to great design?
The problem
At Redgate there was no good oversight of the technologies used by each team and Redgate overall. An oversight was needed so that they could…