3 ms·
> Reading between the lines here, this sounds like an engineer who wants to satisfy requirements that the project doesn't actually have. In my experience, this
by pdonis 6y ago
> Reading between the lines here, this sounds like an engineer who wants to satisfy requirements that the project doesn't actually have.
In my experience, this is one of the least understood aspects of the engineer's job, often by engineers themselves. An engineer's job is not to create the absolute highest quality solution every time. The engineer's job is to match solutions with requirements. Often that means not implementing something that, from a purely technical perspective, would be an improvement, because it's not needed to meet the actual requirement, and would take time and effort from something that is needed.
- gnusty_gnurc 6y agoI get frustrated when it seems like no one is maintaining requirements (or aware of them) and I'm just expected to make something work, as though I can read minds about what's expected. I have no problem with developing solutions on my own with the right accommodations and compensation - but stop handing me sprints based on things where the greatest extent of planning is a single sentence fragment of a Jira issue title.
- pdonis 6y ago> I get frustrated when it seems like no one is maintaining requirements (or aware of them) and I'm just expected to make something work, as though I can read minds about what's expected. Yes, another (often frustrating) part of the engineer's job is to try to get the client (or a manager or someone else who is supposed to be communicating the client's requirements to you) to understand what "requirements" actually means and what does and doesn't count as actually specifying a requirement so it can be met, or at least so that a reasonable estimate of the time and resources required can be given. As others in this thread have said, sometimes the only real cure for this problem is to find a new job where you have different, and more reasonable, clients and/or managers.