- The Intellectual Production of Engineers Reaction Summary became so long that I made a second page in the wake of the lecture.
Lecture given. - Intellectual Production of Engineers Before and After
-
Twitter summary: Devsumi 2019 15-B-1 The Intellectual Production of Engineers Before and AfterdevsumiB - Togetter []
-
I liked âThe Intellectual Production Techniques of Engineersâ - MaikurođŁKirimin
https://twitter.com/gfx/status/1099848587398197248
- In âThe Engineerâs Guide to Intellectual Production,â there is something like, âWhen you feel like youâre not having a hard time learning something new, itâs because itâs not really new,â which is similar to the often quoted quote in the startup community, âWhen everything seems under control, youâre just not getting out as fast as you should. This is a common quote in startup circles.
- I think the context was that if you donât challenge yourself to learn more new things, you canât call it intellectual production (my interpretation).
-
When you are learning a ânew languageâ that you can use without difficulty, (omitted) you are learning few new concepts. ďźThis is a bad mentality to be stuck in and you need to realize it and get out of it.
- I reprinted it myself: When you can learn without effort, you are not actually learning.
https://bookmeter.com/reviews/78964919
- The speed-reading story made sense to me, and Iâm going to try the KJ method. The talk about excellence was also interesting.
https://booklog.jp/users/tomohikon12/archives/1/4774198765
-
What I wanted to remember.
-
How to know if knowledge has been built up
- Can you explain in your own words?
- Can you give specific examples that followed your experience?
- Can I use that knowledge to achieve my goals?
-
People who are unmotivated are not able to focus on a single task.
-
To be able to do more than you can do today, âItâs up to the barrel of your thought.
-
The phenomenon of shouting âgeniusâ without seeing the âeffort behind the scenes.â
https://twitter.com/tkdn/status/1105813245338640384
- When you think you are learning, but you only know as much as you can, you are not learning (from âThe Intellectual Production Techniques of Engineersâ). The learning starts when you get stuck and donât know what you donât know.
- Iâm not comfortable with this expression.
https://twitter.com/neko_suki/status/1105014653388652547
- The part about management strategy really stuck with me. I am strong in network protocols, and I know a little bit about GPUs, automated driving, and deep learning, so I would like to differentiate myself by combining them.
https://twitter.com/shootacean/status/1104393829036126208
- It was an easy read with a good balance of abstract and concrete stories.
- Most of what I hadnât been able to verbalize was written in an organized manner, and I realized a lotâŚ
- I also appreciate that the citation information is well documented in the annotations!
https://twitter.com/shootacean/status/1104389055750402049
- The âcrossing the borderâ of the Kaizen Journey and the âexcellenceâ of Chapter 7 of The Engineerâs Guide to Intellectual Production are similar.
https://twitter.com/shootacean/status/1104267501913890821
- Iâm glad I read about the intellectual production of engineers!
- Chapter 4 was written in a way that organized what I usually think about, so I felt so much clearer!
https://twitter.com/auxps/status/1103581315952070657
- Talking about âinformation cardâ
- I also recommend a book called âAn Engineerâs Intellectual Production Techniqueâ by NISHIO Hirokazu on how to organize information using cards. (This guy does it with âfusen.â)
- It is originally Jiro Kawakitaâs KJ method, but it is very easy to understand because he actually practices output to the point of putting ideas together and writing a book.
https://twitter.com/sasakinoblog/status/1103566679559159809
- I found the second half difficult.
https://twitter.com/hrgn_tw/status/1102939220178620416
- This book made me realize how much I usually donât think about anything. Letâs start by writing down on paper the deadlines and goals of what we want to do.
https://twitter.com/Xyo/status/1102938063704023040
- Right now I am reading âThe Intellectual Production of Engineersâ. I would like to send it to my past self in a time machine to read it, but even if my younger self reads it, he would not understand it due to lack of experience, and would be in a state of piling up boxes in the sky, which was the metaphor of the book⌠I felt this dilemma. I felt something similar when I read the refactoring book.
https://twitter.com/sasakinoblog/status/1102415844523401216
- I am currently reading âIntellectual Production for Engineersâ and âOutput Compendiumâ.
- Both have many points in common, but they are written from different perspectives, so it is good to be able to read them while comparing them.
- knowledge consistency p.167-168 real life examples.
https://twitter.com/kurupical/status/1102355745369055232
- I enjoyed the idea of Serial Specialist in chapter 7 and the overall machine learning tics explained.
https://twitter.com/sunalabo/status/1102073078312390656
- Iâve started reading âThe Engineerâs Guide to Intellectual Production.â In my Scrapbox, âabstractionâ and âKJ methodâ were already linked words, but Iâm excited to see that the link will be further strengthened.
https://twitter.com/otakumesi/status/1101800191189897216
- Using the KJ method to write down your thoughts is a good exercise in going back and forth between the concrete and the abstract.
- Iâve been using it ever since I read The Engineerâs Guide to Intellectual Production.
https://twitter.com/NikkoMonkey/status/1101762690173743104
- The book is a compressed version of work techniques often seen in business books, arranged in a style for engineers. The book addresses common problems such as âhow to be motivated,â âhow to remember for a long time,â and âhow to read efficiently,â and incorporates physiological/psychological aspects into methods that can be practiced on a daily basis.
- I think I like that kind of thing because I generally find stories that explain or hack the behavior of the human body or groups of people in a hardware/software abstraction interesting.
- I really like the nonsensical stuff like âNmsec is the limit of the eyeâs afterimage recognition, and the pace of reading aloud is Nsec, so the pace of reading is in the range of N to Msec. On the practical side, I think the Pomodoro method of dividing task time is pretty useful.
https://twitter.com/benevolent0505/status/1100350096112181248
- What was unconscious is being verbalized anyway.
https://twitter.com/kappezoro/status/1099924891132776448
- Does the math department need to understand one page at a time to move on? ⌠I had one line when I was there, and as soon as I was unclear on even one line, the professor would⌠I stopped, so I went looking for books to understand the essence of the subject and kept my notes at 1~2 pages per line. So I didnât finish reading one book even in a year.
Reading The Intellectual Production Techniques of Engineers By NISHIO Hirokazu Book Review by Naoki Shiho | Naoki Shiho Official Site []
https://twitter.com/kigh/status/1098801343718813696
- The SECI Model. Scrum as an intelligent creation system.
- Iâm reminded of what I read at the beginning of the year in âThe Intellectual Production of Engineers.â That one is individual play, this one is team play.
https://twitter.com/mike_neck/status/1115235478431645699
- I collected about 100 contents for jjug ccc according to the list of 100 anyway in âThe Art of Intellectual Production of Engineersâ.
https://twitter.com/yuuki_script/status/1115140602541236224
- It was not a how-to on engineering, but rather how to leverage the nature of engineering to become stronger. The talk about excellence based on differentiation strategy, etc., stuck with me personally. I want to put it into practice.
https://twitter.com/disneyduffy1118/status/1114302838773911553
- The Intellectual Production of Engineers, interesting đ I feel like what Iâve been feeling in the atmosphere is falling into my stomach in writing. I see what you mean about flow theory! I thought. When Iâm anxious or bored, Iâll review the challenge đ.
https://twitter.com/Xyo/status/1113452079819804672
- Chapter 4 of âThe Intellectual Production of Engineers,â How to Read a Book. It had the biggest impact on me. I have not read many books of this type, so I subconsciously read aloud quietly, and I was concerned about reading through the book, but now I feel that I donât have to do that. I knew this was a book I wanted to send to myself 10 years ago.
https://twitter.com/Xyo/status/1113449605042102272
- Chapter 3 of âThe Engineerâs Guide to Intellectual Production,â the importance of the output needed to remember. It was kind of a rule of thumb, but I still remember things better once I write them down. Even if I donât have confidence in my memory, I can remember how to deal with technical problems that I used to write about in my old blog (which I donât use anymore).
https://twitter.com/mesh1nek0x0/status/1111949697365622784
- I have a feeling that we will learn about abstraction, which was also found in the intellectual production techniques of engineers (Table of ContentsThe Magic of Memos
- I feel that abstraction and diversion from facts is similar to the patterning and trial-and-error that I read the other day in the engineersâ intellectual production techniques. Itâs interesting to see how we all arrive at the same place. Reproducibility gives it a name. Iâm sure thatâs the case. The magic ofnotes
https://twitter.com/bc_rikko/status/1111838753201348608
- In âThe Intellectual Production Techniques of Engineers,â there is a phrase, âUse knowledge to gain a position, and then use that position to acquire knowledge.â I would like to use my position as a CSS framework world ranker to connect with various people and absorb various things!
https://twitter.com/tkt_horikoshi/status/1111243244115918848
- I found myself reading The Intellectual Production of Engineers. Iâll read it five more times.
https://twitter.com/43memo_com/status/1111066630665068544
- I bought a copy of âThe Engineerâs Art of Intellectual Production,â and flipping through it, I found that it explains various things related to intellectual production in a considerable volume, and the illustrations are easy to understand. I think Maruzen in Marunouchi has been pushing the book for almost half a year, and the fact that it has been on the shelves for that long suggests that it must be a big seller. Even non-engineers should read this book.
https://note.mu/raynote/n/n8ee6caebb80f
- Role as a map for those who will be doing intellectual production
https://twitter.com/_chick_p/status/1109585339985747968
- When choosing a reference book, you should look at the syllabus of the university. However, the author says that he excludes those by the lecturers themselves or those related to the university.
https://twitter.com/stand_arrow/status/1109435178483507200
- It was good to realize that I had incorrectly remembered how to do the KJ method.
https://twitter.com/AndSaino/status/1109240963090644992
- Letâs do sutra copying now and then. According to âThe Engineerâs Art of Intellectual Productivity,â modeling is advanced by discovering similarities and differences.
https://twitter.com/yukitakaiha/status/1108628516059271168
- I read âThe Intellectual Production Techniques of Engineers,â and Yuji Maeda said the exact same thing about how he writes his notes.
- The flow of âconcrete â abstract â appliedâ can be applied to all studies, not just program studies, and I think it is so important to be aware of this process when learning something.
https://twitter.com/kurupical/status/1107999355489771530
- I quite like the idea of the âstraw man strategyâ of learning new things using your current weapons as bait. The book: The Intellectual Production of Engineers also talked about the same thing with the term âserial specialistâ - I think.
- Iâm vaguely aware of these places in a corner of my mind (but I havenât done anything about it lol).
https://twitter.com/tomo_yoshizaki/status/1107634290248962049
- I used to use the Pomodoro Technique only for study breaks, but when I read about the intellectual production techniques of engineers and applied it to my work, I had 7 Pomodoro in one day.
- Surprisingly, tasks cannot be processed in a day.
https://twitter.com/windymelt/status/1106856613984403458
- By the way, I had finished reading âThe Intellectual Production of Engineersâ. There were a number of passages that I was unsure about, and I wish I had read this earlier. The best part was âThere is no âstoryâ in source code.
https://twitter.com/hellomyapple777/status/1118548363824091137
- I read âThe Technology Behind Codingâ by NISHIO Hirokazu. I learned a lot. I would like to read this book again when I write programs in the future. I wish I had it when I was a student.
- As I thought in âThe Engineerâs Art of Intellectual Production,â I am glad that the author has managed to discard the details while carefully considering the order in which the topics are presented so that they can be easily absorbed into the mind. I also appreciate the back and forth between concretization and abstraction.
- There are surprisingly few books like this that âcreate a rough map in your mind,â which is valuable. Many of them are too dictionary-like and exhaustive, making it difficult for beginners to grasp the important points, and many of them do not touch on the purpose of various mechanisms and concepts.
https://twitter.com/ledsun/status/1118611439416033280
- Iâm wondering if thereâs a pro-management version of the book âThe Intellectual Productivity of Engineers.â Itâs become the norm with Agile and Scrum in the last 20 years or so. A book that outlines techniques such as project charters, estimates are probabilities, decide on the done of tasks, combine buffers into one, donât move on to the next phase with a reverse line table, etc.
- PMBOK is too much. It should be more like a how-to, introducing techniques and original sources. That would reach people who have not been exposed to Agile for 20 years.
- The âEngineerâs Art of Intellectual Productionâ consciously concentrated on âwhat one can do alone.â Because change is slow when you try to move others. Many PM books assume that you are in a position to move others. So I think we need a book that fills in the gaps here, and Kaizen Journey is much closer to that.
https://genkiroid.github.io/2020/05/11/learn-tech/
This page is auto-translated from [/nishio/ă¨ăłă¸ăă˘ăŽçĽçççŁčĄ ĺéżăžă¨ă ăăŽ2](https://scrapbox.io/nishio/ă¨ăłă¸ăă˘ăŽçĽçççŁčĄ ĺéżăžă¨ă ăăŽ2) using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. Iâm very happy to spread my thought to non-Japanese readers.