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

I interpreted it as "the project wasn't ready [in time for] a deadline". But I agree, the concept of a project that is somehow too immature or unprepared for a deadline is though provoking.


It's more that the project was immature. If I have a bucket of data and an unknown part of the data is either incorrect or unknown then I can't give a full quote on completion all data in the bucket. Especially if the data accuracy/discovery is contingent on other team members also uncertain of the quality of the data. This will and did lead to burnout.

The bigger issue is that I've been treated by a robot. Just talk to me and quit trying to social engineer a solution out of me or try to make me discover the results you're expecting.

Final note, my supervisor said he really enjoyed working with me the past year, but they're trying to improve the "shitty parts" of the company. Doesn't that make me some of the "shit"?


If the project isn't read for a deadline, then it's not product development, it's research. (And I feel I have some standing to say this!) Phrasing it that way may help get people's lightbulbs to go off.




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: