In a cave with pen and paper is nearly what I learned with. I learned with the run time, msdn, notepad and the cmd line. And yes you do end up in many situations where you simply don’t have or can’t use a full on ide everytime. Sounds like you’ve never really left your comfort zones and stuck your neck out in some tech you don’t understand quite yet. Or worked in areas under strict software controls.
No you can’t if you don’t know the libraries
IDE.
Python is entirely dependent on what libraries you include
??
If you don’t know what you need you can’t do shit.
IDE.
The problems you propose in your comment are not only greatly exaggerated but already been solved for decades using conventional tools AND apply to literally all languages, having nothing at all to do with python. Good try! My statement holds true.
Zexks@lemmy.world 3 weeks ago
theunknownmuncher@lemmy.world 3 weeks ago
It’s telling that you’re focused on personal assumptions instead of addressing the argument
Zexks@lemmy.world 3 weeks ago
What was the argument. Use an IDE which was the proposed answer for most of my objections. Which i did address.
theunknownmuncher@lemmy.world 3 weeks ago
Actually, nope! Claiming that you personally didn’t learn with an IDE and that there are make-believe scenarios where one is not available is not actually addressing the argument. There really aren’t any situations that make any sense at all where an IDE is not available. I’ve worked in literally the most strict and locked down environments in the world, and there is always approved software and tools to use… because duh! Of course there is, silly, work needs to get done.
MagicShel@lemmy.zip 3 weeks ago
It sounds like you are a much better developer than me, but to be fair I’ve had to teach myself everything using nothing but books and Google for thirty years. I’ve rarely had the luxury of working with someone who had the knowledge to mentor me, so I’ve probably missed some critical skills along the way.
In a lot of ways, the AI fills that role because it’s better at answering questions than it is writing code. Earlier today it was explaining to me how a DOM selector could return a stale element in some cases because of a failing end to end test. It took a few back and forths with some code examples before I really understood why the selectors might not be working.
It also suggested some code changes that I had to push back on because, even though the code had errors, the errors weren’t causing the problem. While building an array of promises I had awaited them, causing them to run serially instead of in parallel during Promise.all(). So you definitely have to know what you’re doing to avoid having the AI waste your time (or at least more time than it takes to push back).
I’m still trying to debug it, but without the AI, I’d be googling the fuck out of typescript syntax, JavaScript idiosyncrasies, and a whole testing framework I’ve never seen before.
So…