milani
Joined 14 years ago
Joined 14 years ago
The community is moving fast though. Now higgsfield allows using arrows and pointers to edit the video but so far, no one is doing a good camera control visually.
I was scrolling and everything on the hardware looked great (although I was looking for how the tech is different from e-ink, not how better its properties are).
Then I reached "Introducing Sol:OS" and stopped right there. Didn't look further and closed the tab. I'm skeptical when it comes to custom OS. Not a lot of startups can handle a hardware+software company. Hardware is hard enough. Software is second class citizen and doesn't get regular updates after a few years.
I had two options: 1. Learn everything first and then start prototyping. 2. Start prototyping and learn along the way. I chose the latter. But instead of searching stackoverflow and putting the pieces together, I used GPT and learned from the generated outputs in the context of my own problem.
It may not save a lot of time in larger projects because as you said, one should ultimately learn the "what and why", but it definitely provides a more pleasing experience. And I guess the time-saving part becomes more relevant with better tooling, like the suggestion I had.
And that's why it is a "pain point". These all can be done automatically.
In addition to the selected lines, does Continue support getting related definitions from the language server and inject them in the prompt? That would be huge.
The cost aside, I'm wondering how fly or heroku support their customers when they grow to microservices ecosystems.
The problem shifts from deploying easily to deploying reliably meaning one release of a service should not break the other services. Other problems appear too, like service discovery, peer authentication, gateways, test and staging environments where there are downstream dependencies, etc.
Are customers supposed to leave when they grow to this level? Or are there solutions for these?
The difficult part for me is maintaining the docs over time. I can generate 80% of what theneo does automatically in swagger style. The remaining 20% (manual editing, what your platform offers) is the missing part with my current solution, yet I cannot see how theneo solves updating most of the doc and placing back the manual edits.