HN user

nosvince

14 karma
Posts3
Comments11
View on HN

Not op, but my answer to this would be years of practice and skills. Someone might have an amazing idea, but might have trouble putting their vision on paper. ChatGPT and generative art helps "idea people" concretize their vision more easily. The promise of generative AI is exactly this in my opinion; giving the ability to anyone to simply wish an idea into a concrete "thing"

See others' advice on seeking professional help.

In my opinion, don't put too much effort into schooling if you want to code. Learn and build. Join a startup if you want to learn to touch a bit of everything, or build your own project if you want to learn to fail and still progress.

Also, what I can say from my experience, is that people that I know that felt lost and depressed around your age are the most interesting people I know today. They're still lost, in the sense that they haven't figured out what they want to be when they grow up (even though they're 40+). They just learned to use and channel their energy and creativity and turn it into positive for them and those around them.

Can someone ask why does it needs to cater to AA and AAA studios?

Unreal is already great for this, with Unity trying it's best to get there. We need an engine focused on the problems of smaller developers, especially on mobile. Defold is another open source engine that seems focused on this, which makes more sense to me.

Wow, that's a horrible way of thinking about the user experience. And honestly, I'm not surprised. That's why companies that really care about the user experience will always steal market share from those that don't.

And that's why there's room for automation to take a lot of the complexity away.

Granted it's not going to be easy to have a platform where every tool can seamlessly connect, but we can start with baby steps such as services that automate multi-cloud deployments like the article suggests.

I don't think the point of the article was to say technically how to automate everything. But rather that the tools to automate are coming and that we should be on the lookout and ready when they come.

I think you're mixing theory with practice; DevOps should not be a role, but it often is...

As for requiring another specialist role, that's not the goal of building an automated system. Or at least, this specialist will not part of the team that's building the product, but rather of the company that's building this automated platform. If you can automate the orchestration and management of Kubernetes or serverless, then developers just need to know how to build a container or upload code on a serverless platform.

Things like this are definitely a very welcome change but running a production workload on Kubernetes is still no where near a hands off exercise, even with the cluster creation and scaling aspect abstracted away. There's still learning, using and applying Kubernetes.

I think that's what this article alludes to. You won't need to manage Kubernetes with an automated container orchestration platform that just needs your container or cluster. If an automated system can take care of the management, then the "cloud management" part of DevOps is greatly reduced.