Comments by "ForgottenKnight1" (@ForgottenKnight1) on "Continuous Delivery" channel.

  1. Just say it: management thinks that pair programming is losing them money, so that is why there's so much push back.
    1
  2. "...have to use..." - who's forcing you ?
    1
  3. In that case, you can do pair programming 2,3 hours a day (you're lieing to yourself if you say you'll do it 8 hours a day) Language barrier - this seems to me like a communication issue, so improve that over time. Cultural differences - same as language.
    1
  4.  @AndrewEddie  That sounds like a management issue.
    1
  5.  @mecanuktutorials6476  "Cleanup after checkin is unrealistic because there won’t be any time for that later." - says who ?
    1
  6.  @deanschulze3129  Unfortunately ? That sounds like you like micromanagement.
    1
  7. "Agile" is implement like shit, excuse my French, by 99% or more of the companies that toot their horn for being "Agile".
    1
  8.  @disgruntledtoons  Companies exist for profit, and automotive is no exception. They would rather overpromise and work you overtime, than be more sensible about it, because the competition is just as ruthless.
    1
  9. 7:50 - Method split is not getting enough love even today. Too bad, because it's one of the best refactorings to improve readability, clarity and add more context and meaning to your code. Instead, I see engineers prefer to leave multi-line comments instead of refactoring their code...
    1
  10. Compliance and regulatory settings should be secured configuration settings, not magic values in code. I know, it's hard, but that's the correct way of doing it :)
    1
  11. Sometimes a sign off is needed because of bureaucracy before a release is done. I worked on some project, where I had to get an approval from my manager for every deployment....
    1
  12. Sometimes a service interface changes because the business changes and the new modifications might be breaking changes for consumers. The solution I found in this case is to keep both versions, but mark one as Obsolete (I am working mostly with C#/.NET). There are also many other ways to notiy your users that you are going to decomission this functionality in the near future, so they should start making changes to adapt to the new version.
    1
  13. You will NOT change the rules if the rules were established by people above you. That should be a no brainer. At most, you can advise. If they listen, good, if not, GTFO of there.
    1
  14. Never knew about this paper. Holy crap ! Gotta read it
    1
  15. Money talks, the rest is BS. Companies exist for one sole reason: profit. Silly things like "loyalty" and "family" should be huge red flags when interviewing and afterwards because they are manipulation tools.
    1
  16. "Who's writing the automated tests though?" - the engineers that develop the feature.
    1
  17.  @brianmulder4920  It's indeed 2 cents worth because it does not provide a better justified alternative
    1