Upon reading the title I thought this was going to be about how easy it is to write or modify a Linux driver when using a LLM even if you know nothing about the subject.
No LLM needed. Kernel driver code for simple things is usually copy-paste-modify. Find something that works with an HID interrupt based device, and modify that. If you want a /sys led, copy from that. It's only if you try to push to mainline you need to worry about understanding it, but they'd probably smell LLM trash from miles away.
The Valmiki Ramayanam is a much more accessible document than the Gita to learn Sanskrit from as an advanced learner after completing the basics. There's the aspect of a story that unfolds progressively which is nice and engaging, as opposed to the deep metaphysical stuff in the Gita.
The first section of the Ramayanam is the Sankshepa Ramayanam, or, the Ramayanam in summary. This gives the outline of the whole story which then is expounded in detail in the subsequent sections.
What sounds nice, and works, in poetry may not work when narrated in prose.
So, I am avoiding the first four sargas of the Balakanda entirely in my guide. The story starts with a description of Ayodhya and then moves on to Dasharatha and his family. I want to keep things simple and linear so that the story has momentum and readers feel like continuing the story.
I will have to find a way to incorporate all the side stories without damaging the momentum. Will probably add them as "side quests" at the appropriate juncture.
> after completing the basics
I have to disagree here. Best to jump in directly using glosses (will start with an English one. Might add a Hindi one at a future date). This fetish for basics is a big hurdle that I have personally experienced.
You will never be confident enough to start reading the Ramayana no matter how much you study the language because it is a game of vocabulary.
You need vocabulary to understand things. And the only way to acquire vocabulary is to read a lot.
In my experience of having learnt Sanskrit via what I now realize is the comprehensive input method (thank you for introducing that term to me via your comments on this thread), I absolutely think that the "basics" - enough to recognize the seven (eight if you count the sambodhana) vibhaktis (declensions) and the simple past, present, future and the subjunctive tenses - are required in order to get past the huge roadblock of parsing a word.
Once parsed, I can look up the meaning of the word on ashtadhyayi.com or elsewhere, but not before.
Sanskrit grammar is complicated enough for basic knowledge of the cases and the tenses/aspects/moods to be less useful than one would otherwise assume. You have sati-saptami prayogas, krdantas are often uses as adjectives while basic text books talk about them in limited contexts. It is a huge mess.
I wasn't referring to knowledge of the Paninian sutras or pratyayas, to be clear, when I said "the basics".
For this story, you don't need to know the pratyayas but you do need to know the tenses, the ktva-lyap forms, etc to fully understand what is going on. With only an incomplete knowledge of those aspects, one can sort of intuit the overall meaning but eventually would find that they had the wrong idea altogether when reading the corresponding translation in a language they know.
After getting frustrated by the game not accepting my responses to the obvious clues repeatedly I resorted to clicking on each person and selecting both Innocent and Criminal.
- "My only innocent neighbor is to the left of Harold"
- "Barb and I have one innocent neighbor in common"
Thank you for taking the time to go through this. The hint should be clarified. It means "somewhere to the left", so on the same row to the left. It is either Freya or Gary since they are both to the left og Harold, and common neighbors of Barb and Cheryl. You have no way of knowing which one yet. This will be clarified in future puzzles.
I have a childhood friend that I went to school with for all of my school days. Ever since school days, we find the same obscure things funny and always end up in splits whenever we talk. To this day, I don't have this with any other friend.
We had a few years' gap of not really being in touch during undergrad but that changed as we had a few months' overlap at post-grad university. It was easier to meet after that and we did keep in touch, but I felt that he was holding back somewhat and not really being free with his thoughts, letting the conversation flag at times.
So at a friend's wedding a couple of years ago, I opened up to him and plainly told him that it's a shame we don't talk as we used to as we both are clearly on the same wavelength when it comes to shared interests and sense of humour. And this worked - our degree of friendship has increased an order of magnitude since before that time. I would have lost a great friend to the vagaries of life had I not taken that step to become vulnerable for an instant then.
My first job out of college I was hired to follow around an MSP/IT consultant and learn what he did, specifically to cut the expense of having a MCSA/network engineer coming in weekly for basic desktop support.
I met him in the server closet and asked “hey, I’m new here - do you mind if I look over your shoulder?” He turned around and smiled, “if you are here to help, then you should sit down and I’ll walk you through setting up Exchange mailboxes for these doctors.” Before he left, he walked me through a RAM upgrade and gave me his lucky red screwdriver “ you got this, just call me if you have any issues.”
Later in my career, I continue to learn lessons from this interaction; lately the lesson has been one of “don’t be awesome in a vacuum” - a little bit of encouragement to the new guy can go a long way to adding another person to your on-call rotation that you trust.
20 years later, I still have his screwdriver - and I bring it every time we have lunch every once in a while.
Life is too short to not let the people who make life enjoyable for us know so.
You are not alone. Coming from Gerrit myself, I hate that GitHub does not allow for commenting on the commit message itself. Neither does Gitlab.
Also, in a PR, I find that people just switch to Files Changed, disregarding the sequence of the commits involved.
This intentional de-emphasis of the importance of commit messages and the individual commits leads to lower quality of the git history of the codebase.
