I think "Firsts" are always significant.
We always remember them and they go on to define the events and activities that follow.
For example, I don't remember the 857th line of code I wrote but I'll always remember the first!
It was an unbound call to a type 2(value accepting, non returning) polymorphic...perhaps I should use a more normal example?
Well, I bet you can't remember your 12th kiss (if you've even got that many), but I'm sure you can remember your first.
Most likely sloppy and awkward and unmemorable, but you remember it because "Firsts" are powerful.
So, our "firsts" must be powerful, impressive, statement making... or well, so I heard anyway (This is mostly Robert Greene's influence. 48 Laws of Power, 'nuff said).
So, here's my first entry into my journal.
It's about NEPA(or PHCN or BEDC or even ECN sef, depending on who you ask).
To a freelance programmer like me, or even any other small scale business guy, NEPA is the ultimate arbiter. Supremely powerful and you can't ever "do them anything".
There are so many times I've had what is probably the best idea ever and I'm all pumped to dive into code and implement it, but, just as I reach for my power button to turn on my computer, "Pow!" They've "taken light". Again.
That's the ultimate morale killer. Nothing zaps my enthusiasm like that sound of electricity leaving my life and taking with it my hopes and dreams.
Anyway, I pull myself together and valiant turn on my laptop whose battery lasts for 3 hours normally, thinking, "no how, no how, they'll bring it before my battery dies", especially since I managed to squeeze out another 30 minutes from my battery by reducing my screen brightness and CPU usage.
They'll eventually bring the light 13 hours later, at which point my battery will have died along with my enthusiasm.
Just another day in the life of this Nigerian Programmer.