Видео

Who ever tagged the chapters in the video, the company was called "Knight Capital " not "Night Capital"

I do not like this. This does not work for an app with a lot of interactivity. This example is not more complex then a todo app. Why do you need vue at all for something this simple?

51:42 - Today way the day when it all happened.

Interesting stuff, but WHY some things stick seems to be missing? Giving a lot of examples of things that have stuck is just hindsight being 20/20. The mystery of that answer appears to still be out there. With that said, this book has dramatically helped with guiding a proper launch plan for a product (Part 3: Marketing) which is very content rich and worth the read.

5 years later and I’m watching this and it’s still relevant…does that mean its more likely it will still be good content 5 years from now?!

Love it!

hmm is there a way to ssh into the serverless server if I need to apt install some packages ? for example my scheduled tasks run some commands that rely on 3rd party packages etc

Great talk. You looked great with a beard. 😂

He does a good impression of Jack Benny.

Great tips Thank you

The mighty have fallen.. 😆😆

I was there

Didn't the moon landing rocks turn out to be fake, not surprised theyre very similar material to earth 😂

Thank you for sharing the video

That SVG trick was neat. ViewBox is the boss!

This is gold

real content starts 1 hour in! ruclips.net/video/NeXQEJNWO5w/видео.html

I don't want to sound unrespectful , but when was the last time when he wrote production code from actual requirements and dealing with time constraints. I tried to search his projects and everything is just books and courses. Not saying that a lot of what he says does not makes sense, but in the real world those perfect conditions and the perfect architecture, application completely decoupled from everything etc. exists only on the bookshelf.

Does 11:12 solve the class naming problem like css modules does?

What the hell is this? The first 20 minutes are a colossal waste of time. It is flat out disrespectful to an audience to just blabber about nonsense trivia for so long.

Very informative.

"highly entertaining".. Unwatchable

Would have loved to known about this video some time ago. We were going to be starting a project in several months at my job, so I asked "What kind of architecture should we we use? You know, what is at least a rough idea of how we're going to build this thing and work together? We can iterate as we go, but just to get a foundation of what our approach should be." Time goes by without any discussion, the team lead just kept saying there's no need to plan that stuff, we'll just do it the "framework's way". Whatever that means no one really knows it still seems, best I can tell it's like some sort of feeling about how to do things that you just know somehow. I had been advocating for something similar to what Uncle Bob was saying here, that we shouldn't do it the "framework's way" or any other way that makes us completely dependent on a library/framework. Instead I was pushing for this plugin approach where all of our core business logic and services would be written in vanilla JavaScript and the framework would only be responsible for taking that logic to handle creating the view. Well they didn't like that because that framework was of course the answer for everything and they wanted to rely on it 100%, job security or some love affair with the framework or something. We really get attached to these tools... Anyway, we get a month into the project, things are going poorly (surprised?), we're fighting with each other about which way is up or down and how to approach the problems we were facing. We couldn't even decide on how to write CSS and development was about as fast as a sloth. All the way up to the project being taken away from the team there was fighting and indecision and little concept about how we were even trying to work on this thing. Architecture matters for another reason too, it let's us not only build good software, it let's us work together well and with a clear plan so we can get the job done. You wouldn't want to be months into building a house, have the walls up and starting on the roof to only then realize you never laid the foundation, would you?

Jelly buttons and dropshadows are perfect hahahaha

How to use View Presenters with Collection of models (not single model)?

Does putting eloquent codes into model helps in reducing memory usage

28:11 ctrl+c ctrl+v fail xD

The talk was very good, and what he said made a lot of sense. Thing is, what he presents is a very ideal way of developing software, which is not always worth the effort. Many people who build websites know that the 'delivery mechanism' is always going to be the web, not a console or anything else. The lengths one has to go to, to generalise everything is simply not worth it

5:12 Nova Overview 7:04 Resources and Basic Fields 9:14 Panel Field 12:07 Observers (Events) 15:13 SoftDelete 18:00 Advanced Fields (Date and Time, Markdown, Trix, Json, Code, File ) 30:08 BelobgsTo ( Searchable Dropdown Field) 32:14 Search with Laravel Scout 34:50 Global Search 36:43 Place Field 39:30 Relationship 43:35 Overriding field method 😊 45:11 Filters 43:30a Lenses 45:10 Actions 1:02:14 Value Metric 1:05:41 Trend Metric 1:09:10 Partition Metric 1:10:55 Permissions (Policies): Authorization 1:21:10 Customization(Add your own stuff to Nova 😊)

Whats software use to admin your database? please...

I dislike rails very much so I am not to defend it. When he shows the church he shows every component of it so we realize it’s a church. We should expand the directories too for the overview of the app. Just looking at the root directory and bashing it doesn’t seem fair to me. Then don’t show inside of the church too. What do we see? Just a roof.

He is so good at telling story and letting you learn. Still not sure what the science at the start of his talks are for. A little personal interest and a bit of waking up coders to think 🤔

Get to de chopper

What is that browser he's using?

One of the best talk and explanation of the Design Patterns

The goal of coding is not cleanliness. It's functionality. If you want to be in the cleanliness business, then janitor is the better job description for you.

I am creating a report for my Client who wants to buy nova, and I basically take notes when you guys clap,

tailwind is an API for your design system, and only that makes it amazing 👏️

The great talk I stumbled upon only now. It's really nice to see how much Tailwind evolved over these 2 years and some of the stuff such as long compilation times, "no animations", not able to apply arbitrary values per breakpoint, html duplications just for responsive reasons, all of this stuff is no longer the case in the new version of Tailwind and each day some new improvement is on the horizon. Great work, Gendalf Adam! 🧙🏻‍♂️

That has to be the best intro ever...

Wow! Uncle Bob Thank you, sir! This is a big one

“Hey everyone, this is Taylor Otwell BACK with another Laracon keynote...”

I think subqueries aren't a silver bullet imagine having a thousand concurrent users using the app. Your script is now waiting longer to get data(now the db is the performance choker) back from the database hence most people go the caching route is such an instance.

Nowadays you can use Mock, you don't need FakeLocator class

If you want a front-end developer job you are still going to have to learn css

How you deal with code splitting? Or you just loading all of your style on all pages?

This is so good

For the strategy pattern on makeparser method you could register the parsers in an array and instantiate a parser based on format supplied. Love this video by the way

Title: "Clean Coder" Talk: "Architecture" me: *profusely confuselt*

The second to last point about inline styles isn't an issue anymore with the JIT module for Tailwind. You can put arbitrary values on the normal class name with breakpoints and whatever however you want.