71–80 of 100 posts
Slightly contrarian perspective: I'm trying to read less temporal (things that matter now ) and more fundamental (stuff that mattered 1+ year ago and will still matter in 1+ year, with even wider intervals for non-tech content). This does result in missing ~important things occasionally (e.g. I still don't know what happened with SamA at OpenAI, and yes, I am curious), but that's a small price to pay for greater inte…
Big +1 to this. Much of the programming stuff I've read that's made a big difference to me and my skills and career has been the older "classic" and fundamental stuff. Unless it's directly related to the specific tools you're working with on your current project, and even specific issues with those tools, maybe let it age before you spend time on it. "1+ year" actually sounds pretty short to me. Maybe 5 or 10 years t…
Earlier quoted context omitted.
Read Books, is the answer I think. The entire online news chain is polluted it seems to me. If you have access to a decent Library, I believe the benefits to the individual by using it are: 1) economic, save you money 2) social, you interact with people 3) physical, you are moving around 4) mental health, you are using a different part of your brain and being proactive by planning to engage in new knowledge Then hope…
I have a gigantic Dropbox folder with hundreds of PDF tech books that I am slowly working through. The focus is on the canonical and classic over the hippest or latest new thing. There have been a number of books that I read when they were fairly new that are classics now, like some of the Wiley titles on networking. It's one of the best things you can do for your career. Whenever you have some extended downtime, ins…
I found having a Dropbox folder with hundreds of books to be both completely useless and paralyzing. I kept switching books, or i was unable to pick one due to too much choice and ended up just scrolling instagram or Reddit.
Slightly contrarian perspective: I'm trying to read less temporal (things that matter now ) and more fundamental (stuff that mattered 1+ year ago and will still matter in 1+ year, with even wider intervals for non-tech content). This does result in missing ~important things occasionally (e.g. I still don't know what happened with SamA at OpenAI, and yes, I am curious), but that's a small price to pay for greater inte…
I feel this designated intervals approach is working well for me. You slow down and don't clutter your mind, but at the same time you don't miss anything and probably absorb greater amount of information in a much shorter time.
Slightly contrarian perspective: I'm trying to read less temporal (things that matter now ) and more fundamental (stuff that mattered 1+ year ago and will still matter in 1+ year, with even wider intervals for non-tech content). This does result in missing ~important things occasionally (e.g. I still don't know what happened with SamA at OpenAI, and yes, I am curious), but that's a small price to pay for greater inte…
Big +1 to this. Much of the programming stuff I've read that's made a big difference to me and my skills and career has been the older "classic" and fundamental stuff. Unless it's directly related to the specific tools you're working with on your current project, and even specific issues with those tools, maybe let it age before you spend time on it. "1+ year" actually sounds pretty short to me. Maybe 5 or 10 years t…
Slightly contrarian perspective: I'm trying to read less temporal (things that matter now ) and more fundamental (stuff that mattered 1+ year ago and will still matter in 1+ year, with even wider intervals for non-tech content). This does result in missing ~important things occasionally (e.g. I still don't know what happened with SamA at OpenAI, and yes, I am curious), but that's a small price to pay for greater inte…
I am trying to do this as well, but being surrounded by news/social/stream outlets that just push unnecessary hype its hard to achieve this. Any recommendation on how to filter out the junk?
Letting algorithms figure out the presentation of information just doesn't work well for people. Even FT which I read is always putting random crap on the front page and pushing important bits down to the second or third page-down.
None of them. Study Knuth. Study the Intel manuals. Study “The Art of Multiprocessor Programming”. Study compilers. Study TCP/IP. Study algorithms and data structures. Write lots of code for all of those things. Disregard the noise. Ban yourself from reading blogs and magazines and tech news. Focus on what is fundamental to the field. Look where nobody else is looking.
> Study the Intel manuals. Which Intel manuals in particular? How much relevance remains in Intel's content given the popularity of ARM nowadays?
https://www.intel.com/content/www/us/en/developer/articles/t...
Before the internet, Intel used to distribute these manuals in hard-copy for free. One just had to drop by your local Intel sales office to pick up a copy. A good solid foot of shelf-space.
These manuals used to be so much easier to read back in the 486/Pentium era. One could almost build a complete mental model of how a 486 worked, and how to manually optimize code to best effect by avoiding processor stalls.
Since then, intel processors have accumulated an extraordinary amount of cruft, so it becomes much harder to develop a complete mental model. Compilers have also gotten a lot more clever as well, in order to deal with the added complexity of SIMD instruction sets.
For those of us who started with the 8086 Architecture manuals, each generation of processors added additional features which one learned by occasionally revisiting the architecture manuals for new processors.
Coming to the Architecture manuals without having the foundation of previous Architecture manuals as a basis must be a daunting task. But I'm sure there's rich material there anyway.
Paged Out! Institute https://pagedout.institute/ # What is Paged Out!? Paged Out! is a free experimental (one article == one page) technical magazine about programming (especially programming tricks!), hacking, security hacking, retro computers, modern computers, electronics, demoscene, and other similar topics. It's made by the community for the community. And it's not-for-profit (though in time, we hope it will be…
Slightly contrarian perspective: I'm trying to read less temporal (things that matter now ) and more fundamental (stuff that mattered 1+ year ago and will still matter in 1+ year, with even wider intervals for non-tech content). This does result in missing ~important things occasionally (e.g. I still don't know what happened with SamA at OpenAI, and yes, I am curious), but that's a small price to pay for greater inte…
I've been reading all my news on Saturday, I didn't know what happened with SamA at OpenAI for an entire week while it was all anyone would talk about. I just waited until my Saturday slot and now I know probably as much as anyone. I feel this designated intervals approach is working well for me. You slow down and don't clutter your mind, but at the same time you don't miss anything and probably absorb greater amount…
Earlier quoted context omitted.
Read Books, is the answer I think. The entire online news chain is polluted it seems to me. If you have access to a decent Library, I believe the benefits to the individual by using it are: 1) economic, save you money 2) social, you interact with people 3) physical, you are moving around 4) mental health, you are using a different part of your brain and being proactive by planning to engage in new knowledge Then hope…
I have a gigantic Dropbox folder with hundreds of PDF tech books that I am slowly working through. The focus is on the canonical and classic over the hippest or latest new thing. There have been a number of books that I read when they were fairly new that are classics now, like some of the Wiley titles on networking. It's one of the best things you can do for your career. Whenever you have some extended downtime, ins…