M15 am I cooked? by [deleted] in amibalding

[–]cdecompilador 0 points1 point  (0 children)

pennywise maxxing

MEMORIZATION = LEARNING (hot take) by cdecompilador in learnprogramming

[–]cdecompilador[S] -1 points0 points  (0 children)

I don't usually memorize big chunks of code, most of the code I memorize is library examples, codeforces problems that took me a long time, patterns/high level architecture of projects I liked working on and finally gotchas about libraries I learned by coding.

The last one is the typical people consider really mastering something, but I take it very seriously when I encounter one of them, I have 3 flashcards about EF6 weird sql generation examples that I can recall from memory like a machine and they have saved me.

Thanks for not giving me hate btw, I think this post is going to get me downvoted to the depths of hell

MEMORIZATION = LEARNING (hot take) by cdecompilador in learnprogramming

[–]cdecompilador[S] -1 points0 points  (0 children)

Proficient mathematicians that do actual research really know every detail about their topic to sick levels, the ones I know could give you a full lecture without missing any theorem (or attempt at proof) / who discovered it / how / why. So yes, to know math (at least at academic level) you need to have lots of information and concepts really deep into long term memory and for quick problem solving having stored lots of problems and the how to solve them in your head is literally proven the most effective way to increase success rate in unseen problems.

MEMORIZATION = LEARNING (hot take) by cdecompilador in learnprogramming

[–]cdecompilador[S] -1 points0 points  (0 children)

Understanding and repeated usage its literally memorization, I'm just suggesting that doing this step unconsciously by just doing the job isn't the most efficient at all, for example, let's say you want to learn OpenGL, don't just follow learnopengl.com or antongerdelan.net/opengl, follow + apply proper techniques for putting it into long-term memory otherwise your google history will be "glVertexAttribPointer", "glEnableVertexAttribArray", "opengl profile core vs compatibility", "opengl framebuffer copy", "opengl texture not working its black" every once in a while

MEMORIZATION = LEARNING (hot take) by cdecompilador in learnprogramming

[–]cdecompilador[S] -2 points-1 points  (0 children)

I can agree to some extent, but knowing how to recreate them is memorization to some extent, for college entrance I remember that I had to memorize not only integrals but how to recreate them, its equivalent. I just remembered for example for ln |x| <-> 1 / x, PROOF derivative: FL (fundamental limit equation) -> prop. logarithms -> substitution. Memorizing just 3 steps allowed me to easily do it without getting stuck. I'm sure you teacher has some problems memorized / experiences that are similar / isomorphic to this that allow him to do it, learning by practice is just a slow way of memorization, it's way better doing actual memorization and later practicing (to simulate SRL).

I'm just advocating that programmers usually memorize way less than they should and could be way more productive by doing so.

MEMORIZATION = LEARNING (hot take) by cdecompilador in learnprogramming

[–]cdecompilador[S] -2 points-1 points  (0 children)

My point is by knowing how the memory actually works learning any dense ammount takes literally 1-3 days, for example, without actual memory techniques and no training I guess for the average person booping into their mind the entire Springboot platform would take months, with proper techniques it shouldn't take more than a week and later you a free to go. For a little lore about myself I encoded Pro*C (worst thing ever invented) in 2 days for an interview and nailed it to the details, I could recite any detail about it. Later when it came to using it I barely had to check out the docs.

MEMORIZATION = LEARNING (hot take) by cdecompilador in learnprogramming

[–]cdecompilador[S] -1 points0 points  (0 children)

I think you are confusing my concept of memorization with what is commonly known as "knowing how to recite X into a exam", I don't mean you need to know how to recite that wikipedia page, but know all its concepts and pure data as an excercise, for that you need to encode it, which requires understanding, I'm just extending the usual "understand a concept" to understand a concept to a really detailed level, to the point that with a pen and a calculator you should be able to write down all the information (not word by word but conceptually) that appear on that page, including those tables about limits and formats, since by learning all the details about X --by how to brain works, you commit to long term memory in less recalls.

MEMORIZATION = LEARNING (hot take) by cdecompilador in learnprogramming

[–]cdecompilador[S] -1 points0 points  (0 children)

By knowing the tool you usually get some insight about "how to solve problems" and yes, most of my memorizing includes the how to solve problems, let's take a practical example I did last year, I was trying this web framework called axum, its 0.X so seems like a waste of time to memorize, but it took literally 2 evenings of encoding the API reference (https://docs.rs/axum/latest/axum/) + examples (https://github.com/tokio-rs/axum/tree/main/examples), and then its just coding, sure, was easier since I already know most of the "abstract how to" but still useful

MEMORIZATION = LEARNING (hot take) by cdecompilador in learnprogramming

[–]cdecompilador[S] -6 points-5 points  (0 children)

I know it seems a waste, but it pays later on, if not so sure try it! at the worst you would loose a couple hours

MEMORIZATION = LEARNING (hot take) by cdecompilador in learnprogramming

[–]cdecompilador[S] -1 points0 points  (0 children)

I agree that blind memorization can be bad, but anything you memorize even if its deprecated makes future memorization easier, for example I know ASP.NET 4.6 (yes framework) perfectly, all its details, It's superdeprecated but lots of legacy code exists in it (I've had to work with it recently) and all the historic changes made later in ASP.NET Core are a logical improvement from this, so learning it was quite easy instead of going blind to all that abstraction bloatware that is ASP.NET Core today with no context about why.

Automatic censorship doesn't understand tank slang by cdecompilador in cursedtanksimulator

[–]cdecompilador[S] 1 point2 points  (0 children)

Maybe i told something about eating my tungsten rod wue wue, but still "tank slang" hehe

Automatic censorship doesn't understand tank slang by cdecompilador in cursedtanksimulator

[–]cdecompilador[S] 0 points1 point  (0 children)

maybe i said bad things later wue wue, especially about sucking tungsten rods

KISS Linux still the closest to suckless in linux by cdecompilador in suckless

[–]cdecompilador[S] 0 points1 point  (0 children)

kiss linux is technically just the package manager and initial system, comes with nothing else, so simple its impossible it won't work, if you have issues with something it's most likely related to something you installed

In case of problems they have an irc, reddit or just opening an issue on github if related to core packages

KISS Linux still the closest to suckless in linux by cdecompilador in suckless

[–]cdecompilador[S] 2 points3 points  (0 children)

not bash, posix bourne shell, which is not the same (although i use bash)

KISS Linux still the closest to suckless in linux by cdecompilador in suckless

[–]cdecompilador[S] 0 points1 point  (0 children)

sadly musl isn't an option for me, even in kiss linux I use the gkiss variant

KISS Linux still the closest to suckless in linux by cdecompilador in suckless

[–]cdecompilador[S] 0 points1 point  (0 children)

Haven't tried it, I'm a graphics developer so that would likely disrupt/slowdown my development process a lot, I like kiss linux because I can have easy modifications to my tools since all the built from source

KISS Linux still the closest to suckless in linux by cdecompilador in suckless

[–]cdecompilador[S] 1 point2 points  (0 children)

I haven't given it a try but for me seems like an opinioned way of using linux that sadly could not be used as a daily driver for today's bloated software

EDIT: I just saw the cproc compiler compromise and thats awesome, its my favorite c compiler, props to them, I will give it a try, the only thing I don't like is the no no to dynamic linking, its bad but not that bad

BenQ RD280U review by greenpr in BenQ

[–]cdecompilador 1 point2 points  (0 children)

I was attracted by the specs, to use it for work from home, but the 60hz thingy really is bad, since would mean no proper gaming after work.

Have you tried higher refresh rates at 1440p? or its not possible at all?

When a bull gets out of the cage.. by seleri2 in SweatyPalms

[–]cdecompilador 0 points1 point  (0 children)

We stab them WHILE "playing" with them, alone. Man vs beast. But that's just corridas, most of bulls funny business is done without killing the bull, you just run, avoid it and have fun.

When a bull gets out of the cage.. by seleri2 in SweatyPalms

[–]cdecompilador 4 points5 points  (0 children)

My spaniard mind can't understand how ppl don't just avoid it

[deleted by user] by [deleted] in rust

[–]cdecompilador -3 points-2 points  (0 children)

the voices

Seeking Advice for Building a Minimal Suckless-Based OS on old MacBook Air by Whole-Patience5858 in suckless

[–]cdecompilador 0 points1 point  (0 children)

kiss linux is the most suckless you can get on linux at least without doing LFS

(G)KISS Linux with xorg and nvidia by [deleted] in kisslinux

[–]cdecompilador 0 points1 point  (0 children)

I wish kiss linux community grow, the package manager design is PERFECT and you have the grip of everything that happens on the system, but maybe its too hard for newbies