#FAIL

แชร์
ฝัง
  • เผยแพร่เมื่อ 24 ธ.ค. 2024

ความคิดเห็น • 15

  • @DaniDipp
    @DaniDipp ปีที่แล้ว +8

    Kevlin Henney's talks are always engaging, memorable, and thoroughly enjoyable. He's a real TH-cam for the industry.

  • @Anbu_Sampath
    @Anbu_Sampath ปีที่แล้ว +4

    Failure is inventible in software, always learn from your and others mistake and deliver better software continuously to users.

  • @RoamingAdhocrat
    @RoamingAdhocrat ปีที่แล้ว +10

    ok, whatever I had planned for Friday evening can wait an hour

  • @_skyyskater
    @_skyyskater ปีที่แล้ว +3

    Stop getting the Javascript error wrong at 6:18 Kevlin! That Canadian address error is Javascript with a $ at the beginning, which is a perfectly legal token for a variable. There used to be a convention with jQuery selector elements to use "$" at the beginning of variables, but that doesn't seem to be the case here, so no idea why they have it. Nonetheless, PHP uses "->" for object props/methods and PHP does not have a "object.prototype.toUpperCase()" function (that would be strToUpper(string)), but Javascript does.

  • @RupertReynolds1962
    @RupertReynolds1962 ปีที่แล้ว +4

    Seen it twice now. I may watch it again in a few months, because Kevlin says things that need saying :-)

  • @Rx7man
    @Rx7man ปีที่แล้ว +2

    55:00
    Q: What does an incel and MS excel have in common?
    A: Mistaking something as a date

  • @waynewheaton3210
    @waynewheaton3210 ปีที่แล้ว +3

    Great talk. Configuration is code, so true (Is that a foreshadow of GIGO?).

  • @aliensarefromspace
    @aliensarefromspace ปีที่แล้ว +2

    Peraphrasing some thoughts
    > Kelvin : Unit test are great, integration tests are not
    > Kelvin 20 mins later : Always consider things in their next bigger context
    That's what integration tests are.. the next bigger context.

    • @DrSpooglemon
      @DrSpooglemon ปีที่แล้ว +1

      He said no such thing. He said that reliance on only integration testing in distributed system means you miss the bugs that have nothing to do with integration which are most of the bugs you will come across.
      Sheesh, why does the matter of testing always provoke the "No, you wrong," comments from people who don't like to listen? It's pretty.... testing!!

    • @aidenbull7776
      @aidenbull7776 3 หลายเดือนก่อน

      15:30 "... integration testing is of course important ..."

  • @ra2enjoyer708
    @ra2enjoyer708 ปีที่แล้ว +1

    How do you handle errors in the self-destruct module? And how do you test it?

  • @Yupppi
    @Yupppi ปีที่แล้ว

    Makes me think if the Rust's annoyingly pedantic error handling requirements make people write better code in Rust, which would be a good language choice for these applications. However I don't know about Rust's integration to machine learning.
    Also how about designing systems (in case of for example military vehicles) where in case of software failure, you still have mechanical systems to get something done even if you lose the brilliant computer power.
    I wonder if people used to do something like if a or b is 32 bit { a/2 + b/2 } to combat the limitations.

  • @raymondyoo5461
    @raymondyoo5461 ปีที่แล้ว +3

    Another great talk from Kevlin Henney 👍👍
    You taught me a lot as usual

  • @pianochess1882
    @pianochess1882 ปีที่แล้ว +1

    The guy at 53:34 was not fast enough 😅