vimrc VS missing-semester

there are several vimrc files: https://github.com/amix/vimrc

Vim with https://github.com/amix/vimrc

If you want my five cents, then I would say that using something like https://github.com/amix/vimrc without fully understanding the consequences, is a bad idea. And instead you should focus on the basics of vim, vimtutor followed by :h user-manual.

text editors for writing files. Recommended: install plugins ultimate vim to make vim more powerful and colorful.

Archcraft's vim uses this vimrc which adds a lot of plugins including some for improving appearance, so it's more suited for a terminal emulator than a tty.

I'm basically using this as a base with some tweaks :)

Or if you want something very minimal, just for easier editing experience when connected to server, try just a simple preconfigured vimrc file, where you can comment and uncomment stuff that you might need. I use amix as base for my own vimrc file.

git clone https://github.com/amix/vimrc.git ~/.vim_runtime

The recommendations in this thread so far do suggest a lot of nice books - CS:APP and SICP - but given your description of previous struggles with more academic stuff, along with the request for "practical examples or projects", I'm not sure they are right for you. By all means take a look, but don't be discouraged if they don't fit what you're after. An algorithm book with a somewhat different tone that you might check out is Skiena's Algorithm Design Manual. I've been reading Ousterhout's A Philosophy of Software Design recently and that might also be something that would interest you.

However, I might suggest that books and theoretical knowledge are not the main things you need right away. I moved into software engineering after a long time in science. I had done plenty of coding, and had a pretty decent amount of theoretical knowledge, but there was still quite a bit of practical adjustment. I really like Rzor's suggestion of https://missing.csail.mit.edu to start with.

Beyond that, I think maybe I would find some specific codebases that you'd like to understand better, and start with reading more of those. I feel like that's often better than books for picking up idiomatic usage and patterns in given domains. As you hit specific barriers, I think it will be much easier to pick up the intrinsic motivation to dip back into theoretical knowledge at that point.

It is more than just that. I used to recommend a lot the MIT's Missing Semester of your CS Education https://missing.csail.mit.edu/ to people that is not familiar with some topics at work.

The missing semester of your cs education

https://missing.csail.mit.edu/

You mentioned having issues with accessory concepts so perhaps this might help: https://missing.csail.mit.edu/. There's also a chapter on git

https://missing.csail.mit.edu/ is a good way to pass the Dec-Jan break if you want to prep for CS2030S + some more general stuff.

Reflecting a little bit more I don't think it was replit's fault, per-say. But that change should have been made together with a larger adjustment to the program. Like adding a class/unit in the style of [the missing semester](https://missing.csail.mit.edu/) to make sure people came away with a good range of intuitions.

From MJD's post: I think CS curricula should have a class that focuses specifically on these issues, on the matter of how do you actually write software?

But they never do.

FWIW, MIT's "The Missing Semester of Your CS Education" attempts to deal with this lack, though, even there, it's an unofficial course taught between terms, during MIT's IAP -- Independent Activities Period[1] -- and not an actual CS course.

[0] https://missing.csail.mit.edu/

[1] https://en.wikipedia.org/wiki/Traditions_and_student_activit...