Live data from Hacker News

Google Colab will soon introduce AI coding features

blog.google

91–100 of 165 posts

Re: Google Colab will soon introduce AI coding features

#91
post #49

I find VS-code running notebooks with Colab plugin installed pretty helpful for this type of thing already. (1) run notebook in VS-code https://code.visualstudio.com/docs/datascience/jupyter-noteb... (2) install Github Copilot extension https://marketplace.visualstudio.com/items?itemName=GitHub.c... and then it can quite often achieve what you want with just a comment or some previous code snippets. Then if you load…

Hint: VS Code Jupyter even allows connecting to remote kernels, so you can access some remote GPU from within the editor.

I think Colab doesn't support this, but Paperspace Gradient for example does.

https://docs.paperspace.com/gradient/notebooks/notebooks-rem...

Re: Google Colab will soon introduce AI coding features

#92

Earlier quoted context omitted.

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…

10-15 years out AI will be good enough to wipe out at least half of all software developers on the planet (that is, people writing actual code). That's not a risky prediction, that's very easily going to be the case. Those people have nowhere to go to match what they're earning now. Maybe support review roles (which won't pay particularly well), where they approve decisions by the AI that are held up for human approv…

[dead]

Re: Google Colab will soon introduce AI coding features

#93
post #81
post #65

Earlier quoted context omitted.

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

The problem for users (not google) is that its an arbitrarily enforced restriction. Of course companies can do whatever they want. Google could ban all programs that import PyTorch on their free tier, too. Totally their choice. It’s also my choice to mention that people should look into alternatives like Replit if they’re worried about a cool notebook they made on Colab randomly getting them in Google TOS trouble.

Does Replit give free access to GPUs for any use case? The documentation[0] has screenshots that imply that GPUs cost "cycles", which are a virtual currency you buy with real money[1].

[0] https://docs.replit.com/power-ups/gpus

[1] https://docs.replit.com/cycles/about-cycles

Re: Google Colab will soon introduce AI coding features

#94
> "soon introduce"

This looks like an announcement of an announcement, which isn't on topic for HN. https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor...

On HN, there's no harm in waiting for the actual thing: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so...

Re: Google Colab will soon introduce AI coding features

#95
post #88

Earlier quoted context omitted.

Someone non-technical can do the requirements gathering.

I have to strongly disagree with this. If someone non-technical does the requirements gathering, the requirements will be incomplete. Developers will then either assume their own requirements or, if they’re thorough and good at their job, check these assumptions with the business. Either way, this wastes the company’s time. Either the assumed requirements will require re-work or the company has paid two employees to…

It will be a technical person, and they will be payed $65k a year to do it.

Re: Google Colab will soon introduce AI coding features

#96

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…

"paid huge money to literally write if/else"

"most programmers are in denial about how complex the code they’re writing actually is"

I can taste the salt

Re: Google Colab will soon introduce AI coding features

#97
post #88

Earlier quoted context omitted.

Someone non-technical can do the requirements gathering.

I have to strongly disagree with this. If someone non-technical does the requirements gathering, the requirements will be incomplete. Developers will then either assume their own requirements or, if they’re thorough and good at their job, check these assumptions with the business. Either way, this wastes the company’s time. Either the assumed requirements will require re-work or the company has paid two employees to…

The requirements are in the plain english doc

Re: Google Colab will soon introduce AI coding features

#99

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"

It could be posted under anything. I could claim that the earth is going to turn into a ball of cheese and then write off everyone with “only time will tell.”

Re: Google Colab will soon introduce AI coding features

#100

Earlier quoted context omitted.

10-15 years out AI will be good enough to wipe out at least half of all software developers on the planet (that is, people writing actual code). That's not a risky prediction, that's very easily going to be the case. Those people have nowhere to go to match what they're earning now. Maybe support review roles (which won't pay particularly well), where they approve decisions by the AI that are held up for human approv…

Isn't that the nature of tech? In the past most programmers needed to focus on low level details while today most devs kit together libraries and services and yet there are more then ever and salaries are higher then ever. I think nobody that enters tech expects that in 20 years we "code" as we do today but we will still build stuff and need to solve problems... and there are enough problems to solve.

That's pretty much the case. We keep building layers and abstracting away.

Being a prompt wizard won't pay as well as directly writing code for the AI systems. They're different layers. There won't be more people directly developing software than there are today in the US market, there may be more overall jobs in and around the process however (ie the tech industry will continue to expand to more people in terms of employment; benefits will weaken, median pay will fall).

Most software developers will be prompt wizards, with required degrees that say they know how to be effective prompt wizards. Then there will be a lot of supporting roles, oversight roles.

More jobs in the industry, lower skill levels, less pay.

Post reply on HN