|
|
|
|
|
by aristofun
331 days ago
|
|
Modern web design is better commoditized than software development. For example, you need to paint typical pictures for every new blog post, press release etc. But you're expected to build a blogging software only once, and any fixes/bugs are unexpected in scope and complexity. Unless you take advantage of your customer (nobody else can fix that complex system that you left him with) - it doesn't look sustainable to me. |
|
There are instances where the customer already know what he wants, could be typical maintenance, bug fixing, etc... those things can be added to a task queue, details are agreed and work is performed, without preparing quotes every time for each task
For example, I would only use something like this if I can automate as much as possible using CI/CD, etc