Ask HN: How do you deal with clients' requests for tasks that are “below” you?
Say you're an experienced mid-career web programmer, and your (good) client has been using a "no-code" solution to cobble together a website. They can't get it to do the thing they want, so they turn to you to figure it out. Do you do it to keep them happy, or politely turn it down?
How do you approach this dilemma, specifically where actual coding rubs up against these services that are no fun for people who write code?
6 comments
[ 4.7 ms ] story [ 23.3 ms ] threadIf you're a wageslave and it's really someone else's client, you have to discuss with your manager.
I don't really identify with the final part of your original post though. I code a lot, but I also use things like Zapier (and heck, Excel) and find them to be interesting domains of their own, even though it's not what I'd want to do full time. If you're a consultant, sometimes a bit of variety and an opportunity to see a customer problem from a different angle is to be savored.
The suggestion in the other comments to take it but (transparently) farm it out longer-term if needed is also a good one. "Not my usual thing, but I'll solve it and help you find someone to take care of it".
Meetings are usually below me, but telling the client that they will be charged for the whole meeting including commute time makes them reconsider or do it remote. I'm always surprised how fast geople decide not to do meetings when there's a bill attached, but they don't consider it when it's full time work that costs the same.