Is this another "beta" feature? It says it's available today, but I don't see it. Source: currently a Colab pro subscriber based in the U.S., but don't see the AI features in my Colab notebook
Google Colab will soon introduce AI coding features
31–40 of 165 posts
Re: Google Colab will soon introduce AI coding features
#32Earlier quoted context omitted.
That's what they thought 50 years ago. Programming is not anymore "mov eax,1" and "int 0x80". Programming nowadays is much more highly accessible than it was 50 years ago... but still only a few (programmers) do it. AI is not going to change that (i.e., nor my manager nor my mother are suddendly going to "program" anything using high-level constructs)
You may be right, you may be wrong. Only time will tell (and I think it will tell really really soon).
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"
Re: Google Colab will soon introduce AI coding features
#33Earlier quoted context omitted.
I disagree with this as well. The number of people legitimately working on LLMs right now is probably only in the hundreds. One or a few huge models will do all the programming automation. But yes, high paying developer jobs will exist. The rest will not pay as well, and with much worse job security. This field is going to change very fast
> This field is going to change very fast It will be slowed by bureaucracy. Example: To be SOC 2 compliant, you need to have change management controls in place. How do humans manage change management if an AI is doing everything for the humans? Would humans still be doing code reviews? (AI might be so great where code reviews are obsolete, but compliance / regulations may still require humans in the loop) There's al…
Re: Google Colab will soon introduce AI coding features
#34Earlier quoted context omitted.
Are you kidding? Google's main product is waiting lists.
There's Google Wait, Wait+, GWait, Hangwait, Wate, Wait4it, Google Weight List, Alphawait, and last but not least GWait Hangwait. Am I missing any?
Re: Google Colab will soon introduce AI coding features
#35I 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…
Re: Google Colab will soon introduce AI coding features
#36I'm tired of Google announcing something in the future; wake me up when it's actually out.
we debated this; this is going to be a sequential rollout based on availability/capacity, and it seemed better to broadcast it was coming earlier b/c we're not going to have a "launch event" moment.
Re: Google Colab will soon introduce AI coding features
#37Re: Google Colab will soon introduce AI coding features
#38I 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…
Here's a different 10-year prediction. AI will become good enough to be useful for programmers but not good enough to run on its own and will remain an assistant. Given that there is a shortage of programmers, more software will be written than ever. More software will beget more software engineers. Because the output of software engineers will rise, each individual software engineer will become more valuable to thei…
Re: Google Colab will soon introduce AI coding features
#39I'm tired of Google announcing something in the future; wake me up when it's actually out.
we debated this; this is going to be a sequential rollout based on availability/capacity, and it seemed better to broadcast it was coming earlier b/c we're not going to have a "launch event" moment.