Just some well deserved kuddos

Just wanted to pass this on.

I got back from a meeting with the IT department of state agency a couple
of hours ago where I demoed a prototype of a Lucee app that I am doing for
them .

Much to my horror they found a bug that kicked out a stack trace. In my
haste to prep for the meeting I forgot to uncommented out the OnError()
function and inadvertently left debugging on.

As it turned out that was a blessing in disguise. They, a group of geeks,
were more far interested in the stack trace and the debugging info then my
app. And I do not blame them one bit.

The project lead, a seasoned polyglot programmer, was, and I quote, “Very
impressed” with Lucee. Namely the how fast Lucee was (~50 to 100
milliseconds with debugging on vs 1 to 10+ seconds on their current
system), and the quality of the debugging info and stack trace.

You won some Lucee fans.

Thanx
G!

Ha, that’s awesome. How to win someone over by breaking your code ;)On 14 July 2015 at 00:27, Gerald Guido <@Gerald_Guido> wrote:

Just wanted to pass this on.

I got back from a meeting with the IT department of state agency a couple
of hours ago where I demoed a prototype of a Lucee app that I am doing for
them .

Much to my horror they found a bug that kicked out a stack trace. In my
haste to prep for the meeting I forgot to uncommented out the OnError()
function and inadvertently left debugging on.

As it turned out that was a blessing in disguise. They, a group of geeks,
were more far interested in the stack trace and the debugging info then my
app. And I do not blame them one bit.

The project lead, a seasoned polyglot programmer, was, and I quote, “Very
impressed” with Lucee. Namely the how fast Lucee was (~50 to 100
milliseconds with debugging on vs 1 to 10+ seconds on their current
system), and the quality of the debugging info and stack trace.

You won some Lucee fans.

Thanx
G!


You received this message because you are subscribed to the Google Groups
“Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/2d880a1e-d42d-4843-90d7-5bcdf369f957%40googlegroups.com
https://groups.google.com/d/msgid/lucee/2d880a1e-d42d-4843-90d7-5bcdf369f957%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


Pixl8 Interactive, 3 Tun Yard, Peardon Street, London
SW8 3HT, United Kingdom

T: +44 [0] 845 260 0726• W: www.pixl8.co.uk• E: info@pixl8.co.uk
Follow us on: Facebook http://www.facebook.com/pixl8 Twitter
http://www.twitter.com/pixl8 LinkedIn
http://www.linkedin.com/pixl8CONFIDENTIAL
AND PRIVILEGED - This e-mail and any attachment is intended solely for the
addressee, is strictly confidential and may also be subject to legal,
professional or other privilege or may be protected by work product
immunity or other legal rules. If you are not the addressee please do not
read, print, re-transmit, store or act in reliance on it or any
attachments. Instead, please email it back to the sender and then
immediately permanently delete it. Pixl8 Interactive Ltd Registered in
England. Registered number: 04336501. Registered office: 8 Spur Road,
Cosham, Portsmouth, Hampshire, PO6 3EB

Comedy - I had a similar issue where I copy pasted a cfdump output into an
email (of a particularly complex struct) when trying to diagnose some API
calls to an external service - their tech support was like ‘wow, that’s so
clear - what did you use to make that?’ etc etc…On Tuesday, 14 July 2015 13:16:21 UTC+1, Dominic Watson wrote:

Ha, that’s awesome. How to win someone over by breaking your code :wink: