Michal Lipski

Test-Driven Development is for lazy people: Don't think too much ahead Write as less code as possible Write as simple code as possible Focus on one thing at a time

This is an example of OpenAI’s new text to video product. Prompt: “Historical footage of California during the gold rush”

@allenholub @CraigTraynor1 We call it "The Documentation Rule" to wit: you read tests to understand the code, but should never have to read the code to understand the tests.

I just came across this fantastic resource from the guys at @mob__mentality It's an organised collection of links and information to stuff that can help you in your work. trello.com/b/1lfMkCOh/sof…

@sebrose We have just started few weeks ago.

Hello, Twitter. Is there anyone out there using #Jira and #ExampleMapping on a regular basis? I'd really like to talk to some of you about the challenges and successes that you've experienced trying to refine your Jira backlog using example mapping.

The smallest unit of software ownership isn’t the individual, it’s the *team*. Therefore your prime directive as a manager is to craft and tend a healthy, high-functioning team. Even when this leads to outcomes that are less than ideal for individuals.

Going to get a bike now.

Core Web Vitals — Why should you care about them? by Jan Doliński blog.pragmatists.com/core-web-vital…

Check out our latest post about fault tolerance patterns for remote calls by Łukasz Kyć tinyurl.com/w9pj52v4 #resiliency #patterns #microservices #stability Artwork by @UXRosinski

@davefarley77 very good content but I found it very dificult to read the code with this askewed screen. Full screen and bigger font please.

Watch me run through the process of refactoring some pretty horrible legacy code ➡️ bit.ly/How2RefactorLC1 This is a great step by step for anybody that is encountering a similar issue.

@davefarley77 @ajsutton @thinkfoo @RonJeffries @allenholub @johannarothman It feels like continuous code review (ie pairing) is about maximising the benefits of change, whereas post-facto review is about minimising the harm.

@dmokafa I think the Pair Programming is most important and underestimated same time. It is very hard to have Simple Design without TDD and its hard to get grasp on TDD when working alone.

The essence of Extreme Programming is the interconnected set of software development practices. The main practices: - Simple Design - CI / CD - Pair-Programming - Test Driven Development - Continuous refactoring - 40-Hour week - Collective Ownership Which one do you practice?

@dannydeezy @_ericelliott or writing it before the code and seeing it failing aka TDD

@_ericelliott Breaking your code is the only way to test your test!

If you haven't seen your code run, you don't know if it works. If you haven't seen a test fail, you don't know if it's a valid test. #tdd #code

@DocOnDev The best way for small steps refactoring is just a pen, piece of paper and Mikado Method: mikadomethod.info

Refactoring is small steps to simpler solutions. If you're ripping out a whole chunk at once to replace it with your clever new solution, you're probably not refactoring. #agile

@IntelliJSupport @HadrienMP Here is my video demonstrating Extract Method refactoring in @intellijidea Hope that helps: youtube.com/watch?v=9YQdGe…

@HadrienMP hello, unfortunately there is no video covering this type of refactoring, but here is a short manual with sample: #extract_delegate" target="_blank" rel="nofollow noopener">jetbrains.com/help/idea/extr…. Please share your code sample in case of difficulties (you may also share it privately in the issue here youtrack.jetbrains.com).

@intellijidea me and my collegues have been trying to use the "extract delegate" refactor but can't get it to work. Do you have any demo video on this ? Cc. @Tarcaye @dynotipi

@nicoespeon I guess you learn about code structure a lot and you can make a notes but you goal is still to do this refactoring eventually. The Mikado Method allows code exploration with small steps refactoring at same time.

@ygrenzinger @Tyrrrz Agree. There is common misconception that unit is a class or method and if you have three classes than you should have three unit tests. With that approach tests are becoming fragile and blocking you from refactoring. Is less likely that you endup with that kind of test with TDD

@Tyrrrz Yep. Maybe. I would like to know the history of the term. Seems even Kent Beck doesn't say that Unit Tests means a class in full isolation (haven't felt that in TDD by example). But yeah maybe there is a better term that unit test but don't know which one to use.

📝New article: "Unit Testing is Overrated" My thoughts on the industry's obsession with unit testing, which alternatives I found to be more effective for development testing, and how to implement them. tyrrrz.me/blog/unit-test…

@Tyrrrz Yes, I belive all unit tests should be testing a functionalty. The problems starts when you test a code structure insted of functionality. Like checking that one class calls another class or a UI component renders other componenet instead of checking the output or side effects.

@milipski Wouldn't it be a functional test then, if your unit represents a piece of functionality?

There is no Sustainable Development without Clean Code. There is no Clean Code without Refactoring. There is no Refactoring without Test Driven Development. Start with a test.

@mdo It already exists. It is called Pair Programming.

Has anyone built the opposite of code linters? Instead of only telling me all the stuff I did wrong, tell me all the stuff I did right so I'm excited to keep going :D.