The measure we share with Employers / Coworkers
Learning Cycle needs a lot of perspectives, focus, and consistent efforts.
I believe some form of futuristic vision + design thinking is my approach
Keep thinking!!!
- 40 hours attendance
- Responding to emails
- Accounting of tasks
- Attending meetings
- Quickly assemble something working with experiments/assumptions/learning's
- Accountability
- Satisfaction
- Preparedness
- Connecting problems and previous experiences
- Solving newer problems with comfort
- Sharing learnings
- Feeding the learning bus
Learning Cycle needs a lot of perspectives, focus, and consistent efforts.
- Some things I know 'How it works' because I have read about it, observed the working pattern
- Some things I know because 'I have tried and it worked'
- Some things I assume 'It works this way'
- Some things I learn the fundamentals and build my working knowledge on top of it
- The more you learn, the more it pushes you to learn and connect the dots
Am I a Good developer?
Whenever I hear about skill in JD,
Example Keras - I correlate it to, I have used Deep Learning in this project. Did I master everything in Keras? No.
How do I know I have learned everything in Keras?
I use Keras to achieve my Deep Learning model, finetune it. The perspective of learning is more towards a good quality MVP, Production code. Getting good quality in terms of performance and scalability needs learning. The focus is not on mastering technology but learning to solve the required Pieces.
What I do about Architecture evaluation?
Way back in 2016 / 2008, Evaluating cloud stack for Retail Analytics, Warranty Redesign, Salesforce Email Integration for XBOX. I was able to pull out a complete end to end architectural components on how the big picture will look like. Did I do hands-on implementation? No, but I was fairly convinced with patterns and use cases and learning How it works or why it works and successful in this context
I am a Prototype developer?
Yes, certain use cases to demonstrate working implementation had to build a working end to end prototype, ML pieces were working pieces, the mobile, web would be mockups built to show end to end flow.
Prototypes to production architecture refinement?
Taking prototypes to production, the Warranty approach to production is the best use case. Able to sell, migrate, implement the new approaches. Initially, Microsoft gave a 1 billion free warranty. We managed to save this hidden cost by ensuring warranty data is recalculated and it's more customer-driven.
Migration analysis
Migrating from old to a new system. Ensuring data is cleaned up.
Development in all these perspectives is my experience. Somehow my perspective of technology starts from business to technology, I do like data structures, spending time, and learning different implementations. My success or satisfaction is from solving business problems, not from technology learning. Build your vision, future. Keep Going!!!
Learning is Summary of
- Applied Knowledge
- Learned Knowledge
- Experimented Knowledge
- Assumption based Knowledge
I find that number of meetings is actually a good measure of productivity, it's just inversely proportional 😉— Clare Liguori (@clare_liguori) May 28, 2020
I believe some form of futuristic vision + design thinking is my approach
What are mathematical thinking and computational thinking and what is the relationship between them? #mathschat #MTBoShttps://t.co/fSWBlH5qAN pic.twitter.com/c3PncZmoBJ— CambridgeMathematics (@CambridgeMaths) July 13, 2020
Design Thinking : quand coeur, tête et main s'entrecroisent. Un aperçu rapide et quelques principes #DesignThinking #creation #creativité https://t.co/rqPDD7oyWo pic.twitter.com/iiOWKdqro0— Michèle Drechsler (@mdrechsler) August 1, 2019
More Read - LinkOur leading consultant is sharing his experience in Data Science. He suggests applying Design Thinking into Data Science applications. #datascience #designthinking https://t.co/BTHJBVYgGu Y— Smart Data Institute Limited (@SmartDataInsti1) July 14, 2020
Keep thinking!!!
No comments:
Post a Comment