Timeline for Excel VBA to parse JSON out of Google Maps API
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2020 at 13:24 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jun 9, 2016 at 12:56 | comment | added | Mathieu Guindon | @SMeaden join vba rubberducking chat anytime you want to talk about it! =) | |
| Jun 9, 2016 at 12:07 | comment | added | Mathieu Guindon | Not sure it counts as "endorsement", but Mr.Bullen has offered the original VB6 Smart Indenter code to the project; Carlos J.Quintero (author of MZ-Tools) came to our chatroom to congratulate us, and a bunch of MVP's are following us on GitHub and Twitter. | |
| Jun 9, 2016 at 10:18 | comment | added | S Meaden | Do you have any endorsements from people like Steve Bullen (author of Processional Excel Development)? He was a mentor of mine when I worked alongside him for two years. | |
| Jun 9, 2016 at 10:07 | comment | added | S Meaden | On the meta level is Rubberduck like MZTools which also highlighted unused variables etc. It sounds like a 'code police' tool which I have had whilst working on very many large systems with millions of lines of code; are the rules configurable? | |
| Jun 9, 2016 at 10:06 | comment | added | S Meaden | Ok thanks a thorough examination. I could make rebuttals on many points but it is probably better to move to a meta discussion about code police. Just a few rebuttals though, the stack overflow (SO) original poster (OP) had his own API key, so sKey was commented out but actually public in another module (not shown) so as not to expose my API key. Also, I know tests should be in separate modules but I was giving OP a slab of code that they could cut and paste. | |
| Jun 9, 2016 at 5:25 | history | answered | Mathieu Guindon | CC BY-SA 3.0 |