all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
||||||
|
||||||
|
|
|
Notes:
|
|
Code Sign-Off Process: 10. Sign-off on code and add small version control per page. Talking with an adilas intern. 11. I would like to work with developers on their machines and sign-off on things locally. 12. Once a page has been signed off locally, the developer will upload pages into the top secret/need sign offs folder. This will keep it out of production until it gets a final gate keeper review. 13. The gate keeper (Brandon for now) will pull down the files that need a sign-off. The gate keeper will then test and make sure that things are good to go to production. 14. Once put in production, new code will be put up online in the released or normal top secret folders. All developers will go to the FTP server to get the latest files that have been released. We had a request to help manage max & minimum inventory levels across companies. That sounds like application flex grid or real in-line extensions. These projects are gaining momentum and heat. New Developers: 15. Meeting with an adilas associate and talking about a company that can help or who would manage the process of bringing people on board and bringing them up to speed. Both reps and consultants as well as developers. We are focusing on the developers right now. 16. Film and record all of the training pieces and put them up on adilas university. 17. Have a test and/or certification level to help with skill sign offs. Maybe use flex grid tie-ins or elements of time to accomplish this. 18. Do things once and then use over and over again. 19. Make the first video as a 5 minute overview. Keep it brief. 20. Anybody new needs to go through the process. 21. Use the code segment – can act as an evaluation process of sorts. Basically, do we want to spend the money on their education? In other words, a trial period of sorts. 22. Plan some 2 hour session in December & November – monthly & weekly training sessions. 23. -Generally schedule out time frames for each subject. o Topic: • Bullet points • Requirements • Options • Visual aids • Time frame 24. Double the bang for the buck… show code sample and concepts and how they relate to adilas. Put the concepts into action at the source. 25. Use all of the different teaching methods and learning styles. Audio, visual, actual, hands on, etc. 26. There will be quite a lot of time in both pre & post production stuff. 27. API – Play at the wall! This is where we could support the largest number of code developers. 28. Do a small 1-2 hour seminar for interested developers – Look for people who are interested. Pull from a bigger pool! 29. Start the first seminar with hand-picked folks who want to play. 30. Use the seminars and meetings as a screening process for qualified people. Help them get the skills to pay the bills. Share, share, share! 31. Try storming – Be willing to circle back around. 32. It is ok to break models. We do it all the time. BE sensitive about his but don’t fear. Take more counsel from your faith, hopes, and dreams than from your fears. Let faith win! 33. When teaching a code class, it might be cool to have a way for class participants to submit and run code. Maybe use elements of time and sub comments. Maybe each person has their own main element and then uses the sub comments for assignments. |