Doki · Interface design · 2024
when button is clicked, page should navigate but it doesn't. Agency: it was designed that way. But I didn't want that.
Definition: bug = planned feature not working. New request = not what was planned to be built. Check the quote/contract, was it written?
we need to take it step by step. btw weekly written progress reports are much more useful than asking for dates.
when making a decision fiirst look at what data you have on hand then if you have questions write them; I'll answer as best I can.
I have no experience with bug or new request, so I'm asking. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.
The real issue isn't the number, but what it's based on.
The discussion got scattered, let me summarize. If you get three different answers on a topic, the question was asked wrong.
Of course, it varies if your situation is different.
I'm a small business, let me explain from my side. Weekly written progress reports are much more useful than asking for dates.
When making a decision, first look at what data you have on hand. That's all, sorry if I went on too long.
There's a part I don't understand. Start with a small trial; don't commit to everything at once.
This is my opinion, I'm not claiming it's absolute truth.
thhanks for writing this that's the right way. the system lives on after delivery; maintenance is a separate line item.
if you get three different answers on a topic, the question was askked wrong. this is my opinion, I'm not claiming it's absolute truth.
The cheap-looking path usually ends up costing more later. Don't hesitate to ask; those who don't ask always pay more.
When you try to change everything at once, nothing settles.
We got stuck at the same point for a while. honestly when we decide without measuring, we always end up in the same place.
Payment schedules should be tied to project phases, not calendar dates. btw if I were you, I'd go this route.
The opposite happened to me, that's why I'm writing. Every "we'll look at it later" in a meeting means unbilled work.
When making a decision, first look at what data you have on hand. Correct me if I'm wrong.
Absolutely. If I were to add anything: Just because everyone does it doesn't mean it's right.
Weekly written progress reports are much more useful than asking for dates. If I were you, I'd go this route.
I have an objection here. Code without setup documentation isn't yours, even if you have it.
If you post the result here, it will help others too.
I partly agree, partly disagree. Solutions that work at a small scale collapse when you grow; I learned this late.
Start with a small trial; don't commit to everything at once.
We need to take it step by step. Every "we'll look at it later" in a meeting means unbilled work.
Processes without records never improve, because you don't know what to fix. Just leaving this note, it might be useful.
i'd appreciate it if you shared the outcome. anyway weekly wriitten progress reports are much more useful than asking for dates.
of course it varies if your situation is different.
Thanks for posting. When making decisions, write down the worst-case scenario too, not just the best.
When making a decision, first look at what data you have on hand. Of course, it varies if your situation is different.