/tech/ - Technology★

>>928992 (OP)

>good comprehensive resource on all this sort of stuff out there

No, and that would be too hard to maintain. You learn things as the demand for them arises. If you set your own challenges, you'll know when you need SSH because at some point you're going to want to remotely control a server. Starting out with the goal of "I want to know everything" is completely wrong. What do you want to accomplish right now? Once you can answer that, right down what you'd need to know, and chase down all the dependencies.

I'm sure there are academic courses out there which help organize some of the knowledge you're going to need in the real world, but in my opinion it's far more efficient to learn on demand, as you need it. That doesn't just mean reading a wikipedia page either, if for instance you want to really understand image processing algorithms, you'll first have to devote a significant amount of time to learning the requisite mathematics.

Sage because OP, really how do you even get through life expecting everything to be laid out for you? Computing skills are no different than any other. If you wanted to become an arborist, it's not like you can buy one book on trees and then suddenly become a master.

>>928995

*write down.

>>928995

Alright, when you learn stuff on demand do you just do a web search or are there resources you prefer over others?

>>929011

(different anon)

Depends (<-- that's the answer to fucking everything)

I usually start with a web search, but some topics are well-documented so their own manual page or site's guide is often good. These options are usually quick and effective for things like common software/OSs or common programming languages.

If it's an question with an answer you can't find, asking in an appropriate subreddit and/or /g/ \ /tech/ question threads are the way to go. If it's a niche enough topic, you might even have to ask the creators but I've never had to do that.

It just comes with experience, really.

>>929016

Alright I'll just keep at it then, it seems the best way to learn will be to get out of my comfort zone and put myself in situations where I need to know how to do something that I know nothing about.

Gonna sage my own shitty thread now, sorry

>>928995

Bump because you're a faggot

You can probably find some good information from books.

Personally, I just pick up tricks and knowledge stuff as I go along rather than gaining it from books.

>>929011

For languages I prefer books, either by the author of the language, or someone highly involved in its creation.

>>928992 (OP)

Learn it by doing it. It's so fucking easy today as you just ask jewgle and someone will have a tutorial for almost anything.

>>928995

Perhaps OP is teenage, but still he needs to start learning by himself.

>>929039

The problem is "lack of direction" and "lack of motivation". The latter can just GTFO, the former should be solved by "example challenges"

Install OpenBSD, read the FAQ on website, read the man pages. If necessary, you can also read the actual relevant books like Absolute OpenBSD, Book of PF, and their SSH book. That should get you started on the right path.

>>928992 (OP)

>By what means did you all learn computer shit?

through massive amounts of autism

su

>>928992 (OP)

It's as easy as learning what all of the all of the abbreviations mean. Pajeet shit tutorials will never teach you though, you have to look them up yourself and by the time you've read the words, you've basically already memorised it.

>>929108

>relevant books like Absolute OpenBSD

That book is everything but relevant these days.

>>929985

Most of the book is still relevant, although it could use another update. Anyway you don't have many other choices other than man pages and FAQ.