Tech Lead notes from Software Craftsmanship London 2019

As part of working at Redgate I was lucky enough to go to Software Craftsmanship 2019. Here are some notes and key takeaways from the talks. Aligning Product and Software Design, Sandro Mancuso We struggle to find the time to do software design and architecture. If we have a project mindset, we only focus on the external customer goal without focussing on the means and investment. Software products require continuous investment and the point of software design is to make it possible to evolve the business faster. [Read More]

Tech Lead notes from User Research London 2019

As part of working at Redgate I was lucky enough to go to User Research London 2019. It’s even better for me as a Tech Lead on SQL Monitor because, although we do a lot of user research at Redgate, you don’t always get the opportunity to focus on learning more about it as a Technical Lead. It’s a growing conference with around 350 attendees this year. Key experience indicators for product management, Tomer A lot of people care about launching the product more than landing it. [Read More]
redgate  ux 

Dependency Injection in SQL Monitor

Originally posted on Ingeniously Simple Picture source https://flic.kr/p/gwQtNW (Licence under CC BY 2.0)In this blog post we talk about converting SQL Monitor’s base service to use DI. Moving to DI has been a substantial task that improves the architecture of SQL Monitor and provides a number of significant benefits. These include making it faster to add components, faster to fix problems and easier to test larger systems. It has also revealed the hidden architecture behind the base service. [Read More]

Halving SQL Prompt’s unit test time using TeamCity test statistics

Originally posted on Ingeniously Simple On the SQL Prompt team we use unit tests to provide stable releases to our customers. The problem with automated tests is that they take time to run. Ideally we could test a release instantly but in reality we run 6405 tests in 1 minute. We use NCrunch to run tests immediately during development. I began hearing that team members had turned off NCrunch because it was slowing down their development work. [Read More]

Talking with Tech Leads

Talking with Tech Leads is a book by Patrick Kua for Tech Leads from Tech Leads. What is a Tech Lead? Patrick defines a Tech Lead as follows: A leader, responsible for a development team, who spends at least 30 per cent of their time writing code with the team. How Tech Leads provide value Tech Leads provide value by: Helping developers code Collaborating with stakeholders outside the team Justifying coding in a sustainable way Communicating business priorities Prioritising team over code Tech Leads prioritise team focus and harmony over writing code. [Read More]

What we learnt from shipping SQL Prompt 8

Originally posted on Ingeniously Simple The SQL Prompt team shipped SQL Prompt 8 back in May 2017. This blog post talks about what we learnt during the final stages of the project and how we worked with the quality coaches. Reducing the amount of work to do Formatting was a difficult project to finish because our users care a lot about it. The new formatting engine solves over 16 UserVoice requests with over 1000 votes in total. [Read More]

Greatness comes from conscious choice not circumstance. The good-to-great companies were not, by and large in great industries. They focussed on what not to do and what to stop doing as much as they focussed on what to do. Good to great leaders put the right people in the right seats before figuring out where to go next. To be a great company, you need to be the best in the world at your core business. [Read More]

The 4 Best Coding Principles in “Coders at Work”

Coders at Work documents conversations with fifteen great programmers. These four coding principles came up throughout the book as universal principles that are worth adopting: Principle 1 – Keep Code Simple Coding as simply as possible is normally enough to solve most problems. Programs ought to make sense, there are very few inherently hard problems. When you have a hard problem, recognize that there is probably a known solution. [Read More]

3 Career Guidelines from The Pragmatic Programmer

The Pragmatic Programmer by Andrew Hunt provides practical suggestions on all aspects of software development. Guideline 1 – Develop a Knowledge Portfolio “An investment in knowledge always pays the best interest.” Benjamin Franklin Programming is an intellectual activity and the value of a programmer is based on their knowledge portfolio. The portfolio must be built and maintained with regular investment and diversification: Read at least one technical book per quarter Learn a new programming language every year Keep up-to-date with emerging technologies Local user groups are a good way to improve your knowledge portfolio and provide an environment to hear about career opportunities. [Read More]

5 Technical Guidelines from The Pragmatic Programmer

The Pragmatic Programmer by Andrew Hunt provides practical suggestions on all aspects of software development. Guideline 1 – Write Understandable Code Code is read more times than it is written so spend time writing clean code with clear variable names. Add comments when it is necessary to explain why the code is written that way and the decisions behind the implementation. Each software module should be responsible for a single aspect of the system. [Read More]