Comments by "ForgottenKnight1" (@ForgottenKnight1) on "NDC Conferences" channel.

  1. Clean as you go is better, if possible (that is, if you don't have a micromanager) - you might not remember what you did 2 months ago.
    22
  2. "By rejecting incorrect solution" - you mean "by having a human review all the garbage that AI spews out"
    17
  3. His condescending attitude towards developers does not help his case either.
    5
  4. Use DI when needed (like strategy pattern or other patterns where you don't know the concrete dependency before runtime or there can be different dependencies based on conditions in layers above). And stop writing unit tests for internal or private classes. Test public classes, more specifically public methods in those public classes. Mocking couples implementation details to the test, which will make the test fail if you change the implementation, even if the behavior remains the same.
    4
  5. 29:30 - Sonar users will probably not agree with you entirely on this one, because in that context duplication = bad. I've seen enough projects with bad abstractions, bad sharing of code, super high coupling and just bad design, just for the sake of "reducing duplication". F the rest, the Sonar reports are more important. Let's just say those projects sucked.
    4
  6. Go read Test Driven Development by Kent Beck. It contains some clarifications to your questions...
    4
  7. Merging development and QA was a very bad decision that corporations made. Now, their agenda is obvious, more profit, but the outcome is software of lower quality. QA is a different mindset than development itself, and having the developer only testing his code is just asking for trouble because of all sorts of biases.
    3
  8. "but presumably you still want the event to eventually be delivered to the receiver(s)" - then that is not an event, but a message. Events do not require acknowledgement. They are simply emitted - there might be someone who could react now, or after 10 minutes, or never.
    2
  9. I had to hammer my fingers at least a dozen times because of over-optimism. Now when I estimate, I usually take a +50% buffer added to the WORST case scenario. Most cases, not needed, but it's better to be safe than sorry. Doind CI/CD also helps a lot because you can downsize the product to an MVP and estimate that, then, provided feedback, you can decide next step(s) and estimate those and so on. Not all clients understand (some still think software development is like factory production, which is wrong), but most do.
    1
  10. Pascal is the stuff of nightmares. No, thank you, I don't care what problems it fixes.
    1
  11.  @allanwind295  "presumably you still want the event to eventually be delivered to the receiver" - when a message layer is present, there is no coupling. I might have service A put a message on a queue and ... that's the end of it. There might be a service B looking at that queue or topic to get it, or there might not be. If service A expects its messaage to be processed, it means that it expects a service B to exist, take its message, process it and provide some output somewhere in some form. If there is none and service A fails or timeouts, it means service A is dependant on service B and not autonomous anymore. Maybe I interpreted your comment wrong, so feel free to correct me. In some cases, a response is needed and you might also think that if service A is always dependant on service B, you might want to merge them.
    1