1. Last 7 days
    1. Language teacher identity (LTI) is considered a critical element

      This is saying that being a teacher isn't just about teaching. Your identity as a teacher actually matters a lot in how you teach and grow.

    1. extend beyond the academic, spilling into the linguistic, identitarian, and social dimensions, frequently generating significant social suffering

      Their struggles aren't just in school, it affects their whole life.

    2. not experienced as a homecoming but rather as a migration to a country that is paradoxically both familiar and alien

      Returning doesnt feel like home, they feel out of place.

    3. “I left for the U.S. when I was practically 7 months old, so I didn’t know how to speak Spanish.”

      This shows how return students can feel disconnected from their home country because of language.

    1. It is a reality check to read the sentence, "The desire to return home was now a tumor lodged under Perfecto's heart..." (82) because while I often find myself missing home from the comfort of my college apartment, my experience is nowhere near comparable to Perfecto’s and is something I cannot fathom.

    2. The sentence, "... she wanted to tell him how good she felt but didn't know how to build the house of words she could invite him into" (70) is a beautiful way of describing being at a loss for words, even when you want to tell someone something important.

    3. The parallel between the women's swollen veins and the grape vines on 61 is stark and eerie and highlights the subtle and not so subtle ways Viramontes emphasizes their hard work and the side effects that come with it.

    4. At the bottom of 53 and the beginning of 52, Estrella has to imagine herself somewhere else to hold back the tears she felt welling up. I cannot imagine how difficult the task is for her, and I am wondering if she is doing it to put on a brave face for the people around her or to encourage herself.

    5. At the top of page 52, the only water Estrella has to drink is described as "tepid," which is a word I had to look up and means lukewarm, and along with the particles, definitely unappealing.

    6. On page 51, a pregnant mother is described picking cotton, "The sack slowly grew larger and heavier like the swelling child within her," which is a powerful simile. A pregnant mother should have the ability to rest, but that is an impossible luxury for her.

    7. Again at the bottom of page 50 Alejo thinks of all of the sacrifices and hardships his grandmother has endured just for him to have a chance at going to school. As a college student this is an important reminder to not take our education for granted.

    8. The sentence "...a white sun so mighty, it toasted the green grapes to black raisins" on page 50 stood out to me. From what I know, it takes up to 30 days to try grapes, so the author describing this as happening within moments emphasizes their brutal working conditions.

    9. The emphasis on how grueling this manual labor is already appears in the second sentence, "Even the birds wavered on the crest of the heat waves" (49). Birds are animals that have a high tolerance for heat, so highlighting their struggles with the temperature depicts how difficult the labor is, especially under these circumstances.

    1. Battery storage can also help businesses store grid electricity when it is cheap for later use. It can also provide back-up during short power outages if correctly configured and when the state of charge is sufficient.

      pro-battery

    2. The Australian Government’s Solar Consumer Guide provides free and expert guidance on rooftop solar and batteries for your business

      good reference to point out for anyone who wants to look at professional uses for solar power

    3. Where carbon reduction is the main focus, many businesses opt to purchase a proportion of GreenPower through an energy retailer.

      -talking about how companies might be more interested in reducing carbon, and companies usualy get them done through a big company instead of doing it themselves

  2. stylo.ecrituresnumeriques.ca stylo.ecrituresnumeriques.ca
    1. la polarisation des débats. Cette dynamique peut conduite à une simplification excessive des situations complexes, dans lesquelles les individus sont rapidement classées comme coupables ou innocents, sans analyse approfondie.

      Je suis d'accord avec la notion de "polarisation" qui est essentielle ici. Le Web ne met pas de nuance.

    1. Dans

      juste au dessus l'espace crée entre les paragraphes est fait par une balise html, < br > il faut la supprimer. (le commentaire ne concerne pas "Dans" mais je ne pouvais pas sélectionner un espace vide)

    1. If fenebrutinib is not yet available, should ocrelizumab/rituximab be reconsidered as a bridge? (Previously declined, Sep 2025)

      why are we asking this question? we dont think this is a good idea right? and the doctor didnt think so before either.

    1. Earthquake risk assessment of building structures

      这篇论文系统综述了基于概率与可靠性理论的建筑结构地震风险评估方法,重点讨论了如何通过地震危险性分析、结构响应建模以及易损性(fragility)曲线来量化建筑在不同地震作用下达到各类损伤状态的概率。作者指出,传统确定性设计方法难以准确反映实际震害表现,必须引入不确定性(包括随机性与认知不确定性)进行概率分析;并通过钢结构框架实例表明,结构性能评估应以变形或层间位移角等损伤指标为核心。论文进一步强调,将易损性函数与地震危险性耦合可得到结构失效概率,从而为性能化设计与震后评估提供更合理的依据,但同时也指出当前模型与数据的不确定性仍是限制精确预测的关键问题。

    1. A GIS-based earthquake damage assessment and settlement methodology

      这篇论文的核心内容可以概括为:


      一、研究目的

      提出一种基于GIS的地震损失评估方法,用于在地震发生前或发生后,快速评估城市中:

      • 建筑损坏情况
      • 人员伤亡
      • 道路阻塞情况 并辅助灾害应急与城市规划决策。

      二、主要方法

      论文构建了一个综合评估流程,包括:

      1. 地震强度计算 利用震级、断层距离和土壤条件,计算每个建筑位置的地震烈度(MMI)。

      2. 建筑损伤评估 通过fragility曲线(脆弱性曲线),将地震烈度转换为建筑损坏比例。

      3. 人员伤亡估计 根据建筑损伤程度、人口分布和建筑类型,计算死亡和受伤人数。

      4. 道路阻塞分析 根据倒塌建筑产生的废墟体积,评估道路被阻塞的程度。

      5. 避难可达性分析 判断哪些建筑在震后无法通过道路到达临时避难点。


      三、案例研究

      以Tehran某区域为例进行模拟:

      • 预测结果显示:

      • 建筑损坏最高可达约64%

      • 死亡人数约占33%
      • 严重受伤约27%
      • 约22%的道路完全阻塞

      四、验证与结论

      • 使用2003 Bam earthquake进行验证,模型结果略偏保守(偏高估损失)
      • 结论:

      • GIS方法能够有效整合多源数据进行地震损失评估

      • 该模型可用于:

        • 灾前风险评估
        • 城市规划(加固建筑、拓宽道路)
        • 灾后应急救援规划

      一句话总结

      这篇论文提出了一套基于GIS的地震损失评估模型,通过“地震强度 → 建筑损伤 → 人员伤亡 → 道路阻塞”的链式分析,实现城市级灾害风险预测与决策支持。

    1. Building damage assessment after the 2009 Abruzzi earthquake

      这篇文章主要介绍了2009年阿布鲁佐地震后意大利拉奎拉地区建筑物的损坏评估。文章描述了在地震发生后,意大利民防部门协调进行的建筑物检查过程,并使用了AeDES表格进行建筑损坏评估。通过检查了约74,000座建筑,文章分析了建筑类型与地震损坏之间的关系,并探讨了建筑的脆弱性因素,如砌体质量、建筑年代、楼层数以及已有的损伤情况。文章还讨论了检查过程中建筑物使用情况的分类(可用、受限使用、不可用),并指出了不同类型建筑的损坏模式和使用后的风险。

      总结来说,这篇文章通过对拉奎拉地震后的建筑损坏数据进行深入分析,提供了关于建筑物脆弱性、损坏分布以及灾后恢复过程的重要见解,并为未来的建筑评估和防震设计提供了宝贵的数据支持。

    1. To call it theft is accurate in my opinion, but then I'm a bigger believer in copyrigh

      the equation of copyright infringement with theft was wrong when it was the media companies accusing people of it, as it is now when people accuse ai companies of it, imo. Doesn't mean the training of models on our collective creative output isn't wrong, but copyright and theft is not the angle imo.

    2. There's a fundamental problem with these tools beyond the capacity of any deployment strategy to solve: the tool requires expertise to validate, but its use diminishes expertise and stunts its growth

      the paradox here is that using algogens erodes the skills to be able to judge its output. I think we already see that in the code leak from Anthropic.

    3. the way mistakes can compound make this a dangerous proposition. This all worked with my small project, but a bigger one, with more dependencies or more complex project structures, would likely flummox the models. And reviewing changes across a more complex codebase becomes at once more difficult and more critical as the project size increases.

      compounding mistakes. esp in bigger / more complex projects. a neg ratchet This to me points back to vibe assistance in components, less in the overall project. creating libraries of functions above always from scratch. Keeping tech choices clear.

    4. Programming agents might work, but there are a lot of ways they can go wrong. The amount of guardrails necessary to keep the model in check doesn't scale. The more steps of a process rely on generative output, the higher the potential for error and catastrophic failure. Any process that involves these models must strive to maximize determinism and minimize model variance.

      stay close to deterministic. n:: Guardrails grow faster than keeping stuff in check, doesn't scale

    5. I am privileged in that I can make these choices. Not everyone is so privileged. I am hesitant to condemn those who choose to accept the help that shows up, and in so doing fulfilling their obligations of care to those in their lives. Insofar as these models empower people to build something good, and do so without overmuch suffering on their part, we must reckon with the value proposition there. It is a benefit, but it does not eliminate the attendant harms.

      exactly. like I was told by someone in Central Asia, I'll get to your western environmental concerns after I can reliably feed my family. Not a fully correct distinction, but fully understandable when seen from a perspective of agency povert. n:: externalities concerns v-a-v agency poverty

    6. This does not negate the dangerous externalities of the technology at large, but I can only adopt so much of that responsibility as an individual.

      Another strong observation. Knowing the wider externalities and individual agency do not always overlap. The individual aspects cannot be asked to bear the systemic ones. You can work to change the system and still use the individual benefits while doing so.

    7. The help that showed up I turned to generative models not only as an experiment, but out of desperation. I had a need for code that did not exist. Nobody was going to help me build it, nor should I expect help for a project such as this. In the past, I would have cobbled together something quick-and-dirty, probably at the expense of my mental and physical health to get it done. This time, I had another option. In this limited scope, the model was beneficial to all involved: myself, TTI's community, and my family

      A reiteration of the 'help that showed up' and the effects it had on author and his environment.

    8. More plainly: I have no reason to expect this technology can succeed at the same level in law, medicine, or any other highly human, highly subjective occupation.

      I think author is wrong here. Depends on application scope. In law translation e.g. in the EU, where we have verdicts in 27 languages pertaining to the same market is key. In medicine it's not algogens but other AI that is being deployed, and scaled (e.g. wrt analysing imaging like radiology / mri etc.)

    9. The "works" in "it works" is scoped strictly to coding tasks. I have no evidence, and seemingly no one else does, that the same kind of success is available outside the world of highly structured language with deterministic outputs.

      important caveat and back to [[The arc of vibe coding bends towards determinism 20260214145739]]

    10. But CertGen, my certificate application, exists now. It didn't and couldn't without the help of a tool like Claude Code.

      this is the only test I think most people apply. Esp when it comes to individuals, outside deployment in teams or in orgs.

    11. I'm not entirely onboard with Mike Masnick's optimistic view of this technology's democratizing power. I don't think it's as easy to separate the tech from its provenance or corporate control

      true in essence, but in practice it is what I see people experiencing, despite forking 20USD/month over to BigTech

    12. I simply could not have built this project as well or as quickly without help. And as other developers have noted, this is the help that's showing up.

      n:: Claudecode as 'the help that is showing up' consistently. This is what I observe too where it is used by individuals overcoming barriers to entry to make their personal tools. I think this may be relevant to understand those that turn to chatbots for advice too.

    13. One time, during a security fix, the model's code introduced a non-obvious DoS vector. Well, obvious from the perspective of how the code would be deployed, but not from the code itself. That's exactly why reading each change was so important. Once the issue was pointed out, the model produced code that both addressed the security issue and avoided the DoS.

      this is a core issue: the algogen has no concept of 'deployment' and only has the code itself. Even for simple things, not just security like here, it will not be able to look at the intention of a project outside the project. This a better anchor for human in the loop, the connection to reality / intention?

    14. I do know the code very well by way of careful reading of the code, the relevant libraries' documentation, and the proposed changes during the code's creation. But that safety comes down to human discipline. It is entirely possible (probable?) to take the easy road and trust the model to do the right thing.

      n:: having a human in the loop for vibe coding entirely comes down to discipline. Which is a recipe for it not happening. (and for me points to having a fixed starter set of instructions etc, as opposed to coming up with them each time).

    15. In this case, I was the audience rather than the author. I had to back my way into understanding the code, carefully reading and understanding the structure after it had been built. This is much more common for developers who work on large teams or with codebases they didn't build themselves. I have not had as much experience with that kind of development, so this all felt a little awkward.

      vibe coding makes you the audience watching the process, and no longer the author. but: says this is a role various people already have in coding teams. Which may be relevant when looking at adoption patterns, imo.

    16. Although I read each proposed change, knowing the codebase deeply was much more challenging. When I write a new application myself, I'm building an elaborate house of cards in my head, a gossamer structure of interlinked ideas and goals. It's a story I'm telling myself in code—and ultimately, a story I share with users.

      reading everything during production is not the same as producing it. A mental model of the entire construct is not created. Interesting quote: you no longer have a story in your head about what it is you're doing. No helicopter view. The making is scaffolding for your understanding, and that is being cut out.

    17. "Human in the loop" is necessary, but the current process itself makes the loop stultifying, and encourages the human to take themselves out of the loop. That process is straight up dangerous. The temptation to let it rip is always there, and I didn't even have a boss pressuring me to ship code.

      The option 'yes to all in this session' provided at every turn is seen by author as darkpattern.

    18. It was so tempting to press 2: "Yes, and accept all changes for this session." Why wouldn't you? If you're accepting them all manually, what's the harm? What's the harm? harm harm harm harm Yeah, that's how you get got in this process. Once you stop scrutinizing the model's output, the probability something goes off the rails approaches 1.

      putting y on automatic is certain way to end up with stuff you do not have an overview of or no longer comprehend.

    19. I hated writing software this way. Forget the output for a moment; the process was excruciating. Most of my time was spent reading proposed code changes and pressing the 1 key to accept the changes, which I almost always did. I was basically Homer's drinking bird.

      author hated the feeling of being reduced to typing 'y' to questions from Claudecode. Recognisable, like babysitting. I watch output alongside Claudecode in VScode, which helps a bit.

    20. we need to be grown-ups and entertain some seemingly contradicting ideas at the same time, okay?

      n:: maak deze naast [[Holding questions 20091015123253]]

    21. Methodology To maximize determinism, each step of the build used test-driven development (TDD). Using the Markdown planning file as a starting point, the model generated tests for functions that would define the features, then implemented each in turn. After each coding round, cargo check and cargo test were run to confirm compilation and test passing. I reviewed every line of code the model generated. For initial drafts, very little had to change. Now to be fair, this is not a particularly complex app. It's basic CRUD app with some specialized requirements. Still, getting it all right, including auth and data handling, really mattered. After the initial drafting phase, I went through the entire app and made a list of tasks for improvement/change in the codebase. This TODO.md became the new starting point for model context in plan creation. Unexpectedly, as items were addressed in the document, the model updated the file with checkmarks and details of implementations. This was not an instruction I gave the model, but it was behavior I liked, since it created a trail of accountability. After all the features I wanted were functional, context was cleared entirely and new instructions were provided to the model. Instead of acting as a software developer, I instructed the model to perform as a security auditor and secure code expert, finding vulnerabilities in the code and recommending remediations. The findings would be written to a FINDINGS.md file, keeping with our established "Plan, Document, Execute, Log" pattern established in earlier rounds.

      Stated aim was to maximise determinism. That sounds like a good point for any vibing effort. Also ties in with my general sentiment [[The arc of vibe coding bends towards determinism 20260214145739]]

      test driven development. Markdown plan first, then function tests for feature definitions, only then making the functions. Reviewed all code himself. Also makes me wonder about building my own libraries from vibed results. (e.g. the forms I use, the css, the diff functions, although most of the interactive stuff I've written myself already, and use them as components)

    22. In fact, almost all the hands-on-keyboard time for myself in this project was in Markdown syntax. I love me some Markdown, but it didn't feel great writing for a model as an audience instead of human beings.

      interesting observation, when the [[Assumed audience definieren 20211113212257]] is a machine the joy of writing diminishes. Not sure if I think of prompting / editing plans etc as writing, but I recognise the sentiment.

    23. If it works, I'll have my certificate solution, I thought. If it doesn't, at least I'll know more about the technology and its implications. Well, spoiler alert: it works. It's even, near as I can tell, reasonably secure. But good lord, building this way was miserable, even if it was faster than coding it all myself.

      Classic approach: if it works, I have a result, if it doesn't I have hands-on experience with algogens as tech, and can use that elsewhere

    24. So on the one hand, I have to understand genAI coding tools for work. On the other, here's this missing feature I need implemented to complete the TTI migration. I decided to test development using Claude Code for this project.

      the experiment was to create a certificate issuing component for his migrated learning platform to Discourse.

    25. Do I think LinkedIn is the digital River Styx, where damned souls clamber over each other and claw at the boat passing overhead in the dim hope of salvation from those who have escaped the shambling horde? I do. But if we're all in hell together, we might as well try to lift each other up.

      :D

    26. Let's get this out of the way: my feelings about using generative models at all are...fraught. And if you are ready to call me a monster or a hypocrite right now, I understand. I'm navigating some tensions about this and I fully own that I may have made the wrong choices here.

      not a pro or con blogpost but meant as exploration of felt experience

    1. Article de vulgarisation scientifique cherchant à savoir si les jeux vidéos favorisent-ils des comportements violents ?

      Article de vulgarisation scientifique cherchant à savoir si les jeux vidéo favorisent des comportements violents.

    1. L’enjeu n’est plus seulement de comprendre comment nous nous montrons en ligne, mais de décider collectivement du rapport que nous voulons entretenir avec des images qui peuvent désormais, exister sans nous.

      Fin d'article claire et réussie, elle ne se contente pas de résumer mais ouvre sur une question plus large sur l'avenir des images numériques et sur notre rapport collectif à leur circulation.

    2. Ils influencent la manière dont on se montre en ligne. Autrement dit, ils ne se contentent pas d’héberger nos images, mais orientent nos pratiques en mettant en avant certains contenus plutôt que d’autres.

      Cela rappelle que les réseaux sociaux ne sont pas neutres et qu'ils orientent les manières de se montrer.

    3. Plus une image correspond à ces standards, plus elle a de chances d’être mise en avant par les algorithmes.

      Les filtres créent-ils vraiment de nouvelles normes esthétiques, ou renforcent-ils surtout des normes déjà présentes dans la société et dans les médias ?

    4. Beaucoup expriment une anxiété sociale à l’idée de se montrer sans retouche, comme si leur visage « réel » risquait d’être perçu comme insuffisant. Ce contrôle de l’image déborde alors dans le quotidien : certaines personnes adaptent leur maquillage, cherchant à redessiner leurs traits comme en ligne

      C'est pertinent de relier les filtres à des effets concrets sur la vie quotidienne, comme l'anxiété sociale et l'adaptation du maquillage.

    5. Les filtres inspirent des demandes de chirurgie esthétique. Les individus souhaitent ressembler à leur avatar numérique. On observe alors un véritable effet de boucle : en filtrant son visage pour se conformer aux normes esthétiques, on s’habitue progressivement à cette version modifiée. On finit par vouloir la reproduire dans la vie réelle, ce qui contribue à renforcer collectivement les standards qui l’ont influencé au départ. Ce processus contribue à une perte de singularité.

      Je trouve que ce passage pourrait être un peu plus nuancer. Il insiste surtout sur les effets négatifs des filtres sur l'apparence réelle mais toutes les personnes qui utilisent des filtres ne cherchent pas forcément à transformer leur visage de la réalité.

    6. contribue

      Le verbe "contribuer" est répété à deux reprises dans deux phrases très proches, ce qui alourdit le passage. Tu pourrais remplacer par un autre verbe similaire ou reformuler ce passage.

    7. Visage avec et sans filtre

      L'exemple visuel fonctionne bien et montre immédiatement l'écart entre le visage retouché et le visage non retouché. Cela rend l'argument plus concret.

    8. certaines apparences sont valorisées, d’autres marginalisées ou invisibilisées.

      Je suis d'accord avec ce troisième paragraphe. Cela met bien en avant la dimension normative des plateformes.

    9. ils constituent des accessoires qui permettent d’optimiser notre physique.

      Cette phrase reprend un vocabulaire qui suppose déjà qu'il existe une version "améliorée" du visage. Le terme n'est pas vraiment neutre, Il vaudrait mieux le discuter ou le mettre à distance. De plus, j'ouvre un débat : qui décide de ce qu'est une image "optimisée" de soi ? La personne elle-même, le regard des autres, ou les normes imposées par les plateformes ?

    10. Retoucher son visage n’a jamais été aussi simple : un glissement de doigt et lisser, s’affiner devient un véritable jeu d’enfant ! Mais derrière cette habitude se cache une transformation profonde de notre identité.

      Phrase d'ouverture claire : capte l'attention et montre bien que les filtres ne sont pas seulement un outil ludique mais un enjeu lié à l'identité.

    11. Les réseaux sociaux ne sont plus seulement des espaces d’expression : ils sont devenus des laboratoires où l’on fabrique son apparence.

      Je trouve que cette phrase généralise un peu car tous les usages des réseaux sociaux ne tournent pas autour de la fabrication de l'apparence. Il faudrait peut-être nuancer.

    12. Filtres, retouches et perception de soi : une identité numérique déformée ? L’identité numérique filtrée : une extension ou une déformation de soi ?

      Je trouve que le titre principal et le sous-titre disent presque la même chose. Peut-être garder un plus général et faire de l'autre une reformulation plus précise pour éviter la répétition.

  3. inst-fs-iad-prod.inscloudgate.net inst-fs-iad-prod.inscloudgate.net
    1. Such environments may give players the disorientingand somewhat anaesthetizing sense that this could be anywhere or nowhereat all, conveniently overlooking ecological concerns with the finite charac-ter of the natural world and entropic limitations on energy and throughput,or carrying capacity (chapter 4). In an era of widespread anxiety over climatechange, increasingly scarce fuel reserves, and population control, it shouldcome as no surprise that an especially popular recourse is the abstract, ever-receding pastoral ideal that Raymond Williams once derisively called “ababble of green fields” (in a nod to Shakespeare),10 which lurks in all themedieval and pre- or alter-industrial lands of games like Blizzard’s World ofWarcraft or Nintendo’s Legend of Zelda series, and rather explicitly in themultitudes of crop-management games like Harvest Moon (1996) and Farm-Ville. Ecological specificity and accuracy are neither necessary nor sufficientcriteria for successful commercial games, but when we measure games asinstruments of public knowledge, it suddenly becomes worthwhile to makegames that are more meaningfully local, which take seriously the goal of envi-ronmental realism—not solely in terms of visual rendering, but also in sounddesign, weather, species density and distribution, and the arrangement oforganic and inorganic actors in complex interrelation

      Crazy... like free to play white. You can also check soundscape studies from games like Fortnite in Playthrough Poetics, and it's crazy how little nature embeds the area. Compare that to Red Dead 2, Rain World, Flow, Death Stranding 2, Proteus, Caves of Qud, Everything, or Kenshi

    2. (“Why are you playing games in here when you could be playing outside?”)seems to follow the pattern of attacks on the ecocritical project (“Why writeabout the environment when you could just go outside?”). The same flawscharacterize both avenues of questioning: not only the positing of a falselylimiting either/or but also the not altogether ridiculous supposition that theonly way to experience nature is to be exposed to the elements.

      It isn't, but you are spousing a red herring here by pushing normative instrumentalism... yeah games can act as historical reminders, but to defend nature, one must be able to put their physcial body in the line. I am not denying digital activism, I am affirming that its impacts are limited, more constrained, compared to someone who engages in the Internet and in the physical world.

    1. learning within shifting interactions and patterns through time.
      • shifting through time

      plex - nothing u can do but learn how to be u(s) through time

    1. Executieve functies zijn trainbaar en kunnen op elke leeftijd worden verbeterd - waarschijnlijk door veel verschillende benaderingen. Het is niet altijd gunstig om executieve functies bewust uit te oefenen. Soms denk je na over wat je doet en probeer je top-down controle uit te oefenen, maar dat blokkeert juist optimale prestaties.

      vgl [[Ignite by Neeltje van Horen]]

    2. De executieve functies gaan over het kiezen van de activiteiten en het uitvoeren van deze taken. Het gaat er hierbij om op welke taak je je aandacht richt en hoe je deze (cognitieve) taak vervolgens uitvoert.

      werkdef van exec fie

    3. Jelle Jolles onderscheidt in Het tienerbrein. Over de adolescent tussen biologie en omgeving de volgende executieve functies: Filteren Organiseren van aandacht Impulsremming Nieuwsgierigheid en initiatief nemen Werkgeheugen Doelgerichtheid Gedrags-, motorische en cognitieve flexibiliteit Planmatig handelen Kiezen en beslissen Zelfinzicht Zelfregulatie Metacognitie Monitoring Empathie en perspectiefname Motivatie

      1 filteren, 2 aandacht, 4 nieuwsgierigheid, 6 doelgerichtheid, 8/9 planmatig handelen, kiezen/beslissen, 12 metacognitie, 15 motivatie

    4. Margriet Sitskoorn onderscheidt in De beste versie van jezelf twaalf executieve functies:  Aandacht richten, vasthouden, verdelen Emoties reguleren (incl. omgaan met stress) Flexibel kunnen zijn als dingen veranderen Ongewenst gedrag kunnen onderdrukken Taken en zaken starten Dingen organiseren Dingen kunnen plannen Jezelf kunnen monitoren Je werkgeheugen gebruiken Een reëel zelfbeeld vormen Het vermogen tot theory of mind Prosociaal gedrag (het belang van anderen voor ogen houden)

      1, aandacht. 2,3 stress/flex,4 dingen niet doen, 5 taken starten

    5. Zo onderscheiden Peg Dawson en Richard Guare in hun boek Slim maar… help kinderen hun talenten benutten door hun executieve functies te versterken elf soorten executieve functies: Respons-inhibitie: nadenken voordat je iets doet. Werkgeheugen. Emotieregulatie. Volgehouden aandacht. Taakinitiatie. Planning/prioritering. Organisatie. Timemanagement: tijd inschatten, verdelen en deadlines halen. Doelgericht gedrag. Flexibiliteit: flexibel omgaan met veranderingen en tegenslag. Metacognitie: een stapje terug doen om jezelf en de situatie te overzien en te evalueren

      4,5,6. 7,9 aandacht, taakinitiatie, planning/prioritering (ook herziening daarvan obv interne prios), tijdsbesteding, doelgerichtheid

    6. Er zijn vijf soorten situaties waarin executieve functies vereist zijn om tot een optimale prestatie te komen (Norman & Shallice, 1986): Situaties waarbij planning en besluitvorming vereist is. Situaties waarbij bijsturing en foutencorrectie van gedrag nodig is. Nieuwe vormen van gedrag of nieuwe opeenvolgingen van handelingen. Gevaarlijke of technisch moeilijke situaties. Situaties waarbij ingeroest gedrag of gewoontes moeten worden doorbroken.

      1,5 zijn bij burn-out aan de orde lijkt me

  4. bafybeihrnk4hmiwwvhvcdpvfqmickuat4keemz54mlyxqlldgkbvvecg4y.ipfs.localhost:8080 bafybeihrnk4hmiwwvhvcdpvfqmickuat4keemz54mlyxqlldgkbvvecg4y.ipfs.localhost:8080
    1. /💻/asus/🧊/me/📓/2026/03/18/faceted.search.hypothesis/=/symmathesy

      https://bafybeiayvn3r2ujxb2fwibfgx244zhflngch5x5ukzheifegpc7f2xamtm.ipfs.inbrowser.link

      [/💻/asus/🧊/me/📓/2026/03/18/faceted.search.hypothesis/=/symmathesy](/💻/asus/🧊/me/📓/2026/03/18/faceted.search.hypothesis/=/symmathesy](http://webui.ipfs.io.ipns.localhost:8080/#/files/%F0%9F%92%BB/asus/%F0%9F%A7%8A/me/%F0%9F%93%93/2026/03/18/faceted.search.hypothesis/=/symmathesy)

    1. /💻/asus/🧊/me/📓/2026/03/18/faceted.search.hypothesis/=/symmathesy

      experiment

      https://bafybeianzw4pcwdysobdjbctfxpgjkofzkf6qs4ez5imuqbhtgaujtshrq.ipfs.dweb.link/?filename=asus-me-2026-03-18-faceted-search-hypothesis-symmathesy-Files-IPFS-04-05-2026_11_48_AM.png

    1. Eerste versie deze zomer Voor nu is Euro-Office vooral een belofte met een technische preview. De eerste stabiele release wordt komende zomer verwacht.

      Euro-office zou in de zomer met 1e release komen

    2. Euro-Office begeeft zich bovendien in een veld waar al meer initiatieven actief zijn. Zo bestaat bijvoorbeeld al langer openDesk van het Duitse ZenDiS, waarin Nextcloud en Collabora al een rol spelen. Ook partijen als Proton of Infomaniak (Zwitserland) bieden soortgelijke online oplossingen aan. Nextcloud en Ionos willen zich onderscheiden met nauwere integratie tussen de verschillende onderdelen en met extra functionaliteit, waaronder AI-functies. Of dat voldoende is, zal afhangen van uitvoering. Europa kent inmiddels meerdere projecten die digitale soevereiniteit beloven, maar uiteindelijk moeten die ook schaalbaar, beheersbaar en gebruiksvriendelijk blijken. Juist daar zit voor veel organisaties het verschil tussen een interessant proefproject en een serieuze vervanger van Microsoft 365.

      opendesk v Zendis (ook met Nextcloud en Collabora) Proton met Infomaniak ook bezig (maar zij werken wel met VS cloud operators)

    3. Eerder schreven we al over office.eu, een apart initiatief dat eveneens een volledig Europese office-suite wil aanbieden op basis van Nextcloud-technologie. Dat platform mikt op een geïntegreerde omgeving voor documenten, communicatie en opslag. Ook daar worden Europese hosting, soevereiniteit en het vermijden van afhankelijkheid van Amerikaanse hyperscalers genoemd. Ondanks de mogelijke naamsverwarring zijn dit twee verschillende initiatieven. Een van de verschil;en is dat office.eu zich profileert als kant-en-klaar SaaS-platform voor digitale samenwerking, terwijl Euro-Office meer wordt gepresenteerd als opensource bouwsteen en ecosysteemproject. De gemene deler is wel duidelijk: Nextcloud groeit uit tot een belangrijk fundament onder Europese alternatieven voor Microsoft 365 en Google Workspace.

      office.eu wil een complete SaaS oplossing zijn v docs bewerken, communicatie en file opslag. Euro-office is alleen de collaboratieve docs, en een inwisselbaar blokje. Nextcloud zit in beiden als fundamentele bouwsteen.

    1. Everything after the code is "done"I put "done" in quotes because in most orgs, code being written is maybe 20% of the journey. The other 80% is your code sitting in various queues, slowly ageing, like a forgotten sandwich in the office fridge.

      author applies a Pareto division to software dev. Only the first 20% being writing the code. The rest, PR reviews, QA, waiting for next steps, getting it to market etc. is the other 80%

    2. When you optimise a step that is not the bottleneck, you don't get a faster system. You get a more broken one.

      The part of ToC often forgotten: if you optimise a step that isn't a bottleneck, then the entire system will get worse. You'll get pile-ups before the bottleneck, or idle wait times behind it.

    3. In 1984, Eli Goldratt wrote The Goal, a novel about manufacturing that has no business being as relevant to software as it is. It's also the most useful business book you'll ever read that's technically fiction, which is almost the exact opposite of most KPI frameworks.The core idea is the Theory of Constraints, and it goes like this:Every system has exactly one constraint. One bottleneck. The throughput of your entire system is determined by the throughput of that bottleneck. Nothing else matters until you fix the bottleneck.

      [[The Goal by Eliyahu Goldratt]] 1984, on manufacturing and bottle necks in those processes. Software dev is not different by much. [[Critical Chain by Eliyahu Goldratt]] 1997 extended for project management. Vgl. Wolfgang Mewes Engpasskonzentrierte Strategie (EKS, 1971) https://de.wikipedia.org/wiki/Engpasskonzentrierte_Strategie

    4. https://web.archive.org/web/20260405092911/https://andrewmurphy.io/blog/if-you-thought-the-speed-of-writing-code-was-your-problem-you-have-bigger-problems blogpost by Andrew Murphy on how code generation is not the bottle neck in software production, and thus through Theory of Constraints, adding AI vibing will make things worse because it puts pressure on all bottlenecks after the point of code making (while their speed was not the issue to begin with).

  5. stylo.ecrituresnumeriques.ca stylo.ecrituresnumeriques.ca
    1. les effets immédiats sont difficilement perceptibles – ce qui s’avère être un défi pédagogique tout comme une impulsion vers la théorisation de la matière

      N'est-ce pas reprendre ici plutôt le rapport au vrai que le rapport à la justice ? Il me semble que l'auteur ou autrice ici ne développe pas vraiment tout ce qu'implique cette très forte affirmation de BR. Non qu'il faille renoncer à toute théorisation ou à toute réflexion sur le vrai, mais cette théorisation doit être sortie de son effet d'absolu et replacée dans les conditions pragmatiques (donc politiques et sociales) de sa performance, de sa production et de sa transmission. D'où l'importance inattendue allouée à la justice pour l'analyse de cette scène. Et le fait même de la penser comme une "scène".

    2. réactualisation,

      "réactualisation" désigne la simple reprise du passé, BR parle plutôt de possibles "actualisations", ce qui suppose une reprise avec innovation, un retour du passé mais détourné et reconfiguré, un passé dont on se sert pour le caractère subversif qu'il peut avoir dans un présent qui n'est plus le sien...

    3. académique

      universitaire (à la différence de l'anglais "académique" en français désigne un travail qui suit des normes sans vraie inspiration ou originalité)

    4. la récolte issue de la semence noire laissée par les bœufs qui, avec la charrue blanche, labourent le pré blanc, e

      d'autant plus si l'énigme est résolue, comme l'entend généralement la tradition, par l'écriture du savant scribe laissant sur la page blanche les semences noires des phrases. Mais alors, en dehors du sympathique effet de transgression, quelle forme concrète, pour l'écriture universitaire, cela pourrait prendre que de franchir ces lignes d'écriture?

    5. l’enseignement doit convaincre de sa pertinence

      le problème, me semble-t-il, est de savoir par rapport à quoi c'est jugé pertinent, voire quelle est la pertinence du critère de pertinence...