1,865 Matching Annotations
  1. Feb 2021
  2. Jan 2021
    1. that's by design:

      Can't upgrade from EOL version

      Supposed to upgrade from it while it is still supported...

      I can see calling this upgrade path "unsupported", but isn't "by design" going a bit too far?

      It seems like it's not so much an intentional design choice to disallow it as it is an inadvertent side effect of ending support for it, and of only developing support for specific version upgrade paths.

    1. Postsecondary chemistry curricula and universal design for learning: planning for variations in learners’ abilities, needs, and interests

      Evaluates CLUE, Mastering-SP, and POGIL curricula on universal design for learning checkpoints for making materials accessible for students with disabilities Guidelines for universal design for learning valuable for course design

    1. https://hyp.is/go?url=https%3A%2F%2Fwww.archdaily.com%2F627654%2Fthe-computer-vs-the-hand-in-architectural-drawing-archdaily-readers-respond&group=__world__

      I came across this article about the tension between computer drawing and hand drawing in architecture when I replied to an annotation by another user @onion - very interesting read and I would be curious to see this issue revisited in another ten years...how may opinions have changed?

    1. By design, snap apps have no access to /etc. They live in their own little world, but instead of a normal chroot, they are splatted all over the standard Linux filesystem layout. With other bits mounted hither and thither. Its a mess, and subject to change with each release.
    2. The past few years seems to have be a race between Microsoft and various players in the Linux world to see who can produce the worst abomination of a UI. It's as if there's been a ritualistic burning of the UI design rule book that led to many years of largely stable and consistent user experience across all platforms
    1. The span of graphic design is not a history of concepts but of forms.
    2. he meant that the designer’s purview is to shape, not to write. But that shaping itself is a profoundly affecting form.
    3. Paul Rand wrote “There is no such thing as bad content, only bad form,”
    4. The apotheosis of this notion, repeated ad nauseum (still!), is Beatrice Warde’s famous Crystal Goblet metaphor, which asserts that design (the glass) should be a transparent vessel for content (the wine).
    5. Designers also trade in storytelling. The elements we must master are not the content narratives but the devices of the telling: typography, line, form, color, contrast, scale, weight. We speak through our assignment, literally between the lines.

      We tell stories not through words, but through our portrayal of them: visuals.

    1. Open About Popover

      I have to say, I like how it looks in their Apple and Desktop preview better than the Android/Material preview. I wish they had the arrow in Android Material too.

      But on https://sveltematerialui.com/demo/menu-surface it doesn't bother me quite as much...

    1. In my opinion, it can sometimes look odd. Very interestingly, this is by design and is part of the Material design specification. This article isn’t to argue whether it should be this way or not, though; it’s just to change yours such that your MenuItem(s) show below the menu selection, like so:
    1. Material is the metaphor The metaphor of material defines the relationship between space and motion. The idea is that the technology is inspired by paper and ink and is utilized to facilitate creativity and innovation. Surfaces and edges provide familiar visual cues that allow users to quickly understand the technology beyond the physical world.
    1. By default, menus open with an entrance animation. However, on desktop, menus can skip the animation and open instantly instead.

      Why only on desktop? That delay drives me crazy. I would like to skip on web/mobile too.

    1. Small components can set the size of their corner shape using a percentage of the absolute height of the component. This means the corner shape will change as the component height changes.
    1. Outlined buttons are also a lower emphasis alternative to contained buttons, or a higher emphasis alternative to text buttons.
    2. Dialogs use text buttons because the absence of a container helps unify the action with the dialog text. Align text buttons to the right edge for left-to-right scripts.
    3. Text buttons are often embedded in contained components like cards and dialogs, in order to relate themselves to the component in which they appear. Because text buttons don’t have a container, they don’t distract from nearby content.
    4. Don'tAvoid using two contained buttons next to one another if they don’t have the same fill color.

      Interesting. Do I agree with this?

      What is the reason they recommend this? It looks fine to me...

      At least they give alternatives that they recommend...

  3. Dec 2020
    1. We recommend the following changes to the default settings when designing ddPCR assays:

      Primer3 : designing primers and probes for ddPCR

      In the General Settings window, change “Concentration of divalent cations” to 3.8, “Concentration of dNTPs” to 0.8, and “Mispriming/Repeat Library” to the correct organism ■In the Advanced Settings window, change both the “Table of thermodynamic parameters” and “Salt correction formula” to SantaLucia 1998 ■In the Internal Oligo window, we recommend setting 15 for the minimum number of bases for the oligo. We recommend 64°C as the minimum Tm for the probe, 65°C as the optimal Tm for the probe, and 70°C as the maximum Tm for the probe. These parameters can be relaxed to allow for smaller/larger oligos, which may be necessary for high GC or low GC targets. Oligo size should be no smaller than 13 and no larger than 30 nucleotides

      Note: After you have made the desired changes in Primer3Plus, select Save Settings under General Settings and save these parameters in a file. To apply these settings in the future, upload them by selecting Browse in the General Settings tab, find this file, and click Activate Settings.

    2. Strive for a Tm between 50 and 65°C. One way to calculate Tm values is by using the nearest-neighbor method. Use the Tm calculator at http://www.basic.northwestern.edu/biotools/oligocalc.html, with values of 50 mM for salt concentration and 300 nM for oligonucleotide concentration
    1. has developed novel bioinformatics software called OliVar, which allows researchers and assay developers to automate and design assays that target regions of the virus genome that have the lowest frequency of mutation
    1. page is a { host, path, params, query } object where host is the URL's host, path is its pathname, params is derived from path and the route filename, and query is an object of values in the query string.

      I like that we don't have to manually parse params/query out of the full request URI. It provides the data that you are most likely to need, in an readily/easily-usable form.

    1. Facebook’s stated mission—to make the world more open and connected—

      If they were truly serious about the connectedness part, they would implement the Webmention spec and microformats, or something just like it, but open and standardized.

    1. The best solution that I found while trying to build a masonry component was to package up a pair of components and place child components inside a wrapper - I chose CardLayout and Card such that users would write something like: <CardLayout> <Card><MyBeautifulCard /></Card> <Card><AnotherCard /></Card> </CardLayout>
    2. Hm, React-way is really hacky... When we talking about lists, masonry, or any other table-style components, first of all, we talk about arrays and iteration through them. If you iterate over the children in the Masonry component, somewhere (in parent component I guess) you also iterate over the actual items. Over and over again, in all places you use this component, you perform almost the same iteration twice. Why we should do this? I believe the interface of this kind of components should look like this: <Masonry {items} {colsNum} let:item> <SomeItemComponent>{item}</SomeItemComponent> </Masonry>
    3. <script> export let items = []; export let colsNum = 3; $: cols = items.reduce(...); </script> {#each cols as col} {#each col as item} <slot {item} /> {/each} {/each}
    1. For a long time, the blue flame coming out of a gas burner has evoked cleanliness. That was no accident, but the result of a concerted advertising campaign.

      design gone wrong

    1. Sometimes, systems just scale the problemA UI design system is more than the code of a component library. It’s more than the colors, styles, and margins of your elements. It’s an ever-growing and ever-evolving creature that entails your brand and your user’s feelings.

      If you don't understand the problem - you can [[scale the problem instead of solve the problem]], and it's important to remember that a [[design system is more than a component library]]

    1. Instead of publishing a single one-size-fits package for components, we create an ecosystem where everyone works together yet deliver independently. The design system’s team role is to facilitate and regulate, not block or enforce.

      I think this is a really important point - the design system's team is to facilitate, not gatekeep.

    2. What you see here is a page composed of shared components. However, these are independent components developed and owned by different teams and published from different projects, which are mixed and integrated together.

      the move towards single page applications, component centric frameworks, etc has shifted how we view building webpages.

      It is not so much that we are building a page, but we are building components that we assemble into a page.

      We’re not designing pages, we’re designing systems of components.—Stephen Hay via atomic design

    3. The design of your system is not ready until you have two assets:a) A style-guide that defines the styling and implementation of your UI. This is usually a rather long document with a lot of text and typography.b) A set of reusable visual elements that bring together both visual (UI) and functional (UX) consistency through components. This is usually a rather large canvas with elements drawn on Figma or Sketch etc (we use both).

      there are two [[primary assets of a design system[[

      • the style guide
      • the reusable elements - an implementation of the style guide
    4. The benefits of our system go way beyond UI/UX consistency. We greatly accelerated and scaled our development, improved our product quality, and greatly improved work between developers, designers, and everyone else.

      Design systems enable faster development and delivery, and help teams scale - and have value beyond UI/UX consistency.

  4. Nov 2020
    1. The syntax of the fallback, like that of custom properties, allows commas. For example, var(--foo, red, blue) defines a fallback of red, blue — anything between the first comma and the end of the function is considered a fallback value.
    1. I love the Material Design System’s buttons just because their principles are really well thought through.
    2. Generally speaking, one will use smaller or less prominent buttons style for this.
    1. Curcumin, but not fish oil, reduces postprandial glycaemic response and insulin demand for glucose control.

      This backs up the two studies on fasting glucose in diabetes and per-diabetes. It is also a higher quality study (crossover design).

    1. because we still remember the quality of service that the restaurant gave us.

      This is pretty much what Service Design, (Digital) Product Design and User Experience Design professionals are (or at least should be) concerned about.

    1. hub.cards allows you to create and design your next modern business card for free. Our newly developed editor is like no other on the web and makes all your creative dreams come true. If you're not a creative genius, you can choose from thousands of templates to create an appealing card.

      Best free editor for creating business cards. Digital & physical ones.

  5. Oct 2020
    1. BTech in design engineering or BTech engineering design: Design thinking is a popular concept that spans multiple industries and there are courses, independent of any branch purely focussing on designing products. This is also often referred to as an engineering design course or design engineering course. The idea is to teach how to not just bring in design to develop great products that are aesthetically perfect and ergonomically usable and consumer-focused but also to introduce design as a tool for innovative thinking. The curriculum develops design thinking concepts in a manner basis which students can conceptualise and develop products that are innovative while also boasting of high aesthetic value. These graduates are sought after by all manufacturing industries.

      Design thinking fosters innovative thinking.

      It involes designing user focused, highly utilitarian and aesthetic products.

    1. “Outdoor adult learning can be an antidote and complement to the digital world . . . offering holistic, mentally and physically challenging learning experiences.”

      Adult Learning often takes place within walls or in front of a computer screen this can lead to health problems. This article offers reasons and methods for getting adults outdoors and using Universal Design. Outdoor learning can be used to complement digital learning.

    1. Interaction strategies are a type of accommodation that typically go unnamed and unwritten

      How many times do we use "accommodations" which dance around the relational issues, instead of dealing directly with them?

    1. Typically, platform accessibility APIs do not provide a vehicle to notify assistive technologies of a role value change, and consequently, assistive technologies may not update their cache with the new role attribute value.

      It's too bad they couldn't just allow role to be changed, and assistive technologies would just have to be updated to follow the suit.

    1. Good article about the importance of Universal Design when designing learning opportunities. The authors use plenty of strong sources to back their findings and keep the information concise.

      9/10

    1. Adult learning theories are not just a collection of jargons, concepts, and ideas about how adults learn. These theories help you plan your course during conception, development, and execution, in a way that will facilitate the learning process.

      Outlines adult learning "theories": Andragogy, Transformational Learning, and Experiential Learning, and states that they are important to educational designers, but doesn't really connect them to instructional design, let alone e-design. 3/10

    2. Insights 3 Adult Learning Theories Every E-Learning Designer Must Know

      Adult learning theories for Instructional Designers - Article names adult learning "theories" (andragogy, neuroscience, experiential learning, SDL, and transformational learning). Discusses why these "theories" are relevant to ID. Rating 3/10

    1. Handbook of Research on Student-Centered Strategies in Online Adult Learning Environments

      This article showcases a framework for course design using theory and research in the learning sciences. It defines student-centered learning and explains how it can/ should be used in the creation of the course and when establishing which theories and methods to structure the course around. 9/10, very detailed source.

    1. Instructional Design Approaches For Adult Learners

      (Available as text or podcast.) This article review adult learning theory, cognitive flexibility theory and accompanying design approaches (problem-based learning, collaborative learning). While it affirms strategies, it does little to address incorporation of technology. (2/10)

    1. Blended learning: Efficient, timely and cost effective

      (Click Download full-text PDF to read.) In this article, the authors discuss the blended learning instructional delivery method. Through case study, the authors demonstrate the benefits of blended course design. Furthermore, the article addresses potential detriments (financial, instructional design) of a blended course design. A brief review of considerations and recommendations for a blended design was provided. Though this article focuses on the relationship to forensic science, the information is applicable across disciplines and delivery venues (corporate, academic). (6/10)

    1. Considering that one of the most significant factors of online course quality is instructor presence and interpersonal interaction,4 one of the benefits video can offer is creating faculty presence in an online environment. In the interviews, students cited faculty presence as a key factor related to their engagement and perceived learning from videos. Humor and wit were described positively. Participants also mentioned the benefits of adding personable context to a subject; for instance, faculty members giving examples from their professional experiences about subject material. As one student explained, "The reading is very didactic or academic, but the videos are very real-case scenarios. The instructor narrates: 'How do you take that academic learning into the real world? What does that mean when you're looking at these financial statements?'" Another participant offered: "[The videos] are better than just reading the material because it has more of that human element."

      Melanie Hibbert, the Director of Instructional Media & Technology and Media Center at Barnard College in New York City, writes about what is necessary for good online instructional videos. Hibbert discusses media at Columbia University, methods for creating videos, an what analytics tell us. She concludes by describing the importance of instructor presence more so than the production quality of videos.

      Rating: 9/10

    1. Good instructional design is based on the industry-standard Instructional System Design (ISD) model. The ISD model comprises five stages—analysis, design, development, implementation, and evaluation—and is a systems approach to instructional design in that it views “human organizations and activities as systems in which inputs, outputs, processes (throughputs), and feedback and control elements are the salient features.”

      This article discusses visual, auditory, and kinesthetic learning styles and the importance of communicating in ways that appeal each style. It then outlines what this means for the Instructional System Design (ISD) model. The author concludes by outlining learning outcomes, organization, interactive instruction, and content versus connection versus application. The author proposes that "good instructional design is based on the industry-standard Instructional System Design (ISD) model" (p 5).

      Rating: 7/10

    1. Service design principles support the development of services which deliver high quality experiences to users and customers
    2. Data shall be normalized between the organization and its customers and within the organization itself Data shall be easy to transfer and be reusable within the organization and within the partner network Wherever possible data entry shall be avoided and be replaced by data lookup, selection and confirmation utilities instead
    3. Information flow is key to delivering high quality services; if people don’t know what they’re supposed to and when they’re supposed to know it – service suffers.
    4. Work groups are to be organized so that they match the processes and the competencies required Individual workers will be given sufficient autonomy to make useful decisions Work will take place in a location where it is done with the most efficiency

      Organizational Design Principles for Service Design

    5. Any activity that fails to add value for the customer should be eliminated or minimized Work is always structured around processes and not around internal constructs such as functions, geography, product, etc. Work shall not be fragmented unless absolutely necessary. This enables accountability and responsibility from a single individual and reduces delays, rework, etc. It encourages creativity, innovation and ownership of work. Processes should be as simple as possible. Focus on reducing process steps, hand overs, rules and controls. Wherever possible the owner of the process should have control over how it is delivered. Processes should reflect customer needs and many versions of a process are acceptable if customers have different needs. Process variation should be kept to a minimum. Process dependencies should be kept to a minimum. (I.e. process in parallel) Processes should be internalized rather than overly decomposed (e.g. training is better than work instructions) Process breaks and delays must be kept to a minimum Reconciliation, controls and inspection of process must be kept to a minimum KPIs for processes will only measure things that matter

      Process design principles for service design

    1. Author explores characteristics of adult learners respective to online learning environments. Andragogy is discussed as a theory, along with SDL and transformational and experiential learning. Author applies theory to design of physical environments to produce optimal circumstances for adult learning. Rating 8/10

    2. Characteristics of Adult Learners With Implications for Online Learning Design

      The author reviews assumptions of the adult learner and adult learning theory. In discussion of adult learning theories (self-directed learning, experiential learning, transformational learning), the article investigates their use in online learning. Furthermore, the author provides online course development recommendations for the adult learner. A brief critique of andragogic principles is provided. Adult learning principles used in a live environment are of benefit and necessary in the virtual environment. Click "Full Text" to read article. 7/10

    1. In highlighting the dangers of big-up-front-design (BUFD) and waterfall development, Agilists seem to advocate no-up-front-design (NUFD) or no-up-front-requirements (NUFR) or no-up-front-architecture (NUFA).
    1. Doctoral programs are often highly unstructured learning and training environments, where individual autonomy and freedom are highly valued. Decisions as to what counts as a good idea, a worthwhile project, or adequate progress are often left to the discretion of professors, and criteria for success can be opaque for students. This is even more so for those who are not already “in the know.”
    1. When using React hooks there is no concept of onMount because the idea of only running some code on mount leads to writing non-resilient components, components that do one thing when they mount, and then don’t take prop changes into account.
    2. A component shouldn’t break because it’s rendered more or less often.
    3. Keep the local state isolated.Think about which state is local to a particular UI representation — and don’t hoist that state higher than necessary.
    4. Props and state can change, and components should handle those changes whenever they happen.
    5. Even if a component is rendered just once, your design will improve if rendering twice doesn’t break it.
    1. We get a boilerplate-free API where shared state has the same simple get/set interface as React local state (yet can be encapsulated with reducers etc. if needed).
    1. This piece makes a fascinating point about people and interactions. It's the sort of thing that many in the design and IndieWeb communities should read and think about as they work.

      I came to it via an episode of the podcast The Happiness Lab.

    2. Most of the tech news we get barraged with is about algorithms, AI, robots, and self-driving cars, all of which fit this pattern. I am not saying that such developments are not efficient and convenient; this is not a judgment. I am simply noticing a pattern and wondering if, in recognizing that pattern, we might realize that it is only one trajectory of many. There are other possible roads we could be going down, and the one we’re on is not inevitable or the only one; it has been (possibly unconsciously) chosen.
    1. The path must not twist so much that visitors think they are being led astray, nor be so slow that visitors give up and strike cross-country through search engines. Nevertheless, twists and detours can help designers give their readers more than they expect.

      This makes me wonder if there are interesting major features or patterns we've not created for the web in general. Upsell, crosssell, alternatives, etc... are all corporate features. What about some interesting new artistic features perhaps?

      Almost no websites I run across are designed like this simple garden example. It's as if the website idea has been so rigidly crystalized that there's no room for exploration anymore.

    1. duty of care

      This reminds me of Mike Monteiro's book Ruined by Design from last year which pushes for a code of ethics for designers.

    Tags

    Annotators

    1. The attention of the audience is a writer's most precious possession, and the value of audience attention is seldom more clear than in writing for the Web. The time, care, and expense devoted to creating and promoting a hypertext are lost if readers arrive, glance around, and click elsewhere. How can the craft of hypertext invite readers to stay, to explore, and to reflect?

      A very early statement about what was about to become the "attention economy"

    1. A fun thing to watch for on news sites is when a draft of an article is submitted with an initial slug and title. Later, the title is changed but the slug is left untouched. This can result in some fun situations where the headline of an article has been made more subtle - but the slug retains some fairly blunt language.
    1. It wasn’t just that the headlines, free-floating, decontextualized motes of journalism ginned up to trigger reflexive mouse clicks, had displaced the stories. It was that the whole organizing structure of the newspaper, its epistemological architecture, had been junked. The news section (with its local, national, and international subsections), the sports section, the arts section, the living section, the opinion pages: they’d all been fed through a shredder, then thrown into a wind tunnel. What appeared on the screen was a jumble, high mixed with low, silly with smart, tragic with trivial. The cacophony of the RSS feed, it’s now clear, heralded a sea change in the distribution and consumption of information. The new order would be disorder.

      How can we design against this sort of disorder?

    1. A social network that has the users’ interests in mind would look completely different than today’s Twitter and Facebook. It would be designed to help you with your social interactions, quickly and efficiently, not trying to make you spend maximum amount of minutes on the site. Facebook, and increasingly Twitter (as their owners have started demanding profits), are doing the opposite. They . . . steal your time, make you do pointless stuff, filter in advertising in your news feeds, delete pages and users organising protests etc, mine their “big data” to find the best ways to use our weaknesses for pointless click-bait . . .

      This is a great quote which highlights the difference in the overall design ideas of social sites like Facebook and Twitter and the design of IndieWeb sites.

    1. However, if you want to create a backend API that is meant to be consumed only by your frontend, then you don't need REST nor GraphQL — RPC, such as Wildcard, is enough.
    1. Öffnet für mich nach der ersten Lektüre einen ganz neuen Zugang zur Verbindung von Theorie und Design Praxis. Man kann sich von hierher einen Rahmen für eine "Content strategy for degrowth" als eine nicht anthropozentrische Designpraxis vorstellen. Sehr viele Verweise.

    1. The $ contract for auto-sub­scrib­ing is lovely in its sim­plic­ity and flex­i­bil­ity. You can adapt your own preferred state-man­age­ment pattern or library, with or without Svelte stores as helpers. Svelte does not fuss about how you want to manage your state.
    1. In Formik, validateOnBlur defaults to true and it allows you to tell Formik not to validate on blur. React Final Form validates on every change by default, and setting validateOnBlur to true is a way to tell React Final Form to only validate on blur (to not validate on change).
    2. both copied much of their API from Redux Form, so, despite working very differently under the hood, there is a lot of overlap in their APIs.
    1. Domain-driven design separates the model layer “M” of MVC into an application, domain and infrastructure layer. The infrastructure layer is used to retrieve and store data. The domain layer is where the business knowledge or expertise is. The application layer is responsible for coordinating the infrastructure and domain layers to make a useful application. Typically, it would use the infrastructure to obtain the data, consult the domain to see what should be done, and then use the infrastructure again to achieve the results.

      Domain Driven Design separates the the Model in the MVC architecture into an application layer, an infrastructure layer and a domain layer.

      The business logic lives in the domain layer. The infrastructure layer is used to retrieve and store data. The application layer is responsible for coordinating between the domain and infrastructure layer.

  6. Sep 2020
    1. detach, as an api, should be declarative (ensure the node is detached) instead of imperative (detach the node), allowing it to be called multiple times by performing a noop if the node is already detached. This way, it won't matter if the node is removed from the DOM from outside of svelte.
    1. Mobile App Design Process: How We Build UI And UX

      Check this blog post by Cleveroad if you're wondering how to make app design.

    1. Did you know that you can create a Svelte component and with almost no extra steps distribute- and use it like any classic old Javascript library through a global constructor (let myComponent = new MyComponent())?
    1. For my point of view, and I've been annoyingly consistent in this for as long as people have been asking for this feature or something like it, style encapsulation is one of the core principles of Svelte's component model and this feature fundamentally breaks that. It would be too easy for people to use this feature and it would definitely get abused removing the style safety that Svelte previously provided.
    1. On the other hand, we could impose restrictions to the feature in order to avoid these hard paths.
    2. Since one of Svelte's main principles is reacting only to data changes (as opposed to re-render the whole app with the full state all the time)
    3. I mean, it's not that bad and it's certainly not much of a runtime cost (especially since it'd only affect components which actually use it -- thanks disappearing framework!).

      "disappearing framework"

    1. Instmctional systen1S design (IS D ) is the process for creating instructional sys­tems. It is both systematic and scientific in that it is d ocume ntable , replicable in its general application, and leads to predictable outcomes

      BIG KAHUNA OF DEFINITIONS.

      ISD is the process of creating Instructional Systems which are

      An arrangement, an organized approach, a set of resources and procedures.

    1. we need to step back and make a closer look at the DRY principle. As I mentioned earlier, it stands for "Don’t Repeat Yourself" and requires that any piece of domain knowledge has a single representation in your code base. The words domain knowledge are key here. DRY is not about duplicating code. It is specifically about duplicating domain knowledge

      This is actually a good point – to have a single representation of specific piece of domain knowledge in the code.

      DRY is not about duplicating code.

    1. in constructing representations of how to supportlearning in particular cases

      It reminds me of conjecture mapping. Are we going to make the similar thing?

    1. 8-Up works like this: 1. Get eight people in a room and ask them a design ques-tion like “How might we do a better job of moving peo-ple around?”2. Then tell them: “You each have three minutes to come up with three ideas for how we might do a better job of moving people around.”3. Once those three minutes have passed, all eight people should have three ideas each. You then tell them: “Great, now turn to your neighbor, show them your three ideas, they will show you their three ideas, take those six ideas and whittle them down to two.”4. After they’ve done that, say to each pair: “Okay, show your two ideas to the pair next to you. They’ll show you their two ideas. Take those four ideas and whittle them down to two.”5. After that, you’ll have two groups of four with two ideas each. You get all eight people together and say: “Take those four ideas and whittle them down to one.”This tends to produce better ideas than just saying, “Hey, eight people, come up with ideas and we’ll vote on the best one.” Or: “Hey, eight people, I’m gonna lock you in a room until you agree on an idea.”

      How about the opposite of this with throwing out the worst option first as a means of setting a bar for coming up with better. Example: In a group of people going out to lunch, suggest everyone goes to McDonalds, a restaurant you're reasonably sure no one will want to go to, to get better ideas. This is another sort of framing by creating a dreadfully low set point.

    2. What you generally can’t do is press a button that says, “Let’s collaborate to make this better.” And even if you could, it’s not clear what that process would look like.

      I want this button!

    3. Question design is one of the key tools we have at our disposal when trying to get people to work together. The art of turning a “should” statement into a “how might we” statement works something like this: for any “should” question, understand what the goal of the proposed solution is, and then frame a “how” question around that goal.

    Tags

    Annotators

    1. Independent Variable Manipulation

      Independent variable manipulation is the hallmark of experimental design.

    2. Writing proficiency is an essential learning outcome for undergraduate education as a whole and, specifically, in postsecondary psychology education. The American Psychological Association (APA, 2013) explicitly names effective writing as a goal in its guidelines for psychology majors,

      Effective writing is a core principle in education, emphasized by the most noted national psychological associations (APA; American Psychological Association). The following sections outline efforts to streamline the methods used instructor to student feedback for essays in a psychology class.

  7. Aug 2020
    1. Walls, A. C., Fiala, B., Schäfer, A., Wrenn, S., Pham, M. N., Murphy, M., Tse, L. V., Shehata, L., O’Connor, M. A., Chen, C., Navarro, M. J., Miranda, M. C., Pettie, D., Ravichandran, R., Kraft, J. C., Ogohara, C., Palser, A., Chalk, S., Lee, E.-C., … King, N. P. (2020). Elicitation of potent neutralizing antibody responses by designed protein nanoparticle vaccines for SARS-CoV-2. BioRxiv, 2020.08.11.247395. https://doi.org/10.1101/2020.08.11.247395

    1. Mobile App Design Cost: What’s the Price of UI/UX Design?

      Read this informative article by Cleveroad to know the price of UI/UX design.