Welcome to first edition of datum newsletter
Get Smarter about data & analytics, learnings to help you deliver successful data products/solutions
Welcome to the first edition of the datum newsletter.
Thank you so much for subscribing!! and please tell a few friends if you feel like it.
Why the newsletter:
Welcome to the Datum newsletter. My name is Vijaya Phanindra and I am working in the data domain since 2011. I worked in multiple roles as engineer, architect, solution consultant, and product owner. The Datum newsletter summarizes learnings and thoughts about data & analytics both from technology and business perspective. Hopefully the insights make you smarter and help with your data initiatives.
I would like to share my experience and also of others through this blog and newsletter. If you want to contribute your thoughts on this blog please do get in touch by by commenting on the post, I will reach out to you.
Summary of last week posts
A work breakdown structure (WBS) for big data analytics projects — Part 3-Process
Interview with a seasoned principal architect R Lakshminarayanan on how to navigate your career in the big data domain.
1. Tell me a bit about yourselves and what you do?
Work as an architect designing CRM applications using big data technologies.
2. What motivated you to pivot to the big data domain?
Limitations with the traditional database systems.
3. How did you go about learning the Big Data tools?
Self interest, necessity of adaption, support from the management.
4. What were the challenges you faced in learning?
Mostly self exploratory since it was hard to find out an expert in this area for instant answer with the challenge.
5. Was your previous experience helpful?
Yes. Though several of concepts are the same, was in a situation to choose right implementation approach out of many - in a hard way.
6. Now that you are successful in pivoting to big data domain if you have to approach this process again what would you change?
Try to improve the development processes.
7. How are you updating yourselves on all the changes happening so fast in the industry?
Identify the area of improvement, discuss with focus groups, go through blogs, do hands-on.
8. Big data domain and data domain as such is going through a rapid phase of transformation? Is there a change in your thinking now compared with when you started with big data?
Certainly yes. Adapting the best practices while migrating the applications to cloud with big data.
9. Is it difficult to find a new job/role without previous experience in big data?
All depends on the years of experience & the type of role you are looking for.
10. What is the advice you give to professionals who want to transition to a big data domain?
Define the goal with a timeframe, have a mentor, do hands-on, make sure that your goal is achieved in the set timeframe. If you don’t have any programming background, learn at-least Python.
Note: R Lakshminarayanan is a former colleague of mine, he graciously accepted my request for an interview.
Other Recommendations
Datalake — An understanding and approach to extracting value
A decade of Big data & Hadoop and questions are similar, Can Hadoop replace RDBMS? Can Big Data technologies replace DataWarehouse systems…
Archives
A work breakdown structure (WBS) for big data analytics projects — Part 2-Store
Continuing with the theme of typical big data solution pattern below, part 2 covers the storage aspects of a big data solution
A work breakdown structure (WBS) for big data analytics projects — Part 1
Ever wondered what activities are involved in a big data project? A work breakdown structure (WBS) helps in selecting technology/tools…
Understanding tradeoffs in designing real-time streaming analytical applications
There is no good or bad design instead, there will be many tradeoffs to make and hopefully, those tradeoffs are good for a particular use…
You are receiving this email because you have subscribed via our website.
All the posts are available on the website.
Disclaimer: All the opinions expressed are personal independent thoughts and not to be attributed to my current or previous employers.