Live data from Hacker News

Google Colab will soon introduce AI coding features

blog.google

61–70 of 165 posts

Re: Google Colab will soon introduce AI coding features

#61

Earlier quoted context omitted.

You may be right, you may be wrong. Only time will tell (and I think it will tell really really soon).

I find that this comment adds absolutely nothing to the conversation. It could be posted under every comment that says "AI is (not)? going to revolutionize (the world|everything|this industry|my job)" Anybody making a prediction about the future might be right or might be wrong, and we won't know until it happens. This is just a snarky way of saying "nah dude you're wrong"

No, they also said they think we'll find out "really really soon", which seems highly likely.

Re: Google Colab will soon introduce AI coding features

#63

I really think the current paradigm of literally typing if else logic all day into programs, and then getting paid huge money to do so will go away. Programming is going to be much higher level and accessible, though still complex. It will take five years or so. Edit: My prediction is essentially that: You give it a set of requirements for an api, with edge conditions written in plain English. Test cases are provided…

Since people are bad at describing what they want there will be some kind of person that deals with the business and makes the computer work.

Already we have prompt engineering. And also we could have said the same thing for people who write in assembly language, and each higher level language and also programs that are designed to be low code . I see that this is a new type of spreadsheet but scaling these up or using these programs aren’t going to make coders / software engineers / data scientists go away in fact historically we have seen the opposite.

Re: Google Colab will soon introduce AI coding features

#64

I really think the current paradigm of literally typing if else logic all day into programs, and then getting paid huge money to do so will go away. Programming is going to be much higher level and accessible, though still complex. It will take five years or so. Edit: My prediction is essentially that: You give it a set of requirements for an api, with edge conditions written in plain English. Test cases are provided…

A possibility, and I think the way we work will evolve as well. But coming from a more "numerical" background, I can imagine a different route. Twenty years or longer ago, people who wanted to process a larger amount of data needed to understand low-level details, compilers, C/C++/Fortran, mathematical details, and so on. Today, we have JAX, scikit-learn, and many more tools. But these tools did not make the old 'numerical' people jobless; instead, their jobs evolved. Today, we have more data scientists than ever. You can create your own app faster than years ago, including hosting, persistent storage, load balancing, ... And again, we have more web developers than ever. The same goes for jobs like DevOps and other jobs that I probably don't even know. The level of abstraction got higher as you better now what the algorithm is doing but you do not need to implement it again. The point is the field will evolve, and right now, it may be the biggest jump ever, but that does not mean jobs will go away. We might end up in a situation like self-driving, where we are really close but still missing the last bit and need human intervention. I hope LLMs will solve the tasks that have been solved many times before, like bootstrapping a CRUD app, and we can focus on the edge cases and niche problems.

Re: Google Colab will soon introduce AI coding features

#65
post #62

Free of charge, unless they don’t like what sort of programs you run! Google bans certain open source AI models in Colab, like Pygmalion. See https://colab.research.google.com/github/PygmalionAI/gradio-...

What's the problem here? They get to choose how they offer their free service?

Re: Google Colab will soon introduce AI coding features

#66

I really think the current paradigm of literally typing if else logic all day into programs, and then getting paid huge money to do so will go away. Programming is going to be much higher level and accessible, though still complex. It will take five years or so. Edit: My prediction is essentially that: You give it a set of requirements for an api, with edge conditions written in plain English. Test cases are provided…

Who will write in plain English? Granted I'm not in software development, but work in an adjacent area. Communicating requirements is already a hard, unsolved problem.

In an adjacent discussion about ChatGPT, we will look forward to when nobody learns to write in plain English any more.

Re: Google Colab will soon introduce AI coding features

#67

(Shamelessly spreading the word about my open source tool) You can do GPT-4 powered coding chats in your terminal today with aider. It's not free in the sense that you need a gpt-4 api key, which openai charges you for. But it's a pretty great way to collaborate with AI on code. https://github.com/paul-gauthier/aider

This looks great, thanks for sharing. Esp interested in:

> Complex Multi-file Change with Debugging: A complex code change involving multiple source files and debugging.[0]

[0] https://aider.chat/examples/complex-change.html

Re: Google Colab will soon introduce AI coding features

#68

I really think the current paradigm of literally typing if else logic all day into programs, and then getting paid huge money to do so will go away. Programming is going to be much higher level and accessible, though still complex. It will take five years or so. Edit: My prediction is essentially that: You give it a set of requirements for an api, with edge conditions written in plain English. Test cases are provided…

> You give it a set of requirements for an api, with edge conditions written in plain English. Test cases are provided. And the vanilla api is generated. Sometimes I wonder where some of the posters here work or if I'm working in a dystopia. > You give it a set of requirements for an api with edge conditions written in plain English This part is the job! If my job was 100% writing logic, it would be infinitely easier…

Someone non-technical can do the requirements gathering.
Post reply on HN