Skip to content

Sam McNaull

Find me on:

Recent Posts

What is an acceptable level of technical debt?

The acceptable level of technical debt can vary depending on the organization and project but it is generally considered to be the amount that can be managed and controlled within the budget and resources of the company. It is also considered acceptable when it's incurred with a clear plan, understanding the trade-offs, and the costs involved and when it aligns with the organization's goals and objectives.

Can you ever get rid of technical debt?

Completely getting rid of technical debt may not be possible as new software systems and features will always be added over time and the codebase will continue to evolve and become more complex. Additionally, some degree of technical debt is often unavoidable as it can be a necessary trade-off to meet immediate business needs or to deliver new features quickly.

What is Technical Debt

Technical debt is a term used to describe the cost of maintaining and updating existing software systems, often as a result of poor design or short-term decision making. The term is used to describe the trade-off between taking short-term action to meet immediate needs and taking long-term action to minimize the total cost of ownership.

Two types of contracting categories within Canadian Federal Government

Typically, there are two giant buckets people fall into when they are looking at federal contracting...IT and non-IT. The IT contracting space is much larger and has it's own section of categories and job descriptions. The reason it is important to know the difference is because the titles between some types of roles will be exactly the same however the content within the resume and job requirements will be different. Take note of what you are applying for and be mindful of the language used on the posting. Sometimes they will post the exact category they are leveraging and mention this in the posting. Not a bad clarification question to ask the recruiter you are working with. 

An intro to writing your resume for the Canadian Federal Government

Creating a resume is not easy. Writing it for a person, group, department or entire government that has a particular set of standards can be intimidating. Giving you a rundown on how to create it in under 500 words would not do it justice. I'll break down the specific components of what is needed to write a resume for the Canadian Federal Government in order to get the job application in, send unsolicited emails to hiring managers or even that IT contract you have been waiting to get. 

RECOMMENDATION

LNine Achieves Prestigious AWS Global Security & Compliance Acceleration (GSCA) Partner Status

We are thrilled to announce that LNine has achieved the prestigious status of AWS Global Security & Compliance Acceleration (GSCA) partner. This accomplishment marks a...
Read More

RACI Matrix: Streamlining Stakeholder Management in SA&A

The RACI matrix is a valuable tool for organizations to effectively manage the SA&A process, ensuring that all stakeholders are aligned and accountable for the security...
Read More

Key Considerations for Risk Acceptance in SA&A

In the dynamic landscape of cybersecurity, the Security Assessment and Authorization (SA&A) process is a crucial framework for organizations. Central to this process is...
Read More

From Risk to Resilience: Exploring ATO and SA&A in Modern Cybersecurity

Welcome to our 4-part blog series covering the intricate process of the Authority to Operate (ATO) and the key considerations for the Canadian government. In this...
Read More