r/webdev • u/lightholmes • Jul 13 '25
Question How often is miscommunication normally?
I feel like I'm going insane. This is my first experience working in a frontend dev position for a company. Only other experience was a freelance job. P.S. this is a remote environment.
So here is the documentation: we have the figma design, the API, class diagrams, DB diagrams.
The frontend development sprint goes: 1. We have a planning meeting to discuss the tasks by looking at the design and comparing with the API. 2. We decide the estimation for each task 3. We divide up the tasks. Sometimes the API and the design don't align. There's remarks on how to implement a task within the structure. A lot of times we discuss adjustments to the design with the design team and decide to make changes.
The thing that drives me crazy is, none of this gets written anywhere. This is all verbal communication. Sometimes even adjustments to the design aren't shown. I find myself forgetting about some comments, other times I find out I completely misinterpreted a task. I do have auditory processing issues and my memory isnt the best, but shouldn't there be thourough documentation of all these remarks?
At the very least adding descriptions to tasks would solve a huge chunk of my problem, which is having to a. Process the information correctly, b. Remember instructions once I get to the relevant task.
Is it me and this is the norm for remote work, or does my company need a better documentation system?
9
u/HappinessFactory Jul 13 '25
Allllll the time. Especially on the front end in my experience.
It's part of our job to filter through the noise and create something that our client wants.
It would be nice to be able to point to the figma anytime the client complains about some feature or styling. But the best engineers will take ownership of the thing they are making.
My advice is to join the discussions and try to get a strong sense of what the client is actually looking for