Is this the story of the Pea Sea and the DOS Fish?

> On Oct 18, 2017, at 12:23, CBB - Jay Fuller <[email protected]> wrote:
> 
> 
> That may be why we have these chats...
> 
> Or maybe what keeps me from falling asleep while waiting on my mom at a 
> doctors appointment.....
> 
> Sent from my Verizon 4G LTE Smartphone
> 
> ----- Reply message -----
> From: "Matt Hoppes" <[email protected]>
> To: <[email protected]>
> Subject: [AFMUG] Sonar
> Date: Wed, Oct 18, 2017 11:21 AM
> 
> OK this is news to me, although it may be accurate, I'm not entirely up on 
> the history of power code. If that is the case that makes me feel much better 
> about sonar.
> 
>> On Oct 18, 2017, at 12:20, Chuck McCown <[email protected]> wrote:
>> 
>> I have heard the same from other PC users. 
>>  
>> From: CBB - Jay Fuller
>> Sent: Wednesday, October 18, 2017 10:19 AM
>> To: [email protected]
>> Subject: Re: [AFMUG] Sonar
>>  
>>  
>> Based on what I witnessed - it was Simon who led the team to save powercode. 
>>  We got on it (Simon reached out to us when I complained about not being 
>> able to access a customer forum of a competing product). 
>>  
>> I sure don't remember Simon or his team causing any problems in Powercode
>>  
>> Sent from my Verizon 4G LTE Smartphone
>>  
>> ----- Reply message -----
>> From: "Matt Hoppes" <[email protected]>
>> To: <[email protected]>
>> Subject: [AFMUG] Sonar
>> Date: Wed, Oct 18, 2017 11:04 AM
>> 
>> Simon,
>> Can you describe how customer data is isolated on the cloud hosted SONAR 
>> system?
>> 
>> Josh - I think there are valid reasons to be concerned about the SONAR cloud 
>> code. Powercode had significant software issues when it first came out. 
>> These issues have been fixed since Simon left. 
>> 
>> Simon is at the helm of SONAR. 
>> 
>> We all make mistakes. We all learn from mistakes. I'm just looking to 
>> understand how the mistakes made at Powercode have not carried over to 
>> SONAR. =

Reply via email to