top of page
  • Writer: VC Healy
    VC Healy
  • Oct 9, 2020
  • 1 min read
  • Absence of trust - A good team trusts one another on a fundamental and emotional level. The members of the team are comfortable with their weaknesses, mistakes, fears, and behaviors.

  • Fear of conflict - A good team isn't afraid to discuss issues and decisions.

  • Lack of commitment - Unhindered discussions improve support from everyone on important decisions, even when there an initial disagreement. As all points of interest have been discussed

  • Avoidance of accountability - A good team will not single out a team member as accountable when the decisions were made by the whole team.

  • Inattention to results - A good team will set aside their individual needs or agendas and focus on what is best for the team.

 
 
  • Writer: VC Healy
    VC Healy
  • Oct 9, 2020
  • 1 min read

Continuous Security requires three elements:

  • A strong security-focus for the company's culture

  • Adopting the latest security recommended practices to implement and operate infrastructure.

  • Software delivery that is focused on security

Combined with the three principles of shifting left, automation, and continuous improvement, gives a good view of security in DevOps.


In a Security DevOps culture, awareness and building security principles should be at the heart of a companies design strategy.


The costs of a security breach is not just the loss of sales or trust in the company.

Continuous Operations can reduce or eliminate the need for planned downtime. The user should never need to know that upgrades have occurred!


The right balance between innovation (speed) and business continuity (control) is what DevOps is trying to achieve.

 
 
  • Writer: VC Healy
    VC Healy
  • Oct 9, 2020
  • 1 min read

I have been asked this interview, asked this when trying to improve.


My answer to this is always the same.


When I know what to do, I will always do my best.

It's not working, we made a change to the website/webapp/etc. are not going to get the best out of my skills to resolve an issue.


Explaining the issue in more detail is always going to have a better chance of a successful outcome.


What is not working?

What were you doing when it stopped working?

Did something happen during the time is started to stop working.

What did you change?

This list can on and on.


It all comes down to quality. The better the quality of the request the better quality of the answer.

 
 

© 2020 by Vincent Healy. Proudly created with Wix.com

bottom of page