961 Matching Annotations
  1. Oct 2021
    1. Product configuration and bundling are your key building blocks for designing the right products for the right segments at the right price points. Product configuration is about putting the appropriate features and functionality — those customers need, value, and are willing to pay for — into the product; this process has to be done for each identified segment. Systematic product configuration prevents you from loading too many features into a product and producing a feature shock.

      Un prodotto deve essere creato configurando le giuste caratteristiche in dei bundle che rispettino i determinati segmenti che abbiamo individuato. Ogni configurazione di prodotto deve rispettare i determinati bisogni, valori e WTP dei segmenti.

    2. Does our product development team have serious pricing discussions with customers in the early stages of the new product’s development process? If not, why not?What data do we have to show there’s a viable market that can and will pay for our new product?Do we know our market’s WTP range for our product concept? Do we know what price range the market considers acceptable? What’s considered expensive? How did we find out?Do we know what features customers truly value and are willing to pay for, and which ones they don’t and won’t? And have we killed or added to the features as a consequence of this data? If not, why not?What are our product’s differentiating features versus competitors’ features? How much do customers value our features over the competition’s features?

      Queste sono valutazioni che deve fare il CEO riguardo il #pricing del prodotto da lui creato.

      Tra le valutazioni e domande da porsi ci sono:

      • Il team rivolto al prodotto ha avuto una seria discussione riguardo il #pricing? Se no, perché non è accaduto?
      • Quali dati abbiamo che indicano che c'è un mercato che può e vuole pagare per questo prodotto?
      • Conosciamo il range di #WTP del nostro concetto di prodotto? Sappiamo il nostro target quali prezzi ritiene accettabili, esagerati ed immotivati? Come lo abbiamo scoperto?
      • Sappiamo quali caratteristiche del prodotto hanno maggiore valore agli occhi dei consumatori, quali sono disposti a pagare e quali invece non hanno alcun valore? Se no, perché?
      • Quali sono le caratteristiche del nostro prodotto che sono elemento di #differenziazione rispetto ai prodotti dei nostri competitor? Quanto valore hanno queste caratteristiche agli occhi dei consumatori?
    3. Did we segment before we designed the product? If not, why not?What were the segments? How did we get to these? Which ones would we serve initially? Do they represent a sizable market?What criteria were they based on? How different are these segments in their WTP? Can we respond differently to each segment? If so, how?How did we describe the segments? What observable criteria do we have in these descriptions? Do our descriptions and observable criteria on each segment pass our sales team’s sniff test?How many segmentation schemes do we have in our company? Can we consolidate to one segmentation across product, marketing, and sales?Who in our company is responsible for segmentation? At what point in the innovation cycle does this person (or people) get involved?

      Queste sono le domande che un CEO dovrebbe porsi riguardo la segmentazione per la creazione di un prodotto.

      • Abbiamo fatto una segmentazione prima di creare il prodotto? Se no perché?
      • Quali sono i segmenti che abbiamo individuato, in che modo ci siamo arrivati, quale abbiamo deciso di servire inizialmente, rappresentano un mercato sostenibile?
      • In funzione di quale criterio sono distinti i segmenti? In che modo cambia la #WTF dei differenti segmenti? Possiamo rispondere diversamente ad ogni segmento?
      • In che modo descriviamo i segmenti? Quali sono i criteri osservabili che abbiamo in queste descrizioni?
      • Quanti schemi di segmentazione abbiamo? Riusciamo a consolidare su un solo segmento tutte le nostre energie aziendali?
      • Chi è il responsabile della segmentazione? In che momento interviene?
    4. Do Segmentation Right:Begin with WTP data — By clustering individuals according to their WTP, value, and needs data, you will discover your segments — groups of people whose needs, value, and willingness to pay differ.Use common sense — Practicality and common sense are as important as statistical indicators.Create fewer segments, not more — Serving each new segment adds significant complexity for sales, marketing, product and service development, and other functions. Smart companies start with a few segments — three to four — and then expand gradually until they reach the optimal number.Don’t try to serve every segment — The products and services you develop should match your company’s overall financial and commercial goals. A segment must deliver enough customers — and enough money — to make the investment worthwhile.Describe segments in detail in order to address them — Investigate whether each segment has observable criteria for customizing your sales and marketing messages to them.

      Come si può segmentare in maniera efficace?

      1. Si comincia con i dati emersi dall'analisi sul #WTP, si creano cluster di individui in funzione di WTP, valori e bisogni, così emergono dei segmenti;
      2. Punta a pochi segmenti, non molti, ogni segmento porta con sé entropia che deve essere gestita, il numero ideale di segmenti è 3-4 e poi ci si espande in maniera graduale fino a raggiungere il numero ottimale;
      3. Non devi servire ogni segmento, il prodotto che crei dovrebbe essere coerente con gli obiettivi generali ed economici della tua azienda. Un segmento deve essere visto come un investimento;
      4. Descrivi ogni segmento in dettaglio e cerca criteri evidenti nel comportamento del segmento per poter customizzare il più possibile;
    5. The message here is clear: You need to create segments in order to design highly attractive products for each segment. And you must base your segmentation on customers’ needs, value, and WTP. This way, segmentation becomes a driver of product design and development, not an afterthought.

      Quale è il modo migliore per definire le caratteristiche migliori di un prodotto?

      Bisogna analizzare il mercato e segmentare i bisogni, valori e WTP dei consumatori. In questo modo la segmentazione diventa la guida della creazione del prodotto.

    1. I didn't have to think too much of what’s good for the company - I usually assumed that whatever I’m doing is what the business needs.

      It may even be a sign that management is doing well.

  2. Sep 2021
    1. A potentially interesting task management plugin for obsidian. I'm a little worried about long-term support. I'm going to wait and see what happens.

    1. A PFC assessment can be incorporated into an integrated riparian management process through a logical sequence of actions (figure 2). Figure 2. Recommended steps for managing riparian areas using an integrated process. After effectiveness monitoring has been done (step 6), initial objectives are validated and modified if necessary. After implementing adaptive actions, step 6 is repeated to monitor the effectiveness of those actions.Step 7: Implement adaptive actionsStep 6: Monitor and analyze the effectiveness of actions and update resource condition ratings (PFC)Step 5: Design and implement management and restoration actionsStep 4: Identify issues and establish goals and objectivesStep 3: Prioritize reaches for management, restoration, or monitoring actionsStep 2: Identify riparian resource values and complete additional assessmentsStep 1: Assess riparian area function using the PFC method • Identify assessment area and assemble an interdisciplinary team • Review existing information and delineate and stratify reaches • Determine the potential of the reach • Assess the reach and determine its functional rating (validate with monitoring data if necessary)Modifyobjectivesif necessaryMonitoradaptiveactions
    1. Areas of Integrated Governance

      Major areas of integrated governance for enterprise architecture looks like Integrated Project Management Framework

    Tags

    Annotators

    1. . Three points may be proposed about task-orientation. First, there is a sense in which it is more humanly comprehensible than timed labour. The peasant or labourer appears to attend upon what is an observed necessity. Second, a community in which task-orientation is common appears to show least demarcation between "work" and "life". Social intercourse and labour are intermingled - the working-day lengthens or contracts according to the task - and there is no great sense of conflict between labour and "passing the time of day". Third, to men accustomed to labour timed by the clock, this attitude to labour appears to be wasteful and lacking in urgency.1
    1. Smart leaders will not focus so much on exhorting people not to be afraid of change and will instead work to do everything they can to increase a sense of stable, supportive community. Unfortunately, many leaders see stability, community, and a sense of belonging as enemies of innovation — when in reality they are the prerequisites.
    1. When important decisions are not documented, one becomes dependent on individual memory, which is quickly lost as people leave or move to other jobs.
    2. A good manager must have unshakeable determination and tenacity. Deciding what needs to be done is easy, getting it done is more difficult. Good ideas are not adopted automatically. They must be driven into practice with courageous impatience. Once implemented they can be easily overturned or subverted through apathy or lack of follow-up, so a continuous effort is required.
    3. To do a job effectively, one must set priorities. Too many people let their “in” basket set the priorities. On any given day, unimportant but interesting trivia pass through an office; one must not permit these to monopolize his time. The human tendency is to while away time with unimportant matters that do not require mental effort or energy. Since they can be easily resolved, they give a false sense of accomplishment. The manager must exert self-discipline to ensure that his energy is focused where it is truly needed.
    4. The man in charge must concern himself with details. If he does not consider them important, neither will his subordinates. Yet “the devil is in the details.” It is hard and monotonous to pay attention to seemingly minor matters. In my work, I probably spend about ninety-nine percent of my time on what others may call petty details.
  3. Aug 2021
    1. And back in the day, everything was GitHub issues. The company internal blog was an issue-only repository. Blog posts were issues, you’d comment on them with comments on issues. Sales deals were tracked with issue threads. Recruiting was in issues - an issue per candidate. All internal project planning was tracked in issues.

      Interesting how versatile GitHub Issues can be

    1. Müller-Wille and Scharf ‘Indexing Nature’, also points out that Linnaeus interleaved blanksheets into his texts so that he could take notes. Cooper points out that this had been a common practice in natural historysince at least the late seventeenth century (Cooper, Inventing the Indigenous, 74–5).

      Apparently interleaving blank sheets into texts was a more common practice than I had known! I've seen it in the context of Jonathan Edwards (1703-1758) using the practice to take notes in his Bible, but not in others.

    2. First, what were the economies of attention thatguided his commonplacing techniques? Second, what type of impact did his note-taking skillshave upon the way that he arranged information in texts?

      The two questions addressed in this article.

    3. The foregoing studies suggest two strands of commonplacing circa 1700. The first was thecollection of authoritative knowledge, usually in the form of quotations. The second was thecollection of personal or natural knowledge, with Francis Bacon’s lists, desiderata and apho-risms serving as early examples. While Moss has shown that the first strand was losing popular-ity by the 1680s, recent scholarship has shown that the second retained momentum through theeighteenth century,9especially in scientific dictionaries,10instructional cards,11catalogues,12

      loose-leaf manuscripts,13syllabi14and, most especially, notebooks.15

      There are two strands of commonplacing around 1700: one is the traditional collection of authoritative knowledge while the second was an emergent collection of more personal knowledge and exploration.

    1. https://en.wikipedia.org/wiki/Sammelband

      Sammelband (/ˈzæməlbænt/ ZAM-əl-bant, plural Sammelbände /ˌzæməlˈbɛndə/ ZAM-əl-BEN-də or Sammelbands), or sometimes nonce-volume, is a book comprising a number of separately printed or manuscript works that are subsequently bound together.

      Compare and contrast this publishing scheme with the idea of florilegium and commonplace books.

      Did commonplace keepers ever sammelband their own personal volumes? And perhaps include more comprehensive indices?

      What time periods did this pattern take place? How does this reflect on the idea of reorganizing early modern information management practices? Could these have bled over into the idea of the evolution of the Zettelkasten?

  4. Jul 2021
    1. How Task management software is useful for small as well as big organizations? Task management software is used to handle tasks performed by employees.. Essentially, this means that processes must be smooth and productivity must be improved and useful for any sized organizations.

      Visit: https://anuchandola009.blogspot.com/2021/07/how-task-management-software-is-useful.html Call us :+919315540497

    1. Task Management Softwares Task Management Software is used to manage tasks by monitoring employees . You can track employees in real time, which will allow employees to concentrate more on their tasks.

      Visit: https://issuu.com/shivaniss1/docs/task_management.pptx Call us:+919315540497

    1. BlackRock employs a stable of former policymakers, underscoring the importance the company occupies in both financial and policymaking ecosystems, in something akin to a shadow government entity.[157] Good government groups have documented 118 examples of “revolving door” activity by the company—cases in which a government official joined BlackRock’s roster, or vice versa.[158] In one particularly troubling example of how Washington’s revolving door operates, in 2017, a former BlackRock executive was put in charge of reviewing the FSOC’s work for the Treasury Department.[159] Unsurprisingly, the Department’s conclusion was that FSOC should “prioritize its efforts to address risks to financial stability through a process that emphasizes an activities-based or industry-wide approach,” the company’s preferred position.[160] This conclusion all but ensures that BlackRock will not be designated for greater regulation by the FSOC under the Trump administration.

      To Big To Fail? Above The Law? Shadow Government?

      The term "shadow government" comes up often when investigating Revolving Door partnerships between corporations and former government policymakers. One particular public corporation, BlackRock Investments is the poster child of revolving door activity and comparisons to a shadow government.

      BlackRock is front and center in the manipulation of todays Real Estate bubble.

      BlackRock should be marketed as;*The Largest Asset Manager and Keeper of The Neo-liberal Flame; We Kill Children to Make You Money and We Enjoy Doing It!*

    1. The operative content object is the content object to which a request is directed – this is the content object that the user specifically wants, and that the request primarily operates on.
    1. urql stays true to server data and doesn’t provide functions to manage local state like Apollo Client does. In my opinion, this is perfectly fine as full-on libraries to manage local state in React are becoming less needed. Mixing server-side state and local state seems ideal at first (one place for all states) but can lead to problems when you need to figure out which data is fresh versus which is stale and when to update it.
    1. On the difference for writing for one's self and for others. Of course there's also the need to be able to re-decifer one's notes again in the future. It may be best to keep more detailed for your future self as if you're writing for the public.

      I like the idea of distance in "communication space" which comes up in the comments. This is related to context collapse and shared contexts which are often too-important in our communication with regard to being understood in the far future.

      <small><cite class='h-cite via'> <span class='p-author h-card'>Matthias Melcher</span> in Commonplace Book | x28's new Blog (<time class='dt-published'>07/06/2021 11:13:34</time>)</cite></small>

    1. Forty years ago, Michel Foucault observed in a footnote that, curiously, historians had neglected the invention of the index card. The book was Discipline and Punish, which explores the relationship between knowledge and power. The index card was a turning point, Foucault believed, in the relationship between power and technology.

      This piece definitely makes an interesting point about the use of index cards (a knowledge management tool) and power.

      Things have only accelerated dramatically with the rise of computers and the creation of data lakes and the leverage of power over people by Facebook, Google, Amazon, et al.

    2. In 1791, France’s revolutionary government issued the world’s first national cataloging code, calling for playing cards to be used for bibliographical records.

      Reference for this as well?

    3. Linnaeus experimented with a few filing systems. In 1752, while cataloging Queen Ludovica Ulrica’s collection of butterflies with his disciple Daniel Solander, he prepared small, uniform sheets of paper for the first time. “That cataloging experience was possibly where the idea for using slips came from,” Charmantier explained to me. Solander took this method with him to England, where he cataloged the Sloane Collection of the British Museum and then Joseph Banks’s collections, using similar slips, Charmantier said. This became the cataloging system of a national collection.

      Description of the spread of the index card idea.

    1. Linnaeus had to manage a conflict between the need to bring information into a fixed order for purposes of later retrieval, and the need to permanently integrate new information into that order, says Mueller-Wille. “His solution to this dilemma was to keep information on particular subjects on separate sheets, which could be complemented and reshuffled,” he says.

      Carl Linnaeus created a method whereby he kept information on separate sheets of paper which could be reshuffled.

      In a commonplace-centric culture, this would have been a fascinating innovation.

      Did the cost of paper (velum) trigger part of the innovation to smaller pieces?

      Did the de-linearization of data imposed by codices (and previously parchment) open up the way people wrote and thought? Being able to lay out and reorder pages made a more 3 dimensional world. Would have potentially made the world more network-like?

      cross-reference McLuhan's idea about our tools shaping us.

    1. Against Canvas

      I love that he uses this print of Pablo Picasso's Don Quixote to visually underline this post in which he must feel as if he's "tilting at windmills".

    2. All humanities courses are second-class citizens in the ed-tech world.

      And worse, typically humans are third-class citizens in the ed-tech world.

    1. Why isn’t there anything on our class’s Canvas page? Because Canvas and Blackboard are evil and must be destroyed. So-called “learning management software” is very possibly the worst software ever created by anyone for any purpose, and I will not add to the store of suffering in the world by making use of it. I explain in more detail my objections to Canvas here.

      Awesome AND true.

  5. Jun 2021
  6. May 2021
    1. Stay engaged. As mentioned above, you are expected to check your GVSU email twice daily, read new posts on CampusWire twice daily, contribute to the discussion board daily, and make at least two significant contributions to CampusWire per week. Make daily engagement with the course a habit, and don’t take days off (unless it’s a weekend and you have all your work done).
    2. Budget your time. MTH 124 is a 5-credit course with no meetings, so you will need to plan on spending about 15-20 hours per week doing mindful work. That’s 3-4 hours per weekday if you choose not to work on weekends. If you are taking other courses or have job of family responsibilities, you’ll need to think about where to put these hours in your daily and weekly schedules. In my experience, the #1 reason students don’t succeed in online courses is overcommitment and not managing time well.
    1. I particularly enjoyed the California water commons, with its quiet nod to Elinor Ostrom’s original post-graduate research on emergent cooperation between county water-boards.

      A quiet nod here in it's own right. Now I want to dig into Elinor Ostrom's research and work.

    1. I can refer to a section of page in a book by using #(booknr)p(pagenr)(section), for example #8p113a. There are four sections in my journals: A (upper left), B (down left), C (upper right), D (down right).

      An interesting page/section reference method.

    1. We still do not understand how information practices from the worlds of learning, finance, industry, and administration cross-pollinated. From the fourteenth century onward, accountants developed complex instructions for note-taking to describe holdings and transactions, as well for the recording of numbers and calculations. By the seventeenth century, merchants, and indeed ship captains, engineers, and state administrators, were known to travel with trunks of memoranda, massive inventories, scrap books, and various ledgers and log books that mixed descriptive notes and numbers. By the eighteenth century, tables and printed forms cut down on the need for notes and required less description and more systematic numerical notes. Notaries also were master information handlers, creating archives for their legal and financial documents and cross-referencing catalogue systems.

      I'm noticing no mention here of double entry book keeping or the accountant's idea of waste books.

      There's also no mention of orality or memory methods either.

    2. Humanists had the tools and even the concepts to invent the cross-referenced thematic library catalogue, but they did not do so. We do not know why it took several hundred years and the Italian director of the British Museum, Antonio Panizzi, to create a truly modern reference catalogue through his “Ninety-One Cataloguing Rules” in 1841.

      Origin of the modern reference catalogue...

    3. Why did a figure such as Leibniz fail to use his own tools? Perhaps messiness was the source of his creativity. This is a fact of intellectual originality with which Google must still grapple—libraries, after all, allow for the type of manageable disorder which is often the spark of creativity.

      Manageable disorder, messiness, and even chaos can be the source of boundless creativity.

      There's an idea in complexity theory that the most interesting things happen at the edge of chaos.

    4. In effect, Too Much to Know is a reference book about reference books, containing chapters on early “information management,” note-taking, reference genres and “finding devices,” compiling, and the impact of reference books.

      I love all of these various topics.

    5. The humanist remedy for information overload was to produce an unprecedented number of manuals about how to read books. They outlined what Blair calls the four S’s of early modern information management: storage, sorting, selection, summary.

      I'd love to have a list of these and some of their similarities. What would oral cultures have done? How would/did they manage their overflow of information, besides overwriting the new/improved and forgetting the old/unuseful?

    1. Sam Bowman. (2021, January 25). If the govt can’t keep a few thousand people fed in hotel quarantine, how exactly was it supposed to provide for fifteen million pensioners self-isolating in Great Barrington-style ‘focused protection’ while the virus was spreading across the rest of the population? [Tweet]. @s8mb. https://twitter.com/s8mb/status/1353666214883684352

    1. the three types of power commonly discussed in management theory: power-over, power-with, and power-to. These three types of power were first identified by the Mother of Modern Management, Mary Parker Follett. You may also recognize her as the person who coined the term “win-win.” Here are the three types of power: Power-over is extractive. Power-over is extracted from other people, the natural world, etc. Power-over means getting more of the pie. Power-with is gained when we work together, i.e, collective action. Power-to is generative. Power-to is the power we have to create new things. Power-to means making the pie bigger. 

      An interesting break down of power.

  7. Apr 2021
    1. This post articulates a lot of what I've been thinking about for the past 18 months or so, but it adds the additional concept of community integration.

      Interestingly, this aligns with the early, tentative ideas around what the future of In Beta might look like as a learning community, rather than a repository of content.

    1. The same is true with my time. So I started blocking all 24 hours of my time (mental breaks, yoga workouts, prepping dinner, sleep, everything) into my digital calendar. There is no time unaccounted for. 

      This Is the Time-Management Hack That Helped Me Double My Income

  8. Mar 2021
    1. Assessing Open Source Journal Management Software

      this is a good start of a mega analysis of all journal management platforms, isn't it?!

    1. Yes, Virginia, PMs Are Responsible for Accessibility

      Link to Session

      Angela Hooker, Microsoft

      Why build in a11y from the start?

      • Much easier / less "expensive" than adding it after the fact.
      • PMs are expected to set expectations and manage scope. Set the expectation from the beginning that team delivers accessible product.
      • Consider budget, timeline, people, & other resources. The design phase is "too late."

      Getting support from leadership

      • Talk about ROI & $8+ trillion in disposable income that people with disabilities have worldwide
      • Helps the org be more competitive
      • Show them how inaccessible content hurts. Demo use of product with a screenreader with no visuals, ask them to navigate with keyboard only. If possible, have a person with access needs do that demo.

      Include multiple accessibility reviews in your timeline

      • Team should check their work as they go along

      Choose the standards and level of compliance you'll achieve

      • Compliance and accessibility are not the same. You can conform to WCAG 100% but be unusable for people with certain disabilities
      • If project is used globally, consider laws worldwide. Some countries require specific documentation & standards will vary

      Put accessibility requirements in contracts with outside vendors

      • Be specific about the standards they need to meet
      • Ask for proof they can produce accessible work

      Carefully choose the tech you'll use to build your project

      • If you don't have a choice in what tech you'll use, see if team can fix those a11y issues. If it would expand scope or timeline to do so, flag as risk for leaderships

      Document all your team's work

      • Good to have on hand for showing "good faith effort" to be accessible
      • Prepare a general statement about project's a11y status.
      • Document known a11y issues and create a roadmap for resolving

      Get training for your team

      • Pointing toward info on the web is risky, as there is lots of misinformation. Start with info from W3C a11y curriculum.

      How do you coach your team and oversee their work?

      • Don't make it about any one person. Discourage things like "if we can't make you happy, we can't move forward." It's not about you being happy, it's about putting out the most usable and successful product you can!
      • Publicly praise team members as a way to motivate them to prioritize a11y in the long run

      Written content comes first

      • This is the easiest to remediate, so get this out of the way.
      • Ask people with cognitive impairments to read through with you to find out where things might not be clear

      Working with designers

      • Annotate design docs to indicate to engineering where they'll need to consider a11y
      • Review mockups & wireframes for missing a11y considerations so eng can raise concerns or questions
      • Start with user personas based on people with disabilities
      • Invest in usability testing at several points during project build

      What if you're updating a legacy project?

      • Start small
      • Have an auditor review for a11y and create a plan to give team "quick wins." Create roadmap for remaining items.
      • Talk to team responsible for product to find out what questions/concerns they have
      • Get training & other needed resources for team
    1. ReconfigBehSci on Twitter: ‘Session 1: “Open Science and Crisis Knowledge Management now underway with Chiara Varazzani from the OECD” How can we adapt tools, policies, and strategies for open science to provide what is needed for policy response to COVID-19? #scibeh2020’ / Twitter. (n.d.). Retrieved 5 March 2021, from https://twitter.com/SciBeh/status/1325720293965443072

    1. It is much easier to track what is going on within the activity. Instead of transporting additional state via ctx, you expose the outcome via an additional end event.

      Note: It's only super easy to see what's going on if you have the benefit of a diagram.

    1. NOTE: Your strategy should be supported using project management best-practices found within the Management Practices. These practices have been developed by industry, spending billions of dollars each year in projects. Of course, they would want their projects to succeed. Your quality of life is at least this important. Take your efforts seriously and manage your efforts.

      Don't Forget These 10 Project Management Best Practices: https://www.wrike.com/blog/project-management-best-practices-infographic/

    1. ReconfigBehSci on Twitter: ‘1 week to the SciBeh workshop “Building an online information environment for policy relevant science” Join us, register now! Topics: Crisis open science, interfacing to policy, online discourse, tools for research curation talks, panels, hackathons https://t.co/Gsr66BRGcJ https://t.co/uRrhSb9t05’ / Twitter. (n.d.). Retrieved 2 March 2021, from https://twitter.com/SciBeh/status/1323207455283826690

  9. Feb 2021
    1. Establish structured daily check-ins: Many successful remote managers establish a daily call with their remote employees.

      make sure there is space during standup for chit-chat.

    1. The great thing about working with reinteractive is you get to work directly with the developers, which is a huge plus. As a technical founder, I find proxying through a project manager adds unnecessary layers of complexity and creates opportunity for human error.
    1. Encapsulation is used to hide the values or state of a structured data object inside a class, preventing direct access to them by clients in a way that could expose hidden implementation details or violate state invariance maintained by the methods.
    1. DSLs can be problematic for the user since the user has to manage state (e.g. am I supposed to call valid? first or update_attributes?). This is exactly why the #validate is the only method to change state in Reform.
    2. The reason Reform does updating attributes and validation in the same step is because I wanna reduce public methods. This is to save users from having to remember state.

      I see what he means, but what would you call this (tag)? "have to remember state"? maybe "have to remember" is close enough

      Or maybe order is important / do things in the right order is all we need to describe the problem/need.

    1. One can now picture a future investigator in his laboratory. His hands are free, and he is not anchored. As he moves about and observes, he photographs and comments. Time is automatically recorded to tie the two records together. If he goes into the field, he may be connected by radio to his recorder. As he ponders over his notes in the evening, he again talks his comments into the record. His typed record, as well as his photographs, may both be in miniature, so that he projects them for examination.

      This is one of the most important aspects of the essay. Noting that he is continuously talking about the work of a scientist, he stresses the act of recording, of looking at reality. This is radically different from what Ahrens claims in his book "How to take Smart Notes", in which there is not a single hint to the fact that you must look through the window and not just into previous works.

    1. Using integrations with other tools in the product stack such as Jira and GitHub, progress on specific items can be viewed directly from the digital product roadmap, offering an accurate view of how well things are sticking to the schedule

      Why not just use built in tools in Jira and Github? Still struggling to see how roadmapping tool differs from, for example, Github project boards

    2. Translating these concepts into attractive visual product roadmaps that connect with a diverse set of internal stakeholders,

      In a small organization like Hypothesis, I'm not sure that a visually pretty roadmap is a pressing need. Willing to keep reading, but color me skeptical.

  10. Jan 2021
    1. There are lots of trees around us but we don’t know which one plant is harmful for us means a trigger to pollen allergy. Let’s know the pollen allergy symptoms which include sneezing, nasal congestion, wheezing etc. Don’t worry if you are suffering through this allergy, just stick to the allergy medications suggested by your doctor for better allergy management.

    1. Theemergence of the termcontent strategyitselfrepresents widespread recognition that componentcontent management was in great need of aroadmap.

      For me this is one of the key sentences of this paper. It is impossible to understand content strategy without taking component content management into consideration. For an academic approach to content strategy component content management is a key.

    2. In its most commondefinition, a genre is a rhetorical action that istypified and socially recognized based on recurrentsituations; members of organizations use genresfor specific communicative and collaborativepurposes [6], [7]

      This might be translated following the approach of semiotic practices defined by Fontanille et.al.

  11. Dec 2020
    1. "Organizational change management ensures that the new processes resulting from a project are actually adopted by the people who are affected.”

      Definition of change management

    1. React will update state throughout the user’s session. localStorage won’t change.When the user ends their session, save whatever the state is at that time to localStorage, making it available for hydrating in the next session.

      Is this safe/reliable to defer saving until then? What if browser crashes? I guess that's why onbeforeunload is needed. Hopefully onbeforeunload is reliable and can't be skipped (unless browser crashes?).

    2. So rather than continuously keeping localStorage in-sync with React state, let’s simply save state to localStorage whenever the user ends their session, either by leaving the app (‘unmounting’ the component) or refreshing the page.
    1. Our large project is going to need highly structured and predictable state management, and Svelte’s flexibility scales from trivial projects up to our big one. We’re looking at statecharts and XState to wrangle this problem.
    1. Microsoft says it will make changes in its new Productivity Score feature, including removing the ability for companies to see data about individual users, to address concerns from privacy experts that the tech giant had effectively rolled out a new tool for snooping on workers.

      It's great that MS has reacted so quickly to the outcry around the privacy of workers.

      I thought it would be super-interesting to see how academics might have responded to the idea of institutional administrators keeping tabs on the number of hours that they'd spent in meetings (via Teams), composing and reading emails (via Outlook), writing articles (via Word), and so on.

      And yet these would be the same academics who do this kind of monitoring of student work.

  12. Nov 2020
    1. Almost all interfaces today, with the exception of TheBrain visual user interface, are limited to organizing information into hierarchies, where a piece of information can only be categorized into one place. For simple applications this is fine, but for users engaging in more complex business processes, it is simply inadequate. A document will have a variety of different issues or people associated with it – with hierarchies one cannot show all these relationships without multiple copies of the information.

      Shelley Hayduk also identifies the issue that most information management software uses a file cabinet metaphor (i.e. hierarchy). This has the limitation that a piece of information can only be categorized in one place. For more complex things, this is inadequate.

    1. This conflicts in very basic ways with what other engineering disciplines expect. Toyota's stylists might be able to sell their renderings in art galleries, but you can't drive to work in one. In software, you can.

      I don't really understand the sentence. Does it mean that you can't really use a project's design until it's built, in classical engineering, while instead with software all that detailed design is actually the product?

  13. Oct 2020
    1. Before you start a weight-loss program, it’s crucial to identify and create a treatment plan for any obesity related illnesses or diseases.

      Find out more about medical weight loss here.

    1. Similarly, we use an opportunity algorithm to quantify which of the customer’s desired outcomes are unmet, and to what degree. A desired outcome statement is a uniquely defined need statement that describes how customers measure success when getting a job done. We assign a number to a desired outcome that indicates whether products or services used in a given market adequately or inadequately serve it.
    1. Imperative UI causes all sorts of problems, most of which revolve around state, which is another fancy term meaning “values we store in our code”. We need to track what state our code is in, and make sure our user interface correctly reflects that state.
    1. Yet many teams struggle to achieve a unified way of evaluating what they’ve delivered. Only 1 in 10 have a process for assessing the success or failure of newly-launched products and features.

      we've done this informally, but might consider a more formal approach

    2. For the product teams lacking a systematic way of logging these feature requests, pain points, and other bits of user feedback, a lot of valuable information ends up slipping through the cracks.

      we are working at getting better at this but there is room for improvement

    1. Microlearning: Knowledge management applications and competency-based training in the workplace

      Lynn C. Emerson, & Zane L. Berge. (2018). Microlearning: Knowledge management applications and competency-based training in the workplace. Knowledge Management & E-Learning: An International Journal, 10(2), 125–132.

      https://search.ebscohost.com/login.aspx?direct=true&AuthType=shib&db=edsdoj&AN=edsdoj.8793b57070bd45918c6e0875f40ced31&site=eds-live&scope=site&custid=uphoenix

      The focus of this article is a threefold discussion on microlearning 1) how microlearning best practices facilitate knowledge acquisition in the workplace by engaging and motivating employees through short, personalized, just-in-time learning, 2) ways microlearning integrates with knowledge management applications through situational mentoring, and 3) how competency-based microlearning, via subscription learning, is both an innovative approach to e-learning and an asset to learning organizations focused on improving the performance of their employees.

      8/10

    1. Instead of using classes and local state, Deku just uses functions and pushes the responsibility of all state management and side-effects onto tools like Redux.
    1. role-based access control, or RBAC
      • Is an approach to restricting system access to authorized users.

      • Controlling access to resources isn't all you can do. You can also centralize configuration management.

        You wouldn't want to setup printers or software for each and every user.

    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. So today, as a somewhat limited experiment, I played around with my Hypothes.is atom feed (https://hypothes.is/stream.atom?user=chrisaldrich, because you know you want to subscribe to this) and piped it into IFTTT. Each post creates a new document in a OneDrive file which I can convert to a markdown .md file that can be picked up by my Obsidian client.

      Trying to see if this work for me when linking with google drive. Unsure how to convert to markdown.

  14. Sep 2020
    1. This last characteristic may be the easiest to evaluate. Unless the position is very junior, I’ll usually hire product managers who’ve actually shipped a product. I mean from start to finish, concept to launch. Nothing is a better indication of someone’s ability to ship great products than having done it before. Past performance is an indication of future success
    2. I always insist that at a minimum, representatives from engineering, design, and marketing meet a potential PM candidate.
    3. I often joke that much of the time your job is to be the advocate for whoever isn’t currently in the room - the customer, engineering, sales, executives, marketing. That means you need to be capable of doing other people’s jobs, but smart enough to know not to. Great PMs know how to channel different points-of-view. They play devil’s advocate a lot. They tend to be unsatisfied with simple answers.
    4. So what do I look for in a PM? Most importantly, raw intellectual horsepower. I’ll take a wickedly smart, inexperienced PM over one of average intellect and years of experience any day. Product management is fundamentally about thinking on your feet, staying one step ahead of your competitors, and being able to project yourself into the minds of your colleagues and your customers.
    1. 2. Develop specific superpowers — don’t just rely on being a smart generalist.

      Bring something to the table. Could be solid design skills in my case (which I don't have yet)

    1. Whatever the future intentions of the PM, one thing remains for certain: this position is at the intersection from where founder strategy, user feedback, development team management, and market awareness come together. From what’s been said, it certainly appears that this is not a role that you “fall” into, but rather could aspire to be in.
    2. What’s more, to be a good PM, individuals also need to understand that it’s all about the bigger picture. Great managers “win” games, meaning that it’s not about getting a product out the door, but by ensuring that over the long-term, the team helps solve a larger problem. Nash says it’s not about getting an “E for effort” and brush off things that don’t work.
    3. The product manager isn’t the one that’s just sitting around overseeing the various teams and seeing whether it’s on track to meet the scheduled delivery or launch date. They are the ones who need to understand the market and that means knowing who the competitors are, what consumers want, and being able to help the marketing and sales teams better target them.
    1. More tactically,helping your team often means being the person who writes and summarizes notes after a long meeting, or writing a spec to make sure you have captured the team’s consensus and plan in written form.
      • Write notes after meeting and share with team.
    2. A lot of people describe a product manager as a CEO of the product or the “owner” of the spec, but I think that over-ascribes influence and authority to the product manager. The best teams operate in a way where the team collectively feels ownership over the spec and everyone has had input and been able to suggest and promote ideas. The best product managers coordinate the key decisions by getting input from all team members and are responsible to surface disagreements, occasionally break ties, and gather consensus (or at least ensure that everyone commits to a plan) when decisions get made.

      "CEO" of the product is an overrated term to describe PM.

      • Everybody on the team should feel heard/collective ownership
    3. Great product managers understand the very tricky balance between getting it right and getting it out the door.

      Balance between ship/get right = good product manager

    4. While shipping matters, the best product managers help the team make sure it’s the right product. Building something that doesn’t exist yet is always fun, but never a slam dunk.

      *

    5. More importantly, once shipped, the best product managers can measure whether the product shipped is the right one. They should work closely with the team to make sure the right moments in the product are measurable, and that the hard questions about whether people are really using the product can be answered.

      Once shipped good PM's know how to measure success fo the product

    6. Great product managers listen to user feedback all the time — whether it’s from usability tests, meeting users in the field, reading support emails or tweets, or working with the people in your company who do all of those things on a daily basis.

      *

    1. What do you think the most important things we should be doing over the next year? What will get in the way of us doing that? What’s going well, i.e. what should we make sure we don’t change? Is there anything you think I should know about?

      Good questions to ask as a new PM

    1. To me, abandoning all these live upgrades to have only k8s is like someone is asking me to just get rid of all error and exceptions handling and reboot the computer each time a small thing goes wrong.

      the Function-as-a-Service offering often have multiple fine-grained updateable code modules (functions) running within the same vm, which comes pretty close to the Erlang model.

      then add service mesh, which in some cases can do automatic retry at the network layer, and you start to recoup some of the supervisor tree advantages a little more.

      really fun article though, talking about the digital matter that is code & how we handle it. great reminder that there's much to explore. and some really great works we could be looking to.

    1. React Stately is a library of state management hooks for use in your component library.
    1. Provides state management for tree-like components. Handles building a collection of items from props, item expanded state, and manages multiple selection state.
    1. So why don't we extract the shared state out of the components, and manage it in a global singleton? With this, our component tree becomes a big "view", and any component can access the state or trigger actions, no matter where they are in the tree!