gashaw

Programming on Purpose - Essays on Software Design, by P.J Plauger

This is probably the best (and most effortul) way to aquire the knowledge initialy. I did it a lot back in school, then few months upto a year later I would forget most of the material all the same.

I'm already rereading the most valuable books and it does help to retain their knowledge. I guess doing spaced repetition every x time would help even more. I feel that rereading and to a larger extent spaced repetition are very wasteful.

I am. About 70% are technical books related to my job (SWE) and the rest are combination of textbooks and popular science in fields that I find very interesting.

If for some reason I lose interest in a book then I just stop reading it and don't mind if I don't remember anything from it.

Of course you are.

Exactly.

How can you prove something about yourself before first proving your existence?

I know it sounds outlandish but it does point the gap in your proof.

I think consciousness is one of those things that is not defined well enough for us to understand it. Until there is a breakthrough in the understanding of consciousness itself there won't be any real conscious ai.

It's like when we learned to fly, we needn't understand how birds' wings work. We had to understand the principles of aerodynamics or what is flying itself.

That's why I think imitating the brain won't work, (deep learning etc.) just like the early attempts to fly didn't, even if we'll know the function of every single neuron.

You can't prove even that. If you examine it closely, the argumnent only proves that "it" thinks. "It" is not necessarily an "I", for what restricts the thinking to an I (i.e a part of reality)? It could be the whole reality that does the thinking as far as the argument goes.

Sorry.

I used it few times, it's as good as the others. I don't think there ever will be a silver bullet, what works for some companies won't work for others. The real issues are people issues.

Release it! by Michael Nygard has lots of good info on design issues related to production systems and operations/devops of such systems.

I highly recommend "The Secrets of Consulting" by Gerald Weinberg.

On the project and management level read Rapid Development by Steve McConnell. On the detailed technical level read Code Complete by same author.

Then read some blog posts on agile, scrum and kanban only to get familiar with the jargon.

Don't you mind having 5000+ LOC model? Methods being redefined because the class is huge and the developer didn't notice the existing method?