Pete, I look at it this way… can you explain the code you wrote?    Can you fix 
it when it breaks….   Then its good code….  Optimization comes later.

Don’t use code you can’t explain in production….. cause when it breaks well….  
:)

The guys I work with constantly say their UCCE scripting is bad….   Sure could 
be cleaner, but when I ask them to explain it they can and thats all that 
matters….

My .0002 cents…

Thanks for the link




> On Dec 6, 2019, at 7:36 PM, Pete Brown <[email protected]> wrote:
> 
> I realized it’s been a year since I’ve even sent anything to this list.  
> Unfortunately I don’t have the time to work on the UC tools much these days.  
> Instead of letting them stagnate any longer I’ve made the GitHub repo public. 
>  Just clone it and build with VS2019.
>  
> https://github.com/adhdtech/uctools <https://github.com/adhdtech/uctools>
>  
> As stated in the README, these were the first C# apps I ever wrote.  So no 
> griping about the offensive code quality.  If anyone is interested in 
> contributing, just let me know.
>  
> I’ll leave the existing binaries up on https://www.adhdtech.com/uctools.html 
> <https://www.adhdtech.com/uctools.html> for the time being.
>  
> Merry Christmas!
>  
> -Pete
> _______________________________________________
> cisco-voip mailing list
> [email protected] <mailto:[email protected]>
> https://puck.nether.net/mailman/listinfo/cisco-voip 
> <https://puck.nether.net/mailman/listinfo/cisco-voip>
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to