The Future of Working in IT

The Future of working in IT

Transcript

1. The Future of Working in IT
2. Disclaimer Presentations are intended for educational purposes only and not to replace independent professional judgment. The views and opinions expressed in this presentation do not necessarily reflect the official policy or position of blibli.com. Audience discretion is advised.
3. HOW ARE (SOFTWARE) PRODUCTS BUILD?
4. Who contributes in product development? Business Team Product Team Tech Team QA Team Analyze the market and produces business idea Translates business requirement to product roadmap Figure out how to create the product Make sure the product delivered are of good quality
5. Inside the Business Team • Business analyst – Responsible in analyzing business needs and how it integrates with current process / tech
6. Inside the Product Team • Product / Program Manager – Focus on what we want to build, based on business requirement – e.g. what features must we have for a e-wallet?
7. Inside the Product Team • UI – UX Team – Focus on how the user interacts with the product – e.g. where should the user be taken to after login?
8. Tech Team • Splits into two general fields: 1. Engineering • Responsible in providing solution to problems 2. Operational • Responsible in making sure the solution from engineers run smoothly Ps. In modern teams, sometimes they are mixed
9. Tech Engineering Backend Engineer Frontend Engineer Mobile Engineer Systems Engineer Data Engineer … Ps. This is only the commonly found ones, different industries have different specialization
10. Tech Operational Network Admin IT Helpdesk / IT Support Devops / SRE Security Database Engineer … Ps. This is only the commonly found ones, different industries have different specialization
11. QA • Some does QA manually, i.e. testing the program how the user use it • Some does QA with automation • Others do process improvement • Some do all
12. INSIDE THE TECH DEPARTMENT
13. Typical Web Application (Simplified) Load Balancer App Server App Server App Server DB
14. Typical Web Application (Simplified) Load Balancer App Server App Server App Server DB Software Engineer
15. Typical Web Application (Simplified) Load Balancer App Server App Server App Server DB DB Engineer
16. Typical Web Application (Simplified) Load Balancer App Server App Server App Server DB Connect, Monitor, Observe? Network / Ops Engineer
17. …and more
18. The Career Path
19. DAY TO DAY AS A TECH WORKER
20. Monthly / Bi-Weekly Ritual Beginning: Sprint Planning, Sprint Grooming Ending: Sprint retrospective
21. Daily Ritual Daily standup: tell your team your progress, challenges, etc. Work: code, review, meetings, tests, etc.
22. How do we coordinate tasks? • Issue Trackers – e.g. JIRA, Trello, YouTrack, Phabricator, etc.
23. How do we coordinate tasks? • How are issues filled? – On sprint planning, by the team. Based on priority and effort estimation. • Who takes what ticket? – Varies team by team. Some assigned on planning, some do Kanban (takes whichever have the highest priority and no one else worked on yet), etc. • How many tickets for each period? – Discuss with the team on sprint planning
24. To Simplify • Plan the tasks to take with your team • Split the task to small chunks • Work on it (write code, write tests, etc.) • Get review from your peers • Let QA clean it up • Repeat until no task left • ??? • Release!
25. WHAT’S OUR FUTURE?
26. Where do we work? • Notice how for much of the tasks are asynchronous – Only meeting and planning needs to be done together with all the team • The place of work is not as important as the task itself
27. What will we work on?
28. What will we work on? • Mostly automating job (including ours!) • Make sure those AIs and robot enhances your mind, instead of making it lazy
29. Thank You Slides at: https://s.id/obk0N