[worik]

Not a good idea. That is not a good idea of you let anybody in a management role see your prototype.

It will be the product. They will start selling it straight away. If there are any problems, you, my dear young and foolish friend, will be the one at fault. It is your wonderful self that will staying up all hours desperately trying to fix the problems.

Otherwise peachy!

[atomicity]

I do not understand how you cannot easily "spin" a prototype that the company wants to sell into a good thing.

When you write that awesome prototype, your management will be thinking about rewarding you, not blaming you. They will listen to your concerns.

So, you can say that it's not ready. You can mention that you alone are not enough to fix the bugs that come up in greenfield code right away. You can even ask for people to help on your project. Why would management say no if they want to sell it?

Then when a manageable amount of bugs come down the road and everybody is happy, you are now in a far better position to negotiate a higher salary. You have far more responsibility. You have a great track record. Nobody wants you to leave.

The cost of developing a prototype when you handle every error you see along the way, set up all of those dev tools (tests, logs, CI, formatting, etc.), and test every branch like a madman is too high. You'll probably end up taking weeks to develop something that you could "code in a weekend". Then, since you never verified, it may turn out that nobody wants to use the prototype for obvious reasons

[worik]

Spin? My leaky, fragile, missing important parts, flaky prototype has been sold for a lot of money and is now supporting business decisions.... Spin? Like tail spin....

When the prototype explodes in exactly the way I expect it to management are not going to reward me...

I said it is not ready. Several times. To the point where management stopped taking my calls.....

Manageable amount of bugs? There is a problem of definition here.

The cost of developing a prototype that demonstrates the interesting and cool parts of the project - whilst leaving the tricky bits for implementation is my job. So I gota ask: that cost is too high for whom?

It has been fun....

[m463]

> hat is not a good idea of you let anybody in a management role see your prototype.

That also goes for your REAL goals or technical debt or other list of minor-todos you've created. They will meddle. They can't help it. Only give status/etc for clear goals.

Kind of like the driving test. Of course you don't break the speed limit pass the person weaving in the lane ahead of you. (but irl you do, and you should)

[User23]

One of my interns thanked me several years later for what he said was the best advice he ever got from a mentor: learn to recognize when a project is about to collapse under its own weight and get out before it does.