วีดีโอ

Is that a right definition of clean? To always use the newest shit? Sometimes it seems just because people can speak on a stage doesn’t mean they know what they are talking about

Well, that certainly is an opinion and a story to go with it. Yep.

This just seems like a horrible idea :D. You would never get anything done, except redo the existing code and even better, you would have to be constantly debugging a code, that was working just fine without any need for "repairs"

Yeah, take working / debugged production code and "clean" it with the latest library and language that is popular at the moment. Let's stuff a Ruby library in this PHP program because - reasons. Has this guy actually had to maintain production software???

Just me or did the first half of the video seem out of context?

Outro song?

don't just blindly use some new library

This rule really works, highly recommended

Hot take: if the team needs to be reminded to keep it clean, then you need to get a new team.

First

It is, until it is not.

wow, what a great quick video.

Facebook succeeded because the powerful elite wanted it to succeed, so they used all their channels to brain wash us into getting it.

Sun was giving away all the software as a loss leader for sparc. At the time people were charging for compilers and sdks. Along w/free app servers like tomcat and glassfish.

Why does software need to change?

publicstaticvoidmain publicstaticvoidmain publicstaticvoidmain publicstaticvoidmain j++ meikrozoff klaut echt alles und macht alles kaputt, genauso den netscape navigator, stattdessen mussten wir uns ewig mit dem scheiss internetexplorer rumergern. der ie war der grund warum webframeworks und weblibs erfunden wurden. darum mussen wir uns jetz mit den scheiss webrfameworks und weblibs rumergern. webprogrammieren war ursprungslich mal herrlich einfach und machte spass. dann kam der spassverderber meikrozoff. typisch banker und bwler halt, die machen alles kaputt nur um eigenen profit zu machen.

To be fair, Java was a failure as a hardware sales tool, since its big selling point was cross-platform portability by compilation to bytecode run by a JVM (remember "Write Once, Run Anywhere" - which really became "Write Once, Test Everywhere"?). Then, having been burned by Microsoft turning on them and killing OS/2, IBM also drank the Java koolaid and promoted it heavily with tools like Visual Age for Java. So, in the end, Java couldn't save Sun from acquisition by Oracle.

then javascript became the language of the internet

You could also call this: The origins of the C# programming language :)

"Clean code looks like it was written by someone who cares" that's always resonated with my the most. Even if I didn't know what I was doing, or I didn't have a specific design pattern down, I always wanted it to be a welcoming experience to come back to at any time.

CLEAN CODE IS CODE I CAN READ.

If I had a nickle every time "free" overengineering saved my a**, I would be very rich man. By "free" I mean something that didn't materially increased development time. Sometimes it's a matter of making slightly different turn. You usually do know what you will need tomorrow, in a week or two. Sometimes you know what you'll need in month or two. Creating abstractions to make your future self life easier is just common sense. Adding them when needed causes expensive regression retest.

Scrum is just a fancy way to talk about how most secondary school teachers and management works, ie with a few smaller teams (subject departments).

I once worked for a company that had a guy whose whole job was to design an application. He didn't even have a computer. He just sat at his desk all day writing design documents. For years. Ultimately he was fired, all of his work was scrapped, and they started over with a new design. My boss said that if they had tried to implement the system he had designed, by the time it was finished man would no longer be in corporeal form.

I want to hate the advice in the video... but... yeah... refactor when stuff isn't making sense anymore and new use cases need to be supported. I think the power of this video is to be able to excuse not using interfaces and complex abstractions on each and every little thing and being able to counter "but what if we X later" and to be able to squash that ever so present indecision... when there is a need to support multiple things, then you add the support for multiple things. which is fair enough I think.

I add comments for the reasons code does something, or to create visually different "bookmarks", and I write comments for myself, because I won't always remember why I did something years later, and I write comments for the people who will maintain code after me. As there are no guarantees about how good others will be at their job, and because I care about my employer and/or customers, I don't want them to suffer longer downtimes for pedantic ego-filled arguments against good commenting practices.

That's some rich advice coming from the guy who wrote a book full of promoting overengineering ("clean code").

The default should be declarative unless you have a really good reason to do otherwise

Polymorphism is simply not suitable for many many enums. Yes, it might be possible we forget to update a switch somewhere, but that's why you have a default clause with an exception. Simple. Problem solved.

Btw , great videos , please make more ❤‍🔥❤‍🔥🙏🙏

My Left ear enjoyed the video a lot ☺

I like to close my eyes and pretend its Vizzini from princess bride talking

That's a really under rated video!

Declarative is nice as small isolated LINQ queries or something, I would absolutely not trust a full million lines of project in a declarative language.

I hate declarative programming. Imperative is way better.

When you have never written code that runs in production, this argument holds. A boolean can come from a configuration. Even if I am going to write two functions I am not gonna duplicate all of that code just so that I do not have to have an if condition.

Agile is just people being disorganised…

First

For a moment I read his name as uncle Ben

Big reasons why it's easier to keep code in one place: it's simpler and if you need to find anything you just ctrl+f in the file, which you can't do if it's split into different classes.

Uncomfortable music

Mental frameworks work until people realize how they can manipulate the framework for their own personal gain. If there is a human in the equation, they will twist the framework to fit their desired goals. It is irrelevant whether the framework and their goals are aligned or diametrically opposed to one another as just being associated with the framework gives them the tiniest shred of credibility.

I always say, code should tell a story.

Thank you for posting and for including the link to the original video!

Agile has been ruined beyond all recognition. It started out as a good approach, but as soon as the con artists and grifters moved in, the entire word has lost all meaning. I spent nearly 30 years working in the corporate world for a large tech company, and the last 10 years of that was largely ruined by Agile and the people pushing it. It took me far too long to recognize the fact that every single person pushing for some sort of agile approach was a no-talent hack who wasn't able to contribute any real value to our work, and instead was using agile as a way to collect a paycheck. All a bunch of parasites. I knew one scrum master who had actual skill and integrity, and she jumped to a different role the first chance she got.

I was waiting for the immobility and viscosity discussion…

This is true but not profound.

This music is rude

It probably failed just because it was something no one actually wanted to purchase.

with help from AI, this is doable.