Remix.run Logo
mauvehaus 4 days ago

As a working furnituremaker, it depends on the client's budget. I try to get a sense of budget early in the design process so that I can both provide the best bang for the buck for the client and also a uniform level of quality throughout the piece. If push comes to shove, though, I'm not going to turn a job down because there isn't budget for a frame and panel back. I'm not going to turn someone's work away because they can't afford a higher-end option that nobody will ever see. That's not how to treat people with dignity.

In a couple instances, I've turned down work because the budget and expectations were wildly incompatible, but that's as simple as saying "I can't do the work you're looking for at that price." I'll offer suggestions for a more cost-effective alternative if I can. In one instance, that's turned into work down the line when the client came back with a different project with a budget more in alignment with their goals.

Lastly, while everything Nancy Hiller (RIP) has ever written is worth reading, these two pieces are highly relevant to the question of standards, budgets, and delivering the whole project.

https://www.finewoodworking.com/2019/09/11/dont-knock-the-la...

https://www.popularwoodworking.com/editors-blog/lets-make-ev...

wslh 4 days ago | parent [-]

The same applies to software: it's common to criticize someone's work without knowing the context or the story behind the system. The typical triangle dilemma is budget, time, and quality.

acomjean 4 days ago | parent | next [-]

I’m add to existing legacy Code. I can’t be judgy most of the time. Sometime I can suss out the first build then the additional features tacked on at later dates which is where things get messy.

I’m at the fourth update and I did a little clean up. I didn’t tear it and start from zero, but I cleaned it up so future me will be happier when the next change comes (and we now know they keep wanting updates to this)

The original way worked and was clean and I just assume that the next updates were done under some time constraints. A lot of code here just keeps working for years with no updates so it made sense to do it faster with less flexibility. Not everything needs to be great when more good enough functionality is more useful.

bravetraveler 4 days ago | parent | prev | next [-]

If it's supported, by who

sanjit 4 days ago | parent | prev [-]

Yes! And design, too…