4 ms·
I would suggest you start with analytics and testing. This way you can test everything and use GA (or whatever) to gain insight into your app/sites usage. If
by tjtrapp 14y ago
I would suggest you start with analytics and testing. This way you can test everything and use GA (or whatever) to gain insight into your app/sites usage.
If you wanna really geek out, try to learn HTML+CSS and build some mocks.
Logs? After you review a prod log and notice a bug or exception, you create a bug and assign it to a developer. I guess this could be helpful. But that dev will probably review the same log and do some tests to find a root cause then go fix it. I feel the same for any log review or server/app alerts. Unless you know the code, its simply one interpretation.
Editors? I'm not sure this will help out much.
Git? I think that anything git related will eventually lead you to code.
Testing + Analytics, imo, should be your sweet spot for now.
Good luck.
- adam 14y agoI think the reason I began trying to understand production logs and bug alerts was more of a calming mechanism than anything else. The developers get the same alerts and are already reviewing the logs, but by me understanding them I rarely need to ask if it's anything to worry about, etc. So it's not really me trying to help them with anything, it's more about knowing when to be worried vs. not, say if a client is launching their site on our platform tomorrow and I see some New Relic error come through at 2am the night before.