Journal #174 – Productive Tuesday, Maybe

I like to think that I have a productive day. Maybe? Maybe not?

Let’s see.

I woke up this morning still feeling both physically and mentally tired. But I still forced myself to get out of bed, have my breakfast, and go to work. Today, I left my house 5 minutes but I purposely walked slower to the train station. So I ended up reaching office at around the same time.

With a large cup of Cold Brew from Starbucks, I powered through the morning. My workflow when it comes to development usually goes like this:

  1. Develop a rough software design in my head.
  2. Start coding based on that rough design.
  3. Identify use cases.
  4. Draw the actual software diagrams.
  5. Continue development and test
  6. Repeat 3 and 5.

So today, I did number 3,4, and 5 until lunch time.

After lunch, I actually took the diagram and ran through it with the team leader. After going back and forth, he agreed to the direction I’m taking and so I continue development.

By about 4pm, I managed to get at least two WCF services up and running but I won’t call it completely done. There are certain scenarios which I have yet consider in the context of it being an identity access management system.

Personally, I never liked having not cover all possible scenarios in whatever code that I do and given time, I will probably perfect it. Time is not my friend in most of the cases. And so these days, I only focus on getting it to work properly covering approximately 60% of the use cases. Part of the reason for that low percentage is because of my desire to balance mental energy use and resting from work.

As a HSP (highly-sensitive person), I do take way longer than normal people to wind down at the end of a workday.

Well, I took a short break from 4.00pm until 4.30pm before continuing my work again. When I start working again, I went back to discuss with the team lead on what I want to do next.

By 6pm, I had already finished inputting the one part of core data necessary for the module to work properly. So I guess I will continue that tomorrow as well as do more coding. I did promise my team lead that I will finish most of the implementation by next Friday for proper integration with the rest of the system.

And I will use this chance to sum up what I learnt or improved on over the past few days:

  1. Entity Framework for Dot NET
  2. Code First Approach with Existing Database
  3. Applying predicate logic for the purpose of implementing domain behaviors and querying the database through the DbContext.
  4. Reinforcing my OOP through domain driven design.

That’s all for my update today.