Comments by "Stephen D Green" (@stephendgreen1502) on "The Difference Between Developers u0026 Software Engineers" video.

  1. What annoys me most in terms of what can go wrong, is how a developer or support techie following our work might have to make live database changes as a result of failures of our weak logic such as data inconsistencies. Such live changes are quite stressful. Are our design weaknesses causing stress to colleagues, present and future? Will they have to endure health hazards?
    5
  2. I do tend to focus on risk assessing everything crucial and mitigating the risks, as part of a sense of responsibility instilled into me in public service. It might not qualify me to be called a software engineer. But it is seen as a weakness of mine by those with a more ‘positive’, ‘optimistic’ approach. It can be used against me. Today people having slogans to use against my ilk such as “go fast and break things” and calling my ilk “risk averse”. You can lose a job over it these days. Career even. That is what can go wrong. How do we mitigate it?
    2