m0rc

8 ms·

1.
by m0rc 1mo ago
You see, it seems that the issue is not learning by itself. But, learning by reading a book cover to cover about a topic. It is not fast enough as the current times seem to require. A complex book can take me 1 year or more (Visual Complex
2.
by m0rc 1mo ago
For learning, I find LLM's helpful as a knoledgeable "tutor" or "friend" during the reading of a complex paper or book. Before, when I got stuck, I spend lot's of time going around different books/pages&#x
3.
by m0rc 8mo ago
I think the article has a point. There seem to be two reactions among senior engineers atound me these days. On one side, there are people who have become a bit more productive. They are certainly not "10x," but they definitely de
4.
by m0rc 11mo ago
So far, the best reference for software engineering research appears to be R. Glass et al.'s 2002 work, Facts and Fallacies of Software Engineering. I haven't found a better or more comprehensive reference. It would be great to se
5.
Show HN: Through the Geek's Lens(github.com)
2 points by m0rc 1y ago|0 comments
6.
by m0rc 1y ago
Author here. I appreciate the feedback and I'm glad you like it. As far as I know, it is not possible to sell PDF through Amazon KDP. As a promotion, Kindle was free for 5 days. I will perhaps publish free of charge in one year or two
7.
I wrote a book: Through the Geek's Lens(github.com)
1 points by m0rc 1y ago|3 comments
8.
by m0rc 1y ago
What do a crowded airport in Beijing, parenting, the risk-return frontier, and micromanaging bosses have in common? Everything—if you look at the world through the right lens. In Through the Geek’s Lens, you’ll embark on a personal, humorou
9.
by m0rc 2y ago
I think the problem is not just software estimation, but project cost and time estimation is difficult across many domains (construction, transportation, IT, defense, and even the organization of events). The word "mess" seems to
10.
by m0rc 5y ago
As a baseline on what is know and not know about managing software projects, I always recommend Robert L. Glass Facts and Fallacies of Software Engineering . More speculatively, I think that the following biology readings are inspiring: -
11.
by m0rc 6y ago
>the optimal leverage being below 1 in all cases involving multiplicative processes This is wrong. Instead I should have written: "there is an optimal leverage point, most likely close to 1. The optimal leverage point does not depen
12.
by m0rc 6y ago
I remember the first time I heard someone (N. Taleb) expressing a negative opinion about economists because they were not "getting" the concept of ergodicity (in addition to other issues not relevant for this discussion). Initial
13.
by m0rc 6y ago
It is not equivalent, but if someone has the time to read the list, I would recommend instead the reading of R. L. Glass "Facts and Fallacies of Software Engineering" [1]. [1] https://www.amazon.com/Facts-Fallacies
14.
by m0rc 6y ago
First of all, I think that the idea and the effort behind the book are a fantastic and worth undertaking. The issue for me is that the connection between the individual topics and its relevance for Software Engineering is not clear or prese
15.
by m0rc 8y ago
Hamming, Richard R. Art of doing science and engineering: Learning to learn. CRC Press, 2014. ...and for papers, I like the curated list in Fermat's Library: https://fermatslibrary.com/journal_club
16.
by m0rc 8y ago
The best advice I have seen about this topic is the classic book "The Unwritten Laws of Engineering" from W.J. King. I always recommend the book to newcomers. Note that the latest re-print of the book is named "The Unwritten