I'm in the same boat and curious if other more experienced users have any resources to point to. My anedoctal data point is that after starting with doom emacs and having problems to set it up on another machine i fund out all i needed was a very small configuration file to accomplish my orgmode/agenda usage needs. So all it took was an issue and a clear vision of the goal to find a way through. Maybe it is a healthy approach to keep the complexity manageable to your usage
That was an interesting read. Even more if you take a look into another of the author's text on the decline of personal thought [1]. I believe the author is engaging with very interesting questions: what is knowledge? How can I achieve it? How does it feel during the pursuit?
Of course the answer is deeply personal. My take is that I agree with the author on that knowledge should be inhabited, as I quoted Arendt on a former blog entry of mine [2] "For memory and depth are the same, or rather depth can only be reached by man through remembrance.".
If your journey using whatever tool du jour helps you, more power to you! But if it feels like a burden, drop it and adapt. In my process, I tried many different methods of note taking, but the one I haven't dropped is pen and paper. The act of writing is thinking to me. I do not have a plan to go through what I have written and treat them as a fortuitous encounter rather than having a procedure/method in place. But I still find the idea of having digital notes somewhat appealing, luring even.
This brings back memories. We used this in my mechanical engineering mechanisms class. It was cool to have the (simplified!) symbolic formulas describing the movements we were designing.
I'm keeping a detailed log of my activities in orgmode. But only because I have to input the hours in another system. It is interesting that even though the categories summarized are from the org-clock-table, I write small descriptions on each category for each day. For instance I might have multiple entries throughout the day for "Client X - Report", but I summarize what I've actually done in the notes. At the end of week I export it and archive with the clocktable along it, using a narrow-subtree. I also paste them in an archived section with the Year/week so I keep track of the activities and they are searcheable. So far, the clock tables themselves have been most valuable to me, especially for review purposes. Still, I believe a brag document complements this quite well and is something I plan to restart doing.
Instead of relying on things like "Playlist made for you" I still like leveraging the algorithm to discover "new vectors" by actively going to a song that some aspect caught my attention and going to its radio (only tried on Spotify). Sometimes I'm surprised with new soundscapes.
On my master's thesis, I ended up using a line that I wrote when preparing the template at the beginning of my 'journey': "I thank everyone who contributed to making this work possible." By the end of the master's program, I didn't feel the need to update it, as it remained true to me. I felt that if someone was going to read that section, they would immediately identify themselves there, and I didn't have to name them.
Tangent since it is not exclusive to image processing, but When I was studying Fourier Transforms at university I recall that the book "Fourier Series" by Gerogi P. Tolstov helped me a lot. Just throwing it out there in case it helps anyone, including to refresh the definitions the article starts with.
I read this book too and it really drove things home. I remember after feeling a little bit unsure about the relevance of orthogonal systems, feeling the thrill of beginning to see and anticipate where the argument was going. It felt like I was discovering it for myself. I think there are lot of good math and physics books from the Soviet era.
Jago: A life underwater [1]. It's been a while so I'll refer to the synopsis [2]:
"JAGO: A LIFE UNDERWATER is the story of Rohani - an 80-year-old hunter who hobbles around on land but who dives like a fish on a single breath descending to great depths for several minutes to stalk his prey like a true underwater predator."
I have found the life story of Rohani incredibly humbling and his connection to the sea unique. He lived on it. He lived in it. The images pictured this relation in such a way that left me mesmerized. The human aspect of the documentary is worth it by itself, but if you want some stunning underwater images, you are in for a treat.
Regarding the size x quantity, I believe the reason lies in where the best wind is, which is usually high above the ground. The roughness of the terrain and obstacles generate shear and turbulence, which translates into more stress for the components. The higher wind has a more uniform distribution across the rotor and is higher in magnitude than in lower heights. So for small wind turbines to have access to the best wind, you would have to build expensive structures to reach there, making it infeasible. Hence kite approaches like the one posted and Makani (with different principles).
Haven't read the whole article yet, but the state of latex editing in emacs diagram caught my attention. Anyone has a clue what software was used to create it? Found the color schemes and hyperlinks pretty neat.
reply