u/githelp123455

Hello,

I'm on a Performance imporvement plan. I am given a metric that it is impossible to meet. What can I do? Document the metric and give it to my employment lawyer after the PIP ? Bring it up to the higher ups on why it seems like an unfair metric, etc?

More context on the metric if people are interested: https://www.reddit.com/r/legaladvicecanada/comments/1ti4nta/comment/oms0egi/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Im front-end leaning dev but Im trying to pick up more backend tickets to expand my backend skills.

I am wondering, what are the responsibilities? Id like to bring it up to my manager and push similar iniatives as well.

So far I have done:

- Done database migration by creating new tables or add/modify columns

- Create and adjust endpoints, so that the client can say update a new column in the database with new API versioning

- Logging and monitoring to some degree

- I only worked on repositories where it's the API and API gateway itself. I don't touch other stuff like Kafka setup, Redis, etc.

I have not done:
- Query optimization. I think for Query optimizaiton I will have a chance if people are reporting the backend to be slow.

Im only doing simple shallow backend tickets now, I think I am missing alot of the 'beef' of backend

Do you populate the actual test database like so?

// userRoutes.test.js
it("POST /users should create a user and persist it", async () => {
  const res = await request(app)
    .post("/users")
    .send({ name: "John", email: "john@email.com" });

  expect(res.status).toBe(201);

  // actually check the DB
  const user = await db.findOne({ email: "john@email.com" });
  expect(user).toBeTruthy();
});

Which is different from unit tests where you can use mock values?

it("should call db.save with correct data", async () => { 
  db.save = jest.fn().mockResolvedValue({ id: 1, name: "John" }); 
  await createUser("John", "john@email.com"); 
  expect(db.save).toHaveBeenCalledWith({ name: "John", email: "john@email.com" }); 
});

If we use an actual test database, that means that whenever we run our test is filled. which can be too much?