Doki · Interface design · 2026
they showed the mockup, i approved it. after the code was written, colors remained light, button positions shifted. It deviates from the mockup.
Mockups should define color codes and dimensions. If not written, deviation can be considered normal. These should be written in the contract: hex color, pixel size, animation timing.
This approach has a cost, which isn't discussed. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.
Most time waste accumulates in tasks waiting for approval. I'm also curious if anyone does it differently.
there's a common mistake people make when doing this. access credentials should be oepned in the company's name, not personal accounts.
if you get thre different answers on a topic, the question was asked wrong... honestly if you have questions, write them; I'll answer as best I can.
My question might sound amateurish, sorry about that. Every "we'll look at it later" in a meeting means unbilled work.
Quick summary for newcomers: The answer varies greatly by industry; there is no one-size-fits-all rule.
Proven by experience.
This thread is archived. The real issue isn't the number, but what it's based on.
The harder it is to reverse a decision, the slower you should make it. I'm also curious if anyone does it differently.
You're right. The answer varies greatly by industry; there is no one-size-fits-all rule.
If I were you, I'd go this route.
Doki · Penetration test · 2024
How did you solve this? If it's your first time, start small; scaling comes later.
I'm also curious if anyone does it differently.
Following. tbh in legacy systems the most expensive thing is unknown dependencies.
People defend habits, not processes. like resistance comes from there. Good luck with that.
Let me speak from the other side; Im on the supplier side. The real issue isnt the number, but what its based on.
Doki · Phishing awareness training · 2024
Exactly, and not many people know this. When making a decision, first look at what data you have on hand.
That's all, sorry if I went on too long.
We got stuck at the same point for a while. If you don't write this down from the start, it leads to arguments later.
If I were you, I'd go this route.
I disagree with you on this point. When you try to change everything at once, nothing settles.
Correct me if I'm wrong.
I think differently. If acceptance criteria aren't written when the work is done is open to debate.
In legacy systems the most expensive thing is unknown dependencies.
The opposite happened to me, that's why I'm writing. Don't hesitate to ask; those who don't ask always pay more.
Hasty decisions become decisions you have to fix six months later. I'm also curious if anyone does it differently.