$TTCM More conversation with Jordan Gray Head deve
Post# of 107318
(Total Views: 924)
Posted On: 05/05/2019 12:48:27 AM
$TTCM More conversation with Jordan Gray Head developer of #Arknet
Great question regarding how close I get to the fire... as it turns out - we are not really structured off of a typical hierarchical model as much as you might find in a large corporation - I am the original architect and designer of our digital asset management platform starting back in the early 2000 timeframe. But I also architect of our Single sign on infrastructure, all of our data strategy deployments, all of our customer integrations and new development projects, our e-commerce/ elearning / content management / lead generation /event management platform – all of these really become part of the overall picture when we are innovating and connecting existing modules and pieces.
So I do not touch the programming directly - excepting in experimental capacity at times in parallel or ahead of the dev team – but I try to keep my hands out of any coding meant for production development paths - leaving that to the team of engineers. Available on this project about seven engineers – but there are very specific activities that are made more complicated by throwing too many engineers at the same problem for long periods - we do gather as many of the heads as possible into one room when we hit a wall to make sure that we are vetting the problem across our entire brain trust – but then it breaks down to work in smaller sub teams.
In any case I am touching the mobile team every single day / and other parts (infrastructure/platform) of the team multiple times a day as needed because there are constantly choices that need to be made different directions to turn if we hit a wall in one area and we need to shift our strategy.
(I do not typically run a team of developers off on an expedition mode where I wait to hear back from them for weeks on end while hoping for the best – I like to keep my brain in the language and the dialogue going daily so that I can remain in the conversation and answer questions that really most other people would not be able to answer about how we will best leverage existing components. this saves someone else from creating something that we already have elsewhere in our toolkit.)
Great question regarding how close I get to the fire... as it turns out - we are not really structured off of a typical hierarchical model as much as you might find in a large corporation - I am the original architect and designer of our digital asset management platform starting back in the early 2000 timeframe. But I also architect of our Single sign on infrastructure, all of our data strategy deployments, all of our customer integrations and new development projects, our e-commerce/ elearning / content management / lead generation /event management platform – all of these really become part of the overall picture when we are innovating and connecting existing modules and pieces.
So I do not touch the programming directly - excepting in experimental capacity at times in parallel or ahead of the dev team – but I try to keep my hands out of any coding meant for production development paths - leaving that to the team of engineers. Available on this project about seven engineers – but there are very specific activities that are made more complicated by throwing too many engineers at the same problem for long periods - we do gather as many of the heads as possible into one room when we hit a wall to make sure that we are vetting the problem across our entire brain trust – but then it breaks down to work in smaller sub teams.
In any case I am touching the mobile team every single day / and other parts (infrastructure/platform) of the team multiple times a day as needed because there are constantly choices that need to be made different directions to turn if we hit a wall in one area and we need to shift our strategy.
(I do not typically run a team of developers off on an expedition mode where I wait to hear back from them for weeks on end while hoping for the best – I like to keep my brain in the language and the dialogue going daily so that I can remain in the conversation and answer questions that really most other people would not be able to answer about how we will best leverage existing components. this saves someone else from creating something that we already have elsewhere in our toolkit.)
(2)
(0)