Michal Lipski

Test-Driven Developer @snowflakeDB. Teaching how to build better code and in better ways. Tweets about TDD and good software practices

[Michal Lipski @milipski]

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

[Historic Vids @historyinmemes]

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

[Tim Ottinger @tottinge]

@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.

[Dave Farley @davefarley77]

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.

https://t.co/qBVTg71ccu

[Michal Lipski @milipski]

@sebrose We have just started few weeks ago.

[Charity Majors @mipsytipsy]

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.

[lavitalenta @lavitalenta]

Going to get a bike now.

[Michal Lipski @milipski]

Core Web Vitals — Why should you care about them? by Jan Doliński https://t.co/3BiUQsJfp4

[Pragmatists @pragmatists]

Check out our latest post about fault tolerance patterns for remote calls by Łukasz Kyć https://t.co/0UL8F13igs

#resiliency #patterns #microservices #stability

Artwork by @UXRosinski

[Michal Lipski @milipski]

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

[Tom Johnson @tom_a_r_johnson]

@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.

[Michal Lipski @milipski]

@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.

[Michal Lipski @milipski]

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

[Michal Lipski @milipski]

@DocOnDev The best way for small steps refactoring is just a pen, piece of paper and Mikado Method: https://t.co/ETuUMjuJxH

[Michal Lipski @milipski]

@IntelliJSupport @HadrienMP Here is my video demonstrating Extract Method refactoring in @intellijidea Hope that helps: https://t.co/BYJp5AliHN

[Michal Lipski @milipski]

@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.

[Michal Lipski @milipski]

@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

[Michal Lipski @milipski]

@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.

[Michal Lipski @milipski]

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.

[Michal Lipski @milipski]

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