49:40 there’s no end to the work that we want to get done, and solving a problem means we unlock the potential to solve new problems. It’s an endless cycle. We will never get to a point where we can say we are done.
On the more philosophical subject I agree with Lane. I feel like taking things to the extreme, even in a utopian world where all our physical needs have been automated away and money is no longer a thing, people would still by and large look for some kind of productive outlet. I'm sure on an individual level there would be people who just don't care, but by and large I feel like people would simply focus more on creative pursuits or other productive output. I think the big issue with automating jobs away isn't so much that it reduces the overall number of jobs in some particular sector, but that it takes time to for things to stabilize after a big change. When the industrial revolution happened, the effects were twofold: you had some jobs suddenly require far less human labor; but you also had the growth of entirely new sectors which required the new technology to even exist. Factories as we know them today did not really exist prior to the industrial revolution. AI being able to automate some software jobs, assuming it actually does continue to improve at the same rate it has been (which I'm not so sure it will), it will undoubtedly improve individual output per person and lead to a reduction in jobs explicitly doing certain kinds of work. However, even if it causes a contraction in the entire industry at all levels, on the level of society that means that we'll have to reallocate labor towards different markets. There's currently a real lack of people entering the skilled trades in North America, for example. There's also a shortage of medical workers, teachers, and many other jobs. Of course, this abstracts away the difficulty that retraining presents, which is something that we have been chronically horrible at, to the detriment of everyone involved. When a particular market sees a contraction in jobs, this inevitably means people need to move to different markets, and this implies that many of those people will require some kind of retraining or additional education, and that is something we as a society have so far been absolutely godawful at.
Damnit BackendBanter, Ocaml was mentioned getting me pumped and now I am deep learning about TS and going to need to explain to my Danish wife why Americans use guns instead of swiss army knifes...what a bambooze lovely pod btw 🙂
undefined - value not set or maybe just not loaded/fetched null - I explicitly know that the value is not set For example if I give you an object that was result of TypeORM query. And that object/table has some relations. If we do not have undefined AND null you would not be able to distinguish if the relation on the object was just not fetched or is actually not existing in the database (first is undefined, second is null).
25:00 Leave out the keyword entirely and just assume a new identifier followed by (0 or more parameters then) equals is introducing a new function. There, now you're writing Haskell.
how can you trust anything made my microsoft? typescript constantly "solves" problems that it creates, i wish matt would try another language like Elixir. we could use his radio voice over there.
Thank you! And sure, here's the link github.com/microsoft/TypeScript/wiki/Coding-guidelines#null-and-undefined. One thing to mention though... I forgot to mention the disclaimer at the top of the page, which, is REALLY important
And you can tell that code in his entire portfolio was written by a voice coach: Delivery for which is "powerful and confident", but is just average in true knowledge about how hardware is to be used optimally via the intentions communicated, which are of a class oriented (not object) nature.
