Based on my experience of AI coding I think this will only work for simple/common tasks, like writing a Python script download a CSV file and convert it to JSON.

As soon as you get anywhere that isn’t all over the internet it starts to bullshit.

But if you’re working in a domain it’s decent at, why not? I found in those cases fixing the AI’s mistakes can be faster than writing it myself. Actually often I find it useful for helping me decide how I want to write code because the AI does something dumb, and I go “no I obviously don’t want it like that”…

deleted by creator

600?? Did you automate it or something?

Definitely the best option.

Yeah that is true. Not all IDEs support that though.

Doesn’t seem that bad to me, but I’m not a junior, or in the US.

TL;DR: Intellisense works best if you write bottom-up (true) and it means you have to remember less stuff (also true), therefore it makes you write worse code (very doubtful).

So I don’t think IntelliSense is helping us become better programmers. The real objective is for us to become faster programmers, which also means that it’s cheapening our labor.

This doesn’t make any sense though.

1. People don’t have unlimited time. Writing high quality code takes time and wasting it remembering or typing stuff that Intellisense can take care of means I have less time for refactoring etc. Also one of the really useful things about Intellisense is that it enables better refactoring tools!

2. It doesn’t make you dumber to use tool assistance. It just means you get less practice in doing the thing that the tool helps you with. Does that matter? Of course not! Does it matter that I can’t remember how to do long division because I always use a calculator? Absolutely not. Similarly it doesn’t matter that I can’t remember off the top of my head which languages use starts_with, HasPrefix, startswith, etc. doesn’t matter at all if Intellisense can easily tell me.

3. You don’t have to use the Intellisense suggestions. Just press escape. It’s very easy.

4. It’s very well known that making something easier to do increases demand for it.

It’s not hard and fast but:

• API is the actual interface for the functions, not the implementation. It’s possible for one API to be implemented by more than one library.
• Library is a bunch of code provided together. It might have more specific meaning depending on the language.
• A package is something you can install. It’s pretty much synonymous to library since most packages contain one library.
• A framework is just a library that dictates a lot about how your app works.

Apart from API they don’t really have strict definitions so they’ll be used interchangeably and differently depending on the language.