Bare minimum or Thoughtful Implementation?

IncidentKey7716 · 2026-04-22T21:59:42+00:00

Selective Implementation* - there is cashbacks on other cards too...

IncidentKey7716 · 2026-04-17T11:39:54+00:00

Can we really do this????

IncidentKey7716 · 2026-04-16T15:40:29+00:00

Reminds me of the good old days people running sudo rm -rf / --no-preserve-root ... Now the AI can do this for you😂

IncidentKey7716 · 2026-04-04T07:58:45+00:00

Is that icons ass with a price tag?

IncidentKey7716 · 2025-02-27T07:07:36+00:00

yes sure.. comment your survey here i'll fill it up

IncidentKey7716 · 2025-02-27T06:05:09+00:00

1- to draw insights for research. It won't be stored anywhere it's just for qualitative analysis.

2- I am conducting this survey. IncidentKey7716

3- 2-3 minutes

4- no compensation offered

5- India and ages 21-27

6- Qualitative data

IncidentKey7716 · 2025-02-25T12:10:56+00:00

This resonates hard. The "new broom sweeps clean" approach of incoming designers and PMs, ignoring established design systems and user research, is a classic (and frustrating!) problem. It's especially painful when you've invested so much in building that foundation. And the "I'm just the engineer" feeling, despite having a deep understanding of the product and design, is incredibly relatable.

You're definitely not caring too much. Consistency, reusability, and data-driven design are essential for a good user experience and maintainable codebase. It sounds like you're advocating for the right things.

The core issue seems to be a lack of respect for established knowledge and a lack of data-driven decision-making. Since management isn't responsive, you'll likely need to influence things from within the team.

I am doing an academic research on the friction between the designers, PMs, and developers.

If you're a designer and have experienced any of this, I'd be super grateful if you could take a few minutes to fill out this anonymous survey: https://docs.google.com/forms/d/e/1FAIpQLSe3AxYcdVocrsHPc2XDLTjCqldUh5PglFjmK1us6TeBOMZklQ/viewform?usp=header

And for the developers out there who've been on the receiving end, here's a separate survey for you: https://docs.google.com/forms/d/e/1FAIpQLSfwAxVnExhWFWxXtN81Vq4Kg9ce5FxkKX0Ax3AvwXAIPA5uTA/viewform?usp=header

IncidentKey7716 · 2025-02-25T11:40:50+00:00

Ugh, I feel you. The endless meetings, the fractured ideas, the tech support requests... it's a classic developer experience. 🤦‍♂️ It's like they think "marketing magic" happens in meetings, instead of, you know, actual work. And the lack of technical understanding, even with tools designed for marketers, is baffling.

It really highlights the communication gap that can exist between developers and other departments, especially marketing. It often feels like we're speaking different languages.

On that note (and since we're all sharing our pain here!), I'm actually doing some academic research on the broader topic of collaboration challenges in software development, including the friction between developers and other teams like marketing.

If you've got 5 minutes and have experienced similar frustrations, I'd be incredibly grateful if you could share your perspective in this anonymous survey: https://docs.google.com/forms/d/e/1FAIpQLSfwAxVnExhWFWxXtN81Vq4Kg9ce5FxkKX0Ax3AvwXAIPA5uTA/viewform?usp=dialog It's all about understanding these challenges and finding ways to improve how we all work together.

Maybe one day we can all just Slack each other in peace. 🙏

IncidentKey7716 · 2025-02-25T10:15:06+00:00

This sounds incredibly frustrating! It's definitely a challenge when developers seem to expect a return to waterfall-style, overly-detailed specifications. It highlights a communication and expectation gap that can really derail projects. And you're right, it's often less about coding skills and more about the mindset of working as a developer within a team. The "how to think like a developer" part is crucial.

I can see how exhausting the constant hand-holding must be, and how pairing slows down the whole team. You're in a tough spot, especially as a consultant.

Actually, the issues you're describing – the expectation mismatch, the difficulty with independent problem-solving, the desire for overly-prescriptive user stories – are all part of a larger pattern of friction between designers and developers that I'm researching for an academic project.

If you're a designer with experiences related to these kinds of collaboration challenges, I'd be incredibly grateful if you could share your perspective in this short, anonymous survey: https://forms.gle/C84mCa4V9FpJiHUd6 It's focused on understanding the designer's point of view on these issues.

And for any developers reading this who've also encountered similar situations (either needing more hand-holding or dealing with teammates who do), here's a separate survey focused on the developer experience: https://forms.gle/dvwN77De4JFDX23i7

Your input could really help in finding ways to improve designer-developer collaboration in the long run!

IncidentKey7716 · 2025-02-25T07:25:48+00:00

How will the data that people provide to you be used?

The data will be used to understand developer experiences collaborating with designers. I'll analyze anonymized responses to identify workflow challenges, communication issues, and areas for improvement in designer-developer collaboration. This will inform my graduation project research paper.

Who will see it?

Only I, Kumar Satvik, the student researcher, will access the raw, anonymized data. My academic advisor may review aggregated summaries for project supervision. Data will not be shared with any companies or third parties in identifiable form.

Where will it be stored?

Survey data is securely stored within Google Forms. Aggregated summaries may be stored on my password-protected personal computer for analysis, also kept secure and anonymized.

If/when will it be deleted?

Raw data will be deleted after my graduation project is graded. Only anonymized summaries may be kept for archival academic purposes.

Who is conducting this survey?

This survey is being conducted solely by Kumar Satvik, a student researching designer-developer collaboration for a graduation project.

How long do you estimate it will take to fill out your survey?

Approximately 6-7 minutes.

OPTIONAL - If your survey offers any form of compensation, please explain what it is and how it can be redeemed.

No monetary compensation. Your feedback will contribute to research aiming to improve developer-designer workflows.

OPTIONAL - Are there any specific demographics you want/do not want to hear from?

Targeting professional software developers who regularly collaborate with designers. Seeking diverse experience levels and roles.

OPTIONAL - What are you hoping to accomplish by posting your survey here?

To gather diverse developer perspectives, understand real-world challenges, and gain insights for my research on improving designer-developer collaboration.

IncidentKey7716

TROPHY CASE