are YOU a garbage collector?

 If I will ask you: "Are you a garbage collector" - I bet I will hear: "NO", so I ask you: show me your code....

It is unbelievable that so many developers are pushing changes with commented out code, because  there could be a chance to re-use that piece. In fact that time never comes to me and the lines stays there forever.
Clean code means no rubbish commented code - we have git to remember that for us.

Now, when you need to comment a few lines in a row... there are better solutions, but if someone is lazy and slumsy then we can see diffs on code review like that:

Now this is a mystery for me, when I am able to see that this is going to the main branch as the guys who is called code reviewer is there only to click Approve - I am truly believing that it is not you my reader.

I need to admit that, when I was a kid, together with grandma we were collecting garbage as a way to get some $$ for a life and then every piece we found had a material value and were able to exchange old books for toilet papier :D.

But now - where we have git - why someone is adding an extra work to maintain more rubbish on the screen - as our brain does not know negation (this is an abstract term) - we see and read the lines when scrolling and looking for place we need to find.

Comments

Post a Comment

Popular posts from this blog

an actual controversy switch vs if chain (a benchmark example using LinqPad 7 free edition), but the real problem was hidden in a different place [refactoring stuff]

Image
 In Linqpad 7 user can execute BenchmarkDotNet, as I love LinqPad for it is simplicity and ability to test somestuff without the burden of creating a project. After installation (of LinqPad) we can find a predefined query called BenchmarkDotNet, with an example benchmarks defined, so we can start 'doing stuff' After first run we can see that all methods with attribute [Benchmark] are executed in the harness, so we can start digging.  Right click on the query and select use as a template - so we will not use the orginal one.  The simple code is here:  gist  (and at the end of this post) Creating a class for each method allows to have it nicely displayed on the results pane. From the benchmark results we can see  that there is nothing to worry with the practicular code as both methods have fairly same time of execution - and let's try to add more steps (up to 10 and see if we will be still close or switch will take an advantage) And the results are very inter...
Read more

why do we need messaging system (maybe massaging...)?

Image
Messages. messages all about messages. Is that a real thing - do we need them? Messages are nasty, you send it in one piece of code, receive in other and you can't just debug that. No function calls, no stack trace - so how you people like those messages? Primero messages are great way to allow separate application components, especially when we are inheriting legacy solution with huge number of dependences. To start with messaging, we don't need Kafka, MSMQ, rabbitMQ or other animals - we can start with stuff that are already in our .Net tool case.  In below example we use a very basic approach that enables us to avoid method calls in destination with our parameters and we are using queue so we are messaging each other! let's define a queue(s): Then we can add a producer (something that will be adding messages, like our web api controller): and a consumer (like our database writer): And as you can see, our data is enriched by database query and send to next processing step...
Read more

can you believe that more code gives ability to add much more faster?

Image
In last blog click  we have the chance to refactor a logic expression to be more developer friendly, but it was generating more IL code lines. I was wondering if that will have an impact on the performance (u know when u use a language that is focused on extending your product not on high performance - then this is a bit of over engineering case 💩💩💩). So yes, I made a benchmark in LinqPad making my friend Selciuk unhappy a bit, but the results are very interesting. In 2 form 5 test cases, refactored code was performing a bit better, but I am more happy that in the other three cases it was not terribly slow, with a maximum of 4% slower. So having those results, let's say that it is more important to write code that is easier to extend!  If you willing to write a high performance stuff - then you need to be ready to decipher every line, every time when you read it :D.
Read more