On countless occasions, I felt so stressed I didn't figure out the solution of a particular problem.
Especially where I work - I am an accountant but an automation programmer on Visual Basic Applications for Excel - I find it too challenging to automate a process ( creating macros that convert formats to different formats or to automate some reports .. etc ) when I really cannot figure out where the problem is, especially with VBA cause it doesn't show you where exactly is the bug that needs to be fixed.
What is you toughest moments ? Share your experience and let's discuss it
Top comments (6)
For me the "toughest moments" are the times when you have already released your work and some inexplicable bug happens; there's a tremendous stress in the room, your heart works at 200% but your brain is at 20%; adrenaline is for flight-or-fight, not structured thinking.
And in those moments you also need useful error messages: the ones that point into the right place. On the other hand the worst errors are the ones that are silently ignored, you just face something that just does not work, no explanation, no direction.
Totally I know what you mean. I have experienced that several times.
Which programming language you're working with ? which framework - if any . ?
Learning from AWS docs with all the quirks, edge cases, tons of outdated docs and over the top verbose syntaxes, poor logging, slow console etc. But after you memorize everything (or use some abstraction that "just works"), it is a great ecosystem. Talking about Lambda here, but i was learning it long time ago, so maybe it got easier ;-)
Awesome :)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.