LLMs estimating time is HIGHLY inaccurate. When implementing complex features, LLMs provide me sometimes with estimations of weeks/months and it's done in 2 hours max. So I would not recommend this as an argument for cost-basis of features.
You are viewing a single comment's thread from:
Let me lay it out as clearly as possible. I know how much time I spent building this project... and I know Mark got 0, and I made roughly 1/3rd of the budget while we wrote or rewrote nearly every line of code here.
Go ahead and try and justify what Starkerz spent of the DHF funds any way you like.
I'm not here to justify anything. It's unfortunate that you're in this situation, and I can sympathize with how you feel, you obviously invested a lot of time and opportunity costs - I can relate there. I stumbled upon the comment by chance and wanted to share a neutral point of view: arguing with a work/time-analysis based on an LLM won't give you an accurate range. Nothing more, nothing less. I genuinely wish the best for you and the project.