Week #33

Finally a bit of stress reliving week. After constant hustle at work, this week felt a little less stressful (not stress as that stress, just too much cognitive load to handle). However I made 2 releases happen, a few experiments and brainstorming for cracking a problem.

Work

This week made me realise, I sometimes do things. I was asked to figure out a metric that we need to provide to a customer based on their customers data, they basically need to understand the data of the customer, however the data is too much and they forward to us to extract and analyse on top of that. So, my job was to figure out the requirement of them, they need to understand the pattern in the data of the customer and that is not quite easy.

Week #34

It was a pretty busy and productive week. After three hectic weeks of research, hacking, scripting, implementing, Google Sheets, and Python Vulture coding an API, I made a few releases. Yes, that is the normal role of a software engineer at a startup. I get to wear multiple hats: analysing, writing, debugging, scripting, testing, and obviously communicating effectively.

I was able to complete the implementation successfully. The release somehow happened on a Friday evening, which I am skeptical about, but it happened without any hiccups, a few minor ones. It will all be well if it ends well.

I was looking at a long list of logs, (debugging of course).

I had a list of transactions

• Two list of transactions, one as ground truth and other as predicted. Transactions is a list of object(dictionary or map), each object has fields like date, amount, description, etc.
• Those objects in a list need not necessarily be in order, however I do want to compare them, how to do that?
• I decided to sort them based on date(one field in that object).

Then for each date, I group the transactions and this would narrow down the search space for comparison of one-one transaction, since now I can compare which of the ones are closely matching, the date will be a exact match the amount should also be, the description can be fuzzily matched.

I was looking at a long list of logs, (debugging of course).

I had a list of transactions

• Two lists of transactions, one as ground truth and other as predicted. Transactions is a list of object(dictionary or map), each object has fields like date, amount, description, etc.
• Those objects in a list need not necessarily be in order, however I do want to compare them, how to do that?
• I decided to sort them based on date(one field in that object).

Then for each date, I group the transactions and this would narrow down the search space for comparison of one-one transaction, since now I can compare which of the ones are closely matching, the date will be a exact match the amount should also be, the description can be fuzzily matched.

A well written and concise guide on template parsing with golang. I used to get confused with parsing and rendering the template, this makes it really clear by showing bit-sized examples.

• Using custom functions is a high-value tip, I can see myself using those for string-related functions like title case, stringify, date parsing, etc.
• Another great example is the templates, we can create partials for reusability.

Must read for golang beginners.

Interesting read,

If you graduated last year and are entering the workforce this year, then it doesn’t unless you take action. It’s a COVID19 moment in life again.

have edge over others

Understand that time is on your side if you take action. You have about a year, maybe less. Whatever you do - do not squander it. Your edge right now is a large majority of software engineers have not discovered what you have. When they do - it’s game over unless you have an edge.

Python is tactile

Week #32

Weeks of chaos have left me on the brink of burnout, with no time to breathe or reflect. Didn’t get much time to just sit and think, just had to complete a few hacks here and there to get the demo running, poor management and blind eyeing.

I am a bit stressed at the moment, not able to do anything, occupied in work from 9 to 12. Yes, that is a bit stressful and hectic to carry this daily.

Week #31

What a week, again, a bit of thump and bumps, a bit of scare at work.

Last week was hectic, this week was continuing that bump in increased responsibilities. I think I might be transitioning from Junior to Senior, but the mindset might be of a junior, need to step up.

Thanks for reading Techstructive Weekly! Subscribe for free to receive new posts and support my work.

Might be the first time I felt a bit pressured, making me doubt myself, negative thoughts, quitting decisions, etc are flowing in my mind. Nothing bad, just wired stuff happening in life, it’s tough to live life sometimes, its hard to show it, no one knows what you and your family is going through in life, before they lash out and ruin it further. No one has patience and empathy anymore.

Week #30

What a week captain! Realized this on Wednesday truly. A bit of exhausting yet exciting week, it was a wild ride, true but learnt a lot. A lot of mistakes popping up at once.

I had to scamper and get things done, not just do it, but do it correct, not only do it correct , but also do it more, that was exaggerated, but yes, it was a bit taxing at some point, but the reward? I don’t care, I did my best (to some extent) and I am leaving the result to nature, really can’t control that now. A lot of intense debugging sessions, pair programming, side scripting, a lot of fun conversations and moments, it was worth it.