Navigating Dark Nebula

Its been two tri-weeks,

we entered into this dark nebula.

Like dreary dark winters of old-earth,

this is extremely difficult on crew.

We wished for a glimpse of at least a single star –

the hell, we even prayed to almighty.

Forced to conserve energy –

means indoors are not lit bright.

adding bonus frustration and depression.

The doctor is busy,

patients are plenty.

Bridge is deserted, other than few ensigns.

Then there is little glimpse.

Is it for real?

Or only in our imaginations?

Only time will tell …

We continued our journey across dark nebula.

[In Progress] Code Reviews

Before Sending CR

  1. Keep trivial changes like renaming, reformatting, moving code around in its own Pull Request (PR) ; Keep refactoring code in its own PR; Keep rest of the code in separate PR. Combining these three will dilute PR, people either won’t review by looking at sheer number of changes or will leave too many comments ending up in a myriad of ping pongs resulting in overall compromising tiresome experience.
  2. Keep smaller PRs, Keep them to one issue (or minimal logical conclusion of feature) ;
  3. Try to develop one or two buddies. This greatly improves turn around time of your PRs. Of course you need to reciprocate the same.

An old woman and her Rooster which wakes up the sun!

Long long ago there was a village, in that village lives an old woman alone in her humble hut. Her husband passed away few winters back, her sons and daughters didn’t survived beyond infantry. She was a good person at heart. The village folks are busy during farming season and busy preparing for farming in off-season. They never bothered to visit old woman and say Hello!

The old woman had a rooster, it is very bright, energetic and young. Every day before sunrise it climbs up on the hut and sings cock-a-doodle-doo three times. After that sun comes up. Old woman sees this every day and she was so proud of her rooster who wakes up sun with a good morning song.

One day the village celebrated harvest festival. But everybody forgot about old woman, nobody invited her to celebrations! Her heart felt really bad, depressed and she got angrier. Then she got an idea to punish the villagers. She took her rooster along with her and went to forest and started living there. She knows – once the sun stops coming as rooster no longer sings – the villagers will call her back.

It has been quite a number of days – nothing changed. But she is adamant and strongly believed the villagers can not stay for more than couple of weeks without sun.

She started living in a cave and travels to nearby water stream every day twice. One day she met with a rabbit whose skin is a tan burned as it escaped northern forest fires and came to this forest recently. The woman felt pity and used her medical knowledge to apply some soothing oil to the rabbit’s skin.

After that she ended up treating broken-winged-eagle, limping deer, broken-hand-bear. She removes thorns from several animals with kindness. She brushes monkeys every day with her special comb and they are grateful for that.

One day old woman looked sad, as the villagers seems to have learned how to survive without sun and never came back to her. Animals saw that she is sad – asked her what’s the matter. She explained every thing.

Then all the animals met in a secret meeting and decided to send eagle as an agent to the village to invite old woman back. Then eagle went to village and tried to talk to the villagers, but everybody is so busy – nobody stopped to listen to the eagle.

Eagle felt annoyed and used her magic to disappear the sun! The villagers felt panic!! Then eagle used big magical voice to say “Until you fetch the old woman and her rooster back to the village the sun won’t return”

All the villagers now remembered old woman and her rooster which sings to the sun every day. They also realized they haven’t seen her from quite some days. They flocked to forest and convinced old woman to come back to village

Old woman said – “I am happy here, but take this rooster along with you, she will sing to the sun and everything will be alright”

The animals and old woman lived happily ever after in the forest.

Single drop of salty liquid –

rolled out from my right eye,

carrying all my burden away.

Single poem of sweet nectar –

rolled out from my left heart,

carrying all of me away.

My face is now a mural –

painted out on a front wall,

flashing all light railers.

My story is now forgotten –

extracted out from the back of,

all souls carrying ocean inside.

The Highly Scalable system by humans is the family

 

Apparently the highly successful high scalable system designed, evolved by humans is neither AWS nor Azure (nor Google Cloud not OCI nor FB one), rather it is the unit of family.

Imagine you are given a task to organize seven billion entities and yet –

  1. be productive
  2. be competitive
  3. be mindful
  4. survive and propagate
  5. be selfish and at the same time be helpful to other entities.
  6. etc…

Your brain is going to explode isn’t it ?

But humans did it with a simple design called the family.

This is summer

This is summer,

warm some times,

blazing hot mostly.

Berry picking,

Cherry picking,

Merry riding.

Long days,

long drives.

blue skies,

camping clouds,

mapping birds,

running rabbits,

producing gardens,

jolly weekends ,

This is summer.

Git(hub) feature request – Make Code review comments available to developers forever during their edits

One of the recent trend is to minimize quantity of comments inline in code files and improve quality of comments. This caught up like fire and moving towards the danger zone of no comment-era. This is all good provided the code is written with maintenance in mind and not for short term goals of long running product to satisfy some OKR set by somebody higher up or to meet some dead line which coincidently aligns with your performance review period 🙂

I am all for those learning of clean code. Good variable names, smaller classes, smaller methods, meaningful names to methods, highly readable code, lesser number of lines of code, let the compiler worry about optimizing my code etc…

But this comments is a tricky thing. when the code is written first time a lot of thought goes into it. compromises will be made, hard decisions will be made. Developers are moving intra-companies, inter-companies like crazy Salagars. All this context is lost for future developers. Now they are told more comments is bad pattern.

One natural place for all this information is code review description, self-comments, discussions. It is already happening there – just that this information is not easily available to future developers readily.

If Git(hub) can find a way to make this information available to editors (e.g.. VSCode, which already shows lot of Git history while you try to edit a code-file) it will be pretty useful to developers who are trying to fix that nagging bug and keep swearing “who the fuck wrote this shit and why?”

stringObject.IsNullOrWhiteSpace() a simple c# extension method

Every time doing String.IsNullOrWhiteSpace(input) is irritating. Moreover we try to input. and look for this method in intelligence. But it won’t be there, as it is static, unless we do String. we don’t see this method.

Writing an extension method will save us this trouble.

public static class MustHaveCSharpExtensions
{
	public static bool IsNullOrWhiteSpace(this string input)
	{
		return String.IsNullOrWhiteSpace(input);
	}
}

c# new feature request : AutoInitListsOnFirstUse

Another sugar coating – a compiler should easily generate code for this (?) without any side effects. why force people to do new boiler plate code ?

List<string> myListOfStrings;

myListOfStrings.Add(“firstString”);

This throws NullReferenceException until we do new List<string>();

The probability of it happening is more when this is part of another data class, which we initialized but forgot to look into all hose other initializations we need to do.

In case somebody want to avoid this behavior we should have an attribute to support old behavior.

[SansAutoInitListOnFirstUse]