About me and Why read this blog?

About me : 

Hello there, I'm Ananya Jayakumar 

- 33 years old when I start this blog , 5 months into my pregnancy , 10 years experience in tech : Operations / Data analysis / ETL / dash-boarding / managing teams / Solving problems.

Pregnancy - Slowing your career

I just completed a personally fulfilling year onboarding a team and training them to perform, tackling fraud, building dashboards and creating automated ETL behind the dashboard. But since I'm going on maternity leave, I'm training folks on my job - making it easy to replace myself and jeopardizing a promo that I'd otherwise been well placed for and also having to coming back from maternity leave - and starting from scratch as if all the stuff I did before the leave does not count. It's also a time when my company is getting acquired, the business and products are changing and not the best time to be planning maternity.  I feel like I have potential to be in a better place.

Pregnancy - the baby's most important phase of growth.

This is also the time of pregnancy - a time I have to learn about a baby's different phases of growth and physically , mentally and creatively spend myself for her growth. 

Feminity or Ambition?

During my first trimester when I was tired, I wondered if I was up to continuing my career at a time when so many things were up that I had no idea how to deal with, and my physical limitations were increasing. 

In the second trimester , when my health picked up I realized that I cannot so easily give up what I stand up for. Yes, I want to be a great mom but I also want to be a great career-woman. What if I can turn what is a challenging phase for a woman into a rewarding phase?

This blog is my attempt at improving my career.

Comments

Post a Comment

Popular posts from this blog

Udacity - Data Engineering - Cloud Data Warehousing

 So I've roughly navigated this course and it was quite a challenge going through the theory because once the architectures were discussed it was just a whole bunch of clicking through in AWS and that can get boring. Architecture : For the architecture itself, the idea is a back office and a front office. The back office is all the sources and individual processes that bring in data. The Data warehouse simplifies these schemas into (possibly) a star model and then makes it easier and faster to use for the analytics / BI division (front office).  There are a few variants, where BI can directly access the main source, where DW can be department specific, or unique for each department still maintaining integrity among common columns. Cloud / AWS : Doing this in the cloud provides quicker start time, elasticity, scalability. The general idea is to read from sources and move to a staging S3 bucket and then push to a DW. For smaller tables it might be possible to directly use an EC2 inst
Read more

Designing Data Intensive Applications - Ch 2 - Data Models and Query Languages

  Relational Model Others that competed and did not last: network model hierarchical model XML database Object database NOSQL: specialized query options, expressive data model polyglot persistence impedence layer : the mismatch when moving from OO applications to relational databases Impedence is reduced by a translation layer like JSON JSON (document databases): flexible schema better locality : sub categories in one place instead of complex joins hard for many to many relations (easier in SQL) closer to data structure used by app layer schema on read instead of schema on write network model - tree structure like hierarchical but allowed multiple parents and so many-to-many - pointers and access paths instead of joins in SQL - complicated code even though efficient in small drives SQL - no access paths, just individual tables - access paths on the fly using query optimizer - can change indexes without changing table - conurrent - fault tolerant - shredding  Graph Model Query Languages
Read more