Comments by "Benjamin Rood" (@benisrood) on "ByteByteGo" channel.

  1. 3:05 small mistake here: your labelling of Chinese and Japanese is wrong, it should be the other way around.
    4
  2. Then use the playback speed control to slow it down?
    3
  3. No Event Sourcing?
    3
  4. Happy path is the absolute minimum. Ensuring functioning invariants which prevent the bad path should also be the minimum, imo.
    1
  5. ​ @brucewayne2480  No, it just means that you can skip the kind of type and input sanitisation testing that you might write for a dynamically typed language. If you think that is all testing is used for then you are either writing very trivial programs or have a lot to learn still.
    1
  6. ​ @antonioamaral400  It depends on the type of tests. Unit tests are relatively static if you are writing properly-defined single-responsibility functions with clean inputs and outputs without side effects. In fact you can most likely generate the test code in those cases. Integration and E2E tests fit closer to what you are saying.
    1
  7.  @TheZhouh12  Because you want to be a programmer, not a dev/sec/ops tool?
    1
  8. Excellent analogy, thank you.
    1
  9. There is not way that an HTTP request over a network is slower than an SSD read, unless you are talking about an HTTP request between two local servers with cached data or in-memory data. That's a bit misleading.
    1
  10.  @VincentJenks  True, but if all you are using Kafka for is "an effective data bus for microservices", unless what you are working on is really big, very distributed, and for a big company, you can use something much more lightweight like RabbitMQ. Most developers don't work for Uber or Netflix-scale companies, nor anywhere close. I agree with you though, Kafka is a fantastic product, but you need to require its full value proposition in order to justify using it in your system.
    1
  11. Literally in the video description.
    1
  12. ​ @br.3250  The short answer is "it depends". But no, a small company cannot handle the resource overheads (AWS for example is extremely expensive), the development costs, and the additional staffing costs of dedicated SRE team members. The whole DevSecOps trend failed because even if developers want to take on all those responsibilities the reality is that they will master none and not have the time to do any of them well. It's a false economy.
    1
  13. Nahhh, it's correct as-is.
    1
  14. ​​ @peregrin71  For system design level problems, including in senior-level+ interview questions, you need to know these things also. For regular software development work though, your priorities are correct.
    1