Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If your work isn't professional, high-stakes stuff for a client, perhaps you can take some sting out of the hard finishing part by heavily and prominently disclaiming your work, and writing down the things you haven't done.

Is the purpose really to release polished products? Or to learn and try something new and share it?

By stating the purpose you can make those disclaimers more relatable and reasonable and set your users expectations.

Also know that starting, exploring and learning are brilliant useful skills by themselves.

Finishing is another skill, and if you want to be good at it I think it's useful if you can take some pressure out of it, start with low expectations and then with practice you get better, like all things.

Also, you can't expect yourself to finish all things because its time consuming like all the steps.

Example and shameful plug: models I release here that are plastered with disclaimers, but this is what lets me share something and move on.

https://observablehq.com/@declann/pension-calculator-ireland...



Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: