My Three (actually four) Takeaways: 1: Learning is something specific to an individual. Work out what works for you. 2: Focus on building something rather than on frameworks and tools. 3: Spend time identifying what tool/framework/language to learn. 4: Choose to go hands-on at the right time. What are yours?
Things I really liked Koushik: 1. Learning is not acquiring knowledge. It's a behaviour change. 2. Don't get attached to technology or tool. Shiva: 3. Allocate some time to learn while working on your project task. 4. Environments (Java/Python/JavaScript etc..) follow certain standards.. And limits our way of looking at things.. There could be other ways of doing things we don't learn unless we try.. Also one more thing I learnt today is people with 20 years of experience also start with "Hello World" example..😂
This is absolutely wonderful session. Thank you Ranga. I started learning last 18 months on cloud technologies and never stopped learning. Everyday learning is so much rewarding, It became hobbit for me! Thank you Siva & Koushik for sharing your experience!
I thought am the only person who learns many things and forgot soon. But now i understood after learning, even though after implementing need to revisit topics frequently so that i can remember those for long time.
I completely agree with Mr Koushik on the way he look at the new technology or any technical stuff for that matter is looking at problem space, where that particular technology really designed, developed and meant for. For ex, as per my knowledge and understanding , Hibernate is primarily ORM tool and it meant for achieving DB independence. Similarly, JPA - When i looked at JPA, I was really trying to understand, what it really meant for and I later understand that it is for - Achieving ORM independency. 1) We can switch to Different database through ORM tool, by simply changing the dialect, in case if there is nothing from our project specific to that DB. 2) We can switch to Different ORM tool by using JPA.
Engineer in any field is someone who really just not understanding the field of the engineering ( Ex : Software Engineering, Mechanical Engineering, Civil Engineering...etc) he studied, but applying that properly at right time is all really matters of his engineering skill.
My Takeaways: 1. Refer Intellij Inspect Code or configure Sonar to check code related issues 2. Read book like "Code Cleanup" which improves code qualiy 3. Maintain checklist for given reviews, so they should not repeated.
My 3 key take aways from the video: 1) Reasearch on why to learn a specific technology, 2) Practice and do more hands on to persist the learning, 3) Document your learning to review in future.
Best practices of rest api can we make this discussion and every time having curd rest api is not abvuous and achivhing business workflows from rest api how to do some time verbs required in rest api to identify the work flows can we have discussion on this please.
