Welcome Guest ( Log In | Register )

Outline · [ Standard ] · Linear+

> Clean Code Approach Part 1, Short consice clean code part 1

views
     
TSImaizumi
post May 3 2021, 05:44 AM, updated 5d ago

Getting Started
**
Junior Member
240 posts

Joined: Oct 2004
QUOTE(MyRedz @ Apr 27 2021, 01:38 AM)
Anyone suggest some programming test like coderank for practice?
*
Step by step concise clean code and why. Also mention separation between construction and usgae which is important making things testable, hence maintainable by allowing safe refactoring.
https://maziz88.medium.com/practical-clean-...es-f470eeffb98e
pujan
post May 3 2021, 08:38 AM

Getting Started
**
Junior Member
81 posts

Joined: Apr 2009
QUOTE(Imaizumi @ May 3 2021, 05:44 AM)
Step by step concise clean code and why. Also mention separation between construction and usgae which is important making things testable, hence maintainable by allowing safe refactoring.
https://maziz88.medium.com/practical-clean-...es-f470eeffb98e
*
Beautiful. Thanks for sharing this. I hope you don't mind that I will also post this to our programming forum (https://kaki.gg) laugh.gif
malleus
post May 3 2021, 09:54 PM

Regular
******
Senior Member
1,676 posts

Joined: Dec 2011
The part about construct vs usage, it can probably be simplified by using the term, dependency injection, then explaining what DI is.

On naming conventions, a rather useful reference will be the ruby on rails naming guide, where they define what is to be used in singular, plural, etc.


TSImaizumi
post May 5 2021, 05:43 AM

Getting Started
**
Junior Member
240 posts

Joined: Oct 2004
QUOTE(malleus @ May 3 2021, 10:54 PM)
The part about construct vs usage, it can probably be simplified by using the term, dependency injection, then explaining what DI is.

On naming conventions, a rather useful reference will be the ruby on rails naming guide, where they define what is to be used in singular, plural, etc.
*
I think the concept separation of construct vs usage is a precursor to DI. That's a basic I belive should be understood before moving on to higher level concept such as DI.

Off coursep pro like you and other experience developer would feel it's "obvious". smile.gif

*Edited, refering to this? https://gist.github.com/iangreenleaf/b206d09c587e8fc6399e ?

This post has been edited by Imaizumi: May 5 2021, 05:49 AM
malleus
post May 5 2021, 06:21 PM

Regular
******
Senior Member
1,676 posts

Joined: Dec 2011
QUOTE(Imaizumi @ May 5 2021, 05:43 AM)
I think the concept separation of construct vs usage is a precursor to DI. That's a basic I belive should be understood before moving on to higher level concept such as DI.

Off coursep pro like you and other experience developer would feel it's "obvious". smile.gif

*Edited, refering to this? https://gist.github.com/iangreenleaf/b206d09c587e8fc6399e ?
*
Actually, the way that I look at DI is very simple. It's basically just passing a dependency into a class that needs it as a parameter, instead of initialising it within the class that needs it. And then there's those DI frameworks that helps with this, but that's a different thing.

and yup, that's the reference I was talking about as a example for naming conventions.

 

Change to:
| Lo-Fi Version
0.0175sec    0.37    5 queries    GZIP Disabled
Time is now: 9th May 2021 - 10:24 AM