Hi Koushik and Ranga, I am very Thank ful for your help in trainings provided I really love them and am a big fan of you. I got my carrier from your trainings. Seeing these video was too a wonderful to me. Thanks, Padam Dhariwal.
Key Take-Aways 1. An architect should be responsible and play various roles in building a product 2. Be a team player, maintain good relationships with the team and with other stakeholders. Have good interpersonal skills. Be a good storyteller. 3. Understand the client/customer business needs and maintain standards in identifying technology stacks.
Have a decent knowledge on the business domain , map the requirements into technical solutions are the fundamental skills to have as an Architect. Having good knowledge on how different systems behave in the real world will help you make better decisions.
1) Understand the bigger picture 2) Standardize/Automate and Delegate work as much as possible 3) Lead the team by example including Communicate the why part, co-ordinate and taking the full responsibility of the team
Thanks for the wonderful discussion.. I highly appreciate the openness.. Im working as team lead and sometimes I struggle with my personal deliverables because of constant interrupts from team.. but good to know it’s common problem even faced by smartest people.. I will be glad if you post links for tech blogs you guys refer to keep yourself updated.. Once again thanks a lot for the great session!!!
3 key takeways 1. Keen in observing what is happening and around you and upgrade yourself to step in shoes of next higher role 2. From IC transition to lead a team and become accountability for deliverables 3. Contextual communication and management negotiating skills are key things
My 3 take aways are 1. Develop good communication and interpersonal skills 2. To transition to tech lead role start delegating, reviewing , negotiating, helping team and understand big picture 3. To transition to architect role, ask questions on why each decision is made in project, talk to stakeholders to understand business, keep up to date on the areas you work through blogs and feeds, have a 10 000 feet idea on things, follow surveys and presentations of architects
Its very enlightening session where we are looking for..🙂 Key points: 1. Empathy about people will communicate. 2. should switch from technical to common layman communication. 3. should maintain consistency overall framework.
3 key takeaways. 1)Major mind shift from IC role to Tech Lead/Architect role with respect to the whole system design. 2)Empathy, connecting team together with incremental and quality deliverables. 3)Accept the risk and do the negotiation with clients or supervisors in positive manner.
I am in current state of transition to lead role. And I can totally relate to points made here. This discussion gave me some clarifications. Thank u all
Thanks a lot guys. I started my current career as a TL, but the work allocated to me is like an architect. Thant this discussion put me motivated and got shared your experience.
My 3 Takeaway's 1) We need to have very good Communication Skills, need to improve on the same. 2) To Be Team Lead or Architect we need to try to delegate the work to the team members and see it is properly done. 3) Always be a learner on technologies, try to get technical updates from people whom we love register there or any specific source where we don't waste our time like not on social media sites like Facebook, etc. Thanks, Padam Dhariwal
Hi Ranga I have always learnt something from any of your video that I see. From this my three takeaways are: 1. Code reviews should be treated as teaching opportunity rather than fault finding. 2. As a tech lead focus should be on team success rather than our own individual contribution to software development. 3. Having a good relation with the team is very important to which I too believe the same and even i have experienced in my team and by doing that, team surely opens up with us.
Great Discussion!!!...Thanks for the session , it really clear lot of questions i think every programmer has regarding to become architect or Tech Lead Challenges...Thanks!!! in my opinion 3 important takeaways are: 1. Empathy - to improve your communication need to understand other persons mindset. 2. Good relationship with team and make them up to mark for more productive. 3. Why Why Why??? -> Ask the question yourself so you can understand that what is the big picture of your application in big integrated echo system and make the trade-off in business needs and your team's technical need.
3 Takeaways items 1. Work as a team with motive knowledge sharing 2. Inter-personnel communication within team and with senior must improve 3. Automate as much as possible
Such a nice and informative session. Learned many things from this video and gained some insights like the business side/aspect of IT industry. Very useful. Keep posting such sessions. As always, you can never go wrong with Koushik and Siva in the same frame. Keep more sessions with both of these coming. 💯
Three Key Takeaways 1. Technical Lead/Architect is accountable and responsible for timely deliverables and should have good technical/business/communication skills. 2. Should have negotiation skills and have agreement with business to tackle number of features delivery and its timeline . 3. Be empathetic and set framework/ guidelines that ease development/process, and have teaching mindset while doing code review and make sure to delegate tasks and invest time in training juniors.
Thanks Ranga,SIva and Koushik for making this series. How much time do you spend everyday on learning something new? Just curious about how you guys are managing your time..
In my current organization, I hardly find a good architect having sound technical knowledge. And the most difficult thing is that they are not easily reachable. We have to wait long for their help or any response. A few years back the scenario was very different. But a lot of senior members/architects left the organization and those who joined recently are very abusive and not good. What do you suggest in this context?
It was very Informative session. One Question I have for Siva - What is the process he follows for taking a 10000 feet view to stay updated with Trends which mentioned ?
I enjoyed the discussion and learnt as much too. I'm a student of Ranga as well which brought me to this discussion session. Would you have any thoughts on how different a SOLUTIONS ARCHITECT terminology would be used within the company? or is this role, just as the same as Technical architect umbrella? thanks.
3 key takeaways. - Working with stack holders (communication). - Asking why? With a purpose to learn. - consistency in project and further at enterprise level.
Entire Series of Videos - ruclips.net/p/PLBBog2r6uMCS0FX6Ym_8NYeTNykUF5970
Hi Koushik and Ranga, I am very Thank ful for your help in trainings provided I really love them and am a big fan of you. I got my carrier from your trainings. Seeing these video was too a wonderful to me.
Thanks, Padam Dhariwal.
Key Take-Aways
1. An architect should be responsible and play various roles in building a product
2. Be a team player, maintain good relationships with the team and with other stakeholders. Have good interpersonal skills. Be a good storyteller.
3. Understand the client/customer business needs and maintain standards in identifying technology stacks.
Have a decent knowledge on the business domain , map the requirements into technical solutions are the fundamental skills to have as an Architect. Having good knowledge on how different systems behave in the real world will help you make better decisions.
1) Understand the bigger picture 2) Standardize/Automate and Delegate work as much as possible 3) Lead the team by example including Communicate the why part, co-ordinate and taking the full responsibility of the team
Thanks for the wonderful discussion.. I highly appreciate the openness.. Im working as team lead and sometimes I struggle with my personal deliverables because of constant interrupts from team.. but good to know it’s common problem even faced by smartest people..
I will be glad if you post links for tech blogs you guys refer to keep yourself updated..
Once again thanks a lot for the great session!!!
3 key takeways
1. Keen in observing what is happening and around you and upgrade yourself to step in shoes of next higher role
2. From IC transition to lead a team and become accountability for deliverables
3. Contextual communication and management negotiating skills are key things
My 3 take aways are 1. Develop good communication and interpersonal skills 2. To transition to tech lead role start delegating, reviewing , negotiating, helping team and understand big picture 3. To transition to architect role, ask questions on why each decision is made in project, talk to stakeholders to understand business, keep up to date on the areas you work through blogs and feeds, have a 10 000 feet idea on things, follow surveys and presentations of architects
All legends coming together and creating great content is awesome. Thanks for showing a path to us.
Its very enlightening session where we are looking for..🙂
Key points:
1. Empathy about people will communicate.
2. should switch from technical to common layman communication.
3. should maintain consistency overall framework.
Great comments . This will be helpful for me in performing my role as an architech.
Excellent and exciting discussion. Thanks a million, Ranga, Siva, and Koushik.
These guys are really awesome. They discussed current IT industry problems and solutions. Really useful.
Thanks for making this session. It really helps people like me who's aim to be an architect.
3 key takeaways.
1)Major mind shift from IC role to Tech Lead/Architect role with respect to the whole system design.
2)Empathy, connecting team together with incremental and quality deliverables.
3)Accept the risk and do the negotiation with clients or supervisors in positive manner.
Wonderful takeaways! Thanks for sharing Sreenivasulu.
Yes I agree with Siva mentioned points, tech lead role is tougher than architect role.
This is what I am looking since long.
Thanks for making this session.
I am in current state of transition to lead role. And I can totally relate to points made here. This discussion gave me some clarifications. Thank u all
Million Thanks for this collaborative talk. You all added good points. Thank you for leading us, you three are great tech leads for us.
Thanks for doing this Collab. Quite interesting discussion !!
Thanks a lot guys. I started my current career as a TL, but the work allocated to me is like an architect. Thant this discussion put me motivated and got shared your experience.
Thanks for making such videos. We feel so lost when it comes to grow in our career. Please make more videos like this 🙏
Glad to hear that Vishwas! We are expecting to create such videos every week. Good Luck!
My 3 Takeaway's
1) We need to have very good Communication Skills, need to improve on the same.
2) To Be Team Lead or Architect we need to try to delegate the work to the team members and see it is properly done.
3) Always be a learner on technologies, try to get technical updates from people whom we love register there or any specific source where we don't waste our time like not on social media sites like Facebook, etc.
Thanks, Padam Dhariwal
Congratulations on winning a free course! Can you send me the name of the course you want the free coupon for by email rangaATin28minutesDOTcom?
Wow thanks for such an awesome and open discussion....very much relatable and true. 👏
Hi Ranga I have always learnt something from any of your video that I see. From this my three takeaways are:
1. Code reviews should be treated as teaching opportunity rather than fault finding.
2. As a tech lead focus should be on team success rather than our own individual contribution to software development.
3. Having a good relation with the team is very important to which I too believe the same and even i have experienced in my team and by doing that, team surely opens up with us.
Awesome Kuldeep. Thanks for taking the time to post the takeaways! Take care.
Very informative, Thank for the collaboration.
Great Discussion!!!...Thanks for the session , it really clear lot of questions i think every programmer has regarding to become architect or Tech Lead Challenges...Thanks!!!
in my opinion 3 important takeaways are:
1. Empathy - to improve your communication need to understand other persons mindset.
2. Good relationship with team and make them up to mark for more productive.
3. Why Why Why??? -> Ask the question yourself so you can understand that what is the big picture of your application in big integrated echo system and make the trade-off in business needs and your team's technical need.
3 Takeaways items
1. Work as a team with motive knowledge sharing
2. Inter-personnel communication within team and with senior must improve
3. Automate as much as possible
Such a nice and informative session. Learned many things from this video and gained some insights like the business side/aspect of IT industry. Very useful. Keep posting such sessions. As always, you can never go wrong with Koushik and Siva in the same frame.
Keep more sessions with both of these coming. 💯
Yup. Absolutely. A lot more sessions coming up.
This is what i am looking since long ..
amazing podcast , very insightful
Three Key Takeaways
1. Technical Lead/Architect is accountable and responsible for timely deliverables and should have good technical/business/communication skills.
2. Should have negotiation skills and have agreement with business to tackle number of features delivery and its timeline .
3. Be empathetic and set framework/ guidelines that ease development/process, and have teaching mindset while doing code review and make sure to delegate tasks and invest time in training juniors.
Thanks for the takeaways Rani!
Thanks Ranga,SIva and Koushik for making this series. How much time do you spend everyday on learning something new? Just curious about how you guys are managing your time..
Very good discussion, I could echo your thoughts.
Excellent content guys. Keep it up 👍.
In my current organization, I hardly find a good architect having sound technical knowledge. And the most difficult thing is that they are not easily reachable. We have to wait long for their help or any response. A few years back the scenario was very different. But a lot of senior members/architects left the organization and those who joined recently are very abusive and not good. What do you suggest in this context?
It was very Informative session. One Question I have for Siva - What is the process he follows for taking a 10000 feet view to stay updated with Trends which mentioned ?
Apart from gaining knowledge in daily work, are there CERTIFICATIONS that can help becoming an architect?
Excellent conservation
I enjoyed the discussion and learnt as much too. I'm a student of Ranga as well which brought me to this discussion session. Would you have any thoughts on how different a SOLUTIONS ARCHITECT terminology would be used within the company? or is this role, just as the same as Technical architect umbrella? thanks.
It's helpful...
3 key takeaways.
- Working with stack holders (communication).
- Asking why? With a purpose to learn.
- consistency in project and further at enterprise level.
Awesome Takeaways Mayank! Thanks for sharing.
Congratulations on winning a free course! Can you send me the name of the course you want the free coupon for by email rangaATin28minutesDOTcom?
Thank you techies
good one guys :)
How much role TOGAF certification play to become architect.. is it absolutely required in companies for architect position.
TOGAF and Zachman framework and its methodologies help you in various phases of the software development lifecycle.
thanks
take away - expectation of architect role - to have a holistic view of ecosystem not just the product / module only
super excited for this ...
communication
consistency
Give importance to others view
It's nice discussion
These sessions are pure 916.
My sincere respect sir 😊
Dont use words repetitive in your communication like 'probably, basically, lot of, ' Try to use different words.
Are this talks pre-scheduled, I never receive any notification :(
Yup. Please hit the bell icon! More discussions coming up!
This will be interesting.
Absolutely!
Stop war
Missing Basant
Do you know him? Can you connect us?