Відео

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

Great stuff as usual Chris. The background is wild 😂 One thing to highlight is ASB only supports private endpoint on the premium tier. Which is wild considering messaging is probably the most important piece of infrastructure you want to isolate from public traffic.

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

Micdrop moment: AI can take care of the roses, human, the guns. Thank you!

I'm very mixed on the whole issue. I studied Cognitive Science because I thought AI was interesting but these days? It just makes me depressed, for a few reasons. One is the preponderance of grifters using the tech to churn out and endless series of nothing products and passing it off as real human labour. But within the realm of professionals using ML models for their work, I see another issue: A backward slide in skills. I'm not convinced that GitHub copilot or Dall-E exist on the same level as digital recording software or digital cameras. The latter are more convenient media to be sure but the art you make with them still requires actual skill and labour to create. Machine Learning models that write code or paint an image for me are doing the entire process, and I think Dylan identified that people still want to create things. Musicians still make music, photographers still take photos. These people are not going to accept prompting an AI as a replacement for the creative process, they simply aren't the same. And I feel it's a similar story with code. I got into software because I like problem solving, I like learning new things. If the future of the industry is that I ask a computer to write code for me and I bugfix it, well my job is no longer programming, it's PR review, and that's not why I do what I do. I'm also not encouraged to develop new skills like this, or to expand my horizons. I can see the value in reducing busywork for simple tasks, but even there I simply don't trust the technology to do it right, and if on top of that I'm giving my data to a company who are turning my labour into their quick bucks? I'll stick to working for myself, I think. I dunno, the tech is neat but I don't have faith in its trajectory, socially.

NO. This is going in the direction of MAXIMAL COMPLEXITY. Huge developer teams will be needed, ONLY large companies will need to apply. Smaller developers who want to be productive CANNOT benefit from such complexity. Voted down.

I don't know.. keep it simple. He over complicated things

Conferences could do a little more for accessibility for their own attendees by providing live human-curated subtitles, rather than AI-generated!

I'm confused about "only test the public interface that other people depend upon" at 28:04. The implication of that seems to be that if the entire system is developed by one team with full collective code ownership, then you should only test at the user or other external interface of the application. But that can't be right, since testing at the user interface level is generally hard work and fragile. So maybe it means have the app split into modules and test at the module boundary level. But then the problem of what to test isn't really answered, it's just replaced with the problem of how to decompose the app into modules, and if you change that arrangement of modules you'll still need to change the tests. And not all languages have a native module system where a module is distinct from a class or a function. And writing a test for a module may be a lot more complicated and require a lot of irrelevant details that gets in the way. E.g. in the example of calculateFoo, if Foo is something that the customer understands (e.g. foo is the postageAndPackagingCostEstimate for display on a shopping cart) then having a focused test that calls that function or something close to it seems a lot simpler than a test on a bigger scale where more setup is required so we can call a bigger function that e.g. also has to calculate the taxes.

I cannot not think of Werner Ziegler of Better call Saul...

Great migration story!

So he renames System Test / End-to-end test as Component Test (which already mean another thing). The people in this industry has zero capability to respecting the original definition

Nice Talk, thank you.

nice presentaion. i now understand why windows desktop apps are soo bad. so many ways to build a just windows desktop app. confussion cloud. thats why people build desktop app with web technologies.

🎯 Key Takeaways for quick navigation: 00:51 *🛠️ A good schema should solve a business problem effectively, avoiding scope creep and internal technical complexities.* 02:55 *🧠 A good schema should be easy to reason with and understand, facilitating future maintenance and team collaboration.* 04:03 *🗺️ Designing a schema involves transitioning from real-world models to structured database schemas, ensuring alignment with business needs.* 07:53 *🔍 Schema descriptions involve entity graphs, representing relationships between different entities like catalogs, items, and invoices.* 09:59 *⚙️ Schema optimization impacts performance significantly, requiring deep understanding of database engine capabilities and implementation details.* 11:38 *⚠️ Regrettable schema decisions include complexity, downtime during changes, and significant work investments for modifications.* 20:33 *🛑 Avoid incorrect data types, such as storing dates as strings, as they lead to inefficiencies and complications during data processing.* 27:15 *🛠️ In relational databases, designing table schemas with columns that cater to different types of data can improve data integrity and query performance.* 30:27 *📚 Abnormal form in database design leads to inefficiencies and data integrity issues, such as sparse columns and unnecessary null values.* 36:42 *💡 Natural keys, derived from real-world entities, provide meaningful and stable identifiers in database design, promoting simplicity and efficiency.* 39:11 *🔍 Exposed locators, like auto-generated keys, lack real-world meaning and can lead to synchronization issues and hotspot risks in database systems.* 47:55 *🔑 Sequential primary keys and surrogate keys should be meaningful, stable, and convenient to ensure efficient database operations and schema migrations.* 51:07 *🔄 Object-Relational Mapping (ORM) can lead to inefficient database access patterns and challenges in schema management, especially when treating databases as repositories.* 54:54 *🔄 Object-Relational Mapping (ORM) can introduce challenges in concurrency handling and change tracking due to the disconnect between in-memory objects and database entities.* 56:09 *🛠️ While ORMs offer benefits like connection management and data mapping, they can complicate stored procedure calls and introduce unnecessary complexity in handling change detection and concurrency.* 58:01 *📝 Ad hoc Data Definition Language (DDL) changes lack repeatability and reliability, making it difficult to track changes and troubleshoot issues. Using migration scripts enables automation and facilitates CI/CD practices in database management.* 59:49 *🔑 Utilize natural keys and maintain database integrity by storing atomic values and employing concise data types, avoiding the use of ambiguous formats like JSON or XML within relational databases.* Made with HARPA AI

I'm really not into EF Core. I have always the feeling I'm battling the framework. This talk only strengthens my opinion. With Dapper I always have the feeling to work together with the database. I know exactly what is going on and why. With EF not so much.

its a history lesson that skipped a whole decade (Newton, Psion, Symbian) of mobile device operating systems. he describes Neotron within 5mins.