Kodezi - Autocorrect for Programmers
kodezi.com
kodezi.com
"Your code is fully encrypted, never stored, and never leaves your machine."
However it also mentions "Your data is completely secured at rest and in transit with encryption during analyzing and debugging" which leads me to believe they don't know what the prior statement means.
But why encrypt it if it doesn’t leave the machine?
(Also, your code is never stored?)
I'm not sure if Kodezi is any better. But the page as so often doesn't provide me with enough information without having to sign up and try it myself. Wanna know what "Debug bugs" actually looks like? Sure, watch this short styled up video which actually doesn't show anything.
I found some information in the doscs https://docs.kodezi.com/feature-guides/debugging but that's a manual, not a proper feature presentation.
I think that this sort of thing will handicap a dev in the same way that learning to write with a spell checker can (does!) handicap writers.
Treat it as a mildly better autocomplete, and you’ll be happy with it.
Maybe this is far too pedantic, but I do wonder if the community's over-indexing on frameworks to the point that they almost become languages is one of the deeper problems.
It's hard to see how the integration layer adds any long term value. Although this is nicely presented etc. and I don't mean to detract - just the entire class of tool.
I think the paradigm might eventually look like this: - you purchase your token directly from OpenAI - you do an oAuth flow to delegate access to many different wrapper apps (who maybe get a small referrer kickback from OpenAI)
I can certainly see myself subscribing at the source if I could take this token to the many wrapper-apps with trivial/interchangeable commitment.
I don't see myself individually subscribing to wrapper-layer apps.
Don’t do it! And don’t use a spell checker either! Get better and internalise more, you won’t get there with a crutch.
there's nothing wrong with static analysis
Answering some of the questions that was raised.
Our goal with Kodezi is to become a centralized development platform for developers to use regardless of their experience or skill level. We realized early on the amount of autocomplete clones, and our goal from day 1 was to create an autocorrect/Grammarly-like approach to code debugging.
Original Post from 2021: https://news.ycombinator.com/item?id=29635354
In the next couple of months, we plan to release automated code debugging, merging, and automated PRs for Git, along with cloud integrations for Enterprises we are working with and a CLI for Kodezi. As well as a LLM for code debugging at scale.
Kodezi does not store your code; the data from file names we gather for our inference models use encryption.
Kodezi supports and debugs bugs of all nature, functional, syntax, logic, and more. We will have an overview of all types of bugs/errors Kodezi has been trained on to give users a better idea of solving issues.
Kodezi uses large parameter language models trained on a collection of natural and programming languages from various open-source places, along with Open Source LLMs like Bloom and CodeGen. Kodezi has been training data from open-source repositories and StackOverflow data since 2019.
Code productivity and learning have been our goals since day 1; not an auto-completion tool that does not allow new programmers to learn.
Seems like it would make sense to run both at the same time.
Other than that, it might also be useful for the user when either of both operations is not good enough yet and error propagation might be worse than human correction between the two.
Or if anyone has inside info on when that might come out of beta or a comparable alternative.
I wonder if it's actually possible to fine tune text-davinci-003 to be better at programming.
https://marketplace.visualstudio.com/items?itemName=GitHub.c...
The only people who get rich during a gold rush are the people that are selling the shovels. I think that people are tired of rewarding shovel sellers.
* There are hundreds of millions of people living for under $2/day. Coding was a pathway out of poverty.
* There are billions of people with family incomes under $30/day. For those families, kids learning to code was a pathway to wealth.
If tools to be productive cost money, it will go the same way as other domains of engineering, where you can't be productive without a significant investment.
EDA tools to design electronics run $5k-$100k, and making an IC might have NREs of $100k. That places it squarely out-of-line as a career option for many.
At one point in time, computers were limited to very wealthy folks, like Bill Gates. He learned to program by going to an exclusive private high school which had a computer, and later, in Harvard. He had a unique competitive advantage which allowed him to start Microsoft.
A better parable is GNU/Linux/BSD/etc. versus Unix/VAX/etc. Unix cost thousands of dollars. The free alternatives were free. This allowed a whole generation of kids to learn, who didn't have Gates' resources.
I wasn't in a private high school, and without Debian, I wouldn't have the life I have.