I think that software engineering is about two things: building things the right way and building the right things . The second one is more important than the first one. If you don't build the right product, it doesn't matter how well it scales or how it has amazing test coverage or wonderful documentation. To that end, I think that too many managers (and companies) do too much shielding of engineers from customers.…
You are given a figma that wasn't already researched and validated against requirements? If it takes a week for a team to fiddle around with a design asset only to learn customers/clients would be fine with a simpler approach, everyone failed the assignment. This was intended as a rhetorical question... I know many teams let designers waste tons of time in a vacuum and PMs are off in lalaland focused on the wrong act…
Reading this kinda threw me into a loop. Yes, jr and regulars are usually not able to do things generally attributed to senior developers.
Expecting someone that neither knows the implementation nor the language in-depth to be able to do that is kinda monkas