chacha/MyCV
1
0
Fork 0
Code Issues Activity

Update current_situation.md

Browse Source
This commit is contained in:
ChaCha
2023-10-15 18:10:07 +02:00
parent c400cd5600
commit d5e8990b7f
1 changed files with 16 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
current_situation.md
View File

@@ -8,29 +8,29 @@ I have been working in this company for nearly 10 years and climb from software
# Job Key points
- Designing the company TE(Test Equipment) SW Platform so it fit:
- needs of 200 developers (in 4 site / 2 countries), 20-50 new TE every year
- requirements of 3 (main) usages: UUT development / production and maintenance
- both for intern usage and external-customers delivery
- from small system (1 bay, to test a simple card) to big one (a complete warehouse, to test a full system)
- a given version might be used for 20+ years
- Needs of 200 developers (in 4 site / 2 countries), 20-50 new TE every year
- Requirements of 3 (main) usages: UUT development / production and maintenance
- Both for intern usage and external-customers delivery
- From small system (1 bay, to test a simple card) to big one (a complete warehouse, to test a full system)
- A given version might be used for 20+ years
- TE are both an execution and development platform
- Helping people to use this platform:
- Documentation / Training
- Real support in TE integration
- Dedicated support in TE integration
- Design & Develop Test SW template projects to correctly use this platform
- Support on Project & Team management
- Interface with projects:
- Quotations / Planning
- Feature survey or requests
- Some important part I have dedicated responsibility:
- company TE generic self-test software
- critical libraries
- Companie's TE self-test generic software
- Critical libraries
- Improving working methods
- implement CI/CD pipeline for Test SW (and later the SW platform itself)
=> with the specific constraints of this application:
- for Test SW there is almost always hardware involved
- for the Platform itself it’s a system-level test, which add more limitation
- improve reuse and coworking
- making SW catalog and libraries requirements
- defining methods at any stage of the process, including at non-software ones
- technology watch (ATML, uServices approach.)
- Implement CI/CD pipeline for Test SW (and later the SW platform itself)
- With the specific constraints of this application:
- For Test SW there is almost always hardware involved
- For the Platform itself it’s a system-level test, which add more limitation
- Improve reuse and coworking
- Making SW catalog and libraries requirements
- Defining methods at any stage of the process, including at non-software ones
- Technology watch (ATML, uServices approach.)