Пікірлер

• 
  @thechillhacker6 ай бұрын

  Thank you for the talk. One point though, you are not unemployed. You are actively working, you just need to find a way to monetize your work. You are self employed, currently generating zero revenue. It's just a mindset change that enables the shift. I know I am necroposting, but this is a huge thing we all need to adopt, employed or not.

• 
  @user-gu4ho3pj6h6 ай бұрын

  Just get on with it during seminars. Wasting BS time in the beginning.

• 
  @Pedritox095311 ай бұрын

  Great video!

• 
  @Cyril29a Жыл бұрын

  The end result is not the advantage, the reduced friction of management is. I can spend a year or two and plant wheat, raise chickens and make a sandwich but it's easier to use farming and butchering infrastructure to reduce cost

• 
  @Cyril29a Жыл бұрын

  3:25 the answer is that yes they are very similar but Unikernels are easier to deploy because the were built with deployment as the main feature right?

• 
  @Cyril29a Жыл бұрын

  A unikernel is leveraging the complexity of an OS to machine interaction to obfuscate Physical and Datalink layers from possible exploitation by wrapping them in an application layer of a stripped down hypervisor

• 
  @nether_bat Жыл бұрын

  That ribbon cable hurt me

• 
  @laszlob3683 Жыл бұрын

  And people be wondering why its called MAD 😅 Sometimes programming makes us ridiculously fast in a way…

• 
  @helmanfrow Жыл бұрын

  Someone please travel back to 2016 and adjust the podum mic for Katie 1.

• 
  @AshishSharma-wl2og Жыл бұрын

  nice one Jamie ..!!

• 
  @suic86 Жыл бұрын

  Great talk!

• 
  @PacificBird Жыл бұрын

  People who think type errors are an annoyance sure must love running bugs on their client's machines lol. Like No Boilerplate said in their video on the Rust compiler, the only thing worse than bad errors is no errors.

• 
  @hnasr2 жыл бұрын

  Best explication of NUMA I heard in a while 4:40 great talk

• 
  @punggukbulan86742 жыл бұрын

  from where we get SSLKEYLOGFILE ?

• 
  @eddieyu802 жыл бұрын

  LM2940 (26V max) will soon burned out in 12V vehicles soon, even with 24V protection variastor (TVS) in the front.

• 
  @thegiantratthatmakesalloft94152 жыл бұрын

  George fong

• 
  @AlexisFinn2 жыл бұрын

  Nice talk, and pretty interesting. That being said I want to learn Haskell and I feel that one main point has not been addressed and that is what I would call the Elitism of the language. I am a PHP programmer (mainly), and yes php has lots of problems, I'm not trying to say it's better than Haskell. But one thing I really hate about Haskell (not specific to haskell mind you) is the elitism of the code. It's difficult to read and understand. Most haskell code thrives to be "elegant" which is just another way of saying we crammed as much instructions as possible in the minimum amount of space, making it basically impossible to understand for an outsider. Take pretty much any Haskell tutorial and look at the function arguments: 'x', 'y', 'z' , '(x:xs)', '(y:ys)' etc... and this is considered standard practice. Why can't you give your parameters meaningfull names ? Can you at least comment your code to help me understand ? No ! How am I supposed to know what those parameters stand for ? Answer: I can't, I have to go read some kind of Documentation somewhere explaining what they are supposed to be, and generally that documentation just makes me feel dumb because I can't understand half of it so it generally boils down to "If you don't have a Phd in Mathematics and don't fully understand what Lambda calculus is, you are not worthy of using this code". Wheras in reality using meaningfull parameter names, adding some comments in the code and using a more explicit way of doing things would have enabled me to understand what the function does without even the need for documentation. I Hate this, I believe good code should be understandable by pretty much anyone, ideally even someone with no programming background should be able to get the idea of what is going on by reading the code. The prime example of this I feel is if/else vs ternary conditions, or explicit return statements vs directly returning the result of an operation in parenthesis. Yes the code is more elegant and requires less lines, but at the end of the day it doest exactly the same thing and is inherently less readable. If I show a simple if/else condition to my wife, she will probably get it, whereas if I show her the exact same condition in ternary form she doesn't have any chance at all of understanding what the code does. There it is, that's my little rant about Haskell and can definitely be applied to many other languages but I do feel Haskell is one of those languages that goes the extra mile to make sure that people who are "unworthy" are not able to understand the source code.

• 
  @qwing1232 жыл бұрын

  I haven't finished watching this talk yet, but already what I have seen amounts to a kind of response to at least some of what you say here. You say that explicit return statements are more readable than ternary conditionals / not using explicit return statements. But as the talk points out, the reason why you think that's more readable might have to do with your background and prior coding experience. Someone who hasn't done any coding in imperative languages, but who has been exposed to functions in math in primary or secondary school, may find it more intuitive that the function `f`, as defined in Haskell by `f x = x`, is the identity function --- it looks, after all, just like the f(x)=x in math. I'm not saying that everything about Haskell is easier to understand for someone w/o programming experience. But I do think that it's at least not obvious that things like explicit return statements are always easier to understand, and that, as the talk observes, one's perception of what may or may not be confusing might be influenced by one's prior programming experience.

• 
  @springworks00682 жыл бұрын

  These are really great ideas, I can’t believe this talk isn’t more popular

• 
  @alirezaghey87632 жыл бұрын

  Great talk! Great person!

• 
  @lepidoptera93373 жыл бұрын

  Haskell is the new Perl: write once, read never.

• 
  @kenwood71953 жыл бұрын

  Is there anybody who can present this shit without putting me to sleep?

• 
  @bigguy54553 жыл бұрын

  it is physically impossible to make identify management interesting

• 
  @anubhav007ful3 жыл бұрын

  I have replicated multi-master environment of freeIPA server. Now if I lost 1st master server then how can i promote 2nd replicated master in place of 1st master server ?

• 
  @joaquinlabastida60513 жыл бұрын

  I can’t get the mouse to click on a specific frequency. Ex. I would like to click on an fm radio station 102.5; the mouse will either go to 102.000 or 103.000, but won’t go to anything in the middle.

• 
  @maurofarias14373 жыл бұрын

  Ola parabéns! quanto custa? faz um e me vende? moro no Brasil.

• 
  @zureao3 жыл бұрын

  Boa noite Mauro! Estou fazendo um, me chama no WhatsApp pra gente conversar. (85) 997063050

• 
  @hadjakiedeva57493 жыл бұрын

  thanks

• 
  @Reavenk3 жыл бұрын

  26:32 Man, I'm rusty with emoticons. I didn't see scissors; I saw a proctology exam.

• 
  @embeddedmicrocontroller3 жыл бұрын

  Good work

• 
  @limabravo60653 жыл бұрын

  I’ve used two of these systems for customers, one being a small block ford and the other an LS. For about a third the cost of say a Holley, Edelbrock, FAST etc.... you get a very good system. And the bigger companies all advertise their systems as being capable of “self tuning” (a base map is auto corrected based on wideband readings, does not tune for wot), the Speeduino can do the same thing via Tuner Studio

• 
  @8SecSleeper2 жыл бұрын

  It doesn't need Tuner Studio at all. I believe he left it like that to show support for TunerStudio, as people will buy it for the the silly auto tune.

• 
  @armstrodsoftsuit58263 жыл бұрын

  That is an impressive rules based processing engine. Haskell. The engine seems to be applicable for many scenarios. Managing with policy and understanding and translating the policy bullets seems like the challenge step. I liked how she stated it just replicated out and reattached to the rules engine. They visualized this process in 1990. Wow.

• 
  @lepidoptera93373 жыл бұрын

  Your post was about as unreadable as hello world in haskell.

• 
  @lepidoptera93372 жыл бұрын

  @@techtutorvideos You forgot the "main :: IO ()" part. Why in the world do I have to tell the compiler that my program lives in the real world and is not just a mathematical abstraction? And why is line feed part of the function call???? Dudes, that is braindead. Having two different function calls instead of a control character is something that only depraved minds can even think up. You might as well be programming in Brainf*ck. ;-)

• 
  @orenzeshani3 жыл бұрын

  Since then, Singularity came along

• 
  @arzoo_singh3 жыл бұрын

  Awesome work!

• 
  @dagysteinjohansen72683 жыл бұрын

  So where can I buy this new generation of microwave ovens..? Fully agree with the premise, and it's not just microwave ovens. It's as if there was no competition in this field, because the engineers aren't innovating AT ALL for these household items. I'd like to see the relays go as well, in favor of some power MOSFETs (or any other fast, electronic, non-mechanical switch that can do away with the extremely long ON and OFF intervals used to very poorly emulate "power levels").

• 
  @jeonsoft24813 жыл бұрын

  Joy comes in the morning, PYthoNJ4ck made me smile again as I can finally access my Dropbox files and recover missing one’s to, what a resourceful service :

• 
  @jeonsoft24813 жыл бұрын

  Joy comes in the morning, PYthoNJ4ck made me smile again as I can finally access my Dropbox files and recover missing one’s to, what a resourceful service :

• 
  @thegameoflife91793 жыл бұрын

  Programmers learn and use languages like Haskell because somebody above them usually wants them to.... after all, if a language thats stable and been available for years (there are many, and most of us know what they are) can do what you need it to, why learn something else, especially if there is no guarantee it will do as you want? Of course we all want to learn new things, thats how we progress, however, to have the desire to do that we need to know it will enable us to do more or to do better than with what we already have? Does Haskell? That is the question.

• 
  @vapourmile3 жыл бұрын

  Thank you Katie for using "Use case" and actually understanding what it means.

• 
  @DRACOBUCIO3 жыл бұрын

  How can I get digital modulation options? 5:20 I want to decode with FSK, but I guess that standard CubicSDR doesn't have it.

• 
  @indianhuman3563 жыл бұрын

  Awesome

• 
  @tthtlc4 жыл бұрын

  In 1997, I saw a video (while working for Oracle) of how Oracle can migrate all the transactions and processes from one server (in a Oracle Parallel Server product) to another - cleanly maintaining all the two-phase commit transactions and it integrity. (In OPS, two database server will share a common physical storage for database).

• 
  @tdcvol68314 жыл бұрын

  máte špatně informaci o CAS optotronic crank a cam signal zjištění prvního válce je dlouhý puls

• 
  @tdcvol68314 жыл бұрын

  am emmm emmmm emmmm emmmmm emmmme mm mememmmmemmememmmee

• 
  @simivb4 жыл бұрын

  Its just a tiny nitpick, but it drives me crazy that so many people use the term nondeterministic wrongly, like how "exponential" has just become a synonym for "very fast". You have nondeterminism when you know everything there is to know about your current state, but you still can't predict the following state. User input or timing does not introduce nondeterminism. The fact that you don't know the timing or user input simply means that you don't know what state you are in. But if you knew ALL about yout state, you could perfectly predict the next state of a program. In fact, the very approach used here, of replaying these input demonstrates that all software is deterministic!

• 
  @YoloMonstaaa Жыл бұрын

  by that definition, nothing would ever be non-deterministic because if you know everything about everything, you can always predict the next state.

• 
  @answervalidargumentsonly18504 жыл бұрын

  Is that nine hundred Hz a secret tone suitable to indoctrinate us into using Haskell?

• 
  @rajarshighosh1214 жыл бұрын

  Really liked the design of the slides!

• 
  @swarnimbarapatre97334 жыл бұрын

  kzread.info/dash/bejne/aomao5mthbPPnJs.html work of art on haskell junichiro swanson

• 
  @c0mpaq3424 жыл бұрын

  so hot!

• 
  @zgk_tech81304 жыл бұрын

  Amazing , must have a look kzread.info/dash/bejne/eKZ7stdtadGxo9o.html thanks...

• 
  @kayboku72814 жыл бұрын

  Beautiful!

• 
  @kirie_mai90554 жыл бұрын

  This is amazing!

• 
  @coreycole24874 жыл бұрын

  Here are the slides used in the video coaxion.net/~slomo/talks/lca-2016/LCA-Synchronised%20multi-room%20media%20playback%20and%20distributed%20live%20media%20processing%20and%20mixing.pdf