Need to learn Computer Engineering for Free❤

KSPathirana

Well-known member
  • Apr 22, 2015
    7,942
    10,208
    113
    There is no road map dude, unless you want to follow the same path some course takes. even then you will only get the topics of the course and back to googling. End of the day googling is your best friend.

    Only thing is it might lead you down a rabbit hole.
    Showtime Recording GIF by CBS
     

    tharakaf

    Well-known member
  • Oct 19, 2020
    36,620
    75,563
    113
    Best recourse for digital electoronic, VLSI, CPU design
    https://www.youtube.com/@nesoacademy/videos


    me tikath balapn Hardware side ekata asanm
    https://www.youtube.com/@ChipCamp/videos


    උඹලට පොඩි කතාවක් කියන්නම් අපි 2000ස් ගනන්වල කැම්පස් යන කාලේ පොන්න ලෙකාල උගන්න දේවල් 10%ක්වත් තේරුනේ නෑ. උනුත් හෙන ලොකු දේවල් වගේ ඕව ඉගැන්නුවෙ. අනික පට්ට පඩ සීන්.

    හැබැයි ඒ ඔක්කොම ගොඩ දාගත්තෙ මේ වගේ ඉන්දියන් ලෙකාලගෙ විඩියෝ yt එකෙන් බලලා. මුන්ගෙ විඩියෝ වල උන් පට්ට ලස්සනට සරලව විස්තර කරනව.
     

    Blogerwiki

    Well-known member
  • Nov 3, 2022
    1,146
    790
    113
    Darkweb
    www.darkweb.dk
    උඹලට පොඩි කතාවක් කියන්නම් අපි 2000ස් ගනන්වල කැම්පස් යන කාලේ පොන්න ලෙකාල උගන්න දේවල් 10%ක්වත් තේරුනේ නෑ. උනුත් හෙන ලොකු දේවල් වගේ ඕව ඉගැන්නුවෙ. අනික පට්ට පඩ සීන්.

    හැබැයි ඒ ඔක්කොම ගොඩ දාගත්තෙ මේ වගේ ඉන්දියන් ලෙකාලගෙ විඩියෝ yt එකෙන් බලලා. මුන්ගෙ විඩියෝ වල උන් පට්ට ලස්සනට සරලව විස්තර කරනව.
    still same with medicine. we just see slides rocking themeselves
     

    Raskolnikov

    Active member
  • Oct 29, 2019
    183
    166
    43
    ive heard good things about ben eater. for low level coding nir lichtman could be a good starting point. but as many here have already suggested, there's not a clear-cut way i guess. i'd say old sources are superior e.g. knr book for c etc. as they knew what they were talking about and it was before education was commercialized and textbooks adopted mcgrawhill et al's shitty framwework (which assumes people are dumb and have to be spoon-fed w/ 6000+ additional pages of junk). best way would be to install a c compiler, start writing something, try to compile it to see compiler warnings/errors fix those urself, dont even google. always go for the official docs/help files. for example learn to read man output `man 3 printf` says exactly what you wanna know about how to use printf, which libraries you wanna include for that etc. in the tinkering realm for example learn how to read datasheets and where to find them. dont use llms (at least on the things you want a deep understanding, else it's fine ig). be self sufficient. learn to read error messages, just dont copy and paste them to stackoverflow or whatever, most of the times the answer is in the error message itself. but that's just my opinion and most probably would not work for u. and btw im not a coder or a tinkerer so take everything i say with a grain of salt. maybe this is me pushing my fake ideology onto others to quench my ego. anyway good luck and above all have fun!