Видео

I'll take capitalism and free markets every day of the year.

Great talk!

If you just followed this pattern, you'd have functional core, with an imperative shell that deals with IO. Now you have to do more functional stuff that you couldn't do before because it requires the result of the IO. So you do it again, you accept the IO from, do some pure stuff, and then result go to IO. And then again. Scott is completely ignoring how real world application s work by showing toy examples. The reason is because it gets way more complicated, and that makes this functional style a lot more complicated. You're not getting rid of complexity. Next: You never have to mock pure code. Hogwash. You mock those things that are slow. If I'm doing heavy math that takes 10 seconds to calculate, I'm not going to run that in every test simply because it's "pure". I'll mock it when I'm testing other code that depend on it. Scott knows this. He's been doing this long enough. But he loves to trivialize things to make thing seem more stable, and then pull out the "it depends" card later. It just comes across disingenuous.

So all in all this is just an advertising for Deunde server product?

How have you guys not talked about the best part of fsharp? TYPE INFERENCE. seriously. I'd take Hindly Milner type inference over almost any feature. not having to babysit the compiler is the most amazing speed multiplier in code.

Irina's talk made it to the last issue of Tech Talks Weekly newsletter 🎉 Congrats!

This is a really nice intro to vector databases and it has been featured in the last issue of Tech Talks Weekly newsletter 🎉 Congrats Erik!

Nationality: Azerbaijani Accent: Russian Company: Norway Place: United Kingdom Hotel: Trivago, of course

Some of us were rendering client side using Dynamic HTML and JavaScript in the early 2000's.

We need to move past the web and start coding dreams for angels that can save hubmanend cind

This is not technical enough. Not NDC worthy. Unfortunately waste of time for devs.

"Okay, we'll give a UX guy one shot to have a talk this year. What will it be about?" "Pickles!"

When you have to rely on heavy mutability => C# For pretty much everything else, F# is what Microsoft wishes C# could be.

half of the presentation is advertising for azure

I lost interest in the video when he claimed pickup truck drivers dislike electric car drivers based on their voting preferences. For someone who should rely on science and principles, this is disappointing.

2x speed is perfect to watch this video

interesting talk, thanks for putting me on to residuality theory

It is interesting to see bridging various technologies like that. Fantastic Steve Sanderson, as always. I love his presentations and the level of detail and complexity he usually goes into. However, the presented concept of combining technologies is making things on the backend much more complicated than most teams will want to accept unless they really have to integrate some legacy code/functionalities/externalities. The more tech interfaces you have to deal with, the more points of failure for your system and issues that will be hard to overcome. It's really difficult for me to come up with a valid real-world use case. Any specific ideas?

This is it. This is the future and I've been searching & experimenting for MONTHS and this is literally the FIRST instance I have found of this type of implementation of Multi-Modality!

GCP Pub Sub is missed the biggest messaging system in the world lol:)

Very good!

I liked the disclaimer at 46:40. However, the Handle method must be marked async, and the SingleOrDefaultAsync extension method should rather be used to actually compile the code. Other than that, I like the idea of vertical slices and I worked on projects that had grown into huge sizes and suffered from what Chris described. I just would love to see some examples or some discussion around good practices of how to layout the features and their borders because it is a pretty vague term tbh. I also am quite curious about what the design decision-making will be for huge projects when a change order arrives with a new feature that overlaps various existing features. It can become pretty hard to tell where one feature ends and another one begins. Or do you create a new one? This can become pretty messy quite quickly if it's affecting existing views or other end-user experiences.

Really??? People is afraid of computation expressions? Unfortunate

I'm feeling in love with martial arts because they came with the term "Bullshido".

TIL the old weird flashy lights are the equivalent of modern RGB leds

First!

Does your events include the whole aggregate root and everything within? If not, how do you handle out of order events?

There are tools based on tracking cookies deployed by state actors & bad guys to obtain physical location of an individual. Whoever says they don't care about tracking is out of touch

The Facebook diss about “300 billion” was such a miss lol

I love what I ever seen: Microsoft employees never used Microsoft Windows. lol

If you're considering FP, I would recommend Richard Feldman's 2021 talk called Functional Programming for Pragmatists over this talk. These OOP vs. FP talks aren't very helpful because they don't address the software qualities that each tool (i.e. programming language) produces over time. It's like arguing that a sledge hammer is better than a ball peen hammer. They both are useful under certain situations.

Great presentation, thank you!

Bravo! Great presentation! 🙌

I'm almost afraid to bring this up, but here it goes: For me, the biggest disadvantage of F# is that it forces me to use spaces for indention. I don't want to start a tabs vs. spaces flame war here, but at least, I'd like to have the choice. Especially for visually impaired developers, this is a game changer, and forcing spaces for indention borders on discrimination. (Yes, I know there is an option in F# to use tabs if you really want to, but it comes with so much baggage that it's almost unusable.)

Qute superficious. Not a deep dive.

There is a built-in Audacity plugin that can remove the background hum by giving it a sample of it from where there are no other sounds in the source.

Funny and informative - hits close to home on some points as well. Would love to see a "build a good (or just acceptable) one" as well :D

Please get to the point faster. Took 20 minutes to get to the topic of the talk.

Seems like this talk mirror’s Ian Cooper’s TDD talk on many points.

Funcional bros - stand up

It's extremely hard to listen to this talk, this dude constantly uses words "like" and "right". According to the transcript, he said "like" 275 times and "right" 240 times in 58 minutes, which means that he mentions those words on average every 15 seconds!

how to explain common sense with buzzword bingo

What a super video!!!!

46:36 Async/Await Best Practices

F# is so concise and pleasant to work with

What was the exception handling library that Max mentioned?

C# rules forever

Esoteric misinformation. It's funny how she contradicts her own statements by explaining, that every disability is different, and you shouldn't make assumptions. Then goes ahead and claims that increased accessibility can lead to higher revenue and will extend your reach to a previously not accessed audience by over 26%.🤣🤣 How does this work, and I thought not all disabilities are the same? Hey NDC, can we have some quality control? what a joke

Dat hair.

Thanks for the paradigm shift with regard to code duplication