[logseq-plugin-git:commit] 2026-01-28T12:40:41.617Z

This commit is contained in:
2026-01-28 13:40:42 +01:00
parent 380e5dc1d8
commit 01962afcd9
5 changed files with 16 additions and 16 deletions
Binary file not shown.

After

Width:  |  Height:  |  Size: 383 KiB

+1
View File
@@ -27,3 +27,4 @@ boox-notes:: ![BOOX Notes](../assets/../../onyx/TabUltraCPro/Notepad/JOURNALING.
- WP2 - WP2
- Coinvolgere gli use case partners per il deliverable D2.2 - Coinvolgere gli use case partners per il deliverable D2.2
- WP6 - WP6
- ![image.png](../assets/image_1769604034985_0.png)
+7 -7
View File
@@ -17,11 +17,6 @@
todoist-due:: 2026-01-28 todoist-due:: 2026-01-28
todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-01-12T07:28:14Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAiX6FN1AAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Okay, heres a synthesis of the email content, transforming it into actionable tasks for completing the task of reviewing the manuscript. Ive focused on clarity and providing specific steps. **Task Summary:** Review the IEEE Software manuscript ("SWSI-2026-01-0024") for adherence to peer review guidelines, focusing on confidentiality and providing substantive feedback. **Actionable Tasks & Breakdown:** 1. **Review Policies Understanding (Priority: High):** * **Action:** Thoroughly read the reviewer policies document (link: [https://magazines.ieeeauthorcenter.ieee.org/submit-your-article-for-peer-review/about-the-peer-review-process]) to understand the specific requirements for content, format, and communication. Pay close attention to the emphasis on confidentiality regarding AI-generated feedback. * **Deliverable:** A concise summary of key policy points particularly concerning what constitutes acceptable or unacceptable review comments. 2. **Manuscript Review & Initial Assessment (Priority: High):** * **Action:** Begin reviewing the manuscript specifically focusing on the sections related to the agentic system engineering context. Identify key sections: * **Abstract:** Ensure it accurately summarizes the manuscript's purpose and scope. * **Introduction:** Evaluate the relevance of the context engineering concept to the manuscripts topic. * **Methodology:** Assess the methods used are they appropriate for the context? * **Results & Discussion:** Confirm the results are logically supported by the methods. * **Conclusion:** Assess the final conclusion is it justified and well-supported? * **Deliverable:** A brief (1-2 paragraph) summary of initial impressions, highlighting potential areas of concern (e.g., a lack of specific details, unclear methodology). 3. **Identify Key Concerns - Confidentiality & AI Feedback (Priority: Medium):** * **Action:** Specifically look for the sections where the reviewer emphasizes caution regarding sharing information about the manuscript with AI platforms for text generation. * **Deliverable:** A list of 2-3 *specific* concerns regarding the manuscript's use of AI-generated content, which you will need to address in your review. 4. **Content Review & Feedback (Priority: High):** * **Action:** Address the following points based on your concerns: * **Referencing:** Ensure all citations are accurate and properly formatted. * **Specificity:** Ensure claims are supported by evidence. * **Context:** Clarify the agentic system engineering context. Does it adequately demonstrate its significance? * **AI Integration:** Carefully assess the role and influence of AI. Does it feel like a supplementary tool or integral to the core work? (The reviewers concern about shared information is key here.) * **Deliverable:** Draft review comments addressing each identified concern, focusing on providing specific, constructive feedback. (Focus on the *why* behind your comments not just stating the problem.) 5. **Review Score Sheet & Submission (Priority: Medium):** * **Action:** Carefully and accurately fill out the review score sheet, ensuring all sections are completed (Confidential Comments, Public Comments, and any other required fields). * **Deliverable:** Completed review score sheet, with all required fields filled. 6. **Communication Protocol (Priority: Medium):** * **Action:** Respond promptly to any questions from the editor or reviewer. Be professional and courteous. * **Deliverable:** A record of your communication attempts noting the date, content, and outcome of each communication. 7. **Final Review & Submission (Priority: Low):** Once you've completed all steps, submit the manuscript for review. **Important Note:** Document *everything* your reasoning behind the feedback, specific examples, and any changes made during the review process. This will provide a clear audit trail for future review decisions. --- Let me know if you'd like me to elaborate on any of these tasks or provide more specific examples! --- IEEE Software, SWSI-2026-01-0024 manuscript type: SWSI: Agentic System Engineering (Sep/Oct 2026) "Context Engineering for Software Engineering Agents" 12-Jan-2026 Dear Prof. Di Ruscio: Thank you for agreeing to review the above reference manus todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-01-12T07:28:14Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAiX6FN1AAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Okay, heres a synthesis of the email content, transforming it into actionable tasks for completing the task of reviewing the manuscript. Ive focused on clarity and providing specific steps. **Task Summary:** Review the IEEE Software manuscript ("SWSI-2026-01-0024") for adherence to peer review guidelines, focusing on confidentiality and providing substantive feedback. **Actionable Tasks & Breakdown:** 1. **Review Policies Understanding (Priority: High):** * **Action:** Thoroughly read the reviewer policies document (link: [https://magazines.ieeeauthorcenter.ieee.org/submit-your-article-for-peer-review/about-the-peer-review-process]) to understand the specific requirements for content, format, and communication. Pay close attention to the emphasis on confidentiality regarding AI-generated feedback. * **Deliverable:** A concise summary of key policy points particularly concerning what constitutes acceptable or unacceptable review comments. 2. **Manuscript Review & Initial Assessment (Priority: High):** * **Action:** Begin reviewing the manuscript specifically focusing on the sections related to the agentic system engineering context. Identify key sections: * **Abstract:** Ensure it accurately summarizes the manuscript's purpose and scope. * **Introduction:** Evaluate the relevance of the context engineering concept to the manuscripts topic. * **Methodology:** Assess the methods used are they appropriate for the context? * **Results & Discussion:** Confirm the results are logically supported by the methods. * **Conclusion:** Assess the final conclusion is it justified and well-supported? * **Deliverable:** A brief (1-2 paragraph) summary of initial impressions, highlighting potential areas of concern (e.g., a lack of specific details, unclear methodology). 3. **Identify Key Concerns - Confidentiality & AI Feedback (Priority: Medium):** * **Action:** Specifically look for the sections where the reviewer emphasizes caution regarding sharing information about the manuscript with AI platforms for text generation. * **Deliverable:** A list of 2-3 *specific* concerns regarding the manuscript's use of AI-generated content, which you will need to address in your review. 4. **Content Review & Feedback (Priority: High):** * **Action:** Address the following points based on your concerns: * **Referencing:** Ensure all citations are accurate and properly formatted. * **Specificity:** Ensure claims are supported by evidence. * **Context:** Clarify the agentic system engineering context. Does it adequately demonstrate its significance? * **AI Integration:** Carefully assess the role and influence of AI. Does it feel like a supplementary tool or integral to the core work? (The reviewers concern about shared information is key here.) * **Deliverable:** Draft review comments addressing each identified concern, focusing on providing specific, constructive feedback. (Focus on the *why* behind your comments not just stating the problem.) 5. **Review Score Sheet & Submission (Priority: Medium):** * **Action:** Carefully and accurately fill out the review score sheet, ensuring all sections are completed (Confidential Comments, Public Comments, and any other required fields). * **Deliverable:** Completed review score sheet, with all required fields filled. 6. **Communication Protocol (Priority: Medium):** * **Action:** Respond promptly to any questions from the editor or reviewer. Be professional and courteous. * **Deliverable:** A record of your communication attempts noting the date, content, and outcome of each communication. 7. **Final Review & Submission (Priority: Low):** Once you've completed all steps, submit the manuscript for review. **Important Note:** Document *everything* your reasoning behind the feedback, specific examples, and any changes made during the review process. This will provide a clear audit trail for future review decisions. --- Let me know if you'd like me to elaborate on any of these tasks or provide more specific examples! --- IEEE Software, SWSI-2026-01-0024 manuscript type: SWSI: Agentic System Engineering (Sep/Oct 2026) "Context Engineering for Software Engineering Agents" 12-Jan-2026 Dear Prof. Di Ruscio: Thank you for agreeing to review the above reference manus
todoist-status:: ◼️ todoist-status:: ◼️
- [[2026-01-28]] [OpenCode | The open source AI coding agent](https://opencode.ai/)
todoist-id:: [6fpPgGfgM48RfhHg](https://todoist.com/showTask?id=6fpPgGfgM48RfhHg)
todoist-project:: #Inbox
todoist-due:: 2026-01-28
todoist-status:: ◼️
- [[2026-01-28]] [[PAPERS/J-Collaborative-Development]] - [[2026-01-28]] [[PAPERS/J-Collaborative-Development]]
todoist-id:: [6fmMjW88FQ9m8x2g](https://todoist.com/showTask?id=6fmMjW88FQ9m8x2g) todoist-id:: [6fmMjW88FQ9m8x2g](https://todoist.com/showTask?id=6fmMjW88FQ9m8x2g)
todoist-project:: #✏️ PAPERS todoist-project:: #✏️ PAPERS
@@ -153,13 +148,13 @@
todoist-status:: ◼️ todoist-status:: ◼️
- [[2026-01-28]] Certificazione corsi di dottorato non presenti su ESSE3 - [[2026-01-28]] Certificazione corsi di dottorato non presenti su ESSE3
todoist-id:: [6frGFmx63Q8xJ478](https://todoist.com/showTask?id=6frGFmx63Q8xJ478) todoist-id:: [6frGFmx63Q8xJ478](https://todoist.com/showTask?id=6frGFmx63Q8xJ478)
todoist-project:: #Inbox todoist-project:: #🎓 Services-PHDICT
todoist-due:: 2026-01-28 todoist-due:: 2026-01-28
todoist-desc:: From: leonardo.fazzini1@graduate.univaq.it Received: 2026-01-27T15:58:11Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAih8lmlAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Here's a summary of the email and an actionable task description: **Task Title:** Ensure PhD Course Registrations are Completed on ESSE3 **Task Description:** Leonardo Fazzini, a second-year ICT PhD student, is requesting assistance with the registration of two PhD courses on the ESSE3 platform. He completed both courses during his first year: * **Research Methodology** (internal, taught by Prof. Thanh Phuong Nguyen) * **Neural Networks and Deep Learning** (external, taught by Prof. Giorgio Buttazzo at Scuola Superiore Sant'Anna) Leonardo submitted all required documentation for both courses during the transition from his first to his second year, but neither course is currently registered on ESSE3. **Recommended Actions:** * Investigate the status of the course registrations on the ESSE3 platform. * Contact the relevant administrative office or individuals responsible for ESSE3 course registration to understand the delay. * Follow up with the professors or departments involved if further information or documentation is required. * Ensure both "Research Methodology" and "Neural Networks and Deep Learning" courses are officially registered for Leonardo Fazzini on ESSE3. * Confirm with Leonardo Fazzini once the registrations are successfully completed. --- Gentili Professori Di Ruscio e Di Mascio, sono Leonardo Fazzini, dottorando in ICT al secondo anno, con supervisor Giacomo Valente e Luigi Pomante (in cc). Vi scrivo per segnalarvi una questione relativa alla registrazione dei corsi di dottorato. Nel co todoist-desc:: From: leonardo.fazzini1@graduate.univaq.it Received: 2026-01-27T15:58:11Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAih8lmlAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Here's a summary of the email and an actionable task description: **Task Title:** Ensure PhD Course Registrations are Completed on ESSE3 **Task Description:** Leonardo Fazzini, a second-year ICT PhD student, is requesting assistance with the registration of two PhD courses on the ESSE3 platform. He completed both courses during his first year: * **Research Methodology** (internal, taught by Prof. Thanh Phuong Nguyen) * **Neural Networks and Deep Learning** (external, taught by Prof. Giorgio Buttazzo at Scuola Superiore Sant'Anna) Leonardo submitted all required documentation for both courses during the transition from his first to his second year, but neither course is currently registered on ESSE3. **Recommended Actions:** * Investigate the status of the course registrations on the ESSE3 platform. * Contact the relevant administrative office or individuals responsible for ESSE3 course registration to understand the delay. * Follow up with the professors or departments involved if further information or documentation is required. * Ensure both "Research Methodology" and "Neural Networks and Deep Learning" courses are officially registered for Leonardo Fazzini on ESSE3. * Confirm with Leonardo Fazzini once the registrations are successfully completed. --- Gentili Professori Di Ruscio e Di Mascio, sono Leonardo Fazzini, dottorando in ICT al secondo anno, con supervisor Giacomo Valente e Luigi Pomante (in cc). Vi scrivo per segnalarvi una questione relativa alla registrazione dei corsi di dottorato. Nel co
todoist-status:: ◼️ todoist-status:: ◼️
- [[2026-01-28]] 6 days late? IEEE Software, SW-2025-10-0161.R1 - [[2026-01-28]] 6 days late? IEEE Software, SW-2025-10-0161.R1
todoist-id:: [6frPc34wCFgXX4Rg](https://todoist.com/showTask?id=6frPc34wCFgXX4Rg) todoist-id:: [6frPc34wCFgXX4Rg](https://todoist.com/showTask?id=6frPc34wCFgXX4Rg)
todoist-project:: #Inbox todoist-project:: #💺 EditoringChairing
todoist-due:: 2026-01-28 todoist-due:: 2026-01-28
todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-01-28T05:48:37Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAii1IcIAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Here's a synthesized task description and actionable recommendations based on the email: **Task Description:** Finalize and send out the re-review for the paper "Explainer Pattern A Design Pattern for the Integration of Explanations in Code" (IEEE Software, SW-2025-10-0161.R1) to expedite its publication. **Actionable Recommendations:** * **Review and Finalize Paper:** Prof. Di Ruscio, please review the paper "Explainer Pattern A Design Pattern for the Integration of Explanations in Code" and make any necessary final adjustments. * **Send Re-review:** Once finalized, please send out the re-review of the paper. **Deadline:** * The email implies urgency, noting that three weeks have passed and a "week late is not a big deal, but it can quickly add up." While no explicit date is given, the context suggests the re-review should be completed as soon as possible. **Recommendation:** Aim to complete and send the re-review within the **next 2-3 days** to align with the implied urgency. --- 28-Jan-2026 IEEE Software, SW-2025-10-0161.R1 "Explainer Pattern A Design Pattern for the Integration of Explanations in Code" Dear Prof. Di Ruscio: Maybe a week late is not a big deal, but you really have had 3 weeks to finalize this, and it todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-01-28T05:48:37Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAii1IcIAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Here's a synthesized task description and actionable recommendations based on the email: **Task Description:** Finalize and send out the re-review for the paper "Explainer Pattern A Design Pattern for the Integration of Explanations in Code" (IEEE Software, SW-2025-10-0161.R1) to expedite its publication. **Actionable Recommendations:** * **Review and Finalize Paper:** Prof. Di Ruscio, please review the paper "Explainer Pattern A Design Pattern for the Integration of Explanations in Code" and make any necessary final adjustments. * **Send Re-review:** Once finalized, please send out the re-review of the paper. **Deadline:** * The email implies urgency, noting that three weeks have passed and a "week late is not a big deal, but it can quickly add up." While no explicit date is given, the context suggests the re-review should be completed as soon as possible. **Recommendation:** Aim to complete and send the re-review within the **next 2-3 days** to align with the implied urgency. --- 28-Jan-2026 IEEE Software, SW-2025-10-0161.R1 "Explainer Pattern A Design Pattern for the Integration of Explanations in Code" Dear Prof. Di Ruscio: Maybe a week late is not a big deal, but you really have had 3 weeks to finalize this, and it
todoist-status:: ◼️ todoist-status:: ◼️
@@ -173,3 +168,8 @@
todoist-project:: #Inbox todoist-project:: #Inbox
todoist-completed:: [[2026-01-28]] todoist-completed:: [[2026-01-28]]
todoist-status:: ✅ todoist-status:: ✅
- [[2026-01-28]] [OpenCode | The open source AI coding agent](https://opencode.ai/)
todoist-id:: [9932763374](https://todoist.com/showTask?id=9932763374)
todoist-project:: #Inbox
todoist-completed:: [[2026-01-28]]
todoist-status:: ✅
+7
View File
@@ -12,3 +12,10 @@
todoist-desc:: [https://www.overleaf.com/project/69675da0f0967462b3bd0c9d](https://www.overleaf.com/project/69675da0f0967462b3bd0c9d) [Web Link](https://outlook.office365.com/owa/?ItemID=AAkALgAAAAAAHYQDEapmEc2byACqAC%2FEWg0AjoVpQvBez0Ss5ZY2WGWEJgAIg57bhwAA&exvsurl=1&viewmodel=ReadMessageItem) Okay, heres a task description for the email “R: Aggiornamento Paper DRAMA: Nuova Metodologia e Risultati,” crafted with actionable steps, aiming to help someone understand and complete the task: **Task Title:** Finalize & Share the DRAMA Paper Update **Description:** This task focuses on finalizing the updated DRAMA paper and ensuring its presented effectively to stakeholders. It involves reviewing the document, incorporating feedback, and preparing it for distribution. **Actionable Steps:** 1. **Review the Document:** Carefully read the entire updated DRAMA paper. Pay particular attention to the section regarding [Specifically mention the key section or data point the paper focuses on - e.g., methodology, results, conclusions]. 2. **Gather Feedback:** Share the document with [Assignee - specify who needs to review it - e.g., Team Lead, Senior Analyst]. Actively solicit feedback on clarity, accuracy, and completeness. 3. **Address Feedback:** Respond to each piece of feedback received. Document all changes made based on feedback. Prioritize revisions based on the severity of the feedback. 4. **Incorporate Changes:** Implement the necessary revisions to ensure the document accurately reflects the updated methodology and results. 5. **Draft a Summary/Executive Summary:** Create a concise executive summary highlighting the key takeaways, the updated methodology, and the most significant results (approximately [Specify length e.g., 1-2 paragraphs]). 6. **Finalize & Format:** Ensure the document is properly formatted, including consistent headings, tables, figures, and citations. 7. **Prepare for Distribution:** Choose the appropriate distribution method (e.g., email, shared drive, presentation). Consider adding a brief introductory paragraph explaining the update. 8. **Proofread:** Conduct a final proofread to catch any errors before final submission. **Priority:** Medium - This task requires focused effort and attention to detail. **Due Date:** [Specify a realistic deadline e.g., End of Day Tomorrow] **Notes:** If you have any specific areas youd like me to focus on during the review, please let me know. --- **To help me refine this further and make it *even* better, could you tell me:** - **Who is the intended audience for this task?** (e.g., Team, Management, Clients?) - **What is the *specific* goal of the updated paper?** (e.g., present a new strategy, demonstrate improved efficiency, provide data insights?) todoist-desc:: [https://www.overleaf.com/project/69675da0f0967462b3bd0c9d](https://www.overleaf.com/project/69675da0f0967462b3bd0c9d) [Web Link](https://outlook.office365.com/owa/?ItemID=AAkALgAAAAAAHYQDEapmEc2byACqAC%2FEWg0AjoVpQvBez0Ss5ZY2WGWEJgAIg57bhwAA&exvsurl=1&viewmodel=ReadMessageItem) Okay, heres a task description for the email “R: Aggiornamento Paper DRAMA: Nuova Metodologia e Risultati,” crafted with actionable steps, aiming to help someone understand and complete the task: **Task Title:** Finalize & Share the DRAMA Paper Update **Description:** This task focuses on finalizing the updated DRAMA paper and ensuring its presented effectively to stakeholders. It involves reviewing the document, incorporating feedback, and preparing it for distribution. **Actionable Steps:** 1. **Review the Document:** Carefully read the entire updated DRAMA paper. Pay particular attention to the section regarding [Specifically mention the key section or data point the paper focuses on - e.g., methodology, results, conclusions]. 2. **Gather Feedback:** Share the document with [Assignee - specify who needs to review it - e.g., Team Lead, Senior Analyst]. Actively solicit feedback on clarity, accuracy, and completeness. 3. **Address Feedback:** Respond to each piece of feedback received. Document all changes made based on feedback. Prioritize revisions based on the severity of the feedback. 4. **Incorporate Changes:** Implement the necessary revisions to ensure the document accurately reflects the updated methodology and results. 5. **Draft a Summary/Executive Summary:** Create a concise executive summary highlighting the key takeaways, the updated methodology, and the most significant results (approximately [Specify length e.g., 1-2 paragraphs]). 6. **Finalize & Format:** Ensure the document is properly formatted, including consistent headings, tables, figures, and citations. 7. **Prepare for Distribution:** Choose the appropriate distribution method (e.g., email, shared drive, presentation). Consider adding a brief introductory paragraph explaining the update. 8. **Proofread:** Conduct a final proofread to catch any errors before final submission. **Priority:** Medium - This task requires focused effort and attention to detail. **Due Date:** [Specify a realistic deadline e.g., End of Day Tomorrow] **Notes:** If you have any specific areas youd like me to focus on during the review, please let me know. --- **To help me refine this further and make it *even* better, could you tell me:** - **Who is the intended audience for this task?** (e.g., Team, Management, Clients?) - **What is the *specific* goal of the updated paper?** (e.g., present a new strategy, demonstrate improved efficiency, provide data insights?)
todoist-labels:: #outlook365 todoist-labels:: #outlook365
todoist-status:: ◼️ todoist-status:: ◼️
- [[2026-02-03]] Coinvolgere gli use case partners per il deliverable D2.2
todoist-id:: [6frRcFg85GgXvvC8](https://todoist.com/showTask?id=6frRcFg85GgXvvC8)
todoist-project:: #🚀 Projects-EU-MOSAICO
todoist-due:: 2026-02-03
todoist-desc:: [Link to Logseq](logseq://graph/Logseq?block-id=697a017b-a305-447a-a844-e73f5a08fb8b)
todoist-labels:: #source_logseq
todoist-status:: ◼️
-8
View File
@@ -2377,10 +2377,6 @@
todoist-id:: [662G247F3qrWg432](https://todoist.com/showTask?id=662G247F3qrWg432) todoist-id:: [662G247F3qrWg432](https://todoist.com/showTask?id=662G247F3qrWg432)
todoist-project:: #📚 Reading list todoist-project:: #📚 Reading list
todoist-status:: ◼️ todoist-status:: ◼️
- [[No due date]] [10 things I learned from burning myself out with AI coding agents - Ars Technica](https://arstechnica.com/information-technology/2026/01/10-things-i-learned-from-burning-myself-out-with-ai-coding-agents/)
todoist-id:: [6fpWwFF9wCJXCvF8](https://todoist.com/showTask?id=6fpWwFF9wCJXCvF8)
todoist-project:: #Inbox
todoist-status:: ◼️
- [[No due date]] Read "[Shockingly Simple:"KEYS" for Better AI for SE](https://ieeexplore.ieee.org/document/9354395/)" - [[No due date]] Read "[Shockingly Simple:"KEYS" for Better AI for SE](https://ieeexplore.ieee.org/document/9354395/)"
todoist-id:: [662FQF23HWr6WH6R](https://todoist.com/showTask?id=662FQF23HWr6WH6R) todoist-id:: [662FQF23HWr6WH6R](https://todoist.com/showTask?id=662FQF23HWr6WH6R)
todoist-project:: #📚 Reading list todoist-project:: #📚 Reading list
@@ -2705,7 +2701,3 @@
todoist-project:: #🚀 Projects-EU-MOSAICO todoist-project:: #🚀 Projects-EU-MOSAICO
todoist-labels:: #deepwork #goal #logseqed todoist-labels:: #deepwork #goal #logseqed
todoist-status:: ◼️ todoist-status:: ◼️
- [[No due date]] [I didnt expect a free research engine to pair this well with NotebookLM](https://www.makeuseof.com/free-research-engine-stanford-notebooklm/)
todoist-id:: [6frPgV5gpx4pFHFg](https://todoist.com/showTask?id=6frPgV5gpx4pFHFg)
todoist-project:: #Inbox
todoist-status:: ◼️