Ugh! Salseforce! Fuuuuuck youuuuuu!

I have worked with C++, Java (little bit), Javascript, Python, R for so many years without any complaints ever! But this shit makes me feel so incompetent. Maybe I am actually incompetent but lack of constraints and good debuggers helped me hide that till date. 😭

Idk. I'm going to sleep.

Nah, debugging a proprietary, poorly documented stack like this is a royal PITA. A bunch of times I was in this situation it wasn't even me, it turned out to be a platform bug.

It's not you, it's Salesforce. I've heard quite a few people complain about it, which beings me to the conclusion: it's not you.

Hi again.
Debugging is a bitch.

Add lots of
System.debug("this variable" + xyz);

And enable debug logs, sometimes you need that "finer" log which is a mile long to identify an issue.

You also need to understand what is happening when you execute something.

Map out each trigger / method / flow / process builder and workflow that is triggered so you can track down what is actually going wrong and where, Salesforce has an assumed level of system and process knowledge which bites hard early on.

This can help read that horrible debug log:
https://github.com/financialforcede...-

It's not you, it's Shitforce.

Sounds like sharepoint
The platform that exposed web apis that didn’t work

@C0D4 https://github.com/financialforcede...

apparently I can't link to things.

😅