[logseq-plugin-git:commit] 2025-06-05T08:36:10.944Z
|
After Width: | Height: | Size: 77 KiB |
|
After Width: | Height: | Size: 11 KiB |
|
After Width: | Height: | Size: 54 KiB |
|
After Width: | Height: | Size: 60 KiB |
|
After Width: | Height: | Size: 6.6 KiB |
|
After Width: | Height: | Size: 5.5 KiB |
|
After Width: | Height: | Size: 37 KiB |
@@ -0,0 +1,2 @@
|
||||
-
|
||||
-
|
||||
@@ -0,0 +1 @@
|
||||
- This is test
|
||||
@@ -0,0 +1 @@
|
||||
-
|
||||
@@ -0,0 +1 @@
|
||||
-
|
||||
@@ -0,0 +1 @@
|
||||
-
|
||||
@@ -0,0 +1 @@
|
||||
-
|
||||
@@ -0,0 +1 @@
|
||||
query-table:: false
|
||||
@@ -0,0 +1,116 @@
|
||||
- TODO [Fare check bilancio familiare](https://todoist.com/showTask?id=5260435250)
|
||||
todoistid:: 5260435250
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [Fare questione TARI ad AQ](https://todoist.com/showTask?id=6382072537)
|
||||
todoistid:: 6382072537
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [Gestione SCP Original Software Publication Special Issue](https://todoist.com/showTask?id=6481814868)
|
||||
todoistid:: 6481814868
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [Paper A domain-specific environment for engineering multi-layered IoT systems](https://todoist.com/showTask?id=6517834583)
|
||||
todoistid:: 6517834583
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [MODELS 2023 Organizing Committee](https://todoist.com/showTask?id=6549921434)
|
||||
todoistid:: 6549921434
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [Consegna SDA](https://todoist.com/showTask?id=6565013908)
|
||||
todoistid:: 6565013908
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [[Manuscript ID JSME-23-0044 now in your Reviewer Center - Journal of Software: Evolution and Process](https://mail.google.com/mail/u/0/#inbox/1867d94e5f88c367)](https://todoist.com/showTask?id=6643375943)
|
||||
todoistid:: 6643375943
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [[SoSyM] Theme Issue about predictive modeling, ML, data modeling, etc.](https://todoist.com/showTask?id=6697458379)
|
||||
todoistid:: 6697458379
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [Software: Practice and Experience - Decision on Manuscript ID SPE-22-0516](https://todoist.com/showTask?id=6703505028)
|
||||
todoistid:: 6703505028
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [Richiesta patrocini](https://todoist.com/showTask?id=6719178348)
|
||||
todoistid:: 6719178348
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [Invio documentazione](https://todoist.com/showTask?id=6728817102)
|
||||
todoistid:: 6728817102
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [MAV - Alleanza Assicurazioni S.p.A. - Polizza nr. 22097045 - ANTONIA LUCCITTI](https://todoist.com/showTask?id=6732805541)
|
||||
todoistid:: 6732805541
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [Fare conti via dei sali e zara](https://todoist.com/showTask?id=6759453199)
|
||||
todoistid:: 6759453199
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [Invio documentazione](https://todoist.com/showTask?id=6763483696)
|
||||
todoistid:: 6763483696
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [FW: Caricamento su ESSE3 dell’offerta formativa, regole di scelta e verbalizzazione esami per i Dottorati di Ricerca a partire dagli iscritti del XXXVIII ciclo. RICHIESTA DATI.](https://todoist.com/showTask?id=6765391631)
|
||||
todoistid:: 6765391631
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [Verbale](https://todoist.com/showTask?id=6766458225)
|
||||
todoistid:: 6766458225
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [GPTSniffer](https://todoist.com/showTask?id=6768674124)
|
||||
todoistid:: 6768674124
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [È disponibile la tua attestazione dei premi versati nel 2022](https://todoist.com/showTask?id=6768807887)
|
||||
todoistid:: 6768807887
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [La nuova Bolletta Web GAS del 09 aprile 2023 è online](https://todoist.com/showTask?id=6777972451)
|
||||
todoistid:: 6777972451
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [I: invito a Seminario su CULTURA DEL LAVORO NELL'UNIVERSITA' - Siena 11 maggio 2023](https://todoist.com/showTask?id=6781953349)
|
||||
todoistid:: 6781953349
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [Corsa Davide](https://todoist.com/showTask?id=6786237477)
|
||||
todoistid:: 6786237477
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [I: Seminario GEO-UniSI sulla Cultura del Lavoro - Siena 11 maggio 2023 +email](https://todoist.com/showTask?id=6788012343)
|
||||
todoistid:: 6788012343
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
- TODO [Scrivere a Mohammad](https://todoist.com/showTask?id=6789515510)
|
||||
todoistid:: 6789515510
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-14 Fri>
|
||||
-
|
||||
@@ -0,0 +1,2 @@
|
||||
-
|
||||
-
|
||||
@@ -0,0 +1,9 @@
|
||||
- {{query }}
|
||||
query-table:: true
|
||||
query-sort-by:: page
|
||||
query-sort-desc:: true
|
||||
-
|
||||
-
|
||||
-
|
||||
-
|
||||
-
|
||||
@@ -0,0 +1,7 @@
|
||||
-
|
||||
-
|
||||
-
|
||||
-
|
||||
-
|
||||
-
|
||||
-
|
||||
@@ -0,0 +1,97 @@
|
||||
- TODO [[Guarda "How to stop screwing yourself over | Mel Robbins | TEDxSF" su YouTube](https://youtu.be/Lp7E973zozc)](https://todoist.com/showTask?id=6640998252)
|
||||
todoistid:: 6640998252
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[This is the current status of my presentation. Is there any further improvement that you would propose? (attachments: Ph.D. pre-defence.pdf)](https://teams.microsoft.com/l/message/19:6412ea90-0d16-428b-8313-0798aad2c4f4_c2787b22-cc39-410e-a383-56cbdb9b69c9@unq.gbl.spaces/1677243612518?context=%7B%22contextType%22:%22chat%22%7D)](https://todoist.com/showTask?id=6647035020)
|
||||
todoistid:: 6647035020
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[L'essere umano è fatto per correre a lungo](https://www.runlovers.it/2023/lessere-umano-e-fatto-per-correre-a-lungo/)](https://todoist.com/showTask?id=6673707667)
|
||||
todoistid:: 6673707667
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[Docker Image Management](https://dev.to/waji97/docker-image-management-3558)](https://todoist.com/showTask?id=6687819360)
|
||||
todoistid:: 6687819360
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[Researchers From Stanford And DeepMind Come Up With The Idea of Using Large Language Models LLMs as a Proxy Reward Function - MarkTechPost](https://www.marktechpost.com/2023/03/08/researchers-from-stanford-and-deepmind-come-up-with-the-idea-of-using-large-language-models-llms-as-a-proxy-reward-function/)](https://todoist.com/showTask?id=6690894668)
|
||||
todoistid:: 6690894668
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[Le aziende cercano disperatamente professionalità nell’automazione industriale e nella robotica. La formazione con FANUC e la certificazione della competenza - Orizzonte Scuola Notizie](https://www.orizzontescuola.it/le-aziende-cercano-disperatamente-professionalita-nellautomazione-industriale-e-nella-robotica-la-formazione-con-fanuc-e-la-certificazione-della-competenza/)](https://todoist.com/showTask?id=6695835119)
|
||||
todoistid:: 6695835119
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[Quale sarà il destino delle auto a metano e GPL? Ecco cosa accadrà](https://www.tuttomotoriweb.it/2023/03/11/quale-sara-destino-auto-a-metano-gpl/)](https://todoist.com/showTask?id=6695835742)
|
||||
todoistid:: 6695835742
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[Cambiano le regole della residenza fiscale - ItaliaOggi.it](https://www.italiaoggi.it/news/cambiano-le-regole-della-residenza-fiscale-2596072)](https://todoist.com/showTask?id=6713220195)
|
||||
todoistid:: 6713220195
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[Nasce in Abruzzo il primo mercato regionale dei crediti fiscali per lo sblocco del Superbonus: firmata l'intesa Confindustria-Ance](https://www.ilpescara.it/economia/superbnous-ance-confindustria-creano-primo-mercato-crediti-fiscali.html)](https://todoist.com/showTask?id=6726429186)
|
||||
todoistid:: 6726429186
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[Come ricominciare a correre dopo uno stop. I consigli by LBM Sport](https://www.lbmsport.it/come-riprendere-a-correre-dopo-stop/)](https://todoist.com/showTask?id=6732679270)
|
||||
todoistid:: 6732679270
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[Superbonus e cessione del credito: tutte le novità nel Dossier della Camera](https://www.lavoripubblici.it/news/superbonus-cessione-credito-tutte-novita-dossier-camera-30734)](https://todoist.com/showTask?id=6748336635)
|
||||
todoistid:: 6748336635
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[Superbonus, cosa si deve fare per dividere la detrazione con i familiari? - la Repubblica](https://www.repubblica.it/economia/diritti-e-consumi/casa/domande-e-risposte/2023/04/02/news/superbonus_cosa_fare_per_divdere_la_detrazone_con_i_familiari-394416787/?ref=pay_amp&_gl=1*1eluoab*_ga*NjNhanY2MlBBMElyVXlHWFdkMF9ucVNjV1c2Ylg4WC1LOG9iNXJEYm5CTDJiTVNqLWY0bUNtT3l2TENCV3ZNNw..)](https://todoist.com/showTask?id=6756305915)
|
||||
todoistid:: 6756305915
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[ContrXT | A global, model-agnostic, contrastive explainer for any text classifier](http://contrxt.ai/)](https://todoist.com/showTask?id=6760459433)
|
||||
todoistid:: 6760459433
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[Enrico Nardelli on LinkedIn: The main threat chatbots pose to humans is that 𝘁𝗵𝗲𝘆 𝗲𝘅𝗵𝗶𝗯𝗶𝘁…](https://www.linkedin.com/posts/enriconardelli_the-main-threat-chatbots-pose-to-humans-is-activity-7051446024506101760-hg2x?utm_source=share&utm_medium=member_android)](https://todoist.com/showTask?id=6780533245)
|
||||
todoistid:: 6780533245
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[GPT-4 Explained and Exemplified: Eleven Ways It Might Blow Your Mind](https://medium.com/ai-tools-trends-encyclopedia/gpt-4-explained-and-exemplified-eleven-ways-it-might-blow-your-mind-1f9fed88656d?source=email-677705797934-1681262634677-digest.reader-5467ec7bcfc6-1f9fed88656d----1-99------------------32a61c8d_ff40_4c5b_b796_1e9596bcc13d-1)](https://todoist.com/showTask?id=6784003204)
|
||||
todoistid:: 6784003204
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[Maratona di Ibiza 2023 | divertimento, salite e discese](https://www.youtube.com/watch?v=iwiMCCU8y7A)](https://todoist.com/showTask?id=6786985081)
|
||||
todoistid:: 6786985081
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[Sonno e sport: 5 consigli per dormire bene](https://channel.endu.net/wellfit/sonno-e-sport-5-consigli-per-dormire-bene/?utm_source=newsletter&utm_medium=email&utm_campaign=editoriale)](https://todoist.com/showTask?id=6799761927)
|
||||
todoistid:: 6799761927
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [[toeverything/AFFiNE: There can be more than Notion and Miro. AFFiNE is a next-gen knowledge base that brings planning, sorting and creating all together. Privacy first, open-source, customizable and ready to use.](https://github.com/toeverything/AFFiNE)](https://todoist.com/showTask?id=6808730956)
|
||||
todoistid:: 6808730956
|
||||
attachment::
|
||||
comments::
|
||||
- TODO [Borsa del Placement | XVII Forum 9-10 maggio | Credenziali di accesso al portale](https://todoist.com/showTask?id=6811278970)
|
||||
todoistid:: 6811278970
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-24 Mon>
|
||||
- TODO [Re: models23workshops notification for proposal 3](https://todoist.com/showTask?id=6812012007)
|
||||
todoistid:: 6812012007
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-24 Mon>
|
||||
- TODO [Notifica emissione Bolletta Digitale Gas di CELANO](https://todoist.com/showTask?id=6812112020)
|
||||
todoistid:: 6812112020
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-24 Mon>
|
||||
- TODO [Lowcomote: Rimborso costi meeting settembre L'Aquila](https://todoist.com/showTask?id=6812274260)
|
||||
todoistid:: 6812274260
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-24 Mon>
|
||||
- TODO [Re: models23workshops notification for proposal 3](https://todoist.com/showTask?id=6816302800)
|
||||
todoistid:: 6816302800
|
||||
attachment::
|
||||
comments::
|
||||
DEADLINE: <2023-04-24 Mon>
|
||||
@@ -0,0 +1,7 @@
|
||||
- #.tabular
|
||||
- ### 🗒️Notes
|
||||
- 
|
||||
- ### 📜Reviews
|
||||
- {{query (and [[REVIEWS]] (or (property :date-end [[22-04-2025]]) (property :date-start [[22-04-2025]]) (property :date-submitted [[22-04-2025]])))}}
|
||||
query-table:: true
|
||||
query-properties:: [:file :year :venue :deadline]
|
||||
@@ -0,0 +1,7 @@
|
||||
- #.tabular
|
||||
- ### 🗒️Notes
|
||||
- 
|
||||
- ### 📜Reviews
|
||||
- {{query (and [[REVIEWS]] (or (property :date-end [[09-05-2025]]) (property :date-start [[09-05-2025]]) (property :date-submitted [[09-05-2025]])))}}
|
||||
query-table:: true
|
||||
query-properties:: [:file :year :venue :deadline]
|
||||
@@ -0,0 +1,3 @@
|
||||
title:: #areas
|
||||
|
||||
-
|
||||
@@ -0,0 +1,3 @@
|
||||
title:: #meetings
|
||||
|
||||
-
|
||||
@@ -0,0 +1,3 @@
|
||||
title:: #todoist
|
||||
|
||||
-
|
||||
@@ -0,0 +1,5 @@
|
||||
title:: #type
|
||||
|
||||
-
|
||||
-
|
||||
-
|
||||
@@ -0,0 +1,3 @@
|
||||
title:: .v-kanban
|
||||
|
||||
-
|
||||
@@ -0,0 +1 @@
|
||||
-
|
||||
@@ -0,0 +1,16 @@
|
||||
full-title:: 02-16-JSSOFTWARE-D-23-01182
|
||||
author:: He, Xiao
|
||||
year::
|
||||
icon:: 📚
|
||||
template:: CITATION-MANAGER
|
||||
|
||||
- *02-16-JSSOFTWARE-D-23-01182*. .
|
||||
- He, Xiao, .
|
||||
- Abstract:
|
||||
- Model-driven development is a model-centric software development paradigm that automates the development process by converting high-level models into low-level code and documents. To maintain synchronization between models and code/documents—which can evolve independently—this paper introduces BIT, a bidirectional language that can serve as a conventional template language for model-to-text transformations. However, a BIT program can function as both a printer, generating text by filling template holes with values from the input model, and a parser, putting parsed values back into the model. BIT comprises a surface language for better usability and a core language for formal definition. We define the semantics of the core language based on the theory of bidirectional transformation, and provide the translation from the surface to the core. We present the proof sketch of the well behavedness of BIT as a formal evidence of soundness. We also conduct two preliminary case studies to empirically demonstrate the expressiveness of BIT. Based on the proof and the case studies, BIT covers the major features of existing template languages, and offers sufficient expressiveness to define real-world model-to-text transformations that can be executed bidirectionally and incrementally.
|
||||
- Notes
|
||||
- undefined
|
||||
-
|
||||
- Uses the filetemplate format to add *all file attachments in the form of a link for example*
|
||||
- This template supports more fields like , and he0216JSSOFTWARED23011822024
|
||||
-
|
||||
@@ -0,0 +1,8 @@
|
||||
tags:: [[⛔ No INSPIRE recid found]], [[#zotero]]
|
||||
title:: @02-23-TOSEM-2024-0012.pdf
|
||||
item-type:: [[document]]
|
||||
original-title:: 02-23-TOSEM-2024-0012.pdf
|
||||
links:: [Local library](zotero://select/library/items/BCYRLKCX), [Web library](https://www.zotero.org/users/1039502/items/BCYRLKCX)
|
||||
|
||||
- ### Attachments
|
||||
- [02-23-TOSEM-2024-0012.pdf](zotero://select/library/items/I879APBF) {{zotero-imported-file I879APBF, "02-23-TOSEM-2024-0012.pdf"}}
|
||||
@@ -0,0 +1,9 @@
|
||||
tags:: [[#zotero]]
|
||||
title:: @02-29-TOSEM-2023-0413_Proof_hi.pdf
|
||||
item-type:: [[document]]
|
||||
original-title:: 02-29-TOSEM-2023-0413_Proof_hi.pdf
|
||||
links:: [Local library](zotero://select/library/items/LRSE8UD5), [Web library](https://www.zotero.org/users/1039502/items/LRSE8UD5)
|
||||
|
||||
-
|
||||
- ### Attachments
|
||||
- [02-29-TOSEM-2023-0413_Proof_hi.pdf](zotero://select/library/items/IDLWYMWL) {{zotero-imported-file IDLWYMWL, "02-29-TOSEM-2023-0413_Proof_hi.pdf"}}
|
||||
@@ -0,0 +1,17 @@
|
||||
links:: [Local library](zotero://select/library/items/54CMGLGM), [Web library](https://www.zotero.org/users/1039502/items/54CMGLGM)
|
||||
library-catalog:: Crossref
|
||||
authors:: Lorenzo Bettini, Davide Di Ruscio, Ludovico Iovino, Alfonso Pierantonio
|
||||
publication-title:: IEEE Access
|
||||
url:: http://ieeexplore.ieee.org/xpl/RecentIssue.jsp?punumber=6287639
|
||||
language:: en
|
||||
original-title:: Quality-driven Detection and Resolution of Metamodel Smells
|
||||
item-type:: [[magazineArticle]]
|
||||
volume:: 7
|
||||
pages:: 16364-16376
|
||||
title:: @11697_132211
|
||||
issn:: 2169-3536
|
||||
date:: 2019
|
||||
tags:: #duplicate-citation-key, Analytical models, Companies, Computer Science (all), Containers, Customer relationship management, Domain-specific languages, Edelta language, Engineering (all), Materials Science (all), Object oriented modeling, Quality assurance, Software, domain-specific languages, formal specification, maintainability, metamodel design, metamodel smells resolution, model-driven engineering, quality-driven detection, reusability, software development practice, software metrics, software quality, software quality engineering, systems analysis, understandability, #read
|
||||
|
||||
- [[Abstract]]
|
||||
- In Model Driven Engineering (MDE), analogously to any software development practice, metamodel design must be accurate and performed by considering relevant quality factors including maintainability, reusability, and understandability. The quality of metamodels might be compromised by the introduction of smells that can be the result of inappropriate design decisions. Detecting and resolving metamodel smells is a complex task. Existing approaches deal with this problem by supporting the identification and resolution of smells without providing the means to explicitly trace them with the quality attributes that can be potentially affected. In this paper, we present an approach to defining extensible catalogues of metamodel smells. Each smell can be linked to corresponding quality attributes. Such links are exploited to automatically select only those smells that have to be necessarily resolved for enhancing the quality factors that are of interest for the modeler. The implementation of the approach is based on the Edelta language and it has been validated on a corpus of metamodels retrieved from a publicly available repository.
|
||||
@@ -0,0 +1,15 @@
|
||||
tags:: [[readingnotes]]
|
||||
title:: @A Metric Recommendation Service for Online Systems using Graph Learning
|
||||
pages:: 12
|
||||
item-type:: [[journalArticle]]
|
||||
original-title:: A Metric Recommendation Service for Online Systems using Graph Learning
|
||||
language:: en
|
||||
authors:: [[Anonymous Author]]
|
||||
library-catalog:: Zotero
|
||||
links:: [Local library](zotero://select/library/items/8FULMW4R), [Web library](https://www.zotero.org/users/1039502/items/8FULMW4R)
|
||||
|
||||
-
|
||||
- [[Abstract]]
|
||||
- Today’s monitoring and failure management mechanisms for online systems heavily rely on metrics, which are time series data that can describe the real-time state of a system from various perspectives. Though several attempts have been devoted to automatic failure management based on metrics, the primary step, metric selection, remains manual to a large extent. To better understand the prior practice, we conduct an empirical study on the selected metrics in prior work and obtain some findings. Based on the findings, we develop a metric recommendation service for online systems, which can automate the metrics selection practice and greatly ease the burden in managing an online system. Specifically, we analyze the needs of two key failure management tasks, i.e., anomaly detection and fault diagnosis, and design metric recommendation mechanisms for them respectively. Graph learning techniques are employed in the automation of metric recommendation. Our experiments demonstrate that the proposed approach can achieve an F1score of 0.912 in selecting metrics for anomaly detection, and an accuracy of 0.859 in retrieving metrics for faults diagnosis, which significantly outperforms the compared baselines.
|
||||
- [[Attachments]]
|
||||
- [Author - A Metric Recommendation Service for Online Systems.pdf](zotero://select/library/items/CVQ64RBK) {{zotero-imported-file CVQ64RBK, "Author - A Metric Recommendation Service for Online Systems.pdf"}}
|
||||
@@ -0,0 +1,23 @@
|
||||
tags:: [[#readingnotes]]
|
||||
date:: [[31-07-2022]]
|
||||
issn:: "0360-0300, 1557-7341"
|
||||
issue:: 6
|
||||
doi:: 10.1145/3457607
|
||||
title:: @A Survey on Bias and Fairness in Machine Learning
|
||||
pages:: 1-35
|
||||
volume:: 54
|
||||
item-type:: [[journalArticle]]
|
||||
access-date:: 2023-02-18T07:10:49Z
|
||||
original-title:: A Survey on Bias and Fairness in Machine Learning
|
||||
language:: en
|
||||
url:: https://dl.acm.org/doi/10.1145/3457607
|
||||
publication-title:: ACM Computing Surveys
|
||||
journal-abbreviation:: ACM Comput. Surv.
|
||||
authors:: [[Ninareh Mehrabi]], [[Fred Morstatter]], [[Nripsuta Saxena]], [[Kristina Lerman]], [[Aram Galstyan]]
|
||||
library-catalog:: DOI.org (Crossref)
|
||||
links:: [Local library](zotero://select/library/items/8LT96USW), [Web library](https://www.zotero.org/users/1039502/items/8LT96USW)
|
||||
|
||||
- [[Abstract]]
|
||||
- With the widespread use of artificial intelligence (AI) systems and applications in our everyday lives, accounting for fairness has gained significant importance in designing and engineering of such systems. AI systems can be used in many sensitive environments to make important and life-changing decisions; thus, it is crucial to ensure that these decisions do not reflect discriminatory behavior toward certain groups or populations. More recently some work has been developed in traditional machine learning and deep learning that address such challenges in different subdomains. With the commercialization of these systems, researchers are becoming more aware of the biases that these applications can contain and are attempting to address them. In this survey, we investigated different real-world applications that have shown biases in various ways, and we listed different sources of biases that can affect AI applications. We then created a taxonomy for fairness definitions that machine learning researchers have defined to avoid the existing bias in AI systems. In addition to that, we examined different domains and subdomains in AI showing what researchers have observed with regard to unfair outcomes in the state-of-the-art methods and ways they have tried to address them. There are still many future directions and solutions that can be taken to mitigate the problem of bias in AI systems. We are hoping that this survey will motivate researchers to tackle these issues in the near future by observing existing work in their respective fields.
|
||||
- [[Attachments]]
|
||||
- [Mehrabi et al. - 2022 - A Survey on Bias and Fairness in Machine Learning.pdf](zotero://select/library/items/VHPDAFE3) {{zotero-imported-file VHPDAFE3, "Mehrabi et al. - 2022 - A Survey on Bias and Fairness in Machine Learning.pdf"}}
|
||||
@@ -0,0 +1,23 @@
|
||||
tags:: [[readingnotes]]
|
||||
date:: 10/2019
|
||||
issn:: 09204105
|
||||
doi:: 10.1016/j.petrol.2019.106223
|
||||
title:: @A realistic and public dataset with rare undesirable real events in oil wells
|
||||
pages:: 106223
|
||||
volume:: 181
|
||||
item-type:: [[journalArticle]]
|
||||
access-date:: 2022-09-12T09:25:02Z
|
||||
original-title:: A realistic and public dataset with rare undesirable real events in oil wells
|
||||
language:: en
|
||||
url:: [Redirecting](https://linkinghub.elsevier.com/retrieve/pii/S0920410519306357)
|
||||
publication-title:: Journal of Petroleum Science and Engineering
|
||||
journal-abbreviation:: Journal of Petroleum Science and Engineering
|
||||
authors:: [[Ricardo Emanuel Vaz Vargas]], [[Celso José Munaro]], [[Patrick Marques Ciarelli]], [[André Gonçalves Medeiros]], [[Bruno Guberfain do Amaral]], [[Daniel Centurion Barrionuevo]], [[Jean Carlos Dias de Araújo]], [[Jorge Lins Ribeiro]], [[Lucas Pierezan Magalhães]]
|
||||
library-catalog:: DOI.org (Crossref)
|
||||
links:: [Local library](zotero://select/library/items/942VATWM), [Web library](https://www.zotero.org/users/1039502/items/942VATWM)
|
||||
|
||||
-
|
||||
- [[Abstract]]
|
||||
- Detection of undesirable events in oil and gas wells can help prevent production losses, environmental accidents, and human casualties and reduce maintenance costs. The scarcity of measurements in such processes is a drawback due to the low reliability of instrumentation in such hostile environments. Another issue is the absence of adequately structured data related to events that should be detected. To contribute to providing a priori knowledge about undesirable events for diagnostic algorithms in offshore naturally flowing wells, this work presents an original and valuable dataset with instances of eight types of undesirable events characterized by eight process variables. Many hours of expert work were required to validate historical instances and to produce simulated and hand-drawn instances that can be useful to distinguish normal and abnormal actual events under different operating conditions. The choices made during this dataset's preparation are described and justified, and specific benchmarks that practitioners and researchers can use together with the published dataset are defined. This work has resulted in two relevant contributions. A challenging public dataset that can be used as a benchmark for the development of (i) machine learning techniques related to inherent difficulties of actual data, and (ii) methods for specific tasks associated with detecting and diagnosing undesirable events in offshore naturally flowing oil and gas wells. The other contribution is the proposal of the defined benchmarks.
|
||||
- [[Attachments]]
|
||||
- [Vargas et al. - 2019 - A realistic and public dataset with rare undesirab.pdf](zotero://select/library/items/55NCB7H3) {{zotero-imported-file 55NCB7H3, "Vargas et al. - 2019 - A realistic and public dataset with rare undesirab.pdf"}}
|
||||
@@ -0,0 +1,10 @@
|
||||
date:: 2018
|
||||
proceedings-title:: Proceedings of the 21st ACM/IEEE International Conference on Model Driven Engineering Languages and Systems: Companion Proceedings
|
||||
isbn:: 978-1-4503-5965-8
|
||||
doi:: 10.1145/3270112.3270123
|
||||
title:: @A tool for automatically selecting optimal model transformation chains
|
||||
pages:: 2–6
|
||||
item-type:: [[conferencePaper]]
|
||||
original-title:: A tool for automatically selecting optimal model transformation chains
|
||||
authors:: [[Francesco Basciani]], [[Davide Di Ruscio]], [[Mattia D'Emidio]], [[Daniele Frigioni]], [[Alfonso Pierantonio]], [[Ludovico Iovino]]
|
||||
links:: [Local library](zotero://select/library/items/R5BXSMS8), [Web library](https://www.zotero.org/users/1039502/items/R5BXSMS8)
|
||||
@@ -0,0 +1,26 @@
|
||||
filters:: {}
|
||||
links:: [Local library](zotero://select/library/items/APELNAAU), [Web library](https://www.zotero.org/users/1039502/items/APELNAAU)
|
||||
library-catalog:: DOI.org (Crossref)
|
||||
authors:: Sagar Sunkle, Krati Saxena, Ashwini Patil, Vinay Kulkarni
|
||||
journal-abbreviation:: Softw Syst Model
|
||||
publication-title:: Software and Systems Modeling
|
||||
short-title:: AI-driven streamlined modeling
|
||||
url:: [AI-driven streamlined modeling: experiences and lessons learned from multiple domains | SpringerLink](https://link.springer.com/10.1007/s10270-022-00982-6)
|
||||
language:: en
|
||||
original-title:: AI-driven streamlined modeling: experiences and lessons learned from multiple domains
|
||||
access-date:: 2022-05-24T07:35:08Z
|
||||
item-type:: [[journalArticle]]
|
||||
volume:: 21
|
||||
pages:: 1-23
|
||||
title:: @AI-driven streamlined modeling: experiences and lessons learned from multiple domains
|
||||
doi:: 10.1007/s10270-022-00982-6
|
||||
issue:: 3
|
||||
issn:: "1619-1366, 1619-1374"
|
||||
date:: 06/2022
|
||||
tags:: #Highlights
|
||||
|
||||
-
|
||||
- [[Attachments]]
|
||||
- [Sunkle et al_2022_AI-driven streamlined modeling.pdf](https://link.springer.com/content/pdf/10.1007/s10270-022-00982-6.pdf) {{zotero-imported-file JYMT5I49, "Sunkle et al_2022_AI-driven streamlined modeling.pdf"}}
|
||||
-
|
||||
-
|
||||
@@ -0,0 +1,245 @@
|
||||
tags:: [[#zotero]]
|
||||
title:: @Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry
|
||||
item-type:: [[document]]
|
||||
original-title:: Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry
|
||||
links:: [Local library](zotero://select/library/items/D8QZHVUG), [Web library](https://www.zotero.org/users/1039502/items/D8QZHVUG)
|
||||
|
||||
-
|
||||
- ### Attachments
|
||||
-
|
||||
-
|
||||
- ### Notes
|
||||
- # Annotazioni
|
||||
(12/3/2024, 21:51:28)
|
||||
|
||||
- “Low-Code Adoption for Advancing Digitalization” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 11) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “Construction Industr” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 11) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “optimization of processes” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 11) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “digitalization in a variety of industrial scenarios” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 11) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “there is a lack of scholarly research analysing how the low-code technology paradigm can support digitalization in the construction sector” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 11) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “The objective of this research project is therefore to address the critical organizational and technical barriers to fill current research gaps and derive practical insights to advance low-code technology in construction organizations.” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 11) #a28ae5
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “RQ1) What are the organizational pre-requisites to ensure low-code scalability in the context of a construction enterprise?” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 11) #a28ae5
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “RQ2) How low-code technology can be integrated with Building Information Modelling (BIM)?” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 11) #ffd400
|
||||
*Why is BIM of interest here? *
|
||||
|
||||
|
||||
|
||||
- “this research will contribute to the body of knowledge in a relatively new field of research by structurally addressing prevailing knowledge gaps and delineating areas for further research” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 11) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “By optimizing resource utilization and streamlining processes, digitalization in the construction industry becomes fundamental to improve overall productivity and support the delivery of a sustainable built environment” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 11) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “inadequate understanding of operations” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 11) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “ow-code technology emerges as a new Information Technology (IT) paradigm having the potential to bridge the gap between technology development and operations.” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 12) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “supporting rapid development of customer-facing applications, requiring minimal hand-coding and enabling productive new development practices” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 12) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “This “democratization” in technology development allows increased participation of subject/domain experts in technology development, facilitating the development process, and ensuring that the final solution meets the requirements of people and their processes” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 12) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “5 to 10 times faster than traditional programming” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 12) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “technical limitations such restricted customization options” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 12) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “Low-code research in industrial setups highlight the need for further research in low-code integration with Industry 4.0, Internet of Things, and Digital Twin” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 12) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “organizational and strategical aspects surrounding the introduction of low-code in corporate environments” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 12) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “organizations need standard processes to channel best practices and guidelines to improve consistency, compliance, and governance throughout the enterprise” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 12) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “70% of business applications will be developed using some sort of low-code technology [27] with the number of “citizen developers” largely surpassing the number of professional developers” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 12) #a28ae5
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “by enabling people closer to construction operations to independently develop digita l solutions, low-code could facilitate the digitalization of a variety of construction processes which are currently run using pen and paper” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 13) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “here is a critical contextual gap and a lack of scholarly research analysing how the low-code technology paradigm can support digitalization in the construction sector” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 13) #ffd400
|
||||
*What are the challenges in the construction sector? What are the issues that are critical and that require the introduction of low-code technologies? *
|
||||
|
||||
|
||||
|
||||
- “through 3 scholarly articles” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 13) #a28ae5
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “This includes the results of a survey to the construction professionals involved in the case studies to understand to what extent low-code benefits and limitations identified in previous literature resonate to them.” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 13) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “This potential derives from the pivotal role of low-code in bridging the gap between development and operations, empowering individuals with expertise in construction processes and operations to actively engage in the development process” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 13) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “applicant's research results allowed the identification of critical limitations and research gaps essential for a broader understanding of low-code in the construction industry” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 14) #ffd400
|
||||
*What are such critical limitations? The construction domain is a critical one requiring deep expertise. How can you put "citizen developer" in a such a critical domain? This is not clear! *
|
||||
|
||||
|
||||
|
||||
- “Area 1: Organizational/strategical - RQ 1: What are the organizational pre-requisites to ensure low-code scalability in the context of a construction enterprise?” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 14) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “Consequently, understanding the essential competencies of a "citizen developer" within the construction industry context becomes critical to expedite low-code” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 14) #ffd400
|
||||
*What does it mean? *
|
||||
|
||||
|
||||
|
||||
- “low-code, particularly in project-based industries like construction” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 14) #ffd400
|
||||
*What's the practical implication for this? *
|
||||
|
||||
|
||||
|
||||
- “there is no studies addressing these research gaps in the construction industry” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 14) #ffd400
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “RQ 2: How low -code technology can be integrated with Building Information Modelling (BIM)” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 14) #ffd400
|
||||
*Before the HOW I would have preferred to read WHY. *
|
||||
|
||||
|
||||
|
||||
- “BIM stands out as the most relevant technology supporting technical activities and collaboration during design, construction, and maintenance of the built assets, and it is cornerstone for Construction industry 4.0” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 14) #ffd400
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “low-code interoperability with BIM is the critical first step to streamline BIM processes and leverage the integrated utility of these technologies on the field.” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 14) #ffd400
|
||||
*What does it mean? I think it is necessary an example!!!! The discussion so far has been vague. *
|
||||
|
||||
|
||||
|
||||
- “intersection” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 15) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “construction digitalization” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 15) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “low-code” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 15) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “Nevertheless, the results of this inquiry were not conclusive, as we discovered the emerging nature of low-code technology and that the current development of research still does not provide answer to the several gaps we realized” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 15) #ffd400
|
||||
*What are the gaps you are referring to? *
|
||||
|
||||
|
||||
|
||||
- “a) Introducing and pioneering the use of low-code to the construction industry” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 15) #ffd400
|
||||
*Already said! *
|
||||
|
||||
|
||||
|
||||
- “Nevertheless, further research in the areas proposed in this project is critical to find alternatives to address prevailing gaps to expand scientific knowledge about how this technology can foster a holistic digital transformation in the construction sector” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 15) #ffd400
|
||||
*The proposal contains many sentences like this that are vague and they are not precise in presenting the problems and the issues that the applicant aims at solving with this project proposal. In other words so far the project has not presented the problem clearly. *
|
||||
|
||||
|
||||
|
||||
- “in the context of a construction enterprise” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 15) #ffd400
|
||||
*Concerning this considered application domain I have the following question:
|
||||
|
||||
- why such a domain requires the usage of low-code platforms?
|
||||
- what are the criticalities of currently available systems that instead should be replaced by low-code platforms?
|
||||
- why it makes sense and it is really doable considering "citizen-developers" in the building construction domain? *
|
||||
|
||||
|
||||
|
||||
- “to understand the available knowledge about organizational and strategical considerations for low-code implementation” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 16) #ffd400
|
||||
*Some preliminary result of this study are required to justify and support the project proposal. *
|
||||
|
||||
|
||||
|
||||
- “Develop a technical solution to facilitate data interoperability between low -code databases and Industry Foundation Classes (IFC) schema in BIM models (e.g., via low-code development platform connectors or Application Programming Interfaces) [45].” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 17) #ffd400
|
||||
*It's not clear what the project aims at producing. Is it a study? Is it a software platform / framework? Is it a set of reusable components? What is the goal of the proposed technical solution? *
|
||||
|
||||
|
||||
|
||||
- “use cases where low-code can be integrated with BIM” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 17) #ffd400
|
||||
*It seems that is something completely new and the applicant has to evaluate if and how the integration of low-code platforms with BIM make sense. The kind of integration that is expected is not clear at all. *
|
||||
|
||||
|
||||
|
||||
- “A representative use case will be selected for the development serving as a baseline to derive the requirements of the technical system.” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 17) #5fb236
|
||||
* *
|
||||
|
||||
|
||||
|
||||
- “Validated technical solution” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 18) #ffd400
|
||||
*Which technical solution? *
|
||||
|
||||
|
||||
|
||||
- “construction sites in Chile” (“Addressing Organizational and Technical Barriers in Low-Code Adoption for Advancing Digitalization in the Construction Industry”, p. 26) #5fb236
|
||||
* *
|
||||
@@ -0,0 +1,18 @@
|
||||
links:: [Local library](zotero://select/library/items/VJ3PSVJB), [Web library](https://www.zotero.org/users/1039502/items/VJ3PSVJB)
|
||||
library-catalog:: Zotero
|
||||
authors:: Phuong T Nguyen, Claudio Di Sipio, Juri Di Rocco, Davide Di Ruscio
|
||||
language:: en
|
||||
original-title:: Adversarial Attacks to API Recommender Systems: Time to Wake Up and Smell the Coffee?
|
||||
item-type:: [[journalArticle]]
|
||||
pages:: 13
|
||||
title:: @Adversarial Attacks to API Recommender Systems: Time to Wake Up and Smell the Coffee?
|
||||
tags:: #Highlights
|
||||
|
||||
-
|
||||
- [[Abstract]]
|
||||
- Recommender systems in software engineering provide developers with a wide range of valuable items to help them complete their tasks. Among others, API recommender systems have gained momentum in recent years as they became more successful at suggesting API calls or code snippets. While these systems have proven to be effective in terms of prediction accuracy, there has been less attention for what concerns such recommenders’ resilience against adversarial attempts. In fact, by crafting the recommenders’ learning material, e.g., data from large open-source software (OSS) repositories, hostile users may succeed in injecting malicious data, putting at risk the software clients adopting API recommender systems. In this paper, we present an empirical investigation of adversarial machine learning techniques and their possible influence on recommender systems. The evaluation performed on three state-of-the-art API recommender systems reveals a worrying outcome: all of them are not immune to malicious data. The obtained result triggers the need for effective countermeasures to protect recommender systems against hostile attacks disguised in training data.
|
||||
- [[Attachments]]
|
||||
- [Nguyen et al. - Adversarial Attacks to API Recommender Systems Ti.pdf](zotero://select/library/items/MZXKUC9V) {{zotero-imported-file MZXKUC9V, "Nguyen et al. - Adversarial Attacks to API Recommender Systems Ti.pdf"}}
|
||||
- Literature analysis
|
||||
- ((631a1a3a-2e2b-4edb-b6bd-80ef23b673d8))
|
||||
- To achieve a good trade-off between the coverage of existing approaches on ML techniques and tools for MDE, we defined the search strategy by answering the following four w-questions (which, where, what, and when).
|
||||
@@ -0,0 +1,28 @@
|
||||
tags:: [[GOAL_Model-Classification]], [[TECHNIQUE_K-NEAREST-NEIGHBORS]], [[notion]], [[#readingnotes]]
|
||||
date:: 2016
|
||||
publisher:: Springer International Publishing
|
||||
place:: Cham
|
||||
isbn:: 978-3-319-39695-8 978-3-319-39696-5
|
||||
title:: @Automated Clustering of Metamodel Repositories
|
||||
book-title:: Advanced Information Systems Engineering
|
||||
pages:: 342-358
|
||||
volume:: 9694
|
||||
item-type:: [[bookSection]]
|
||||
access-date:: 2022-05-10T08:08:32Z
|
||||
original-title:: Automated Clustering of Metamodel Repositories
|
||||
language:: en
|
||||
url:: https://link.springer.com/10.1007/978-3-319-39696-5_21
|
||||
authors:: [[Francesco Basciani]], [[Juri Di Rocco]], [[Davide Di Ruscio]], [[Ludovico Iovino]], [[Alfonso Pierantonio]]
|
||||
library-catalog:: DOI.org (Crossref)
|
||||
links:: [Local library](zotero://select/library/items/KQUTJIG9), [Web library](https://www.zotero.org/users/1039502/items/KQUTJIG9)
|
||||
|
||||
- [[Abstract]]
|
||||
- Over the last years, several model repositories have been proposed in response to the need of the MDE community for advanced systems supporting the reuse of modeling artifacts. Modelers can interact with MDE repositories with different intents ranging from merely repository browsing, to searching specific artifacts satisfying precise requirements. The organization and browsing facilities provided by current repositories is limited since they do not produce structured overviews of the contained artifacts, and the categorization mechanisms (if any) are based on manual activities. When dealing with large numbers of modeling artifacts, such limitations increase the effort related to both managing and reusing artifacts stored in model repositories.
|
||||
- [[Attachments]]
|
||||
- [Notion](notion://www.notion.so/Basciani-et-al-2016-17f7f940205246c2b2040be27847c263)
|
||||
- [Basciani et al_2016_Automated Clustering of Metamodel Repositories.pdf](zotero://select/library/items/WLW2T8BS) {{zotero-imported-file WLW2T8BS, "Basciani et al_2016_Automated Clustering of Metamodel Repositories.pdf"}}
|
||||
- ### Highlights
|
||||
- ((632b2fc3-5398-4a1c-bc53-4bc332384cca))
|
||||
- important #clustering
|
||||
-
|
||||
-
|
||||
@@ -0,0 +1,10 @@
|
||||
links:: [Local library](zotero://select/library/items/L3KC5YK9), [Web library](https://www.zotero.org/users/1039502/items/L3KC5YK9)
|
||||
authors:: Phuong T. Nguyen, Juri Di Rocco, Riccardo Rubei, Davide Di Ruscio
|
||||
original-title:: CrossSim: Exploiting Mutual Relationships to Detect Similar OSS Projects
|
||||
item-type:: [[conferencePaper]]
|
||||
pages:: 388–395
|
||||
title:: @CrossSim: Exploiting Mutual Relationships to Detect Similar OSS Projects
|
||||
doi:: 10.1109/SEAA.2018.00069
|
||||
isbn:: 978-1-5386-7383-6
|
||||
proceedings-title:: 44th Euromicro Conference on Software Engineering and Advanced Applications
|
||||
date:: 2018
|
||||
@@ -0,0 +1,125 @@
|
||||
type:: [[REVIEWS]]
|
||||
tags::
|
||||
year:: 2022
|
||||
venue:: [[ASE-AE]]
|
||||
full-title:: CrystalBLEU: Precisely and Efficiently Measuring the Similarity of Code
|
||||
date-start::
|
||||
date-submitted::
|
||||
external-links:: [ASE'22 Artifacts](https://ase22artifacts.hotcrp.com/paper/6)
|
||||
status:: [[DONE]]
|
||||
deadline-submission::
|
||||
file:: 
|
||||
|
||||
- [[Highlights]]
|
||||
- [[Comments]]
|
||||
- [[REVIEWS/Notes]]
|
||||
- ### Abstract
|
||||
- Recent years have brought a surge of work on predicting pieces of source code, e.g., for code completion, code migration, program repair, or translating natural language into code. All this work faces the challenge of evaluating the quality of a prediction w.r.t. some oracle, typically in the form of a reference solution. A common evaluation metric is the BLEU score, an n-gram-based metric originally proposed for evaluating natural language translation, but adopted in software engineering because it can be easily computed on any programming language and enables automated evaluation at scale. However, a key difference between natural and programming languages is that in the latter, completely unrelated pieces of code may have many common n-grams simply because of the syntactic verbosity and coding conventions of programming languages. We observe that these trivially shared n-grams hamper the ability of the metric to distinguish between truly similar code examples and code examples that are merely written in the same language. This paper presents CrystalBLEU, an evaluation metric based on BLEU, that allows for precisely and efficiently measuring the similarity of code. Our metric preserves the desirable properties of BLEU, such as being language-agnostic, able to handle incomplete or partially incorrect code, and efficient, while reducing the noise caused by trivially shared n-grams. We evaluate CrystalBLEU on two datasets from prior work and on a new, labeled dataset of semantically equivalent programs. Our results show that CrystalBLEU can distinguish similar from dissimilar code examples 1.9–4.5 times more effectively, when compared to the original BLEU score and a previously proposed variant of BLEU for code.
|
||||
-
|
||||
- ((63063e31-2f9f-4a2b-9308-d98c5c9b71d3))
|
||||
- ((63064327-6edb-4a1d-9e22-12f553aa941f))
|
||||
- ((63063e49-ec06-4fb1-8a5f-567100bf353e))
|
||||
-
|
||||
- ### CFPs
|
||||
collapsed:: true
|
||||
- ### [Badges for Papers Published at ASE 2022](https://conf.researchr.org/track/ase-2022/ase-2022-artifact-evaluation#badges-for-papers-published-at-ase-2022)
|
||||
- Authors of papers accepted in any of the tracks of ASE 2022 may submit artifacts associated with those papers to the ASE Artifact Track. Submitted artifacts will receive one of the following badges:
|
||||
- **Available**
|
||||
- 
|
||||
- ---
|
||||
- Open Research Objects (ORO)
|
||||
- Placed on a publicly accessible archival repository. A DOI or link to this persistent repository along with a unique identifier for the object is provided. Artifacts have not been formally evaluated.
|
||||
- **Reusable**
|
||||
- 
|
||||
- ---
|
||||
- Research Objects Reviewed (ROR)
|
||||
- Available + Artifacts are very carefully documented and well-structured, consistent, complete, exercisable, and include appropriate evidence of verification and validation to the extent that reuse and repurposing is facilitated. In particular, norms and standards of the research community for artifacts of this type are strictly adhered to.
|
||||
- Papers with such badges contain reusable products that other researchers can use to bootstrap their own research. Experience shows that such papers earn increased citations and greater prestige in the research community. Artifacts of interest include (but are not limited to) the following.
|
||||
- Software, which are implementations of systems or algorithms potentially useful in other studies.
|
||||
- Data repositories, which are data (e.g., logging data, system traces, survey raw data) that can be used for multiple software engineering approaches.
|
||||
- Frameworks, which are tools and services illustrating new approaches to software engineering that could be used by other researchers in different contexts.
|
||||
- This list is not exhaustive, so the authors are asked to email the chairs before submitting if their proposed artifact is not on this list.
|
||||
- ### [Badges for Reproduced and Replicated Papers](https://conf.researchr.org/track/ase-2022/ase-2022-artifact-evaluation#badges-for-reproduced-and-replicated-papers)
|
||||
- Authors of any prior SE work (published at any previous ASE or other SE venue) may submit an artifact for evaluation as a candidate replicated or reproduced.
|
||||
- Reproduced
|
||||
- 
|
||||
- ---
|
||||
- Results Reproduced (ROR-R)
|
||||
- The main results of the paper have been obtained in a subsequent study by a person or team other than the authors, using, in part, artifacts provided by the original authors. Also, artifacts are very carefully documented and well-structured, consistent, complete, exercisable, and include appropriate evidence of verification and validation
|
||||
- Replicated
|
||||
- 
|
||||
- ---
|
||||
- Results Replicated (RER)
|
||||
- The main results of the paper have been independently obtained in a subsequent study by a person or team other than the authors, without the use of author-supplied artifacts.
|
||||
- ### [Details of the Badges](https://conf.researchr.org/track/ase-2022/ase-2022-artifact-evaluation#details-of-the-badges)
|
||||
- **Available**
|
||||
- This badge is applied to papers in which associated artifacts have been made permanently available for retrieval.
|
||||
- We consider temporary drives (e.g., Dropbox, Google Drive) to be non-persistent, same as individual/institutional websites of the submitting authors, as these are prone to changes.
|
||||
- We ask that authors use Zenodo as this service is persistent and also offers the possibility to assign a DOI.
|
||||
- Artifacts do not need to have been formally evaluated in order for an article to receive this badge. In addition, they need not be complete in the sense described above. They simply need to be relevant to the study and add value beyond the text in the article. Such artifacts could be something as simple as the data from which the figures are drawn, or as complex as a complete software system under study.
|
||||
- **Reusable**
|
||||
- The artifacts must meet the following requirements.
|
||||
- Documented: At minimum, an inventory of artifacts is included, and sufficient description provided to enable the artifacts to be exercised.
|
||||
- Consistent: The artifacts are relevant to the associated paper, and contribute in some inherent way to the generation of its main results.
|
||||
- Complete: To the extent possible, all components relevant to the paper in question are included. (Proprietary artifacts need not be included. If they are required to exercise the package then this should be documented, along with instructions on how to obtain them. Proxies for proprietary data should be included so as to demonstrate the analysis.)
|
||||
- Exercisable: Included scripts and / or software used to generate the results in the associated paper can be successfully executed, and
|
||||
- _Authors are strongly encouraged to target their artifact submissions for Reusable as the purpose of artifact badges is, among other things, to facilitate reuse and repurposing, which may not be achieved at the Functional level._
|
||||
- **Reproduced**
|
||||
- This badge is applied to papers in which the main results of the paper have been successfully obtained by a person or team other than the original authors of the work, with, at least in part, artifacts provided by the original authors.
|
||||
- Example: If Asha published a paper with artifacts in 2020, and Tim published a reproduction in 2021 using the artifacts, then Asha can now apply for the Reproduced badge on the 2020 paper.
|
||||
- **Replicated**
|
||||
- This badge is applied to papers in which the main results of the paper have been successfully obtained by a person or team other than the author, but without any artifacts provided by the original authors.
|
||||
- Example: If Janet published a paper in 2020 with no artifacts, and Miles published a paper with artifacts in 2021 that independently obtained the main result, then Janet can apply for the Replicated badge on the 2020 paper.
|
||||
- Papers with such badges contain reusable products that other researchers can use to bootstrap their own research. Experience shows that such papers earn increased citations and greater prestige in the research community. Artifacts of interest include (but are not limited to) the following.
|
||||
- Software, which are implementations of systems or algorithms potentially useful in other studies.
|
||||
- Data repositories, which are data (e.g., logging data, system traces, survey raw data) that can be used for multiple software engineering approaches.
|
||||
- Frameworks, which are tools and services illustrating new approaches to software engineering that could be used by other researchers in different contexts.
|
||||
- This list is not exhaustive, so the authors are asked to email the chairs before submitting if their proposed artifact is not on this list.
|
||||
- ### [Submission](https://conf.researchr.org/track/ase-2022/ase-2022-artifact-evaluation#submission)
|
||||
- Authors are to submit to our [HotCRP](https://ase22artifacts.hotcrp.com/) website.
|
||||
- Note that that there are two separate separate submission procedures: 1) for available and reusable artifacts, and 2) for replicated and reproduced badges.
|
||||
- ### [Submission for Available and Reusable artifacts](https://conf.researchr.org/track/ase-2022/ase-2022-artifact-evaluation#submission-for-available-and-reusable-artifacts)
|
||||
- All submitters must make their repositories available using the following steps.
|
||||
- Create a Github repo.
|
||||
- Register the repo at Zenodo.org. For details on that process, see [https://guides.github.com/activities/citable-code](https://guides.github.com/activities/citable-code).
|
||||
- Make a release at Github, at which time Zenodo will automatically grab a copy of that repo and issue a Digital Object Identifier (DOI) e.g. [https://doi.org/10.5281/zenodo.4308746](https://doi.org/10.5281/zenodo.4308746).
|
||||
- Submit that DOI to us.
|
||||
- Your Github repo should have documentation files explaining how to obtain the artifact package, how to unpack the artifact, how to get started, and how to use the artifacts in sufficient detail. The artifact submission must describe only the technicalities of the artifacts and uses of the artifact that are not already described in the paper. The submission should contain the following documents (in markdown plain text format).
|
||||
- A README.md main file describing what the artifact does and where it can be obtained (with hidden links and access password if necessary).
|
||||
- A LICENSE.md file describing the distribution rights. Note that to score “available” or higher, then that license needs to be some form of open source license.
|
||||
- An INSTALL.md file with installation instructions. These instructions should include notes illustrating a very basic usage example or a method to test the installation. This could be, for instance, information on what output to expect that confirms that the code is installed and working; and that the code is doing something interesting and useful. IMPORTANT, there should be a clear description of how to reproduce the results presented in the paper.
|
||||
- A copy of the accepted paper in pdf format.
|
||||
- Authors may update their research artifacts after submission only for changes requested by reviewers in the rebuttal phase. To update artifacts: (1) Go to Github; (2) Make your changes; (3) Make a new release; (4) Make a comment in HotCrp that “in response to comment XYZ we have made a new release that addresses that issues as follows: ABC”
|
||||
- ### [Submission for Replicated and Reproduced badges](https://conf.researchr.org/track/ase-2022/ase-2022-artifact-evaluation#submission-for-replicated-and-reproduced-badges)
|
||||
- Submit a one page (max) pdf documenting the maturity of the artifact. This needs to include:
|
||||
- TITLE: A (Partial)? (Replication|Reproduction) of XYZ. Please add the term partial to your title if only some of the original work could be replicated/reproduced.
|
||||
- WHO: name the original authors (and paper) and the authors that performed the replication/reproduction. Include contact information (emails). Mark one author as the corresponding author.
|
||||
- **IMPORTANT**: include also a web link to a publicly available URL directory containing (a) the original paper (that is being reproduced) and (b) any subsequent paper(s)/documents/reports that do the reproduction.
|
||||
- WHAT: describe the “thing” being replicated/reproduced;
|
||||
- WHY: clearly state why that “thing” is interesting/important;
|
||||
- PLATFORM: being the operating system where this artifact was mostly developed on;
|
||||
- HOW: say how it was done first;
|
||||
- WHERE: describe the replication/reproduction. If the replication/reproduction was only partial, then explain what parts could be achieved or had to be missed.
|
||||
- DISCUSSION: What aspects of this “thing” made it easier/harder to replicate/reproduce. What are the lessons learned from this work that would enable more replication/reproduction in the future for other kinds of tasks or other kinds of research.
|
||||
- ### [Review](https://conf.researchr.org/track/ase-2022/ase-2022-artifact-evaluation#review)
|
||||
- The ASE artifact evaluation track uses a single-blind review process. All artifacts will receive two reviews.
|
||||
- Two PC members will review each abstract, possibly reaching out to the authors of the abstract or original paper. Abstracts will be ranked as follows.
|
||||
- If PC members do not find sufficient substantive evidence for replication/reproduction, the abstract will be rejected.
|
||||
- Any abstract that is judged to be unnecessarily critical of prior work will be rejected (*).
|
||||
- The remaining abstracts will be sorted according to (a) interestingness and (b) correctness.
|
||||
- The top ranked abstracts will be invited to give lightning talks.
|
||||
- (*) Our goal is to foster a positive environment that supports and rewards researchers for conducting replications and reproductions. To that end, we require that all abstracts and presentations pay due respect to the work they are reproducing/replicating. Criticism of prior work is acceptable only as part of a balanced and substantive discussion of prior accomplishments.
|
||||
- Note that prior to reviewing, there may be some interactions to handle setup and install. Before the actual evaluation reviewers will check the integrity of the artifact and look for any possible setup problems that may prevent it from being properly evaluated (e.g., corrupted or missing files, VM won’t start, immediate crashes on the simplest example, etc.). The Evaluation Committee may contact the authors to request clarifications on the basic installation and start-up procedures or to resolve simple installation problems. Artifact evaluation can be rejected for artifacts whose configuration and installation takes an undue amount of time.
|
||||
- ### REVIEW
|
||||
- ### Paper summary
|
||||
- The paper presents the software artifacts that are related to the ASE2022 submission titled "CrystalBLEU: Precisely and Efficiently Measuring the Similarity of Code", which gives an extension of the [[BLEU score]] to measure the similarity of source code. The shared GitHub repository contains all the scripts needed to replicate the tables and figures shown in the ASE submission.
|
||||
- ### Comments for author
|
||||
- To make the scripts WORK, I had to convert them through the doc2unix command (I'm using a Win11 machine with the Linux subsystem):
|
||||
- `` dos2unix ./scripts/* ``
|
||||
- To avoid issues like this, I recommend adding a section in the README.md file presenting the requirements (further than those listed in the file requirement.txt) that must be satisfied to make the proposed scripts work. For instance, I would have presented the system configuration used to develop and run the presented approach, including, e.g., the version of the used Python and Java runtime environments.
|
||||
- Further than listing the sequence of commands to execute, I would have clarified the roles of all the considered datasets. Since it took a while to prepare all of them, users would appreciate why such a so long operation is needed and, in particular, for which of the following commands each of them is required. By following such a comment, I would clarify/refine the current statement:
|
||||
- ``Note: this might cause some scripts to crash if they cannot find the required data files``
|
||||
- With a more detailed description of what would crash in the case and why.
|
||||
- Even though the repository contains the scripts to reproduce the tables and figures of the ASE paper correctly, it does not describe in detail how to use the CrystalBLEU approach without the prepared bash scripts. Thus, the usage of the CrystalBLEU approach outside the boundaries of the prepared use cases is limited.
|
||||
- ### Comments for PC
|
||||
- None.
|
||||
@@ -0,0 +1,25 @@
|
||||
links:: [Local library](zotero://select/library/items/4Z4UBSE8), [Web library](https://www.zotero.org/users/1039502/items/4Z4UBSE8)
|
||||
authors:: [[Antonio Mastropaolo]], [[Matteo Ciniselli]], [[Massimiliano Di Penta]], [[Gabriele Bavota]]
|
||||
tags:: [[Computer Science - Software Engineering]], [[#zotero]]
|
||||
date:: [[24-12-2023]]
|
||||
item-type:: [[preprint]]
|
||||
title:: @Evaluating Code Summarization Techniques: A New Metric and an Empirical Characterization
|
||||
|
||||
-
|
||||
- [[Abstract]]
|
||||
- Several code summarization techniques have been proposed in the literature to automatically document a code snippet or a function. Ideally, software developers should be involved in assessing the quality of the generated summaries. However, in most cases, researchers rely on automatic evaluation metrics such as BLEU, ROUGE, and METEOR. These metrics are all based on the same assumption: The higher the textual similarity between the generated summary and a reference summary written by developers, the higher its quality. However, there are two reasons for which this assumption falls short: (i) reference summaries, e.g., code comments collected by mining software repositories, may be of low quality or even outdated; (ii) generated summaries, while using a different wording than a reference one, could be semantically equivalent to it, thus still being suitable to document the code snippet. In this paper, we perform a thorough empirical investigation on the complementarity of different types of metrics in capturing the quality of a generated summary. Also, we propose to address the limitations of existing metrics by considering a new dimension, capturing the extent to which the generated summary aligns with the semantics of the documented code snippet, independently from the reference summary. To this end, we present a new metric based on contrastive learning to capture said aspect. We empirically show that the inclusion of this novel dimension enables a more effective representation of developers’ evaluations regarding the quality of automatically generated summaries.
|
||||
- ### Attachments
|
||||
- [Mastropaolo et al. - 2023 - Evaluating Code Summarization Techniques A New Me.pdf](zotero://select/library/items/MEUEEDN9) {{zotero-imported-file MEUEEDN9, "Mastropaolo et al. - 2023 - Evaluating Code Summarization Techniques A New Me.pdf"}}
|
||||
- ### Notes https://www.zotero.org/users/1039502/items/MEUEEDN9
|
||||
- # Annotazioni
|
||||
- (19/1/2024, 11:16:08)
|
||||
- “Evaluating Code Summarization Techniques: A New Metric and an Empirical Characterization” (Mastropaolo et al., 2023, p. 1) #5fb236
|
||||
- *This is related to project [[PROJECTS/MOSAICO]] *
|
||||
- “Several code summarization techniques have been proposed in the literature to automatically document a code snippet or a function.” (Mastropaolo et al., 2023, p. 1) #ffd400
|
||||
- *This is a comment for a yellow highlight [[P1]] [[STAR]] *
|
||||
- “oftware developers should be involved in assessing the quality of the generated summaries. However, in most cases, researchers rely on a” (Mastropaolo et al., 2023, p. 1) #ff6666
|
||||
- *This is not good [[people/phuong]] *
|
||||
- “falls short: (i) reference summaries, e.g., code comments collected by mining software repositories, may be of low quality or even outdated; (ii)” (Mastropaolo et al., 2023, p. 1) #5fb236
|
||||
- * *
|
||||
- “m a thorough empirical investigation on the complementarity of different types of metrics in capturing the quality of a generated summary. Also, we propose to address the limitations of existing metrics by consid” (Mastropaolo et al., 2023, p. 1) #ffd400
|
||||
- * *
|
||||
@@ -0,0 +1,20 @@
|
||||
tags:: [[GOAL_Model-synthesis]], [[TECHNIQUE_CSP]], [[notion]], [[#readingnotes]]
|
||||
date:: 2013
|
||||
series:: "Proceedings - International Conference on Tools with Artificial Intelligence, ICTAI"
|
||||
isbn:: 978-1-4799-2971-9
|
||||
doi:: 10.1109/ICTAI.2013.156
|
||||
title:: @Ferdjoukh20131044
|
||||
pages:: 1044-1051
|
||||
item-type:: [[conferencePaper]]
|
||||
original-title:: A CSP approach for metamodel instantiation
|
||||
language:: English
|
||||
url:: https://www.scopus.com/inward/record.uri?eid=2-s2.0-84897742023&doi=10.1109%2fICTAI.2013.156&partnerID=40&md5=2b7af224236f6e577c647472382cf91f
|
||||
authors:: [[A. Ferdjoukh]], [[A.-E. Baert]], [[A. Chateau]], [[R. Coletta]], [[C. Nebut]]
|
||||
links:: [Local library](zotero://select/library/items/JCS3PDV2), [Web library](https://www.zotero.org/users/1039502/items/JCS3PDV2)
|
||||
|
||||
- [[Attachments]]
|
||||
- [Ferdjoukh et al_2013_A CSP approach for metamodel instantiation.pdf](https://hal-lirmm.ccsd.cnrs.fr/lirmm-01007571/file/Ferdjoukh_ICTAI13.pdf) {{zotero-imported-file 85V9FLJK, "Ferdjoukh et al_2013_A CSP approach for metamodel instantiation.pdf"}}
|
||||
- [Notion](notion://www.notion.so/Ferdjoukh-et-al-2013-4b64255af6a045e489ebdabbb4804155)
|
||||
- [[Notes]]
|
||||
- cited By 13
|
||||
- ((6318744b-7cdd-4cdc-8668-3e8cb52b6118))
|
||||
@@ -0,0 +1,9 @@
|
||||
tags:: [[#zotero]]
|
||||
title:: @INFSOF-D-23-00931_R1_reviewer.pdf
|
||||
item-type:: [[document]]
|
||||
original-title:: INFSOF-D-23-00931_R1_reviewer.pdf
|
||||
links:: [Local library](zotero://select/library/items/RUKHUVV6), [Web library](https://www.zotero.org/users/1039502/items/RUKHUVV6)
|
||||
|
||||
-
|
||||
- ### Attachments
|
||||
- [INFSOF-D-23-00931_R1_reviewer.pdf](zotero://select/library/items/GBXF3IIH) {{zotero-imported-file GBXF3IIH, "INFSOF-D-23-00931_R1_reviewer.pdf"}}
|
||||
@@ -0,0 +1,20 @@
|
||||
title:: @IoTMoF: A Requirements-Driven Modelling Framework for Adaptive IoT Systems
|
||||
item-type:: [[journalArticle]]
|
||||
original-title:: IoTMoF: A Requirements-Driven Modelling Framework for Adaptive IoT Systems
|
||||
language:: en
|
||||
authors:: [[Paul Boutot]], [[Sadaf Mustafiz]]
|
||||
library-catalog:: Zotero
|
||||
links:: [Local library](zotero://select/library/items/PG2F7JZ5), [Web library](https://www.zotero.org/users/1039502/items/PG2F7JZ5)
|
||||
|
||||
-
|
||||
- [[Attachments]]
|
||||
- [Boutot e Mustafiz - IoTMoF A Requirements-Driven Modelling Framework .pdf](zotero://select/library/items/PAUWRAG9) {{zotero-imported-file PAUWRAG9, "Boutot e Mustafiz - IoTMoF A Requirements-Driven Modelling Framework .pdf"}}
|
||||
- title:: @IoTMoF: A Requirements-Driven Modelling Framework for Adaptive IoT Systems
|
||||
item-type:: [[journalArticle]]
|
||||
original-title:: IoTMoF: A Requirements-Driven Modelling Framework for Adaptive IoT Systems
|
||||
language:: en
|
||||
authors:: [[Paul Boutot]], [[Sadaf Mustafiz]]
|
||||
library-catalog:: Zotero
|
||||
links:: [Local library](zotero://select/library/items/PG2F7JZ5), [Web library](https://www.zotero.org/users/1039502/items/PG2F7JZ5)
|
||||
- [[Attachments]]
|
||||
- [Boutot e Mustafiz - IoTMoF A Requirements-Driven Modelling Framework .pdf](zotero://select/library/items/PAUWRAG9) {{zotero-imported-file PAUWRAG9, "Boutot e Mustafiz - IoTMoF A Requirements-Driven Modelling Framework .pdf"}}
|
||||
@@ -0,0 +1,13 @@
|
||||
links:: [Local library](zotero://select/library/items/ACDXARUY), [Web library](https://www.zotero.org/users/1039502/items/ACDXARUY)
|
||||
authors:: [[Xinyi Hou]], [[Yanjie Zhao]], [[Yue Liu]], [[Zhou Yang]], [[Kailong Wang]], [[Li Li]], [[Xiapu Luo]], [[David Lo]], [[John Grundy]], [[Haoyu Wang]]
|
||||
tags:: [[Computer Science - Artificial Intelligence]], [[Computer Science - Software Engineering]], [[#zotero]]
|
||||
date:: [[12-09-2023]]
|
||||
item-type:: [[preprint]]
|
||||
title:: @Large Language Models for Software Engineering: A Systematic Literature Review
|
||||
|
||||
-
|
||||
- [[Abstract]]
|
||||
- Large Language Models (LLMs) have significantly impacted numerous domains, including Software Engineering (SE). Many recent publications have explored LLMs applied to various SE tasks. Nevertheless, a comprehensive understanding of the application, effects, and possible limitations of LLMs on SE is still in its early stages. To bridge this gap, we conducted a systematic literature review on LLM4SE, with a particular focus on understanding how LLMs can be exploited to optimize processes and outcomes. We collect and analyze 229 research papers from 2017 to 2023 to answer four key research questions (RQs). In RQ1, we categorize different LLMs that have been employed in SE tasks, characterizing their distinctive features and uses. In RQ2, we analyze the methods used in data collection, preprocessing, and application highlighting the role of well-curated datasets for successful LLM for SE implementation. RQ3 investigates the strategies employed to optimize and evaluate the performance of LLMs in SE. Finally, RQ4 examines the specific SE tasks where LLMs have shown success to date, illustrating their practical contributions to the field. From the answers to these RQs, we discuss the current state-of-the-art and trends, identifying gaps in existing research, and flagging promising areas for future study.
|
||||
- ### Attachments
|
||||
- [arXiv.org Snapshot](https://arxiv.org/abs/2308.10620) {{zotero-imported-file MIUBCJ52, "2308.html"}}
|
||||
- [Hou et al_2023_Large Language Models for Software Engineering.pdf](https://arxiv.org/pdf/2308.10620.pdf) {{zotero-imported-file 8G8XW8TW, "Hou et al_2023_Large Language Models for Software Engineering.pdf"}}
|
||||
@@ -0,0 +1,17 @@
|
||||
tags:: [[#nosource]]
|
||||
date:: 2013
|
||||
issue:: 1
|
||||
doi:: 10.1007/s10270-011-0193-0
|
||||
title:: @Managing the evolution of data-intensive Web applications by model-driven techniques
|
||||
pages:: 53-83
|
||||
volume:: 12
|
||||
item-type:: [[journalArticle]]
|
||||
original-title:: Managing the evolution of data-intensive Web applications by model-driven techniques
|
||||
url:: https://www.scopus.com/inward/record.uri?eid=2-s2.0-84874188912&doi=10.1007%2fs10270-011-0193-0&partnerID=40&md5=9835ca1838898b7b6b4982b16893033d
|
||||
publication-title:: Software and Systems Modeling
|
||||
authors:: [[A. Cicchetti]], [[D. Di Ruscio]], [[L. Iovino]], [[A. Pierantonio]]
|
||||
links:: [Local library](zotero://select/library/items/TDJQGJVF), [Web library](https://www.zotero.org/users/1039502/items/TDJQGJVF)
|
||||
|
||||
-
|
||||
- [[Notes]]
|
||||
- cited By 16
|
||||
@@ -0,0 +1,17 @@
|
||||
type:: [[REVIEWS]]
|
||||
title::
|
||||
date-start:: [[25-04-2023]] - 20:37
|
||||
date-end:: [[25-04-2023]]
|
||||
year:: 2023
|
||||
venue:: [[JSS]]
|
||||
external-link::
|
||||
file:: 
|
||||
title::
|
||||
datestart:: [[25-04-2023]]
|
||||
dateend:: [[25-04-2023]]
|
||||
externallink::
|
||||
|
||||
- [[Reviews]]
|
||||
- Revision of [[JSSOFTWARE-D-22-00977_reviewer.pdf]]
|
||||
- I thank the authors for improving the paper and addressing all my comments. The new version of the article is clearer than the initial one. Therefore, I have no further comments or suggestions, and I recommend the paper for publication.
|
||||
-
|
||||
@@ -0,0 +1,16 @@
|
||||
full-title:: Mining StackOverflow to turn the IDE into a self-confident programming prompter
|
||||
author:: Ponzanelli, Luca
|
||||
year::
|
||||
icon:: 📚
|
||||
template:: CITATION-MANAGER
|
||||
|
||||
- *Mining StackOverflow to turn the IDE into a self-confident programming prompter*. ACM Press.
|
||||
- Ponzanelli, Luca, .
|
||||
- Abstract:
|
||||
-
|
||||
- Notes
|
||||
- undefined
|
||||
-
|
||||
- Uses the filetemplate format to add *all file attachments in the form of a link for example*
|
||||
- This template supports more fields like , and ponzanelliMiningStackOverflowTurn2014
|
||||
-
|
||||
@@ -0,0 +1,24 @@
|
||||
tags:: [[Developers Support]], [[Empirical Studies]], [[Recommender Systems]], [[STAR]], [[#zotero]]
|
||||
date:: 2014
|
||||
publisher:: ACM Press
|
||||
place:: "Hyderabad, India"
|
||||
isbn:: 978-1-4503-2863-0
|
||||
doi:: 10.1145/2597073.2597077
|
||||
title:: @Mining StackOverflow to turn the IDE into a self-confident programming prompter
|
||||
pages:: 102-111
|
||||
item-type:: [[conferencePaper]]
|
||||
access-date:: 2017-03-28T09:47:04Z
|
||||
original-title:: Mining StackOverflow to turn the IDE into a self-confident programming prompter
|
||||
language:: en
|
||||
url:: http://dl.acm.org/citation.cfm?doid=2597073.2597077
|
||||
authors:: [[Luca Ponzanelli]], [[Gabriele Bavota]], [[Massimiliano Di Penta]], [[Rocco Oliveto]], [[Michele Lanza]]
|
||||
library-catalog:: CrossRef
|
||||
links:: [Local library](zotero://select/library/items/XADHB8Z3), [Web library](https://www.zotero.org/users/1039502/items/XADHB8Z3)
|
||||
|
||||
-
|
||||
- ### Attachments
|
||||
- [Ponzanelli et al. - 2014 - Mining StackOverflow to turn the IDE into a self-c.pdf](zotero://select/library/items/TUAGTCE2) {{zotero-imported-file TUAGTCE2, "Ponzanelli et al. - 2014 - Mining StackOverflow to turn the IDE into a self-c.pdf"}}
|
||||
- ### Notes
|
||||
- THIS IS A SIMPLE NOTE [[STAR]]
|
||||
|
||||
I would like to import also notes form PDF [[IDEA]]
|
||||
@@ -0,0 +1,13 @@
|
||||
full-title:: Mining metrics for understanding metamodel characteristics
|
||||
author:: Rocco, Juri Di
|
||||
year::
|
||||
icon:: 📚
|
||||
template:: CITATION-MANAGER
|
||||
|
||||
- *Mining metrics for understanding metamodel characteristics*. .
|
||||
- Rocco, Juri Di, .
|
||||
- Abstract:
|
||||
-
|
||||
- Notes
|
||||
- undefined
|
||||
-
|
||||
@@ -0,0 +1,18 @@
|
||||
tags:: [[GOAL_Model-Classification]], [[notion]], [[#read]]
|
||||
date:: 2021
|
||||
issn:: 01641212
|
||||
doi:: 10.1016/j.jss.2020.110860
|
||||
title:: @Nguyen2021
|
||||
volume:: 172
|
||||
item-type:: [[journalArticle]]
|
||||
original-title:: Convolutional neural networks for enhanced classification mechanisms of metamodels
|
||||
language:: English
|
||||
url:: https://www.scopus.com/inward/record.uri?eid=2-s2.0-85096121119&doi=10.1016%2fj.jss.2020.110860&partnerID=40&md5=ca6285b8b8ed222076d39aa568b2626d
|
||||
publication-title:: Journal of Systems and Software
|
||||
authors:: [[P.T. Nguyen]], [[D. Di Ruscio]], [[A. Pierantonio]], [[J. Di Rocco]], [[L. Iovino]]
|
||||
links:: [Local library](zotero://select/library/items/CZEETL7T), [Web library](https://www.zotero.org/users/1039502/items/CZEETL7T)
|
||||
|
||||
- [[Attachments]]
|
||||
- [Notion](notion://www.notion.so/Nguyen-et-al-2021-30df3da5fd3a495ca5e87d47586a222e)
|
||||
- [[Notes]]
|
||||
- cited By 13
|
||||
@@ -0,0 +1,39 @@
|
||||
tags:: [[Mentoring]], [[people/Umar]], [[#zotero]]
|
||||
title:: @Prompt-Injection based Adversarial Attacks in Large Language Models
|
||||
item-type:: [[document]]
|
||||
original-title:: Prompt-Injection based Adversarial Attacks in Large Language Models
|
||||
language:: en
|
||||
authors:: [[Muhammad Umar Zeshan]]
|
||||
library-catalog:: Zotero
|
||||
links:: [Local library](zotero://select/library/items/G3NC2PN7), [Web library](https://www.zotero.org/users/1039502/items/G3NC2PN7)
|
||||
|
||||
-
|
||||
- ### Attachments
|
||||
- [Zeshan - Prompt-Injection based Adversarial Attacks in Larg.pdf](zotero://select/library/items/N65IM7XB) {{zotero-imported-file N65IM7XB, "Zeshan - Prompt-Injection based Adversarial Attacks in Larg.pdf"}}
|
||||
- ### Notes
|
||||
- # Annotazioni
|
||||
- (15/1/2024, 09:11:23)
|
||||
- “trendy” (Zeshan, p. 1)
|
||||
- “prompt attacks in Large Language Models” (Zeshan, p. 1)
|
||||
- “LLMs” (Zeshan, p. 1)
|
||||
- “better” (Zeshan, p. 1) Nothing has been said so far. Better than that?
|
||||
- “ethical issues, bias, and responsible use become crucial factors to take into account” (Zeshan, p. 1) These are critical points. Are you mentioning them because you want to plan to deal with them? If not, why are you mentioning them?
|
||||
- “insufficient safety assessments and guardrails are accompanying this drive toward AI integration” (Zeshan, p. 1)
|
||||
- “A prompt should ideally generate an answer that is accurate, sufficient in both form and content, and of the appropriate length” (Zeshan, p. 2)
|
||||
- “several human feedback-incorporating fine-tuning procedures have been developed to guarantee that LLM outputs are both safe and consistent with human values.” (Zeshan, p. 2)
|
||||
- “around the security.” (Zeshan, p. 2) Some more details about security issues one can have with LLMs are needed.
|
||||
- “According to Zou et al.’s research from 2023, adversarial sequence creation can be automated, producing an infinite number of these attacks. Furthermore, they demonstrate how safety precautions can be circumvented by appending a single adversarial sequence to several damaging prompts” (Zeshan, p. 2) Some illustrative examples are needed here!
|
||||
- “Adversarial attacks detection in RSSE” (Zeshan, p. 2) This section should be on presenting Rec Systems in Software Engineering. Thus the title should be changed and the content should be expanded with the aim of presenting a quick overview on RSSE.
|
||||
- “Adversarial attempts produce perturbations to trick and confuse systems by breaking them down, impairing their ability to provide recommendations. For instance, an adversarial attack on recommender systems may support or disparage a product, depending on the intent, which would have a detrimental effect on the final recommendations. Similarly, malicious users may expose recommender systems to hazardous artifacts by altering training data that is accessible through OSS platforms. Software system disruptions may arise if a recommender is trained to deliver harmful outcomes based on Adversaries. For instance, a recent study reveals that there have been attempts to force Android apps to open ports covertly, enabling unwanted access. Security concerns in machine learning systems and all-purpose recommender systems are investigated via research on adversarial machine learning (AML)” (Zeshan, p. 3) I would show some technical details that will be used later in the text.
|
||||
- “Adversarial Attacks in Promptbased Learning” (Zeshan, p. 4) All the different approaches that are overviewed in this section need to be expanded with concrete examples. It is essential to expand because, as far as I understood, this will underpin and motivate the planned work.
|
||||
- “trendy” (Zeshan, p. 4) I don't like it; it is not for scientific documents.
|
||||
- “backdoor attacks” (Zeshan, p. 4)
|
||||
- “Our Methodology” (Zeshan, p. 5) For what?
|
||||
- It is necessary to conclude the previous section by listing the challenges you plan to address! By clearly listing the challenges at the end of the previous section, in this section you can discuss how you plant to deal with them.
|
||||
- “Limitations in previous methods” (Zeshan, p. 6) This must be moved to the previous section before listing the challenges that you plan to address.
|
||||
- “The main drawback of previous research is that it is case study oriented; for example, it did not define the attacker’s objective in rapid injection assaults in terms of the type of the attack, attacker wants to carry.” (Zeshan, p. 6) The document is plenty of sentences like this one, we are missing concreteness, you have to provide explanatory examples to help reader understand what's the problem by referring to real cases.
|
||||
- “Rather than simply translating a text into English, they demonstrated how an assailant may lead an LLM astray and have them compose a sonnet about pandas. The main drawback of this kind of caseby-case research is how difficult it is to come up with novel prompt injection attacks or carry out a thorough analysis and comparison of other prompt injection assaults. Even the latest studies are focusing on some particular type of prompt injections, which also allow for enhancing the attack by combining all the possible attack scenarios.” (Zeshan, p. 6) Suddenly, we lost the reference to RSSE!
|
||||
- “Research Questions” (Zeshan, p. 6) Are you still interested in RSSE? The research questions you defined are not related to RSSE.
|
||||
- “ll kinds of adversarial attacks defined in literature are discussed which are relevant in this new trendy topic of prompt learning attacks.” (Zeshan, p. 6) Thus, what's the plan? Are you planning to work on a survey work? What do you expect to do further than expanding what you have listed in 3.2?
|
||||
- “threat model is proposed, in which a combined attack model is applied which concatenates all the possible types of attacks in prompts by the attacker.” (Zeshan, p. 6) I don't see it in Section 3.2
|
||||
- “Prompt Injection Attacks” (Zeshan, p. 8) Is this supposed to be a new type of attack? But it is not new, isn't it?
|
||||
@@ -0,0 +1,10 @@
|
||||
tags:: [[/unread]], [[#zotero]]
|
||||
title:: @Regolamento per il conferimento di contratti di ricerca
|
||||
item-type:: [[document]]
|
||||
access-date:: 2025-04-17T07:09:37Z
|
||||
original-title:: Regolamento per il conferimento di contratti di ricerca
|
||||
url:: https://www.univaq.it/include/utilities/blob.php?table=regolamento&id=200&item=file
|
||||
links:: [Local library](zotero://select/library/items/TU2H4ZNK), [Web library](https://www.zotero.org/users/1039502/items/TU2H4ZNK)
|
||||
|
||||
- ### Attachments
|
||||
- [PDF](https://www.univaq.it/include/utilities/blob.php?table=regolamento&id=200&item=file) {{zotero-imported-file MUBUR4J5, "blob.pdf"}}
|
||||
@@ -0,0 +1,7 @@
|
||||
links:: [Local library](zotero://select/library/items/R44U9C7V), [Web library](https://www.zotero.org/users/1039502/items/R44U9C7V)
|
||||
original-title:: Selecting Third-party Libraries: The Data Scientist’s Perspective
|
||||
item-type:: [[newspaperArticle]]
|
||||
title:: @Selecting Third-party Libraries: The Data Scientist’s Perspective
|
||||
|
||||
- [[Attachments]]
|
||||
- [Selecting Third-party Libraries: The Data Scientist’s Perspective](zotero://select/library/items/2BBTJQTC) {{zotero-imported-file 2BBTJQTC, "Selecting Third-party Libraries The Data Scientist’s Perspective.pdf"}}
|
||||
@@ -0,0 +1,20 @@
|
||||
item-type:: [[preprint]]
|
||||
date:: [[24-02-2021]]
|
||||
tags:: Computer Science - Machine Learning, Computer Science - Software Engineering, Statistics - Machine Learning
|
||||
authors:: Stefan Studer, Thanh Binh Bui, Christian Drescher, Alexander Hanuschkin, Ludwig Winkler, Steven Peters, Klaus-Robert Mueller
|
||||
links:: [Local library](zotero://select/library/items/YMVAT7GU), [Web library](https://www.zotero.org/users/1039502/items/YMVAT7GU)
|
||||
title:: @Towards CRISP-ML(Q): A Machine Learning Process Model with Quality Assurance Methodology
|
||||
|
||||
- [[Abstract]]
|
||||
- Machine learning is an established and frequently used technique in industry and academia but a standard process model to improve success and efficiency of machine learning applications is still missing. Project organizations and machine learning practitioners have a need for guidance throughout the life cycle of a machine learning application to meet business expectations. We therefore propose a process model for the development of machine learning applications, that covers six phases from defining the scope to maintaining the deployed machine learning application. The first phase combines business and data understanding as data availability oftentimes affects the feasibility of the project. The sixth phase covers state-of-the-art approaches for monitoring and maintenance of a machine learning applications, as the risk of model degradation in a changing environment is eminent. With each task of the process, we propose quality assurance methodology that is suitable to adress challenges in machine learning development that we identify in form of risks. The methodology is drawn from practical experience and scientific literature and has proven to be general and stable. The process model expands on CRISP-DM, a data mining process model that enjoys strong industry support but lacks to address machine learning specific tasks. Our work proposes an industry and application neutral process model tailored for machine learning applications with focus on technical tasks for quality assurance.
|
||||
- [[Attachments]]
|
||||
- [arXiv.org Snapshot](https://arxiv.org/abs/2003.05155) {{zotero-imported-file NPMTANIZ, "2003.html"}}
|
||||
- [Studer et al_2021_Towards CRISP-ML(Q).pdf](https://arxiv.org/pdf/2003.05155.pdf) {{zotero-imported-file VY7ZE3X7, "Studer et al_2021_Towards CRISP-ML(Q).pdf"}}
|
||||
- [[Notes]]
|
||||
- Comment: Machine Learning Applications, Quality Assurance Methodology, Process Model, Best Practices for Machine Learning Applications, Automotive Industry and Academia, Best Practices, Guidelines
|
||||
-
|
||||
- ((62ffedc9-0c39-477a-99b4-6c3f13a918f7))
|
||||
- ((62ffedea-12ac-4afe-b95a-0f505678c959))
|
||||
- Questo e' un comment
|
||||
-
|
||||
-
|
||||
@@ -0,0 +1,7 @@
|
||||
title:: Il fascismo eterno
|
||||
created:: 2023-05-09T20:37:37.518Z
|
||||
type:: [[Book]]
|
||||
author:: [[Eco, Umberto]]
|
||||
|
||||
- page::
|
||||
location::
|
||||
@@ -0,0 +1,108 @@
|
||||
title:: Get in the game
|
||||
author:: [[Alberto Calcagno]]
|
||||
category:: [[Books]] #Kindle-Highlights
|
||||
last-Read:: [[February 14th, 2021]]
|
||||
link:: https://www.amazon.com/dp/B08F1N95Q2
|
||||
cover:: 
|
||||
|
||||
- «Non c’è notte tanto grande da non permettere al sole di risorgere il giorno dopo».
|
||||
Location: 707
|
||||
|
||||
Più punti in comune vengono generati, più la contaminazione è assicurata, più la probabilità di effettuare ottimi risultati aumenta. Il classico caso dove due più due fa cinque, insomma.
|
||||
Location: 950
|
||||
|
||||
La stessa differenza, insomma, tra affrontare una questione con una persona che non conosco e invece farlo con qualcuno a cui tengo veramente.
|
||||
Location: 968
|
||||
|
||||
Quali sono i fattori che riescono ad accendere e a garantire nel tempo questa relazione? Risposta facile: la bontà e l’eccellenza dei loro prodotti. Risposta profonda: l’intimità e la complicità tra consumatori e tutto quell’insieme di valori, comportamenti, convinzioni, relazioni che rientrano e strutturano il contenitore azienda.
|
||||
Location: 973
|
||||
|
||||
Santo Graal della reputazione, che va difeso con coraggio dagli attacchi dei predoni infedeli del compromesso e delle facili scorciatoie.
|
||||
Location: 981
|
||||
|
||||
Un imprenditore è una persona che non si pone limiti e che cerca di fare tutto ciò che è possibile per creare valore, per migliorare lo stato naturale delle cose cambiandolo e, se possibile, traendone un beneficio, una crescita, un arricchimento.
|
||||
Location: 1,066
|
||||
|
||||
l’essere imprenditori non prevedono il dono di saper predire il futuro, ma il modo in cui noi saremo pronti e aperti mentalmente nella loro gestione farà la differenza. Più
|
||||
Location: 1,077
|
||||
|
||||
Ci si può migliorare partendo dai nostri punti deboli, le nostre incertezze, magari dalla nostra timidezza nell’esporre completamente la nostra opinione, o dalla ritrosia nel fare il primo passo in un ambiente sconosciuto, nell’affrontare discorsi potenzialmente conflittuali, nel ricominciare a desiderare di lasciare il proprio segno anche dopo un errore, dopo esser caduti.
|
||||
Location: 1,085
|
||||
|
||||
dobbiamo entrare nell’ordine di idee che le opportunità di crescita, o di accelerazione dello sviluppo formativo per i nostri figli, vadano cercate in ambito privato.
|
||||
Location: 1,111
|
||||
|
||||
L’azienda investe nella persona, la persona investe su di sé, per poi restituire quanto capitalizzato, aggiungendo valore all’azienda. E il cerchio si chiude.
|
||||
Location: 1,157
|
||||
|
||||
Chiunque poi può essere talvolta nel ruolo del sostenente, talvolta in quello del sostenuto, in una perenne giostra statistica.
|
||||
Location: 1,163
|
||||
|
||||
«Se non li puoi convincere, confondili».
|
||||
Location: 1,226
|
||||
|
||||
Analogamente, nelle aziende, l’energia – che possiamo tradurre nella capacità di far crescere e sviluppare il business in modo organico e industriale – dipende dalla relazione profonda fra tre variabili: l’ambizione della visione aziendale, la capacità di tradurla in comportamenti concreti e consistenti, rafforzati da una determinata propensione al cambiamento.
|
||||
Location: 1,247
|
||||
|
||||
G (Growth)= a (Ambition) *e (Execution) ^c (Change)
|
||||
Location: 1,249
|
||||
|
||||
Più l’esecuzione è mossa da una feroce ricerca del giusto mix tra pragmatismo ed eccellenza, da una relazione bilanciata tra semplicità e utilità, da un umile rispetto per il cliente finale, più la possibilità di progredire e creare un vantaggio competitivo sarà garantita.
|
||||
Location: 1,263
|
||||
|
||||
Tanto più il desiderio di intraprendere sentieri non battuti o di percorrere rotte non convenzionali è vivo nella cultura aziendale, maggiore la probabilità di realizzare velocemente il prodotto di ambizione ed esecuzione.
|
||||
Location: 1,270
|
||||
|
||||
crescita. La crescita, pertanto, sia aziendale sia personale, non avviene per caso. È la conseguenza, quasi matematica, dell’intensità della presenza di ambizione, esecuzione e propensione al cambiamento. In un’organizzazione che promuove la crescita personale dei propri dipendenti, lo sviluppo sarà sempre assicurato.
|
||||
Location: 1,295
|
||||
|
||||
il passaggio per gradi è la soluzione migliore. Cerchiamo perciò un meccanismo di sfide crescenti a cui siano collegati carichi di fatica crescenti: questo meccanismo a ladder segue sempre il principio che tutto si può allenare e quindi anche la nostra capacità di sostenere carichi di lavoro in aumento.
|
||||
Location: 1,348
|
||||
|
||||
Jean-Paul Sartre diceva che la fiducia si guadagna goccia a goccia ma si perde a litri: quello che posso dire io è che organizzare il lavoro di un’azienda cercando di far leva sulla stima e sul rispetto reciproco implica comunque un alto livello di consapevolezza e di maturità da parte di tutti i dipendenti.
|
||||
Location: 1,433
|
||||
|
||||
costringe sempre a offrire un subset di quello che pensiamo o proviamo a livello emozionale; diciamo che è più conveniente e sicuro, e comunque preferibile, galleggiare a vista che fare e consentire ad altri di
|
||||
Location: 1,566
|
||||
|
||||
fare delle apnee in profondità dentro di noi.
|
||||
Location: 1,567
|
||||
|
||||
La positività, del resto, è proprio lo stato d’animo che facilita la contaminazione. Più sono positivo, più sono aperto alle suggestioni che mi arrivano dall’esterno e più il mio strato-scorza sarà permeabile.
|
||||
Location: 1,602
|
||||
|
||||
Gli altri ci completano e ci migliorano, questo è il vero messaggio dell’XXchange management e della contaminazione positiva. E con questa considerazione possiamo andare diretti all’ultimo capitolo per tirare le conclusioni.
|
||||
Location: 1,637
|
||||
|
||||
FIDAL (Federazione Italiana di Atletica Leggera), da quando questa associazione ha scelto Filippo Tortu, l’italiano più veloce di sempre sui 100 metri piani, come principale testimonial della propria campagna pubblicitaria.
|
||||
Location: 1,646
|
||||
|
||||
Erano semplicemente trentadue anni, dalla brillante prestazione di Pierfrancesco Pavoni ai Mondiali di Roma del 1987, che il nostro Paese aspettava di assistere ancora a un momento simile.
|
||||
Location: 1,650
|
||||
|
||||
tutti gli ingredienti per esprimersi al meglio. Il meglio è diverso per ognuno di noi, la cosa importante è che ci ingaggiamo in un processo di miglioramento costante che passa dalla nostra abitudine ad accogliere, promuovere, intraprendere sfide. Come affermavo nei capitoli precedenti, non esiste la sfida giusta per eccellenza ma quella giusta per noi; l’importante è continuare a farsi trovare pronti in pedana quando arriva il momento di saltare e il giudice arbitro chiama il tuo nome.
|
||||
Location: 1,698
|
||||
|
||||
Il mettersi alla prova con piccole sfide quotidiane, mensili, trimestrali e poi alzare il tiro misurandosi con obiettivi più importanti non fa altro che aumentare la nostra confidenza nel provare a misurarci.
|
||||
Location: 1,703
|
||||
|
||||
A un certo punto sarà automatico, la tensione verso il miglioramento diventerà una parte imprescindibile della nostra giornata e, quindi, ci troveremo esattamente nel punto che volevamo. A nessuno viene chiesto di essere sportivi professionisti, tutti però possiamo essere atleti.
|
||||
Location: 1,705
|
||||
|
||||
Non è una gara contro qualcuno, è una gara per qualcosa. Fa la differenza sapere cosa stiamo cercando di ottenere, piuttosto che cercare di correre senza meta. La direzione non basta, dobbiamo sapere anche dove vogliamo arrivare.
|
||||
Location: 1,708
|
||||
|
||||
Se vogliamo elevare le nostre prestazioni personali e, con esse, quelle aziendali, non basta essere allineati con la visione ma dobbiamo anche essere attori dei valori comportamentali a essa sottesi.
|
||||
Location: 1,716
|
||||
|
||||
L’obiettivo non è la spersonalizzazione dell’individuo ma, al contrario, la ricerca della sua realizzazione migliore.
|
||||
Location: 1,719
|
||||
|
||||
Per ogni passo fatto nella giusta direzione, infatti, per ogni conquista quotidiana, per ogni miglioramento sul campo, entreremo in un percorso virtuoso per cui il nostro corpo e la nostra mentalità richiederanno automaticamente di essere di nuovo messi alla prova e con obiettivi ancora più sfidanti.
|
||||
Location: 1,724
|
||||
|
||||
Questo il premio: essere diventati atleti migliori, avendo dato tutto e avendo ricevuto in cambio soddisfazione e realizzazione di sé. Insomma, la miglior medaglia da finisher che si possa immaginare, con un traguardo esistenziale sotto il quale voi stessi vi proclamerete, finalmente e con soddisfazione, Ironman.
|
||||
Location: 1,729
|
||||
|
||||
Gli altri e le loro esperienze ci completano, infatti, e possono darci una mano ad andare oltre i nostri limiti. Non avversari, non nemici ma soltanto generatori di positività e di energia a nostro vantaggio.
|
||||
Location: 1,736
|
||||
@@ -0,0 +1,459 @@
|
||||
#[[Books]] #Kindle-Highlights
|
||||
|
||||
Title: [[Hyperfocus: How to Manage Your Attention in a World of Distraction]]
|
||||
Author: [[Chris Bailey]]
|
||||
Last-Read: [[February 10th, 2021]]
|
||||
Amazon-store: https://www.amazon.com/dp/B077LWZC6Q
|
||||

|
||||
|
||||
[[Kindle-Highlights]]
|
||||
|
||||
disconnecting is one of the most powerful ways to spark new and innovative ideas.
|
||||
Location: 136
|
||||
|
||||
constant connectivity is one of the worst disruptions to our focus and productivity.
|
||||
Location: 138
|
||||
|
||||
Working with my email client open and my smartphone on my desk was simply more appealing than trying to concentrate on one or two simple things.
|
||||
Location: 148
|
||||
|
||||
And I began to discover that by focusing deeply on just one important thing at a time—hyperfocusing—we become the most productive version of ourselves.
|
||||
Location: 167
|
||||
|
||||
Attention is finite and is the most valuable ingredient you have to live a good life—so make sure everything you consume is worthy of it. As
|
||||
Location: 212
|
||||
|
||||
it’s only a matter of time until it begins to waver.
|
||||
Location: 230
|
||||
|
||||
Autopilot mode guides us through actions like these. As many as 40 percent of our actions are habits, which shouldn’t require conscious deliberation.
|
||||
Location: 254
|
||||
|
||||
The more we can manage our attention with intention, the more focused, productive, and creative we become.
|
||||
Location: 268
|
||||
|
||||
Directing your attention toward the most important object of your choosing—and then sustaining that attention—is the most consequential decision we will make throughout the day. We are what we pay attention to.
|
||||
Location: 303
|
||||
|
||||
Without selective interest, experience is utter chaos.
|
||||
Location: 338
|
||||
|
||||
Timothy Wilson, a professor of psychology at the University of Virginia, estimates that our brain receives eleven million “bits” of information in the form of sensory experiences each second.
|
||||
Location: 348
|
||||
|
||||
Simply noticing what is occupying our attentional space has been shown to make us more productive.
|
||||
Location: 438
|
||||
|
||||
Remember, we can focus only on forty bits of information, and a single complex task requires most of these bits—and
|
||||
Location: 489
|
||||
|
||||
we can do one small, habitual task plus one other activity that requires most of our attention.
|
||||
Location: 502
|
||||
|
||||
Intention enables us to prioritize so we don’t overload our attentional space.
|
||||
Location: 528
|
||||
|
||||
At any one time, your attentional space should hold at most two key things that you are processing: what you intend to accomplish and what you’re currently doing.
|
||||
Location: 530
|
||||
|
||||
The best way to avoid this overload is to be more selective with what you permit into your attentional space.
|
||||
Location: 545
|
||||
|
||||
Simplifying our attentional space lets us maintain enough room to work and live intentionally throughout the day.
|
||||
Location: 548
|
||||
|
||||
The state of your attentional space determines the state of your life. When your attentional space is overwhelmed, you, in turn, feel overwhelmed. When your attentional space is clear, you also feel clear. The tidier you keep your attentional space, the more clearly you think.
|
||||
Location: 549
|
||||
|
||||
Continually seeking novel stimuli makes us feel more productive—after all, we’re doing more in each moment. But again, just because we’re busier doesn’t mean we’re getting more accomplished.
|
||||
Location: 560
|
||||
|
||||
Our brain provides a hit of dopamine after sex as a reward for procreating. It does so when we consume sugar, which is energy-dense and enables us to survive longer with less food, which was useful early in our evolution, when conditions weren’t as bountiful as they are today.
|
||||
Location: 566
|
||||
|
||||
productivity means accomplishing what we intend to.
|
||||
Location: 575
|
||||
|
||||
Productivity is not about cramming more into our days but about doing the right thing in each moment.
|
||||
Location: 579
|
||||
|
||||
because it is only when we pay attention to something that our brain actively encodes it into memory.
|
||||
Location: 590
|
||||
|
||||
Leroy coined the term “attention residue” to describe the fragments of the previous task that remain in our attentional space after we shift to another activity:
|
||||
Location: 618
|
||||
|
||||
Time pressure narrows our focus on the task, restricting us from considering a number of more creative ways to complete it.
|
||||
Location: 629
|
||||
|
||||
the best time to take a break is after you’ve finished a big task.
|
||||
Location: 636
|
||||
|
||||
set intentions more often, modify your environment to be less distracting, overcome the mental resistance you have to certain tasks, eliminate distractions before they derail you, and clear the distractions inside your own head.
|
||||
Location: 642
|
||||
|
||||
Hyperfocus means you’re less busy, because you’re permitting fewer objects into your attentional space.
|
||||
Location: 684
|
||||
|
||||
The most important aspect of hyperfocus is that only one productive or meaningful task consumes your attentional space.
|
||||
Location: 692
|
||||
|
||||
Save hyperfocus for your most complex tasks—things
|
||||
Location: 708
|
||||
|
||||
preventing
|
||||
Location: 715
|
||||
|
||||
yourself from focusing on things that aren’t important.
|
||||
Location: 715
|
||||
|
||||
autopilot.
|
||||
Location: 717
|
||||
|
||||
When you’re engaged only with the thoughts in your head, you’re daydreaming.
|
||||
Location: 718
|
||||
|
||||
choose a productive or meaningful object of attention; eliminate as many external and internal distractions as you can; focus on that chosen object of attention; and continually draw your focus back to that one object of attention.
|
||||
Location: 727
|
||||
|
||||
intention absolutely has to precede attention.
|
||||
Location: 737
|
||||
|
||||
The second step to reaching hyperfocus is eliminating as many internal and external distractions as possible.
|
||||
Location: 737
|
||||
|
||||
our mind wanders for 47 percent of the day.
|
||||
Location: 749
|
||||
|
||||
takes an average of twenty-two minutes to resume working on a task after we’re distracted or interrupted.
|
||||
Location: 751
|
||||
|
||||
keep one important, complex object of attention in your awareness as you work.
|
||||
Location: 755
|
||||
|
||||
The best way to become more productive is to choose what you want to accomplish before you begin working.
|
||||
Location: 758
|
||||
|
||||
When we don’t choose which quadrants of tasks to spend time on, we fall into autopilot.
|
||||
Location: 764
|
||||
|
||||
But whenever possible, you should take an active role in choosing where you spend your time and attention.
|
||||
Location: 768
|
||||
|
||||
the best productivity tactics are the ones that require you to step back and remove yourself from your work so you have the mental space to think critically about how you should approach that work differently.
|
||||
Location: 773
|
||||
|
||||
Rule of 3: at the start of each day, choose the three things you want to have accomplished by day’s end.
|
||||
Location: 780
|
||||
|
||||
By forcing yourself to pick just three main intentions at the start of each day, you accomplish several things.
|
||||
Location: 783
|
||||
|
||||
an appointment-free day means you can set intentions to accomplish more important and less urgent tasks.
|
||||
Location: 786
|
||||
|
||||
Because three ideas fit comfortably within your attentional space, you can recall and remember your
|
||||
Location: 788
|
||||
|
||||
you may also find it handy to set three weekly intentions, as well as three daily personal intentions—such
|
||||
Location: 794
|
||||
|
||||
The most important tasks on your list are the ones that lead to the greatest positive consequences. What will be different in the world—or
|
||||
Location: 799
|
||||
|
||||
What task is the equivalent of a domino in a line of one hundred that, once it topples over, initiates a chain reaction that lets you accomplish a great deal?
|
||||
Location: 801
|
||||
|
||||
Writing a guide for new hires may not, in the moment, feel as valuable as answering a dozen emails, but if that guide cuts down on the time it takes to bring each new employee on board, makes her feel more welcome, and also serves to make her more productive, it is easily the most consequential thing on your list.
|
||||
Location: 808
|
||||
|
||||
When your hourly chime rings, ask yourself the following:
|
||||
Location: 827
|
||||
|
||||
setting intentions but also making them very specific. While
|
||||
Location: 848
|
||||
|
||||
Deciding in advance when you’ll work on a task is significantly more important for a difficult one than when your intention is to do something simple.
|
||||
Location: 885
|
||||
|
||||
Whenever you can! Naturally, we need time for the little things, but the more you can hyperfocus, the better.
|
||||
Location: 913
|
||||
|
||||
Around the constraints of your work. Most of us don’t have the luxury of hyperfocusing whenever we wish.
|
||||
Location: 920
|
||||
|
||||
When you need to work on a complex task.
|
||||
Location: 924
|
||||
|
||||
Based on how averse you are to what you intend to accomplish.
|
||||
Location: 927
|
||||
|
||||
we switch between computer applications 566 times during the average workday.
|
||||
Location: 970
|
||||
|
||||
The costs of an unrelated interruption can be massive: it takes an average of twenty-five minutes to resume working on an activity after we’re interrupted, and before resuming that activity, we work on an average of 2.26 other tasks.
|
||||
Location: 980
|
||||
|
||||
When our brain is even slightly resisting a task, it hunts for more attractive things it could do instead.
|
||||
Location: 988
|
||||
|
||||
I’m typing these words in one window on my computer screen,
|
||||
Location: 997
|
||||
|
||||
If I don’t disable computer distractions ahead of time, I might as well wave good-bye to my productivity.
|
||||
Location: 1,000
|
||||
|
||||
Eliminating distractions before you hunker down on a task makes focusing infinitely easier, as important tasks fill your attentional space quite naturally when there is nothing competing with them.
|
||||
Location: 1,011
|
||||
|
||||
productive tasks that are either necessary or purposeful,
|
||||
Location: 1,015
|
||||
|
||||
Jerry Martin’s
|
||||
Location: 1,363
|
||||
|
||||
Something remarkable happens when you externalize tasks and commitments: you work with almost no guilt, worry, or doubt. You experience guilt when you feel tension about your past; worry when you feel tension about your future; and doubt and stress when you feel tension about the present moment. These feelings evaporate when you set intentions and make a rough plan for how you’ll complete your important tasks. You’ll think more clearly too—externalizing what’s on your mind means tasks and commitments won’t pop into your attentional space as you’re working.
|
||||
Location: 1,394
|
||||
|
||||
three measures we can use to measure the quality of our attention:
|
||||
Location: 1,416
|
||||
|
||||
how much time we spend working with intention;
|
||||
Location: 1,417
|
||||
|
||||
how long we’re able to focus on one task;
|
||||
Location: 1,417
|
||||
|
||||
how long our mind wanders before we catch it doing so.
|
||||
Location: 1,418
|
||||
|
||||
Creating a distraction-free mode
|
||||
Location: 1,419
|
||||
|
||||
Working with fewer distractions
|
||||
Location: 1,420
|
||||
|
||||
four stages of hyperfocus: choosing an object of attention, eliminating distractions, focusing on a task, and getting back on track.
|
||||
Location: 1,431
|
||||
|
||||
Little did I know that this guilt had two sources: a lack of working with intent and my work expanding to fill how much time I had for it.
|
||||
Location: 1,490
|
||||
|
||||
doing mindless stuff at work or at home is not only unproductive but also a sign you don’t have enough important work.
|
||||
Location: 1,494
|
||||
|
||||
“the most validated technique for minimizing the disruptive effects of mind wandering.”
|
||||
Location: 1,545
|
||||
|
||||
forty-five-minute meditation exercise twice a
|
||||
Location: 1,547
|
||||
|
||||
Headspace and Insight Timer,
|
||||
Location: 1,554
|
||||
|
||||
Mindfulness
|
||||
Location: 1,561
|
||||
|
||||
it’s about focusing on the circumstances of the present, rather than becoming immersed in them.
|
||||
Location: 1,561
|
||||
|
||||
mindful shower is one in which you focus on the sights, sounds, and sensations of the present, which enables you to train your brain to better focus on what’s in front of you.
|
||||
Location: 1,565
|
||||
|
||||
When you keep a single intention in mind, you’re able to live and work more intentionally for the rest of the day too.
|
||||
Location: 1,580
|
||||
|
||||
few practices will improve the quality of your attention—and the size of your attentional space—more than meditation and mindfulness. While
|
||||
Location: 1,598
|
||||
|
||||
It’s a remarkable thing when you spend not just quality time with someone but quality attention as well.
|
||||
Location: 1,619
|
||||
|
||||
At work, the more attention you give to what’s in front of you, the more productive you become. At home, the more attention you devote to what’s in front of you, the more meaningful your life becomes.
|
||||
Location: 1,628
|
||||
|
||||
solidify a hyperfocus ritual in your work and life: how to battle your inevitable resistance to the mode.
|
||||
Location: 1,633
|
||||
|
||||
ten minutes, you may have felt what I did at first: a mental resistance to focusing on just one thing. This was probably a mixture of restlessness, anxiousness, and succumbing to novel distractions.
|
||||
Location: 1,634
|
||||
|
||||
Understanding the four types of productive and unproductive work tasks lets
|
||||
Location: 1,660
|
||||
|
||||
Recognizing the limits of our attention enables us to become aware of how few things we’re able to focus on in the moment.
|
||||
Location: 1,661
|
||||
|
||||
Hyperfocusing on our most complex, productive tasks lets us activate the most productive mode of our brains and get a large amount accomplished in a short amount of time.
|
||||
Location: 1,662
|
||||
|
||||
Setting strong daily intentions
|
||||
Location: 1,663
|
||||
|
||||
Creating a personalized distraction-free mode, and a reduced-distractions mode,
|
||||
Location: 1,664
|
||||
|
||||
Simplifying our working and living environments
|
||||
Location: 1,665
|
||||
|
||||
Clearing our minds using waiting-for, task, and worry lists lets us work with clarity and prevents unresolved mental loops from interrupting our focus throughout the day.
|
||||
Location: 1,666
|
||||
|
||||
good custodians of our attentional space—by
|
||||
Location: 1,668
|
||||
|
||||
attention is the most important ingredient we have to living a good, productive life.
|
||||
Location: 1,677
|
||||
|
||||
scatterfocus
|
||||
Location: 1,683
|
||||
|
||||
Let’s dive into this second mental mode now. As you’ll quickly see, hyperfocus and scatterfocus can work hand in hand in some truly remarkable ways.
|
||||
Location: 1,687
|
||||
|
||||
Just as hyperfocus is your brain’s most productive mode, scatterfocus is its most creative.
|
||||
Location: 1,706
|
||||
|
||||
First, as I’ll discuss in this chapter, it allows you to set intentions and plan for the future. It’s impossible to set future intentions when you’re immersed in the present. By
|
||||
Location: 1,710
|
||||
|
||||
Second, scatterfocus lets you recharge.
|
||||
Location: 1,713
|
||||
|
||||
Scatterfocus replenishes that supply so you can focus for longer.
|
||||
Location: 1,714
|
||||
|
||||
Third, scatterfocus fosters creativity.
|
||||
Location: 1,715
|
||||
|
||||
more creativity your job or a project requires, the more you should deliberately deploy scatterfocus.
|
||||
Location: 1,717
|
||||
|
||||
attention management.
|
||||
Location: 1,763
|
||||
|
||||
provides scientific evidence for what makes scatterfocus so fruitful.
|
||||
Location: 1,765
|
||||
|
||||
This is precisely why scattering your attention allows your creativity to flourish as you travel through time and connect what you’ve learned to what you’re doing or what you want to achieve.
|
||||
Location: 1,767
|
||||
|
||||
The more time you spend scatterfocusing between tasks—rather than indulging in distractions—the more thoughtful and productive your actions become.
|
||||
Location: 1,798
|
||||
|
||||
I’ve found it helpful to distinguish among a few different styles of scatterfocus:
|
||||
Location: 1,818
|
||||
|
||||
Capture Mode As I mentioned in chapter 5, clearing your mind of open loops is a powerful productivity tactic.
|
||||
Location: 1,825
|
||||
|
||||
probably find capture mode to be the most aversive—at
|
||||
Location: 1,845
|
||||
|
||||
Problem-crunching mode is most useful when you’re brainstorming a solution to a specific problem.
|
||||
Location: 1,848
|
||||
|
||||
the more often we scatterfocus to replenish our mental energy, the more energy we have for our most important tasks.
|
||||
Location: 2,024
|
||||
|
||||
Switching often among tasks and being unable to sustain focus on one thing
|
||||
Location: 2,034
|
||||
|
||||
Losing your grip on your intentions and working in a more reactive way
|
||||
Location: 2,035
|
||||
|
||||
Getting tasks done at a noticeably slower rate (e.g., reading the same important email several times to comprehend it)
|
||||
Location: 2,035
|
||||
|
||||
Opting to do less important, more mindless work—like checking email, social media, etc. Unintentionally slipping into scatterfocus mode
|
||||
Location: 2,036
|
||||
|
||||
Research has shown that a refreshing work break should have three characteristics. It should be low-effort and habitual; something you actually want to do; and something that isn’t a chore (unless you genuinely enjoy doing the chore).
|
||||
Location: 2,043
|
||||
|
||||
You can use scatterfocus mode to become more creative in two ways: first, by connecting more dots; and second, by collecting more valuable dots—a
|
||||
Location: 2,165
|
||||
|
||||
Hyperfocus is about focusing on a single thing. This lets your brain become productive, encode information and experiences so that you remember them later, and engage with the world around you.
|
||||
Location: 2,166
|
||||
|
||||
In scatterfocus mode you do the opposite: you zoom out and connect the constellations of “dots” in your head (a “dot” being any piece of information you hold in your mind).
|
||||
Location: 2,168
|
||||
|
||||
For example, try stopping work on a complicated report midway through a sentence.
|
||||
Location: 2,288
|
||||
|
||||
the more we know about a subject, the less attentional space that information consumes.
|
||||
Location: 2,316
|
||||
|
||||
We can work with more expertise and creativity because we’ve already done the due diligence to cluster this information together.
|
||||
Location: 2,324
|
||||
|
||||
We are what we pay attention to, and almost nothing influences our productivity and creativity as much as the information we’ve consumed in the past.
|
||||
Location: 2,331
|
||||
|
||||
If you’re a software engineer, taking a course to learn a new programming language or reading a book on managing engineers is obviously a productive use of your time, attention, and energy.
|
||||
Location: 2,355
|
||||
|
||||
Your brain even releases more dopamine, a pleasure chemical, when you consume information that supports what you know.
|
||||
Location: 2,358
|
||||
|
||||
useful dots we consume. This information is actionable, is accurate, helps us reach our goals, and remains relevant for a long time.
|
||||
Location: 2,370
|
||||
|
||||
Having an unlimited amount of energy to consume useful information throughout the day would be ideal, but this obviously isn’t possible, even if we frequently replenish our supply of mental energy.
|
||||
Location: 2,376
|
||||
|
||||
consume more useful information, especially when we have the energy to process something more dense; consume balanced information when we have less energy; consume entertaining information with intention or when we’re running low on energy and need to recharge; and consume less trashy information.
|
||||
Location: 2,387
|
||||
|
||||
It’s impossible to become more productive or creative without first reflecting on your work and life—this
|
||||
Location: 2,395
|
||||
|
||||
public speaking.
|
||||
Location: 2,451
|
||||
|
||||
There are some topics you know more about, and some things you’re better at, than almost anyone in the world. The more dots you collect around these particular topics or skills, the more of an expert you’ll become.
|
||||
Location: 2,454
|
||||
|
||||
Malcolm Gladwell wrote: “Practice isn’t the thing you do once you’re good. It’s the thing you do that makes you good.”
|
||||
Location: 2,469
|
||||
|
||||
As he put it, “I have no special talents, I am only passionately curious.”
|
||||
Location: 2,474
|
||||
|
||||
Daniel Levitin, the author of This Is Your Brain on Music, proposed a theory to account for Mozart’s musical genius. “We don’t know how much Mozart practiced,” Levitin writes, “but if he started at age two and worked thirty-two hours a week (quite possible, given his father’s reputation as a stern taskmaster) he would have made his first 10,000 hours by the age of eight.” The “ten-thousand-hour rule” is a popular one—it’s the length of effortful practice, some suggest, that it takes to acquire an expert level of performance at a certain skill.
|
||||
Location: 2,479
|
||||
|
||||
let your mind rest and wander—preferably while doing something habitual.
|
||||
Location: 2,487
|
||||
|
||||
Hyperfocus consumes mental energy, while scatterfocus is energy restorative.
|
||||
Location: 2,489
|
||||
|
||||
When we focus, we consume and collect dots; when we scatter our attention, we connect these dots.
|
||||
Location: 2,521
|
||||
|
||||
Hyperfocusing allows us to remember more, which leads to more valuable connections made in scatterfocus mode.
|
||||
Location: 2,521
|
||||
|
||||
Practicing hyperfocus and working with fewer distractions helps focus more attention on the present.
|
||||
Location: 2,542
|
||||
|
||||
you plan for the future less often and assemble fewer productive ideas.
|
||||
Location: 2,558
|
||||
|
||||
The Zeigarnik effect—which keeps unresolved problems front of mind—forces you to think of them more.
|
||||
Location: 2,561
|
||||
|
||||
Harvard-trained psychologist Shawn Achor found that happier people are 31 percent more productive than those in a negative or neutral state.
|
||||
Location: 2,565
|
||||
|
||||
Happiness also helps you become more creative in scatterfocus mode.
|
||||
Location: 2,566
|
||||
|
||||
Creative Prime Time.
|
||||
Location: 2,600
|
||||
|
||||
Your attention is the most powerful tool at your disposal to live and work with greater productivity, creativity, and purpose.
|
||||
Location: 2,721
|
||||
@@ -0,0 +1,3 @@
|
||||
#[[Books]]
|
||||
|
||||
#URL per recuperare i frammenti evidenziati dei libri letti: [Kindle: Your Notes and Highlights (amazon.com)](https://read.amazon.com/notebook)
|
||||
@@ -0,0 +1,6 @@
|
||||
- I'm Claudio DI Sipio, I'm a PhD student in computer science and I'm currently working on recommender systems. They are developed by exploiting machine learning algorithms.
|
||||
- My research focuses on the development of new methods for the construction of recommender systems, which are able to provide more accurate and personalized recommendations.
|
||||
- In particular, I am interested in methods that use a combination of humans and machines to enhance the quality of recommendations.
|
||||
- Some methods that use a combination of humans and machines to enhance the quality of recommendations are crowdsourcing and active learning.
|
||||
-
|
||||
-
|
||||
@@ -0,0 +1,2 @@
|
||||
- [[@Computing in the Continuum: Combining Pervasive Devices and Services to Support Data-Driven Applications]]
|
||||
-
|
||||
@@ -0,0 +1,6 @@
|
||||
-
|
||||
- Rendicontazione borse PON
|
||||
- Rendicontazione borse PNRR
|
||||
-
|
||||
- Data nomina 24/08/2022
|
||||
- Numero provvidemonto
|
||||
@@ -0,0 +1,12 @@
|
||||
---
|
||||
tags:#dailynotes
|
||||
---
|
||||
2021-01-17, 12:31
|
||||
---
|
||||
# Notes created today already
|
||||
```query
|
||||
2021-01-17 -'2021-01-17'
|
||||
```
|
||||
|
||||
|
||||
|
||||
@@ -0,0 +1,31 @@
|
||||
---
|
||||
tags:
|
||||
- '#dailynotes'
|
||||
created: 2021-04-07
|
||||
title: '2021-04-07'
|
||||
---
|
||||
# 2021-04-07
|
||||
Created: 2021-04-07, 17:11
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Notes created on 2021-04-07
|
||||
|
||||
```query
|
||||
2021-04-07 -'2021-04-07'
|
||||
```
|
||||
|
||||
|
||||
## Tasks from Todoist
|
||||
```todoist
|
||||
{
|
||||
"name": "2021-04-07",
|
||||
"filter": "2021-04-07",
|
||||
"sorting": ["priority","date"],
|
||||
"group" : true
|
||||
}
|
||||
```
|
||||
|
||||
@@ -0,0 +1,31 @@
|
||||
---
|
||||
tags:
|
||||
- '#dailynotes'
|
||||
created: {{tp_date:YYYY-MM-DD}}
|
||||
title: '{{tp_title}}'
|
||||
---
|
||||
# {{tp_title}}
|
||||
Created: {{tp_date:YYYY-MM-DD}}, {{tp_time:HH:mm}}
|
||||
|
||||
|
||||
{{tp_cursor}}
|
||||
|
||||
|
||||
|
||||
## Notes created on {{tp_date:YYYY-MM-DD}}
|
||||
|
||||
```query
|
||||
{{tp_title}} -'{{tp_title}}'
|
||||
```
|
||||
|
||||
|
||||
## Tasks from Todoist
|
||||
```todoist
|
||||
{
|
||||
"name": "{{tp_date:YYYY-MM-DD}}",
|
||||
"filter": "{{tp_date:YYYY-MM-DD}}",
|
||||
"sorting": ["priority","date"],
|
||||
"group" : true
|
||||
}
|
||||
```
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
Todoist:: [Todoist](https://todoist.com/showTask?id=5951923691)
|
||||
type:: [[conferencePaper]]
|
||||
status:: [[REJECTED]]
|
||||
venue:: ICSE2023
|
||||
full-title:: DeepMig
|
||||
year:: 2023
|
||||
|
||||
- Sezione 2 va rivista ancora la terminologia e verificare se la versione attuale e' ok
|
||||
- Rivista parte iniziale di Sez IIB, probabilmente va migliorato.
|
||||
@@ -0,0 +1,18 @@
|
||||
---
|
||||
tags:
|
||||
- '#meetings'
|
||||
created: {{tp_date:YYYY-MM-DD}}
|
||||
title: '{{tp_title}}'
|
||||
---
|
||||
|
||||
# {{tp_title}}
|
||||
|
||||
**Date**: {{tp_date:YYYY-MM-DD}}
|
||||
**Time**: {{tp_time:HH:mm}}
|
||||
**Attendend**: #attendance
|
||||
**Project**: #projects
|
||||
**People attended**: #people
|
||||
|
||||
---
|
||||
|
||||
{{tp_cursor}}
|
||||
@@ -0,0 +1,8 @@
|
||||
title:: Finalmente Ho Capito! La Filosofia (highlights)
|
||||
author:: [[Marina Visentin]]
|
||||
full-title:: "Finalmente Ho Capito! La Filosofia"
|
||||
category:: #[[Books]]
|
||||
|
||||
- 
|
||||
- Highlights first synced by [[Readwise]] [[19-08-2022]]
|
||||
- idee dei principali filosofi, tutti i concetti chiave, le correnti, le scuole e i movimenti. ([Location 7](https://readwise.io/to_kindle?action=open&asin=B0727N8PCG&location=7))
|
||||
@@ -0,0 +1,19 @@
|
||||
|
||||
**Services-Collegio-Docenti-Dottorato**
|
||||
|
||||
**TODOs**
|
||||
<iframe width="80%" height=500 src=https://beta.todoist.com/app/project/2196985010></iframe>
|
||||
|
||||
|
||||
**Emails**
|
||||
["WORK/Services/Services-Collegio-Dottorato-DISIM" - davide.diruscio@gmail.com - Gmail (google.com)](https://mail.google.com/mail/u/0/#label/WORK%2FServices%2FServices-Collegio-Dottorato-DISIM)
|
||||
|
||||
**Notes**
|
||||
```query
|
||||
tag:#services/phd
|
||||
```
|
||||
|
||||
- Note-taking app pages
|
||||
- Additional links
|
||||
- MS Teams
|
||||
- Calendars
|
||||
@@ -0,0 +1,35 @@
|
||||
type:: [[weblink]]
|
||||
source:: [How ChatGPT and Other LLMs Work—and Where They Could Go Next | WIRED](https://www.wired.com/story/how-chatgpt-works-large-language-model/?utm_medium=email&utm_source=pocket_hits&utm_campaign=POCKET_HITS-EN-DAILY-SPONSORED&BABBEL-2023_05_01&sponsored=0&position=10&scheduled_corpus_item_id=3cca70c0-9c13-4244-b6ba-e50bdbe346cb)
|
||||
tags:: [[readingnotes]]
|
||||
date:: [[01-05-2023]] - 18:10
|
||||
|
||||
- How ChatGPT and Other LLMs Work—and Where They Could Go Next
|
||||
- Large language models like AI chatbots seem to be everywhere. If you understand them better, you can use them better.
|
||||
-
|
||||
- AI-POWERED CHATBOTS SUCH as [ChatGPT](https://www.wired.com/story/11-tips-better-chatgpt-prompts/) and [Google Bard](https://www.wired.com/story/11-better-prompts-google-bard/) are certainly having a moment—the next generation of conversational software tools promise to do everything from taking over our web searches to producing an endless supply of creative literature to remembering all the world's knowledge so we don't have to.
|
||||
- ChatGPT, Google Bard, and other bots like them, are examples of [large language models](https://en.wikipedia.org/wiki/Large_language_model), or LLMs, and it's worth digging into how they work. It means you'll be able to better make use of them, and have a better appreciation of what they're good at (and what they really shouldn't be trusted with).
|
||||
- Like a lot of artificial intelligence systems—like the ones designed to recognize your voice or generate cat pictures—LLMs are trained on huge amounts of data. The companies behind them have been rather circumspect when it comes to revealing where exactly that data comes from, but there are certain clues we can look at.
|
||||
- For example, [the research paper](https://arxiv.org/abs/2201.08239) introducing the LaMDA (Language Model for Dialogue Applications) model, which Bard is built on, mentions Wikipedia, “public forums,” and “code documents from sites related to programming like Q&A sites, tutorials, etc.” Meanwhile, Reddit [wants to start charging](https://www.theregister.com/2023/04/18/reddit_charging_ai_api/) for access to its 18 years of text conversations, and [StackOverflow just announced](https://www.wired.com/story/stack-overflow-will-charge-ai-giants-for-training-data/) plans to start charging as well. The implication here is that LLMs have been making extensive use of both sites up until this point as sources, entirely for free and on the backs of the people who built and used those resources. It's clear that a lot of what's publicly available on the web has been scraped and analyzed by LLMs.
|
||||
- [Flow chart outlining three step LLM training model](https://media.wired.com/photos/644c750f3d9e6b1cb17a86d9/master/w_1600%2Cc_limit/How-LLMs-Work-Business-01-model.jpg)
|
||||
- LLMs use a combination of machine learning and human input. OPENAI VIA DAVID NIELD
|
||||
- All of this text data, wherever it comes from, is processed through a neural network, a commonly used type of AI engine made up of multiple nodes and layers. These networks continually adjust the way they interpret and make sense of data based on a host of factors, including the results of previous trial and error. Most LLMs use a specific neural network architecture [called a transformer](https://en.wikipedia.org/wiki/Transformer_(machine_learning_model)), which has some tricks particularly suited to language processing. (That GPT after Chat stands for Generative Pretrained Transformer.)
|
||||
- Specifically, a transformer can read vast amounts of text, spot patterns in how words and phrases relate to each other, and then make predictions about what words should come next. You may have heard LLMs being compared to supercharged autocorrect engines, and that's actually not too far off the mark: ChatGPT and Bard don't really “know” anything, but they are very good at figuring out which word follows another, which starts to look like real thought and creativity when it gets to an advanced enough stage.
|
||||
- One of the key innovations of these transformers is the self-attention mechanism. It's difficult to explain in a paragraph, but in essence it means words in a sentence aren't considered in isolation, but also in relation to each other in a variety of sophisticated ways. It allows for a greater level of comprehension than would otherwise be possible.
|
||||
- There is some randomness and variation built into the code, which is why you won't get the same response from a transformer chatbot every time. This autocorrect idea also explains how errors can creep in. On a fundamental level, ChatGPT and Google Bard don't know what's accurate and what isn't. They're looking for responses that seem plausible and natural, and that match up with the data they've been trained on.
|
||||
- So, for example, a bot might not always choose the most likely word that comes next, but the second- or third-most likely. Push this too far, though, and the sentences stop making sense, which is why LLMs are in a constant state of self-analysis and self-correction. Part of a response is of course down to the input, which is why you can ask these chatbots to simplify their responses or make them more complex.
|
||||
- [Screenshot of Google Bard with prompt give me a hidden gem from the R.E.M back catalog.](https://media.wired.com/photos/644c75100124a91cee27d77b/master/w_1600%2Cc_limit/How-LLM-Work-Business-02-bard.jpg)
|
||||
- GOOGLE VIA DAVID NIELD
|
||||
- You might also notice generated text being rather generic or clichéd—perhaps to be expected from a chatbot that's trying to synthesize responses from giant repositories of existing text. In some ways these bots are churning out sentences in the same way that a spreadsheet tries to find the average of a group of numbers, leaving you with output that's completely unremarkable and middle-of-the-road. Get ChatGPT to talk like a cowboy, for instance, and it'll be the most unsubtle and obvious cowboy possible.
|
||||
- Human beings are involved in all of this too (so we're not quite redundant, yet): Trained supervisors and end users alike help to train LLMs by pointing out mistakes, ranking answers based on how good they are, and giving the AI high-quality results to aim for. Technically, it's known as “reinforcement learning on human feedback” (RLHF). LLMs then refine their internal neural networks further to get better results next time. (These are still relatively early days for the technology at this level, but we've already seen numerous notices of upgrades and improvements from developers.)
|
||||
- As these LLMs get bigger and more complex, their capabilities will improve. We know that ChatGPT-4 has [in the region of](https://www.wired.com/story/cerebras-chip-cluster-neural-networks-ai/) 100 trillion parameters, up from 175 million in ChatGPT 3.5—a parameter being a mathematical relationship linking words through numbers and algorithms. That's a vast leap in terms of understanding relationships between words and knowing how to stitch them together to create a response.
|
||||
- From the way LLMs work, it's clear that they're excellent at mimicking text they've been trained on, and producing text that sounds natural and informed, albeit a little bland. Through their “advanced autocorrect” method, they're going to get facts right most of the time. (It's clear what follows “the first president of the USA was …”) But it's here where they can start to fall down: The most _likely_ next word isn't always the _right_ one.
|
||||
- Get More From WIRED
|
||||
- 📧 Get the best stories from [WIRED’s iconic archive](https://www.wired.com/newsletter/classics?sourceCode=BottomStories) in your inbox
|
||||
- 🎧 Our new [podcast](https://www.wired.com/podcasts) wants you to [_Have a Nice Future_](https://www.wired.com/podcast/have-a-nice-future/)
|
||||
- My balls-out quest to achieve [the perfect scrotum](https://www.wired.com/story/my-balls-out-quest-to-achieve-the-perfect-scrotum/)
|
||||
- As sea levels rise, the East Coast [is also sinking](https://www.wired.com/story/as-sea-levels-rise-the-east-coast-is-also-sinking/)
|
||||
- Everything you need to know [about ethernet](https://www.wired.com/story/what-is-ethernet/)
|
||||
- The case [against momfluencers](https://www.wired.com/story/momfluencers-essay/)
|
||||
- So your kid wants to be a [Twitch streamer](https://www.wired.com/story/so-your-kid-wants-to-be-a-twitch-streamer-three-questions/)
|
||||
- ⛺ Embrace the new season with the Gear team’s best picks for best [tents](https://www.wired.com/gallery/best-camping-tents/), [umbrellas](https://www.wired.com/gallery/best-umbrellas/), and [robot vacuums](https://www.wired.com/gallery/best-robot-vacuums/)
|
||||
- [David Nield](https://www.wired.com/author/david-nield) is a tech journalist from Manchester in the UK, who has been writing about apps and gadgets for more than two decades. You can follow him on [Twitter](https://twitter.com/davidnield).
|
||||
@@ -0,0 +1,3 @@
|
||||
-
|
||||
-
|
||||
-
|
||||
@@ -0,0 +1,51 @@
|
||||
- ```
|
||||
title:: Do Developers Benefit from Recommendations when Repairing Inconsistent Design Models? A Controlled Experiment
|
||||
link:: [#685 - ICSE 2023 (hotcrp.com)](https://icse2023.hotcrp.com/paper/685)
|
||||
external-link:: 
|
||||
|
||||
- ### Paper summary
|
||||
- The paper presents a controlled experiment to investigate how Repair Recommendations (RRs) are perceived and used by developers while repairing design models.
|
||||
- The experiments were performed by involving 24 developers in eight different tasks, with repair recommendations provided in half of the tasks. The authors compared the results of the tasks performed with and without RRs. According to the completed investigation, developers benefit from RRs while working on complex tasks.
|
||||
- ### Strengths
|
||||
- Paper about a relevant topic
|
||||
- Overall well written and structured
|
||||
- ### Weaknesses
|
||||
- Not convincing result conclusions
|
||||
- ### Comments for the authors
|
||||
- **Significance:** The paper is about a significant problem. The performed controlled experiment permits the assessment of how model repairing tools are considered by developers. The critical point is that given a set of models to be repaired, each developer can fix inconsistencies differently. Thus, it is crucial to understand the developers' preferences when repairing models so that it is possible to understand how to improve currently existing tools.
|
||||
- **Soundness:** My main concerns about the paper are related to its soundness. In particular, the authors performed and reported the controlled experiments in a manner which is independent of the technique used to produce repair recommendations. While reading the paper, since the abstract, the reader asks herself, what is the tool/method/technique that provided the recommended recommendations for the task considered in the study? The performed user study might have a sense if authors want to assess the efficiency and effectiveness of a novel recommendation tool using a user study. However, in that case, the authors should have considered an existing baseline and compared the approach with it.
|
||||
- While reading the paper, I raised to myself the following question: "is it possible to do the investigation in an approach-independent manner?" Honestly, I don't think so. Doing the investigation with relevant recommendations or with recommendations that might not have sense can change the outcome of the study! In particular, RRs that are not relevant would affect the EFT, which is currently always 1, as discussed in sec. IV. In other words, we are assuming here that repairing recommendations given by tools are always correct that might not always be the case!
|
||||
- Providing repair recommendations is always preferable. Effectiveness and efficiency can be changed depending on how such recommendations are shown to the user. The opinion of developers can change depending on "how good" recommendations are, and consequently, it is not possible to evaluate how RRs are perceived, whatever they are produced!
|
||||
- **Novelty:** The authors present a novel investigation. Typically repair recommendations are evaluated by assessing their performance while discarding the related perception of the final users, i.e., developers. In this respect, the authors presented a novel work because they explicitly investigate how Repair Recommendation tools are perceived by the final users (i.e., developers) while doing their repair modelling activities.
|
||||
- **Verifiability and Transparency:** The artifacts produced during the experiments are in an online appendix, which is well-structured and organized.
|
||||
- **Presentation:** The paper is overall well-written and structured. I would suggest the authors improve the introduction by mentioning what kinds of models the investigation is about and, in particular, at which stage of the development process developers have been interviewed.
|
||||
- ### Question for authors
|
||||
- Q1: Why do the authors believe that the performed investigation can be done independently from the quality/relevance of the repair recommendations and, thus, independently from the tools that produced them?
|
||||
- Q2: Which tool have the authors used to produce the considered recommendations, and how it performs with existing tools?
|
||||
- NOTES
|
||||
- ((635c0dda-2f1c-40e8-81c2-3a5a0e186183))
|
||||
- Who provided repair recommendations?
|
||||
- ((635c1672-e5d1-4c47-8a8c-ca1860206644))
|
||||
- ((635c1695-1b9d-4d93-a931-9e5aa79d2e68))
|
||||
- ((635c1872-ea83-4b71-b049-f8ce5c14c01f))
|
||||
- ((635c16c1-bed9-4507-8ede-d0456ba202ee))
|
||||
- Concerning RQ3, how is provided and managed user feedback?
|
||||
- ((635c1e75-dc61-4a8e-b14d-b7623255328a))
|
||||
- It is not clear what they are evaluating and thus the goal of the paper. Are your presenting a novel approach to provide repair recommendation and then present the user study you have done to evaluate the approach? So the contribution of the paper is THE APPROACH. If the evaluation if "approach independent", then, what are you evaluating?
|
||||
- ==If you are proposing a novel approach for repair recommendations, then you have to consider one of the considered approach as baseline!==
|
||||
- ((635c1fff-cda0-492c-9dd6-24c4a0857d9f))
|
||||
- In my opinion, this cannot be "approach"-independent. The opinion of developers can change depending on "how good" recommendations are, and consequently, it is not possible to evaluate how RRs are perceived, whatever they are produced!
|
||||
- ((635c21f0-a899-4d57-ba56-50412ee9ff65))
|
||||
- Again this cannot be assessed independently from the recommendation tool that is used
|
||||
- ((635c55a9-61e4-4da2-8312-6f645abb8be4))
|
||||
- ==Same problem here, like the previous comment!==
|
||||
- ((635c213f-585f-465f-b19b-bb2f60a862c0))
|
||||
- Why 60 in formula 2 ???
|
||||
- ((635c5fb6-5e69-464b-acb8-1e4727d80780))
|
||||
- By what / who?
|
||||
- In my opinion the question that should be asked is... is it possible to do the investigation done in the paper in an approach independent manner? Honestly, I don't think so! Doing the investigation with recommendations that are relevant or with recommendations that might not have sense, can change the outcome of the study!
|
||||
- RR that are not relevant would affect the EFT, which is always 1 as discussed in sec. IV
|
||||
- We are assuming here that repairing recommendations given by tools are always correct that might not be always the case!
|
||||
- Providing recommendations in my opinion is always preferrable.... what can change the effectiveness and the efficency is the way such recommendations are shown to the user; in other words, the tool support can make the difference.
|
||||
-
|
||||
```
|
||||
@@ -0,0 +1 @@
|
||||
icon:: ⭐️
|
||||
@@ -0,0 +1,10 @@
|
||||
# GOALS FOR THIS MONTH
|
||||
```todoist
|
||||
{
|
||||
"name": " ",
|
||||
"filter": "@month_february",
|
||||
"sorting": ["priority","date"],
|
||||
"group" : true
|
||||
}
|
||||
```
|
||||
|
||||
@@ -0,0 +1,11 @@
|
||||
# Meetings
|
||||
|
||||
```oql
|
||||
name: 'How many notes use #utrecht'
|
||||
query: "'#meetings"
|
||||
template: "table"
|
||||
wrapper: "div"
|
||||
badge: false
|
||||
sort: "created"
|
||||
fields: ['title', 'created', 'tags']
|
||||
```
|
||||
@@ -0,0 +1,11 @@
|
||||
# Reading notes
|
||||
```oql
|
||||
name: 'How many notes use #utrecht'
|
||||
query: "'#readingnotes"
|
||||
template: "table"
|
||||
wrapper: "div"
|
||||
badge: false
|
||||
sort: "created"
|
||||
fields: ['title', 'created', 'tags']
|
||||
```
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
# TASKS FOR TODAY
|
||||
```todoist
|
||||
{
|
||||
"name": " ",
|
||||
"filter": "today",
|
||||
"sorting": ["priority","date"],
|
||||
"group" : true
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,22 @@
|
||||
type:: [[REVIEWS]]
|
||||
tags::
|
||||
year:: 2024
|
||||
venue:: [[JSS]]
|
||||
full-title:: Microservice-based model-driven architecture for implementing modeling and model-transformation as a service
|
||||
date-start:: [[12-01-2024]] - 18:04
|
||||
date-submitted::
|
||||
external-links::
|
||||
status:: [[DOING]]
|
||||
deadline:: [[21-02-2024]]
|
||||
file:: 
|
||||
parent::
|
||||
todoist:: https://app.todoist.com/showTask?id=7589112337
|
||||
|
||||
- ### [[Highlights]]
|
||||
- ### [[Comments]]
|
||||
- ### [[REVIEWS/Notes]]
|
||||
- ### ❓️Questions
|
||||
- {{query (and [[question]] [[JSSOFTWARE-D-23-01192]] )[[question]]}}
|
||||
query-table:: true
|
||||
query-properties:: [:block]
|
||||
-
|
||||
@@ -0,0 +1,10 @@
|
||||
#type:: [[meeting]]
|
||||
#external-#links:: https://www.google.com/calendar/event?eid=NzRwamFwMW83MWdtYWI5bTYwc2ppYjlrNmxoamNiYjI2NWltYWI5bDZvcDY0cGhsNjloamNkcGtjbyBkYXZpZGUuZGlydXNjaW9AbQ
|
||||
tags::
|
||||
#people::
|
||||
#areas::
|
||||
#date:: Jun 24, 2021 02:30PM
|
||||
#title:: Meeting di test
|
||||
#desription::
|
||||
|
||||
-
|
||||
@@ -0,0 +1 @@
|
||||
## 🔖 Articles
|
||||
@@ -0,0 +1,11 @@
|
||||
-
|
||||
- ## 🔖 Articles
|
||||
- [[2307.08925] Federated Large Language Model: A Position Paper](https://omnivore.app/me/https-arxiv-org-abs-2307-08925-18afc718a7f)
|
||||
collapsed:: true
|
||||
site:: [arXiv.org](https://arxiv.org/abs/2307.08925)
|
||||
author:: [Submitted on 18 Jul 2023]
|
||||
labels:: [[FederatedLLMs]] [[ResearchPaper]]
|
||||
date-saved:: [[04-10-2023]]
|
||||
date-archived:: [[]]
|
||||
is-archived::
|
||||
source:: [[Omnivore]]
|
||||
@@ -0,0 +1 @@
|
||||
## 🔖 Articles
|
||||
@@ -0,0 +1,11 @@
|
||||
## 🔖 Articles
|
||||
- [October’s updates newsletter](https://omnivore.app/me/october-s-updates-newsletter-18b04a4ca87)
|
||||
collapsed:: true
|
||||
site:: [blog.omnivore.app](https://blog.omnivore.app/p/octobers-updates-newsletter?isFreemail=true&post_id=137687662&publication_id=509268&r=z2w67&token=eyJ1c2VyX2lkIjo1ODkyMTU2NywicG9zdF9pZCI6MTM3Njg3NjYyLCJpYXQiOjE2OTY1ODkyMjIsImV4cCI6MTY5OTE4MTIyMiwiaXNzIjoicHViLTUwOTI2OCIsInN1YiI6InBvc3QtcmVhY3Rpb24ifQ.Wz2x1946wariU4j2QW3CMRRIjhD-cPdE8uzmC7cggvg)
|
||||
author:: davide.diruscio@gmail.com
|
||||
labels:: [[Newsletter]]
|
||||
date-saved:: [[06-10-2023]]
|
||||
date-published:: [[06-10-2023]]
|
||||
date-archived:: [[]]
|
||||
is-archived::
|
||||
source:: [[Omnivore]]
|
||||
@@ -0,0 +1,11 @@
|
||||
-
|
||||
- ## 🔖 Articles
|
||||
- [[2308.10620] Large Language Models for Software Engineering: A Systematic Literature Review](https://omnivore.app/me/2308-10620-large-language-models-for-software-engineering-a-syst-18a93e669a0)
|
||||
collapsed:: true
|
||||
site:: [arXiv.org](https://arxiv.org/abs/2308.10620)
|
||||
author:: [Submitted on 21 Aug 2023 (v1), last revised 12 Sep 2023 (this version, v4)]
|
||||
labels:: [[ResearchPaper]] [[LLMs]]
|
||||
date-saved:: [[06-10-2023]]
|
||||
date-archived:: [[]]
|
||||
is-archived::
|
||||
source:: [[Omnivore]]
|
||||
@@ -0,0 +1,11 @@
|
||||
-
|
||||
- ## 🔖 Articles
|
||||
- [[2310.03533] Large Language Models for Software Engineering: Survey and Open Problems](https://omnivore.app/me/https-arxiv-org-abs-2310-03533-18b042a9c58)
|
||||
collapsed:: true
|
||||
site:: [arXiv.org](https://arxiv.org/abs/2310.03533)
|
||||
author:: [Submitted on 5 Oct 2023]
|
||||
labels:: [[ResearchPaper]] [[LLMs]]
|
||||
date-saved:: [[06-10-2023]]
|
||||
date-archived:: [[]]
|
||||
is-archived::
|
||||
source:: [[Omnivore]]
|
||||
@@ -0,0 +1,6 @@
|
||||
full-title:: [Torna il BTP Valore, nuova emissione dal 26 febbraio al 1 marzo - Ministero dell'Economia e delle Finanze](https://omnivore.app/me/https-www-mef-gov-it-focus-torna-il-btp-valore-nuova-emissione-d-18d8fa7b947)
|
||||
site:: [MEF](https://www.mef.gov.it/focus/Torna-il-BTP-Valore-nuova-emissione-dal-26-febbraio-al-1-marzo/)
|
||||
date-saved:: [[09-02-2024]]
|
||||
date-published:: [[09-02-2024]]
|
||||
source:: [[Omnivore]]
|
||||
state:: [[saved]]
|
||||
@@ -0,0 +1,11 @@
|
||||
-
|
||||
-
|
||||
- ## 🔖 Articles
|
||||
- [2309.01715](https://omnivore.app/me/u-aad-8-e-0-de-4-f-4-b-11-ee-b-1-a-2-2-f-13-ff-58-e-925-2309-017-18a7b88ff0f)
|
||||
collapsed:: true
|
||||
site:: [storage.googleapis.com](https://storage.googleapis.com/omnivore/u%2Faad8e0de-4f4b-11ee-b1a2-2f13ff58e925%2F2309.01715.pdf)
|
||||
labels:: [[P1]] [[LLMs]]
|
||||
date-saved:: [[09-09-2023]]
|
||||
date-archived:: [[]]
|
||||
is-archived::
|
||||
source:: [[Omnivore]]
|
||||
@@ -0,0 +1,9 @@
|
||||
## 🔖 Articles
|
||||
- [Recommended articles](https://omnivore.app/me/recommended-articles-18b2012c493)
|
||||
collapsed:: true
|
||||
site:: [omnivore.app](https://omnivore.app/no_url?q=34087de4-1b4f-4bc7-9091-6851e4974dc3)
|
||||
labels:: [[Newsletter]]
|
||||
date-saved:: [[11-10-2023]]
|
||||
date-archived:: [[]]
|
||||
is-archived::
|
||||
source:: [[Omnivore]]
|
||||
@@ -0,0 +1,8 @@
|
||||
## 🔖 Articles
|
||||
- [Femminicidio: uccisa a 21 anni a Bolzano, arrestato l'ex fidanzato - la Repubblica](https://omnivore.app/me/femminicidio-uccisa-a-21-anni-a-bolzano-arrestato-l-ex-fidanzato-189efacd7a8)
|
||||
collapsed:: true
|
||||
site:: [la Repubblica](https://www.repubblica.it/cronaca/2023/08/13/news/femminicidio_uccisa_a_21_anni_a_bolzano_si_cerca_lex_fidanzato-410986500)
|
||||
author:: a cura della redazione Cronaca
|
||||
date-saved:: [[13-08-2023]]
|
||||
date-published:: [[13-08-2023]]
|
||||
source:: [[Omnivore]]
|
||||
@@ -0,0 +1 @@
|
||||
## 🔖 Articles
|
||||
@@ -0,0 +1,8 @@
|
||||
## 🔖 Articles
|
||||
- [Le bugie sull’alluvione e la melina sul salario. Il governo non ha soldi e si butta sul Cnel](https://omnivore.app/me/https-www-editorialedomani-it-politica-italia-le-bugie-sullalluv-189ed710d35)
|
||||
collapsed:: true
|
||||
site:: [Domani](https://www.editorialedomani.it/politica/italia/le-bugie-sullalluvione-e-la-melina-sul-salario-il-governo-non-ha-soldi-e-si-butta-sul-cnel-mza3dh2l)
|
||||
author:: Stefano Iannaccone
|
||||
date-saved:: [[13-08-2023]]
|
||||
date-published:: [[13-08-2023]]
|
||||
source:: [[Omnivore]]
|
||||
@@ -0,0 +1 @@
|
||||
## 🔖 Articles
|
||||
@@ -0,0 +1 @@
|
||||
## 🔖 Articles
|
||||
@@ -0,0 +1,13 @@
|
||||
## 🔖 Articles
|
||||
- [Nordio avvia azione disciplinare contro i pm che indagano Renzi. A giudicarli? La sezione del Csm presieduta dall'ex legale di Bianchi - Il Fatto Quotidiano](https://omnivore.app/me/https-www-ilfattoquotidiano-it-2023-08-12-nordio-avvia-azione-di-189ed77b6f1)
|
||||
collapsed:: true
|
||||
site:: [Il Fatto Quotidiano](https://www.ilfattoquotidiano.it/2023/08/12/nordio-avvia-azione-disciplinare-contro-i-pm-che-indagano-renzi-a-giudicarli-la-sezione-del-csm-presieduta-dallex-legale-di-bianchi/7259918?gaa_at=la&gaa_n=AfHvTEvv5mz4thfrKW9YgeWmhTr5gkb2ff7eHUeRLn04GpbIRqtvyESaBdS2elAbmKgWF-9cgO985CCJN_YbapH8xjTu&gaa_sig=v7zeILVjcKo4nVli6aF6TkfgRs5cv5484ltPHTBvVFs9ROjMAYhpv2349af6HNOKUZUyETqgvRTSWnho5bw4jg%3D%3D&gaa_ts=64d876c4)
|
||||
author:: F. Q.
|
||||
date-saved:: [[13-08-2023]]
|
||||
date-published:: [[12-08-2023]]
|
||||
date-archived:: [[14-08-2023]]
|
||||
is-archived:: 10
|
||||
source:: [[Omnivore]]
|
||||
- ### Highlights
|
||||
- > Il ministro della Giustizia **Carlo Nordio** [⤴️](https://omnivore.app/me/https-www-ilfattoquotidiano-it-2023-08-12-nordio-avvia-azione-di-189ed77b6f1#b5127a0d-7768-4bab-831a-242c0034ba74)
|
||||
- > **stato d’accusa** per “grave violazione di legge determinata da ignoranza grave e inescusabile” [⤴️](https://omnivore.app/me/https-www-ilfattoquotidiano-it-2023-08-12-nordio-avvia-azione-di-189ed77b6f1#f76c7c9e-7daa-4acc-b4c7-cbe9b41b553c)
|
||||
@@ -0,0 +1,11 @@
|
||||
-
|
||||
- ## 🔖 Articles
|
||||
- [[2308.10620] Large Language Models for Software Engineering: A Systematic Literature Review](https://omnivore.app/me/2308-10620-large-language-models-for-software-engineering-a-syst-18a93e669a0)
|
||||
collapsed:: true
|
||||
site:: [arXiv.org](https://arxiv.org/abs/2308.10620)
|
||||
author:: [Submitted on 21 Aug 2023 (v1), last revised 12 Sep 2023 (this version, v4)]
|
||||
labels:: [[ResearchPaper]]
|
||||
date-saved:: [[14-09-2023]]
|
||||
date-archived:: [[]]
|
||||
is-archived::
|
||||
source:: [[Omnivore]]
|
||||
@@ -0,0 +1,42 @@
|
||||
-
|
||||
- * [(20) The Future of Software Engineering with AI Agents | LinkedIn](https://omnivore.app/me/20-the-future-of-software-engineering-with-ai-agents-linked-in-18c6784cdf7)
|
||||
site:: [linkedin.com](https://www.linkedin.com/pulse/future-software-engineering-ai-agents-selim-salman/)
|
||||
author:: Selim Salman
|
||||
labels:: [[PROJECTS/SE-H2020-March-Call]]
|
||||
date-saved:: [[14-12-2023]]
|
||||
date-published:: [[12-09-2023]]
|
||||
date-archived:: 10-01-2024
|
||||
is-archived:: 10
|
||||
source:: [[Omnivore]]
|
||||
state:: [[archived]]
|
||||
- ### Highlights
|
||||
- id:: 389d6042-6a9f-4857-8430-96343428bccc
|
||||
> AI agents are being used to automate many of the tasks involved in software development, from writing code to testing and debugging. [⤴️](https://omnivore.app/me/20-the-future-of-software-engineering-with-ai-agents-linked-in-18c6784cdf7#389d6042-6a9f-4857-8430-96343428bccc)
|
||||
- id:: 6b37d654-f2c1-49aa-9c88-0dbfd03597cf
|
||||
> AI agents are likely to automate even more of the software development process. [⤴️](https://omnivore.app/me/20-the-future-of-software-engineering-with-ai-agents-linked-in-18c6784cdf7#6b37d654-f2c1-49aa-9c88-0dbfd03597cf)
|
||||
- * id:: d27b3bec-4ca3-4607-80e7-f941b3c79d2a
|
||||
> 90% of software development is automated, with only 10% of the work being done by human developers. [⤴️](https://omnivore.app/me/20-the-future-of-software-engineering-with-ai-agents-linked-in-18c6784cdf7#d27b3bec-4ca3-4607-80e7-f941b3c79d2a)
|
||||
- * id:: 814f3d5b-7f0f-472e-bdf3-268394d1e8e2
|
||||
> AI agents can be used to automate repetitive tasks, such as testing and debugging. [⤴️](https://omnivore.app/me/20-the-future-of-software-engineering-with-ai-agents-linked-in-18c6784cdf7#814f3d5b-7f0f-472e-bdf3-268394d1e8e2)
|
||||
- * id:: bbca642d-304a-4d44-9315-e1f86e780ea0
|
||||
> AI agents can be used to generate new ideas and solutions. [⤴️](https://omnivore.app/me/20-the-future-of-software-engineering-with-ai-agents-linked-in-18c6784cdf7#bbca642d-304a-4d44-9315-e1f86e780ea0)
|
||||
note:: How? It's still challenging to see how creative work can be done by AI agents.
|
||||
- * id:: 672476bf-708d-4c4d-bda6-2fca79b7b56b
|
||||
> One challenge is that AI agents can be expensive to develop and maintain. Another challenge is that AI agents can sometimes make mistakes, which can lead to bugs in software. [⤴️](https://omnivore.app/me/20-the-future-of-software-engineering-with-ai-agents-linked-in-18c6784cdf7#672476bf-708d-4c4d-bda6-2fca79b7b56b)
|
||||
note:: #STAR Challenges
|
||||
- * id:: a0748a5d-c752-4ed1-a673-1996aea4eaab
|
||||
> As AI technology continues to develop, we can expect to see even more innovative ways to use AI to automate the process of software development. [⤴️](https://omnivore.app/me/20-the-future-of-software-engineering-with-ai-agents-linked-in-18c6784cdf7#a0748a5d-c752-4ed1-a673-1996aea4eaab)
|
||||
- * id:: 97172a47-f099-418c-bc37-57d24df1fd91
|
||||
> software developers will be able to create software more quickly, easily, and efficiently. This will lead to a new era of software development, where human developers are freed up to focus on the most creative and challenging work. [⤴️](https://omnivore.app/me/20-the-future-of-software-engineering-with-ai-agents-linked-in-18c6784cdf7#97172a47-f099-418c-bc37-57d24df1fd91)
|
||||
- ## 🔖 Articles
|
||||
- [(20) The Future of Software Engineering with AI Agents | LinkedIn](https://omnivore.app/me/20-the-future-of-software-engineering-with-ai-agents-linked-in-18c6784cdf7)
|
||||
collapsed:: true
|
||||
site:: [linkedin.com](https://www.linkedin.com/pulse/future-software-engineering-ai-agents-selim-salman/)
|
||||
author:: Selim Salman
|
||||
labels:: [[PROJECTS/SE-H2020-March-Call]]
|
||||
date-saved:: [[14-12-2023]]
|
||||
date-published:: [[12-09-2023]]
|
||||
date-archived::
|
||||
is-archived::
|
||||
source:: [[Omnivore]]
|
||||
state:: [[reading]]
|
||||
@@ -0,0 +1,29 @@
|
||||
## 🔖 Articles
|
||||
- [CSDL | IEEE Computer Society](https://omnivore.app/me/https-www-computer-org-csdl-magazine-so-2023-04-10176161-1-oa-jx-189fe7b0f74)
|
||||
collapsed:: true
|
||||
site:: [computer.org](https://www.computer.org/csdl/magazine/so/2023/04/10176161/1OAJxGLzPsk)
|
||||
date-saved:: [[16-08-2023]]
|
||||
date-archived:: [[]]
|
||||
is-archived::
|
||||
source:: [[Omnivore]]
|
||||
- [CSDL | IEEE Computer Society](https://omnivore.app/me/https-www-computer-org-csdl-magazine-so-2023-04-10176156-1-oa-jz-189fe7ade2f)
|
||||
collapsed:: true
|
||||
site:: [computer.org](https://www.computer.org/csdl/magazine/so/2023/04/10176156/1OAJz2MyJqg)
|
||||
date-saved:: [[16-08-2023]]
|
||||
date-archived:: [[]]
|
||||
is-archived::
|
||||
source:: [[Omnivore]]
|
||||
- [CSDL | IEEE Computer Society](https://omnivore.app/me/https-www-computer-org-csdl-magazine-so-2023-04-10176168-1-oa-jx-189fe7a7cd2)
|
||||
collapsed:: true
|
||||
site:: [computer.org](https://www.computer.org/csdl/magazine/so/2023/04/10176168/1OAJxc9saEU)
|
||||
date-saved:: [[16-08-2023]]
|
||||
date-archived:: [[]]
|
||||
is-archived::
|
||||
source:: [[Omnivore]]
|
||||
- [CSDL | IEEE Computer Society](https://omnivore.app/me/https-www-computer-org-csdl-magazine-so-2023-04-10176194-1-oa-jt-189fe7a051e)
|
||||
collapsed:: true
|
||||
site:: [computer.org](https://www.computer.org/csdl/magazine/so/2023/04/10176194/1OAJtH6yQak)
|
||||
date-saved:: [[16-08-2023]]
|
||||
date-archived:: [[]]
|
||||
is-archived::
|
||||
source:: [[Omnivore]]
|
||||
@@ -0,0 +1 @@
|
||||
## 🔖 Articles
|
||||