Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Journey from Intern to Architect

Journey from Intern to Architect

This session was conducted at one organization for which I had designed enterprise tablet apps.

I had shared my thought which I follow during design architecture, framework or the large scale mobile/tablet apps.

I also shared about key points that helped/inspired me to deliver a quality app.

Get animated slide from
https://tinyurl.com/y62hxnlw

Himanshu Dudhat

October 18, 2019
Tweet

More Decks by Himanshu Dudhat

Other Decks in Programming

Transcript

  1. About me - Having 8+ yrs of exp. - Working

    on some awesome enterprise apps - Love to design optimal solution - Believes in architecting software rather then writing software
  2. Agenda - Software Developer vs Coder - Architecturing the software

    - Execution of Software development - Be Extraordinary Developer - Try It, trust me you will love it
  3. Software Developer vs Coder Coder - Like a machine. No

    need to think just do it. - Follow the instruction and execute it - Soch na kya jobhi hoga dekha jayega Software Developer - Understand the requirement - Think over it - Come up with the ideas, suggest possible ways - Find best suit solution for the problem - Right Pseudo code for the complex problem - Design solution - Unit Test - Deliver
  4. Architecture Vs Frameworks Architecture - An abstract plan that can

    include design patterns, modules, and their interactions - Ex. MVC, MVP, MVVM, MVI etc - May incorporate multiple frameworks. And multiple layers of framework Frameworks - Architected "physical" structures on which you build your application - Ex. YII, Laravel - Contains set of libraries, Wrapper/Abstract class
  5. Architecture lifecycle - Find the best suit architecture for your

    requirement - Define the team to design architecture - Mold it in your(Team) way - Review it - Test it with all aspect - Give it a try - Start iteration
  6. Executing Software development - Check out the requirement and define

    architecture to use - Check out the APIs and Frameworks which we can use - Segregate the complex/RnD task which need to be developed - Define core process and focus on that - Avoid Duplicacy in code - Think about LOC - Be a story writer - Understand your user base and design according to it
  7. Be Extraordinary Developer - Be lazy, be productive - Define

    coding standards - Write Pseudo code - Review your code and do PR - Keep your weapons sharp - Debugging, MAT, Plugins, Custom Templates and Frameworks - Be a storyteller - Contribute to community - Learn how to use Google
  8. Try It, trust me you will love it - Pseudo

    Code - Versioning and Tagging - GitFlow - CI/CD - Read blog - Listen Podcast - Write blogs - Contribute on Github and stack overflow