[zomglings]

"When I am coding I’m focused on just one thing: delivering value to my users as fast as possible."

Sorry, this rubbed me the wrong way. This is almost a non-statement. It sounded condescending, but that may just be me misunderstanding your tone.

The trick is in how you define that value and how you deliver it quickly. You will probably get a lot more mileage out of building an understanding of what your users need than out of having a "blazing fast inner-loop".

Your users are developers and I'm not convinced you understand what we need. You don't talk about how we can handle service dependencies - How to keep a development database up-to-date and useful for each developer? Should there be one dev database per namespace or a single dev database that the whole team uses? How should third-party APIs be integrated into the development environment? And on and on.

Just running `kubectl create namespace` and rsyncing my code directory into a dev container in that namespace (?) doesn't even get me even close to a proper dev environment. It doesn't solve any REAL problems I have setting up a Cloud Native dev environment.

[pchico83]

Those are really good questions, we have similar requests from our users. We don't have general answers yet, but let me explain a few solutions we have in place. Data: data is hard. There are teams that workout the problem with fixtures and a database per developer. We also have a PoC for cloning namespaces and its data using Velero (this way, you can clone staging on your own developer namespace). We also have teams that have a dev database for all the frontend developers... Service dependencies: we push to define your dependencies using one or more Helm charts. This way, developers have a one-click experience to deploy the full stack on their namespaces. Once the app is running, developers use the Okteto CLI to put on dev mode any service and start synching their local code changes. Some parts of the stack might be shared by all the developers in a common namespace. Third-party APIs: this is also a wide spectrum, but our experience says it is easier to integrate them at the cluster level that in every developer workstation.

[zndr]

Agreed, this is a topic on my mind, we have a need for better cloud based dev environments so this article's titled appealed to me, but it wasn't answering any questions or aligning with common issues.

[pchico83]

We would love to talk more about the issues you have. If you want to schedule a call just drop us an email.

[zndr]

Well first off, we don't touch Kubernetes, so probably not a product we're looking at either way.

[freepor]

Iteration speed is sometimes an effective substitute for deep product insight. If you are a Steve Jobs you can go off and spend a few years building something in secret because you know people are going to love it when you show it to them. For everyone else, being able to ship stuff quickly offers a chance to maximize the number of spaghetti strands they can throw at the wall until they find one that sticks.