HN user

interbased

102 karma
Posts0
Comments169
View on HN
No posts found.

I talk to my manager everyday anyway, so a dedicated meeting to “catch up” isn’t really necessary. If there was a goal and we need to set up a check in meeting for that specific goal, that would make sense.

In a non-technical role, the definition of something being “done correctly” ends when the output/result matches the requirements. Whether that be a user experience, reporting, or whatever the requirements are. As long as those are clearly defined, and you can test the application against those definitions, the trust lies in the development team that it was programmed properly.

Any kind of testing should be defined at a high level. What is being tested and what is the expected result? What should trigger an alert?