One thing I've noticed with software projects is that getting a prototype working is often the easy part. The difficult decisions tend to appear later: architecture, testing, monitoring, security, deployment, technical debt, and making sure the system can handle real users.

I'm curious how other developers here approach that transition. At what point do you start treating a project as “production software” rather than an experiment?

For example, do you prioritize observability and automated testing early, or wait until the product has proven demand? And how much architecture do you consider necessary before the first version goes live?

I've been looking at how teams such as Software Developers Pro approach this problem, and their emphasis on production engineering rather than stopping at the prototype stage got me thinking about it.

For developers who have taken projects from prototype to production, what was the biggest issue you didn't anticipate?

Salem commented: AI slop to name-drop some provider -4

Recommended Answers

All 2 Replies

I find that the people who PAY for the work set the pace and what else you are asking about.

When I wrote apps freelance I would write the proposal and work would begin and stop with the payments.

Right or wrong, when the program ended, so were my thoughts about difficult decisions. It was no longer my problem.

Yes, some will not like that view but a contract is a contract.

Since this post is clearly spam to get their target phrase count up, I'll not expect a response from the author.

But, the example given is based on the premise that the prototype later becomes the production system. This goes against what I would consider good practice.

The PoC can, and arguably should, be hacked together in whatever way proves the concept at the earliest opportunity. Once proven and the decision is made to implement it for real, then everything learned from the PoC is put into creating the real thing from scratch. The original PoC itself is put in the bin.

So, to answer the question directly: The prototype never becomes production.

commented: Quite right +17
commented: We've all seen "Temporary becomes permanent." Proof Of Concept that barely works is fine but as we all know, that becomes the production item. +16
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.