Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

14K
active users

mstdn.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.8

#refactoring

7 posts6 participants0 posts today
Continued thread
Public
Marco Siccardi

The result of the #analysis was a an in-depth report explaining possible pitfalls in my code base including recommendations to fix them.

Finding them manually would have taken me days. This way, I was able to cut down the time for #refactoring and fixing most issues to hours.

Public
Caroline Middlebrook

In this #devlog I start by refactoring my spawning code to improve the gameplay. I introduce a bug, finally fix it and then move onto audio. I build a simple audio manager to handle both sound effects and music in one centralised place. youtu.be/94Xx39KBUF0 #gamedev #gameaudio #refactoring #unity

youtu.be- YouTubeEnjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
Public
Caroline Middlebrook

In this #devlog I implement a lives system, introduce a crash bug, then fix it & create a web playable version of the game. Next I begin work on a pickups system to score points by collecting food and streamline the entire codebase by #refactoring to use the #Unity event system. youtu.be/hrbINTjkdbo #gamedev #buildinpublic #cleancode

youtu.be- YouTubeEnjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
Public
Orchun Kolcu

I find that the issue Kent Beck talks about here:

tidyfirst.substack.com/p/why-t

... is very fundamental to TDD and centers around a couple of commonly missed aspects of it (even though they are spelled out in Test Driven Development by Example)

1- When passing the test, there is a Fake It approach you can take if you don't see the Obvious Implementation right away before you move on to Triangulation and add more tests.

2- When you are using Fake It, the Refactoring step is not primarily about making the code "nicer", but generalizing by removing the duplication between the test and the production code. This is only refactoring in the sense that you are staying green. That's why the step is not optional and getting to green using the simplest, naive implementation is a core part of the process.

I think not using Fake It is one of the two main reasons people fail with TDD (the other is not making writing more testable code a design goal.)

Software Design: Tidy First? · Why TDD Doesn't Lead to Dumb CodeBy Kent Beck
#tdd#softwareengineering#refactoring
ExploreLive feeds
About