A good article that includes symbol resolution in context

https://www.linuxjournal.com/article/6463

I’m probably at about a 1/10 in ampscript. I just don’t use it enough. I tried something like what you are describing but it didn’t work very well. Trying to debug ampscript that runs in an email template at send time by copying into a cloud page and then trying to mimick the various properties only available at send time was just maddening. I can’t comprehend how Salesforce bought such a buggy and poorly thought through piece of junk. It’s a coin toss whether some of the main menus even load half the time. Ergh…

I loathe debugging ampscript and anything to do with marketing cloud with a passion…

With about 12 years in my primary language I’d say my expertise is expressed in knowing exactly what to Google…

deleted by creator

Just remember: imposter syndrome is real. Everything you learn exposes you to ten things you don’t yet know. Successful devs are comfortable with this reality - the job is one of constant learning. Best of luck!

I have worked for financial institutions that have variations of the last one. If I saw it I wouldn’t even blink. Semi realistic reasons might be:

Status attribute - because the project is using the base library of [project whatever] which was the brain child of eNtErPrIsE aRcHiTeCt whose hands on skills are useless and the off-shore dev team who assigned [random newbie] because that’s who was available at the time. They used a status attribute because they didn’t know how to get the status of the http response. No-one with budget control is interested in hearing about technical debt at the moment. Everyone has to use it now else the poorly written test classes fail.

Message code: because “we need codes that won’t ever change even if the message does”. Bonus points if this is, in fact, never used as intended and changes more frequently than…

Message: “because we still need to put something human readable in the log”. Bonus points x2 if this is localised to the location of the server rather than the locale of the request. Bonus x3 if this is what subsequent business logic is built on leading to obscure errors when the service is moved from AWS East Virginia to AWS London (requests to London returning “colour” instead of “color” break [pick any service you never thought would get broken by this]).

I have seen it all etc