Видео

Watching this in it class

Cmake sucks, Bazel sucks... no hope 😂

hi mate, I have your first edition. what's new in the 2nd please? cheers

I'm applying to a tech lead role. Got the interview tomorrow. Great insights Rafał, thanks!

♥️

Hi Smok, thanks for sharing. i wanted to ask you, can you extend your styles to also apply to component diagrams? testing I see that it doesn't apply to package, folders, nodes and other components. Thank you very much for your work!

2:53 - 3:02, THIS SUCKS!!!!! 😂😂😂😂 , i thinks that is a way better comments

Great content

Nice video, really helps me as a newbie to testing.

In Software Engineering, besides programming paradigms and methodologies, I would also highlight Worlds... In the context of software engineering, I discuss an interesting question with my students - what is primary, the Hole or the Bagel body (the algorithm or the code)? Does the Hole generate the Bagel, or does the Bagel body create the Hole, or did the Hole exist before the Bagel body? After that, we move on to discussing two Worlds of software engineering: Algorithm-centric and Code-centric, similar to our understanding of whether the Sun revolves around the Earth or vice versa, the Earth revolves around the Sun. It's very interesting to listen to their reasoning on this topic. In v-agent oriented programming (VAOP), Finite State Machine Programming, and model-driven engineering, we support the Algorithm-centric world with our methodologies, while for many, the Sun continues to revolve around the Earth, and there are no other options. For example, read what representatives of the Code-centric software world write: "The code is the algorithm. The code implements the algorithm. Therefore, the code documents the algorithm automatically." Such zealous Code-centrists burned Giordano Bruno for saying that the Earth is not the center of the Universe, but the Algorithm is. It's best to start familiarizing yourself with VAOP with this article on Medium: "Bagels and Muffins of Programming or How Easy It Is to Convert a Bagel into a Black Hole".

should i buy first edition or second edition?

4:46 Best part

I thought it was Zelenski teaching C++🤣

what editor r u using? why r u not showing the whole window?

I wasn't going to leave any comments but you changed my mind

I am quickly becoming a digital pasta chef.

There are plenty of tutorials on cmake and I've scanned quite a few before this one. You answered the most important question within the first minute, what the fuck is a cmake anyways? Thank you

5 years never happend so hmmm I am always meeting my deadlines, due to team structure cant even put my hands on projects just do what They tell me to do as I am level 1 not level 2, so how do I do project if they dont put me on one due to theris excuses.... time to move I guess.

Amazon link seems to be invalid.

I am new at company most left overs are spaghetti codes

It's hard to believe you got an offer after presenting this surface-level mumbo-jumbo. And the CEO was impressed by the urgent/important quadrant thing? I feel like in management world that would be an equivalent to mentioning DRY to developers and expecting they would be impressed, while in fact they'd probably just roll their eyes. Good on you on getting hired, but I feel like recruiting process is just broken.

i am loving these breakdowns. just explanation of how the architecture works from a meaningful context - its so useful. also i love the way you say libraries. thanks for the insight to see that this needed to be explained in this manner.

Thank you for your simple English. I can understand everything.

I'm doing undergrad research and I need to write c++ code with more industrial standards. this video was SO helpful, i feel like im going in the right direction. Thanks!

Quick answer needs to be played at 1.75x speed

It comes across to me that the whole job is a sales pitch, because so much of this just seems so obvious to me that I wouldn't even say it, yet you've got slides for it. Like the quality risk when hiring that many new developers. Well yeah, I would have thought that be obvious. But you're saying here to say it anyway. So is that what we're after? Assume nothing is obvious and tell the people "above" you absolutely everything?

Thank you for such a simple and short explanation, I appreciate it!

Great video, thanks! I have ordered your book and have added it to my companies recommended reading list, hopefully this will drive some additional orders!

ive ordered this book a 2-3 weeks ago on amazon yet it has unfortunately not come yet, even admitting its late... dp you know why this is? im not here to rant id just lilke to really know

grouping across packages never seems to look right. .StarUML instead.

that rare thing on youtube - someone who knows what they're talking about 🙂 many thanks

Do a video on Bazel. I prefer it because it's just simpler than CMake.

Congrats, is it hard to get an interview at Google for staff level position? I rarely see job openings for staff positions.

Thanks for wasting my time with this a commercial for your book

Heh, nie jestem jedyny ktory sie tu zalamal slyszac to nieszczesne EJPYL z polskich lat 90tych (ale tylko od upadku PRL do uruchomienia internetu)... i bez jakiejkolwiek popularnosci firmy z logiem tego owoca, czyli jak kazda inna gruszka czy sliwka. Jak Ty zes sie chlopie jeszcze z tym uchowal, chyba jak ten film byl nagrywany to mimo plynnosci rozmowy i nienajgorszego akcentu, to jednak pierwsze kroki poza granicami Rzeczpospolitej, co ?

I use an sh-file (and on Windows a bat) that has the command to compile the project, including linking to libs. To further simplify compilation I have a single compilation unit that includes all the other c- or cpp-files.

I love that no one really know what cmake does and therefore pretend to explain it but actually gloss over it by saying "cmake will create the appropriate build system" instead.

Do you guys really see no problem that a tool created to simplify the build process has a 400 page manual? 💀

The 100 devs in a year target is pretty mad. You need a team (if not multiple) solely focused on that if they really want to achieve it with a clear idea on what they'll be working on so really you need various teams ownership defined before you even start so you can hire other team leads for each and then go from there. After they're all hired it will also be an onboarding nightmare. Normally I get devs in the team involved in the hiring process it helps ensure the new recruits are up to standard so in this case that would be taking away most if not all of their time on normal project work. Basically the hiring would need to be the project for the year if this was their number 1 priority. You can try and automate this and they probably should but I've seen too many horror stories where really great devs have been missed because of it.

What IDE do you use?

In my company we use make, what's the benefit of using cmake over c, and if the benefit is huge then why my company is sticking to nake ?

this video's 5-6 mins helped me a lot than lot of videos on youtube

so is it only ffor C++??/

There is only one criticism I have of the book: spacing. The book has a crammed look, I feel it would be more attractive if there were more empty lines. I'm referring to the epub version as read by Sumatra.

What it used to mean: Code is tangled up in such a way that 1 change can break stuff everywhere - global variable hell, everything happening everywhere ad hoc without stuff being sorted into isolated modules What people think it means today: An isolated module that is not split into a bunch of separate files and/or code that isn’t split out at the top level into folders containing e.g. types, components, services (even when one particular component in the simple app only relates to one particular service relating to a handful of related types all chucked together, but somehow it’s considered “organised” since, well, the types are all in one place and that looks pretty and feels tidy therefore it must be the one and only right way even for a very tiny application performing only very basic functionality. I saw it in a massive enterprise app and therefore it must be the only way to organise code, even for tiny pet projects! It’s like having a cabinet for cups and a cabinet for plates and a cabinet for pots despite owning only three of each)

its new to me lol.

JH10CL5742 WMB6773 WMB6773 GOUTAM MISHRA GOURI MISHRA PRADIP MAZUMDER SOMA MAZUMDER GARGI MISHRA SAMARENDRA CHATTAPADHAY CHATTERED ACCOUNTS MANOBENDRA CHATTAPADHAY MPDEV ADHIKARI RATUL ADHIKARI JAYANTA ADHIKARI TUKUN LAIK ADVOCATE

Thanks for the video but this is weird in a few ways: 1) You should use a unique pointer in TestedUnit for legacy_class_ because if you get an exception in one of the tests and the tests fatally crash, it will create a memory leak. I don't think the destructor will be called getting a fatal error. 2) What if you cannot modify the class you are testing? 3) What if you don't want the legacy class to have virtual functions? For example to prevent some methods from being inherited. This would work for testing child classes and classes you can modify. Forcing methods to be virtual for the sole purpose of testing / mocking them seems like a code smell to me.

You need to buy some new t-shits

Not even a developer here, can you believe he kept my attention the whole video and I actually miss that it's over! - Well explained.