วีดีโอ

Where's the new videos!!!!

5:00 (line 13) wouldn't "return x instanceof String" work as well?

Thanks mate , you did it great!

Explaining with the use cases is very clearly understandable. Definitely i will install Contextive extension for VS Code. Thank you🙏

I have recently gotten into the habit of being more verbose in my C# projects and I find that when designing I write my high level code in almost plain English including variable/function/class names. And Then I go back up to the top and hit Alt+Enter then Enter on each line to "generate whatever code" and the implement that code. It forces you to write the whole project before testing, but it only codes what you need, rather than designing each part one at a time and doing full unit tests all the way up. (This is just the first pass, i usually go back and refactor a ton)

Naming Things -Objects are Nouns -Functions are Verbs -Less is More -Description is more

I just getting into the concept of IoC and i loved this explanation. It was simple and easy to understand. Loved the examples too.

The very use of the term "code" as a synonym for the more accurate term "source description" sadly suggests a fundamental limitation in what follows.... There is no intentional or unintentional attempt to ENCRYPT or even subsequently decrypt anything whatsoever in any correct conventional sense of the term code!!!

👍👍

👍👍

Pair programming philosopher. You are probably very human-oriented, but software engineering is not human-oriented profession, but project-oriented. Education in the project is important, but strong leadership is needed to broadcast the knowledge and project assumptions across team members. Pair programming is a wasting of time and no results consuming a lot of energy and distracting from a real work.

There is a trade off though, make code bases too loosely coupled and you lose cohesion

Pair programming is an idea and it should not be enforced.

I'm impressed, that was super clear and well explained. Thank you. I shall check out more of your content and subscribe!

The statement that code ownership is a bad idea and that everyone on the team should share the code seems like a good idea at first but there is a learning curve involved with jumping between the different pieces. We experienced this when we coded a system that spanned database code, front end code and mainframe code. Every few months we needed to refresh on MVS/TSO/JCL/DB2 ...of course if the code base is small this works well. I think pairing works best on initial design approach before coding starts. And then it would be more of a team discussion.

Very nice video man! keep it up! :)

I'm a bit confused about why there is loose coupling between A and B in the example at 2:33. I thought there was no coupling between A and B since they are not dependent on each other. By the way, great video!

From now on, all my stand-ups will be using a Dutch accent.

Your content is fantastic. I will be sharing with my colleagues. 👏👏

thank you so much

What you're neglecting is that a reader is almost certainly reading for the purpose of being able to write. That means that convenience of the writer is of nearly equal priority. Not disputing any of the recommendations just that the motivation is definitely for support of writer as well as reader.

I love this. Thanks!

The Facade Design Pattern, so beautifully explained. Thank you very much. {2024-07-01} - Subscribed!

Thank you! Your teaching style actually fits with mine, which is rare in this field.

Your productivity software reviews are great! By the way, Immersive Translate is a must-have for anyone needing translation help. It’s free and versatile.

Great Video, I have seen several times that using bad Language resulting in big problems, in a recent case I noticed that developers were using contractid and consumerid very loosely, then when the project was ready to be released a use case came up from someone who had multiple contracts (a private and a business one), however everywhere in the database the relation between consumer and contract was 1-1 instead of 1-n, in the end it costed us 2 additional sprints to fix this, and it could have been easily avoided if we agreed on more clear language. Another one, which you see a lot is that there is no clarity about language/country, at the start usually not a big issue, but when a project evolves it often becomes clear that a wrong structure is costly to fix.

So for the iife exemple, if the function is called and not saved in a variable how do you acces it's content doesn't it just get popped away after it's called ? I don't know if my question is clear.

thank you bran. this is exactly what i was looking for.

Good stuff. Will share it with my team.

Im going to propose this at the start-up im workign at 🎉

Really great video. I am running my first post-Mortem meeting tomorrow and this has relieved some anxiety for sure. Wish me luck! Thank you for the quality content

This was very useful!

Vulnerability is for the brave. Very nice introduction, already hooked up. I'm trying out mobp for the first time next week. Can't wait for it to happen 🎉

Great explanation. I was looking for an example in React. However, your speaking tone and the mild music in the background made me a bit sleepy lol.

I have a code paring interview coming up. This video is helpful.

Great topic! Thank you so much for your explanation and reasoning about this topic.

How can I recognize a facade pattern?

this channel is so under-appreciated. Good job on explaining topics realistically and in simple words.

Excellent. Yes your examples were great.

very good explanations, thank you! I've literally been using IoC without knowing it has a name, or that is a common practice

This is actually the best explanation of the Facade pattern I have stumbled upon. Well done sir!

wth this video is so calming i actually wanna go to sleep lmao

An example would be more valuable

Great stuff Bran, as a Product Owner I always insist on empathy with the user, also from the development team (and vice versa) this really helps. I tried building a glossary for the product team and client, never thought it could be implemented into the code.

Detailed explained

That is very helpful! I am not a developer but some of the concepts can definitely apply to other positions as well.

Fantastic video. Very insightful

One of the best videos to get a clear understanding about the big picture. Thanks a lot.

Excellent video quality, thanks 👍

I like that you have mentioned Nest.js Ive being developing in Nest and depedency injection looks like a magic for just use the decorator Ive asked myself tons of time how it was implemented and now Ive a clue I still would like to see an implementation example