I’d use an ide from day 1 instead of wasting time with vim. I seriously dramatically slowed down my advancement as a programmer because I didn’t use a full featured ide straight up. Now I only use vi to edit files in /etc
What I would do differently if I was learning to program again
11–20 of 85 posts
Re: What I would do differently if I was learning to program again
#12Looking back at it, I regret not investing in quality books rather than some online subscription.
Re: What I would do differently if I was learning to program again
#13Earlier quoted context omitted.
I'd use Vim from day 1, instead of wasting time with several IDEs.
Why would anyone not want the power of an ide? Is it a Unix tough guy thing where there’s nothing that a GUI app does that you can’t do better in a terminal? Or is it that you’ve never really spent a lot of time in a professional ide so when you argue against it, it’s cause you don’t know?
Re: What I would do differently if I was learning to program again
#14I don't code anymore (I'm more of a pointy-haired lower boss)...but what i wish i could go back in time and change around this is to have focused - I mean really, really focused - on 2 or 3 different programming languages only. Instead, what I've done over the years - again, when I coded as a dayjob - was to go shallow on far too many different languages (and ecosystems). I don't think it was me just chasing the "new…
Why do you think that would an appropriate moment to do so ?
Re: What I would do differently if I was learning to program again
#15I was able to come up with realistic own projects only after learning in sort of similar way - through structured organizations and from friends advice. Not everyone has friend advice. And having actual task someone will check adds motivation to finish it - finishing those own assigned projects that you are pretty positive are no useful to anyone is demotivating.
Re: What I would do differently if I was learning to program again
#16Earlier quoted context omitted.
It's been a long time I haven't used Vim. I left it in favor of Evil+Emacs a few years ago. And I don't recommend it to every single person I see. The phrase "wasting time with Vim" was the thing that made me reply the way I did. Learning Vim properly has helped me every single step of my way.
So you don’t use vim as a programming environment/editor? So not actually disagreeing with me, just stirring?
Re: What I would do differently if I was learning to program again
#17Earlier quoted context omitted.
I'd use Vim from day 1, instead of wasting time with several IDEs.
Why would anyone not want the power of an ide? Is it a Unix tough guy thing where there’s nothing that a GUI app does that you can’t do better in a terminal? Or is it that you’ve never really spent a lot of time in a professional ide so when you argue against it, it’s cause you don’t know?
Re: What I would do differently if I was learning to program again
#18I don't code anymore (I'm more of a pointy-haired lower boss)...but what i wish i could go back in time and change around this is to have focused - I mean really, really focused - on 2 or 3 different programming languages only. Instead, what I've done over the years - again, when I coded as a dayjob - was to go shallow on far too many different languages (and ecosystems). I don't think it was me just chasing the "new…
> ...either before graduating college, or right after, etc. - work for yourself and not The Man... Why do you think that would an appropriate moment to do so ?
Re: What I would do differently if I was learning to program again
#19Earlier quoted context omitted.
I'd use Vim from day 1, instead of wasting time with several IDEs.
Why would anyone not want the power of an ide? Is it a Unix tough guy thing where there’s nothing that a GUI app does that you can’t do better in a terminal? Or is it that you’ve never really spent a lot of time in a professional ide so when you argue against it, it’s cause you don’t know?
I learned Python much better because I did not use an IDE.
I've written Java and C# using IDEs. I barely remember anything about their standard libraries. Python, in comparison, I know like the back of my hand. Thanks to writing Python in vim, I had to reference the docs, and eventually memorized them. Like vim itself, it made for a steeper learning curve, but the productivity gains in the decade after have been well worth it. I've since done the same thing with Go.
And that's not even mentioning that vim is an IDE - it's an extensible C IDE. Building with go-to-line errors? Yup. View definition? Yup. Syntax highlighting? Yup. The only thing it's missing is having the debugger built into it.
In the end, vim has the best features of an IDE without the bloat. It makes you use your brain when writing new code while giving you the ability to navigate your existing code with ease.
Re: What I would do differently if I was learning to program again
#20Of course, that's not of much use for anyone else. In fact, I'd recommend getting operations experience to more programmers, if only because we always need more people. But I also understand why more people don't aim to get operations experience.