codebytrial

3 ms·

1. 1.▲
   by codebytrial 1y ago

   Totally get where you're coming from—I've been in those same situations where the spec looks solid until you start building and realize half of it is missing or misunderstood. It’s frustrating, and I appreciate you sharing your ex
2. 2.▲
   by codebytrial 1y ago

   Thanks, that’s a fair point. To be more specific: I’m a senior full-stack developer with strong experience in React, React Native, Node.js, and TypeScript. I've also worked with Python for AI/ML integrations and backend scripting.
3. 3.▲
   by codebytrial 1y ago

   That’s a great point — if someone only offers free work without clear signals of fit, it probably won’t help. I see this less as a value flex, and more as a trust accelerant — especially in cases where the work is exploratory, multi-layered
4. 4.▲
   by codebytrial 1y ago

   That’s a fair and valuable perspective — and I agree: in most cases, devs shouldn’t work for free, especially when the company holds all the leverage. I probably should’ve framed it better: this isn’t meant to say “my time has no value.” It
5. 5.▲
   by codebytrial 1y ago

   I should clarify — this isn't meant to undercut developer rates or normalize free work. It’s more of a signal: “I'm confident enough to put in a real day’s work before asking for anything in return.” I’ve had great feedback on my
6. 6.▲
   Ask HN: Would you hire a dev who offers 1 day of work up front, no commitment?

   7 points by codebytrial 1y ago|11 comments