Careful with that though. The guy whose entire job is to "take requirements from the customers and bring them to the engineers" really does get awful tetchy if the engineers start presuming to fill his role. Ask me how I know.

▲

theK 2 days ago | parent | next [-]

Are you talking about the "engineer talked to a customer and now both are mad at each other" trope?

While I have seen this happening it usually has nothing to do with engineers and more with that fact that talking to customers and identifying requirements is a task that requires respect and practice to become good at. Procentually I've seen more junior MBAs alienate customers than I have engineers seen do it.

▲

kaffekaka 4 days ago | parent | prev | next [-]

Please tell more.

I have the same impression. But that is where it is going - roles merging and being able to do the full spectrum will be valuable.

	▲	bitwize 3 days ago \| parent [-]
		Nothing much to tell. About 10 years ago on another job, I wanted more context in what I was building, so I suggested shadowing a user so I could see what they actually did, what value the software provided, and where the pain points were. A business analyst attached to my team became somewhat upset because she felt that impinged on her job. So there went that idea.

▲

latentsea 4 days ago | parent | prev [-]

How do you know?