This is the 20th and the last post in the GetNoticed! competition. So it means that… I DID IT! I survived till the very end, I managed to create 20 posts in 10 weeks. ReMaster is still alive (it could be fed better but let’s leave this subject :P). It’s time to celebrate, I mean, have some sleep ?.
What I’m proud of?
I have a blog! One year ago I was sure that my programming life is boring and even the problems I encounter while coding are too boring to write about them. And I believed that there is everything already written so what’s the point in writing the 100th ASP.Net tutorial?
Now I don’t know which subject from my long TODO list should I choose first!
I also fear less about pushing my code to github PR. I know that my style of coding is far from perfection ? and my code tends to be messy ? so that’s a huge step! I think I can even say that breaking this barrier in my head is the greatest outcome of the competition!
What I’m ashamed of?
Well, the amount of commits! Yeah, ReMaster looks like it was started a week ago. I managed to create only the basis, code responsible for data imports and a few views. That’s not good but even in this rather bad situation, I’m happy I spent most of the ‘coding’ time on actually learning new things. I better understand the patterns used (and planned to use 😉 ) in ReMaster, I discovered the opportunities that github’s projects give. I had a lot of fun with designing ReMaster and so on. The efforts are not visible but I feel more confident now and that’s a valuable thing too ?.
Anyway, I admit there should be more practice and less research ?. In fact I regret that there was no competition rule determining the minimum amount of commits per week. That would be a great motivation!
I also regret that I spent so much time on implementing the imports. Testing and coding this part was really frustrating because of the long data download time.
To sum up, ReMaster needs a lot of work to be done.
Was it really so hard?
Well… Yes! And no! ? If I wasn’t a mother of a toddler I would say it was very hard. But after more than a year of sleep deprivation and fighting with myself for every hour spent on, let’s say, self-development, I got used to the situation. Actually, it was not a big difference if I stayed up till 4 AM writing a post when I planned to stay up till 3 AM anyway.
The hardest moments where the ones when I needed to drop everything and invest my whole attention in my private life and I had this haunting voice in my head whispering ‘You will not make it on time!’. Life would be much easier without this ‘voice’ ?. There were also days when I came back from work tired like a dog and really considered giving up the competition but somehow, I’m still in!
Was it worth it?
Yes! I always have a problem with motivation and it gave me the wind in my back. And although I know I have no chances to even be in the top 100 of the competitors I love the feeling of being the part of this thing.
Ok, let’s admit it, I just love taking part in competitions!
Well, the competition is over, I can finally write about the subjects I want ?. I hate writing the reports about progress in my pet project. I really doubt anybody was interested in these posts ?.
So now I hope to create a mini tutorial about ElasticSearch. The ones available online are outdated so I will treat it rather like notes for myself (because I’m learning it right now).
I’m not sure if I will have enough motivation but I would love to continue ReMaster’s development. But let’s be clear – now, when I’m back at work and I ‘practise’ there programming a lot, I don’t treat it as a priority ?. The fact that I have 2 ideas for mobile apps in my head is not very helpful too ?.
I would like also to work on the amount of commits! The amount of code written at home depends on the amount of time I have and this will not change in a few months/years (decades?) so I have to learn to commit smaller parts of code. And like somebody wrote in the comments under this post – it’s a great idea to divide bigger functionalities into smaller ones so it’s easier to write the code within the minimum amount of time.