6,447 Matching Annotations
  1. May 2021
    1. June Mathis

      Mathis was the first woman executive at MGM and the highest paid executive at age 35. She was voted the third most influential woman in Hollywood after Mary Pickford and Norma Talmadge in 1926, only a few years after this production.

      Mathis worked with Nazimova on four films before Camille, their final collaboration. She was also part of Nazimova's lesbian social circle "the 8080 club" also known as the "sewing circle" a few years later.

    1. I was thinking that illuminati is not real, But today with Mr Anthony carl now believe that illuminati is real, when you come across wrong person’s you will think that life is not real but when you are with the real one you will experience the goodness of your life, To MR Anthony carl has made me discovered my purpose of life. Welcome to the great brotherhood of Illuminati 666 WhatsApp mr Anthony carl +1(267)580-9355, from USA, and every other Country’s on how to join the Illuminati brotherhood to get rich and famous, You may be a politician, business man/woman ,musical artist, student, footballer or whatever occupation you do, you want to be rich, powerful and famous in life. Illuminati can grant all your heart desires join the Illuminati to become rich and famous in life, Illuminati will make you achieve all your dream to become rich and be protected all the days of your life.

    1. If instead of commenting, you write a response on your blog, you are standing behind your words, and associating them with the rest of your writing. The social dynamics are very different; you think more before responding instead of posting a quick flame. You can't really spam, as you are only soiling your own garden.
  2. Apr 2021
    1. As designers, we are often burdened by the responsibility of producing and managing website content. It’s not our job to write it, but it’s not the client’s either. In many cases a vacuum emerges which ultimately gets filled with poor content. We can avert disaster by including content production in the design process.

      Es geht auch um Rollen und die eigenständige Funktion von Contentstrategie neben Design und Coding.

      Wie wichtig ist Inhalt im Entwicklungsprozess einer Website, un wie überzeugt die Auftraggeber davon? Sehr zugängliche Einführung in zentrale Aspekte der Contentstrategie. Danke Matt Saunders/@WeAreCharityBox: Why Content Is Such A Fundamental Part Of The Web Design Process — Smashing Magazine

    1. GRADE K-4 GRADE 5-6 GRADE 7-8 GRADE 9-12 SPANISH TECH TEACHER Teacher Sign Up Sign In Teacher Sign Up Sign In GRADE K-4 GRADE 5-6 GRADE 7-8 GRADE 9-12 SPANISH TECH TEACHER TT GRADE K-4 GRADE 5-6 GRADE 7-8 GRADE 9-12 SPANISH TECH TEACHER Teacher sign up Sign In Why did ancient Greeks and Romans eat lying down? (Thinkstock) Why did ancient Greeks and Romans eat lying down? By: Ask Smithsonian, Smithsonianmag.com November 25, 2015 Published: November 25, 2015 Lexile: 1230L var addthis_config = { services_exclude: 'print,printfriendly', data_ga_property: 'UA-6457029-1', data_track_clickback: true }; var addthis_share = { url_transforms : { shorten: { twitter: 'bitly' } }, shorteners : { bitly : {} }, templates : { twitter : '{' + '{title}' + '}: {' + '{url}' + '} via @TweenTribune' } }; 530L 780L 1040L 1230L Assign to Google Classroom You asked us, "Why did ancient Greeks and Romans eat lying down?"   Reclining and dining in ancient Greece started at least as early as the 7th century BCE and was later picked up by the Romans.   To eat lying down, while others served you, was a sign of power and luxury enjoyed by the elite. People further down the social ladder copied the laid-back dining style, if they could afford to.   I mean, who wouldn't want to stretch out while chowing down, but not everyone was so lucky in ancient Greece. You see, women didn't generally get invited to banquets except for rare occasions like wedding feasts and even then they had to sit upright.   It was only in ancient Rome that customs changed, allowing upper-class women to lounge alongside men, and while it sounds sweet, all that lying down and eating can't have been good for the heartburn. Source URL: https://www.tweentribune.com/article/teen/why-did-ancient-greeks-and-romans-eat-lying-down/ Filed Under:   Video Culture Odd news Smithsonian Assigned 49 times CRITICAL THINKING QUESTION Why did people “further down the social ladder” copy people above them? Write your answers in the comments section below Please log in to post a comment COMMENTS (15) arellanoj-rob 11/30/2015 - 09:46 a.m. I think that people "further down the social ladder" copied people above them because they thought it'd earn them some sort of respect. It probably gave them sense of power back then. julianc-bag 11/30/2015 - 07:32 p.m. I don;t like eating at the dinner table I prefer the living room. ShawnaWeiser-Ste 12/02/2015 - 03:56 p.m. This seems quite unnecessary and dangerous. Its very common for people lying down to choke while they are eating, I mean come on. Good thing the women and the poor were not allowed to engage in such activities; they probably lived much longer than the rich men. laurenc-bag 12/03/2015 - 09:18 p.m. People "further down the social ladder" copied people above them, possibly to make themselves look a little wealthier than they were. It was a sign of luxury and was only enjoyed by the elite, so they wanted to experience that as well. laurenc-bag 12/03/2015 - 09:21 p.m. And, most likely, my weirdest custom at home is listening to music while watching a video on my phone while FaceTiming my friends, if that even counts as a strange custom... But, I also pray before I eat every meal with my family, which might seem strange to some people. laurenc-bag 12/03/2015 - 09:30 p.m. (It didn't allow me to take the test for some reason...) carsonb-2-bar 12/03/2015 - 10:28 p.m. In the early 7th century reclining and dining in Greece started and later on picked up by the Romans. According to the article it was a sign of power, especially when others served you. People in lower social classes copied it. The lower class people probably copied the upper-class people to be cool. Maybe it made them feel powerful. I thought the article was interesting. I never knew why many pictures back in the 7th century show people eating while lying down. I guess you could say they were the first couch potatoes! bellae1-lin 12/04/2015 - 02:57 p.m. People "further down the social ladder" copied people above them because they wanted to feel luxurious and wealthy. They would want to feel this way because they may not be treated like luxury, and they wanted to see with the eyes of a wealthy being. briannec-ste 12/07/2015 - 05:09 p.m. I personally don't like to eat laying down because I feel like I am being choked. I don't understand how laying down and being fed was a sign of wealth. The laying down not at all but the getting fed I understand. gisellem-pay 12/08/2015 - 11:11 a.m. I think that this concept is similar to our current society. Many people find or develop a custom, in which will catch on to others just to prove their power or how modern they believe they are. This also reminds me of China and foot binding. This tradition was passed down for women as a beauty concept. Page 1 of 2 Next » Take the Quiz Leave a comment ADVERTISEMENT TOPICS Animals Video Education Art Entertainment Culture Food & Health Inspiration National news Odd news Science Technology World news ADVERTISEMENT LEXILE LEVELS 500L-590L 600L-690L 700L-790L 800L-890L 900L-990L 1000L-1090L 1100L-1190L 1200L-1290L 1300L-1600L ADVERTISEMENT Take the Quiz Leave a comment ABOUT US FAQs Terms of Use Privacy Statement LOGIN Sign In Teacher Sign Up Can't Login GET IN TOUCH Contact Us Facebook Twitter Pinterest RSS The Smithsonian Institution is a trust instrumentality of the United States established by an act of Congress in 1846 "for the increase and diffusion of knowledge" googletag.cmd.push(function() { googletag.display('div-gpt-ad-tt-outofpage'); }); window.webtrendsAsyncInit=function(){ var dcs=new Webtrends.dcs().init({ dcsid:"dcs8v0iiladzpxfcn5y7c8cy2_5j6f", domain:"logs1.smithsonian.museum", timezone:-5, i18n:true, fpcdom:".tweentribune.com", plugins:{ } }).track(); }; (function(){ var s=document.createElement("script"); s.async=true; s.src="https://static.media.tweentribune.com/js/webtrends.min.js"; var s2=document.getElementsByTagName("script")[0]; s2.parentNode.insertBefore(s,s2); }()); <img alt="dcsimg" id="dcsimg" width="1" height="1" src="//logs1.smithsonian.museum/dcs8v0iiladzpxfcn5y7c8cy2_5j6f/njs.gif?dcsuri=/nojavascript&amp;WT.js=No&amp;WT.tv=10.4.23&amp;dcssip=www.tweentribune.com"/>

      The central idea of the text is that people ate lying down during Ancient Greece because lying down when eating was considered to be a luxury, and symbolized a high class, although high class men and women had different standards. High class women didn't have the right to lie beside men until Ancient Rome, when the customs finally changed.

    1. Neither question nor answer appears to understand the notion of semantic HTML. Height and width are presentational attributes regardless of where you put them. For semantics we establish what the image means to content in the alt tag. I don't remember why it was so important to width/height in the HTML but I suspect it was in case you hit browsers without CSS rendering. It's not a semantics issue. If anything it thwarts separation of concerns to a degree.

      claim: that the OP's question and this answer are incorrect

      Could we say that this answer (that this comment replies to) missed the point?

      I actually believed and thought this answer was spot on ... until I read this comment, and then I reversed my opinion.

    1. It has two very different meanings, that you would have to distinguish by context. One meaning is just expressing that we have limitations. If you don't know something, that's just tough, you don't know it and you have to live with that. You don't have information if you don't have that information. The other meaning is that not only are there gaps in our knowledge, but often we don't even know what the gaps in our knowledge are. I don't know how to speak Finnish. That's a gap in my knowledge that I know about. I know that I don't know how to speak Finnish. But there are gaps in my knowledge that I'm not even aware of. That's where you can say "You don't know what you don't know" meaning that you don't even know what knowledge you are missing.

      I had this thought too.

    1. How is a pseudoconsole different from a pseudoterminal ?

      I'm guessing that's just a Microsoftism to make it easier to search/find things that are specifically about Microsoft's flavor of pseudoterminal.

      I see they don't use the word "pseudoterminal" at all, but they do mention

      ConPTY, or the Windows PTY

      where PTY is another synonym/name for pseudoterminal. So I think we're safe in saying that this is talking about a pseudoterminal.

    1. Of course you must not use plain-text passwords and place them directly into scripts. You even must not use telnet protocol at all. And avoid ftp, too. I needn’t say why you should use ssh, instead, need I? And you also must not plug your fingers into 220 voltage AC-output. Telnet was chosen for examples as less harmless alternative, because it’s getting rare in real life, but it can show all basic functions of expect-like tools, even abilities to send passwords. BUT, you can use “Expect and Co” to do other things, I just show the direction.
    1. In many computing contexts, "TTY" has become the name for any text terminal, such as an external console device, a user dialing into the system on a modem on a serial port device, a printing or graphical computer terminal on a computer's serial port or the RS-232 port on a USB-to-RS-232 converter attached to a computer's USB port, or even a terminal emulator application in the window system using a pseudoterminal device.

      It's still confusing, but this at least helps/tries to clarify.

    1. TTY is right there in the name, but this article makes no attempt to clarify what exactly the relationship between a pseudoterminal and a TTY. I feel like a whole paragraph about the relation to TTY would be warranted, including a link to TTY article, of course, which does link [back] to and explain some of the relation to pseudoterminal:

      In many computing contexts, "TTY" has become the name for any text terminal, such as an external console device, a user dialing into the system on a modem on a serial port device, a printing or graphical computer terminal on a computer's serial port or the RS-232 port on a USB-to-RS-232 converter attached to a computer's USB port, or even a terminal emulator application in the window system using a pseudoterminal device.

    1. This game is severely underrated. I genuinely do not understand all of the negative backlash it gets. It's a solid scribblenauts game with a ton of replay value and a way to past the time with friends. It's not perfect, as the motion controls do drag it down slightly, and some of the minigames offered are less than great, however it does not deserve the overwhelming hate it gets. It's a solid title in the series.
    2. I truly TRULY do not get the hate of this game. I am in my 40's. Played with 2 boys, 10 and 12. And we all had an amazing time playing the board game version of this for an hour. When it was over, the boys said, LETS PLAY IT AGAIN! The game is deep. Also has original sandbox mode with new levels. When they were about to leave, I surprise them by giving them the game as a gift. They were SO excited (and, I will simply buy another one for myself) I am simply BAFFLED at the hate and negativity for this game. Sure, a couple of the mini-games are not top notch. But there are many great ones within. At $40, solid deal. At $20 sale in most places, you have got to be kidding me. Steal it at that price. If you like Scribblenauts or are new to the Scribblenauts world, just buy it.
    3. Yes, it shares the name and the look of those previous games, but it lacks the all-important creative heart of its predecessors, and ends up being a by-the-numbers affair that goes through the motions in a shallow attempt to turn Scribblenauts' unique premise into a multiplayer party game.
    1. COPYRIGHT Rsync was originally written by Andrew Tridgell and is currently maintained by Wayne Davison. It has been improved by many developers from around the world. Rsync may be used, modified and redistributed only under the terms of the GNU General Public License, found in the file COPYING in this distribution, or at the Free Software Foundation.

      Only answered:

      • who maintains
      • what the license is
    1. “Who cares? Let’s just go with the style-guide” — to which my response is that caring about the details is in the heart of much of our doings. Yes, this is not a major issue; def self.method is not even a code smell. Actually, that whole debate is on the verge of being incidental. Yet the learning process and the gained knowledge involved in understanding each choice is alone worth the discussion. Furthermore, I believe that the class << self notation echoes a better, more stable understanding of Ruby and Object Orientation in Ruby. Lastly, remember that style-guides may change or be altered (carefully, though!).
    2. Yet, it certainly is important to make the proper choices when picking up style. Similarly to fashion, code style reflects our credo as developers, our values and philosophy. In order to make an informed decision, it’s mandatory to understand the issue at stake well. We all have defined class methods many times, but do we really know how do they work?
    1. There is a tendency in short luck-heavy games to require you to play multiple rounds in one sitting, to balance the scores. This is one such game. This multiple-rounds "mechanic" feels like an artificial fix for the problem of luck. Saboteur 1 and 2 advise the same thing because the different roles in the game are not balanced. ("Oh, well. I had the bad luck to draw the Profiteer character this time. Maybe I'll I'll draw a more useful character in round 2.") This doesn't change the fact that you are really playing a series of short unbalanced games. Scores will probably even out... statistically speaking. The Lost Cities card game tries to deal with the luck-problem in the same way.

      possibly rename: games: luck: managing/mitigating the luck to games: luck: dealing with/mitigating the luck problem

    1. What's the point of playing a game featuring fjords without also including vikings to pillage the other player's lands...I've actually developed two additional tiles for Fjords: The Dragon and The Marauding Hoard. Both do exactly that.(I've play tested them with a friend well over 40 times and we both agree that with an expanded set of Fjords tiles, these two greatly improve the game for us. I'll write the tiles up and post them to BGG... eventually)
    1. What I dislike from the achievements is the "Dialogue Skipper". I really don't like it because you are encouraging people just to skim or even skip it at all and not get interested with the story. I earned this achievement on a 2nd run but I had a friend who just skipped it all on her 1st try.What devs should encourage is for the gamers to have a lot of playing time on their game so they would recommend it to others and not just do it for the cards and uninstalling it afterwards.
    1. “Digital technology allows us to be far more adventurous in the ways we read and view and live in our texts,” she said. “Why aren’t we doing more to explore that?”

      Some of the future of the book may be taking new technologies and looking back at books.

      I wonder if the technology that was employed here could be productized and turned into an app or platform to allow this sort of visual display for more (all?) books?

    1. unsuspecting childlikeness

      I'd also add [learned helplessness] (https://www.britannica.com/science/learned-helplessness) - the constant need for entertainment is definitely a problem, but if we take a deterministic view of these broader design trends the long-term ramifications are even more disturbing - the rise of Web 2.0 has seen a massive shift towards user-friendly platforms, but in addition to cultural infantilization we are seeing a significant decrease in tech literacy - and sometimes these trends manifest simultaneously. For instance, I'm writing this annotation in Chrome, but if I lose internet access my browser tab would allow me to play the endlessly addictive "Chrome Dino" browser game until my connection was restored - this is a fairly innocuous little easter egg (not coincidentally a term also used by Yelp UI designer Yoni De Beule in one of the articles I linked to above), but it does raise some broader questions about the amount of tech literacy and user autonomy these companies want us to have - features like these suggest that passivity is their preferred state for consumers, which is troubling.

    2. The privacy policy — unlocking the door to your profile information, geodata, camera, and in some cases emails — is so disturbing that it has set off alarms even in the tech world.

      This Intercept article covers some of the specific privacy policy concerns Barron hints at here. The discussion of one of the core patents underlying the game, which is described as a “System and Method for Transporting Virtual Objects in a Parallel Reality Game" is particularly interesting. Essentially, this system generates revenue for the company (in this case Niantic and Google) through the gamified collection of data on the real world - that selfie you took with squirtle is starting to feel a little bit less innocent in retrospect...

    3. Yelp, like Google, makes money by collecting consumer data and reselling it to advertisers.

      This sentence reminded me of our "privacy checkup" activity from week 7 and has made me want to go and review the terms of service for some of the companies featured in this article- I don't use yelp, but Venmo and Lyft are definitely keeping track of some of my data.

    1. Academy Games has always prided itself in the quality of its rules. Most of our rules are taught in stages, allowing you to start playing as soon as possible without needing to read everything. We are very careful about the order we teach rules and rely heavily on graphics and pictures to facilitate understanding. We also include a large number of detailed picture examples, often with 3D renders, that help you understand the context of the rules.
    2. We also include a large number of detailed picture examples, often with 3D renders, that help you understand the context of the rules. For these reason, we generally don't start laying out the final rulebook until production art is complete. Writing and laying out a 20 page rule book like this generally takes about 3 months from start to finish, usually requiring a complete rewrite or two, and involves dozens of editors.
  3. Mar 2021
    1. The reason Final Form does this is so that pristine will be true if you start with an uninitialized form field (i.e. value === undefined), type into it (pristine is now false), and then empty the form field. In this case, pristine should return to true, but the value that the HTML DOM gives for that input is ''. If Final Form did not treat '' and undefined as the same, any field that was ever typed in would forever be dirty, no matter what the user did.
    1. There's a reasonably good overview of some ideas about fixing the harms social media is doing to democracy here and it's well framed by history.

      Much of it appears to be a synopsis from the perspective of one who's only managed to attend Pariser and Stround's recent Civic Signals/New_Public Festival.

      There could have been some touches of other research in the social space including those in the Activity Streams and IndieWeb spaces to provide some alternate viewpoints.

    1. Svelte is different in that by default most of your code is only going to run once; a console.log('foo') line in a component will only run when that component is first rendered.
    1. according to Hao, Mark Zuckerberg wants to increase the number of people who log into Facebook six days a week. I’m not going to get into whether this is good or bad here, but it certainly shows that what you are doing, and how you are doing it, is very important to Facebook.

      Can we leverage these data points to follow a movement like Meatless Monday to encourage people to not use Facebook two days a week to cause this data analysis to crash?

      Anything that is measured can be gamed. But there's also the issue of a moving target because Facebook will change it's target which then means the community activism will need to change it's target as well. (This may be fine if the point is community engagement and education as the overall mission, in which case the changing target continually engages people and brings in new people to consider what is happening and why.)

    1. Muse

      Reminded of Chapter 11 in The Odyssey:

      I am likely going to retire this year and I find resonance in this as it appears that I will be accepting a "voluntary" buyout at the end of this fiscal year. My long sea journey, 25 years worth in teaching, will be officially over. Hence...the appeal to propitiate the gods, to let all the pain go, to ask forgiveness of the implacable Poseidon.

    1. Franklin thereby invented the first newspaper chain. It was more than a business venture, for like many publishers since he believed that the press had a public-service duty

      Long before the internet, and even national level newspapers, Franklin understood the power of the written word. His, and other like minded individual’s words were distributed in the form of pamphlets, that extolled their ideas on liberty and justice, and spread those words to all who were interested.

    1. Second, I don't agree that there are too many small modules. In fact, I wish every common function existed as its own module. Even the maintainers of utility libraries like Underscore and Lodash have realized the benefits of modularity and allowed you to install individual utilities from their library as separate modules. From where I sit that seems like a smart move. Why should I import the entirety of Underscore just to use one function? Instead I'd rather see more "function suites" where a bunch of utilities are all published separately but under a namespace or some kind of common name prefix to make them easier to find. The way Underscore and Lodash have approached this issue is perfect. It gives consumers of their packages options and flexibility while still letting people like Dave import the whole entire library if that's what they really want to do.
    1. here is my set of best practices.I review libraries before adding them to my project. This involves skimming the code or reading it in its entirety if short, skimming the list of its dependencies, and making some quality judgements on liveliness, reliability, and maintainability in case I need to fix things myself. Note that length isn't a factor on its own, but may figure into some of these other estimates. I have on occasion pasted short modules directly into my code because I didn't think their recursive dependencies were justified.I then pin the library version and all of its dependencies with npm-shrinkwrap.Periodically, or when I need specific changes, I use npm-check to review updates. Here, I actually do look at all the changes since my pinned version, through a combination of change and commit logs. I make the call on whether the fixes and improvements outweigh the risk of updating; usually the changes are trivial and the answer is yes, so I update, shrinkwrap, skim the diff, done.I prefer not to pull in dependencies at deploy time, since I don't need the headache of github or npm being down when I need to deploy, and production machines may not have external internet access, let alone toolchains for compiling binary modules. Npm-pack followed by npm-install of the tarball is your friend here, and gets you pretty close to 100% reproducible deploys and rollbacks.This list intentionally has lots of judgement calls and few absolute rules. I don't follow all of them for all of my projects, but it is what I would consider a reasonable process for things that matter.
    1. Whenever majorities trample upon the rights of minorities—when men are denied even the privilege of having their causes of complaint examined into—when measures, which they deem for their relief, are rejected by the despotism of a silent majority at a second reading—when such become the rules of our legislation, the Congress of this Union will no longer justly represent a republican people.
    1. If JavaScript were detached from the client and server platforms, the pressure of being a monoculture would be lifted — the next iteration of the JavaScript language or run-time would no longer have to please every developer in the world, but instead could focus on pleasing a much smaller audience of developers who love JavaScript and thrive with it, while enabling others to move to alternative languages or run-times.
    1. I don't understand why this isn't being considered a bigger deal by maintainrs/the community. Don't most Rails developers use SCSS? It's included by default in a new Rails app. Along with sprockets 4. I am mystified how anyone is managing to debug CSS in Rails at all these days, that this issue is being ignored makes sprockets seem like abandonware to me, or makes me wonder if nobody else is using sprockets 4, or what!
    1. The only place I can find it is in the sprockets-rails gem. javascript_include_tag calls this: def find_debug_asset(path) if asset = find_asset(path, pipeline: :debug) raise_unless_precompiled_asset asset.logical_path.sub('.debug', '') asset end end
    1. I'm kinda stuck at the moment, going around in circles. Everything is really heavily coupled. I would like to get to the point where no load is called from within processors, but i'm not sure if that's possible. Currently the API and the caching strategies are fighting me at every step of the way. I have a branch where i'm hacking through some refactoring, no light at the end of the tunnel yet though :(
  4. jangawolof.org jangawolof.org
    1. Fibar bi jàngal na taawan bu góor ni ñuy dagge reeni aloom.

      Le guérisseur a appris à son fils aîné comment on coupe les racines du Diospyros.

      fibar -- (fibar bi? the healer? as in feebar / fièvre / fever? -- used as a general term for sickness).

      bi -- the (indicates nearness).

      jàngal v. -- to teach (something to someone), to learn (something from someone) -- compare with jàng (as in janga wolof) and jàngale.

      na -- pr. circ. way, defined, distant. How? 'Or' What. function indicator. As.

      taaw+an (taaw) bi -- first child, eldest. (taawan -- his eldest).

      bu -- the (indicates relativeness).

      góor gi -- man; male.

      ni -- pr. circ. way, defined, distant. How? 'Or' What. function indicator. As.

      ñuy -- they (?).

      dagg+e (dagg) v. -- cut; to cut.

      reen+i (reen) bi -- root, taproot, support.

      aloom gi -- Diospyros mespiliformis, EBENACEA (tree).

      https://www.youtube.com/watch?v=BryN2nVE3jY

    2. Dafa ànd ak moroom yi àll ba, fori aloom.

      Il est allé dans la brousse ramasser des fruits de Diospyros avec ses camarades.

      dafa -- he/she.

      ànd v. / ànd bi -- to be together, to go together; copulate; going together, fellowship; placenta.

      ak -- and, with, etc.

      moroom mi -- comrade of the same age group, equal, companion, neighbor.

      yi -- the (plural).

      àll bi -- large expanse of uninhabited land, bush; distant, as opposed to home.

      ba -- the (indicates distance).

      for+i (for) v. -- to pick up.

      aloom bi -- edible fruit of Diospyros mespiliformis (aloom gi for the tree).

      https://www.youtube.com/watch?v=nL4iHgp5ejk

    3. Fexeel ba kër gi bañ ñàkk alkol.

      Veille à ce qu'il ne manque pas d'alcool à la maison.

      fexe+el (fexe) v. -- search/seek by all means.

      ba -- the (?).

      kër gi -- house; family.

      gi -- the (indicates nearness).

      bañ v. -- refuse, resist, refuse to; to hate; verb marking the negation in subordinate clauses.

      ñàkk v. / ñàkk bi -- vaccinate / vaccine (not sure exactly how this fits in the sentence if it's even the right translation -- perhaps it has to do with surgical alcohol rather than drinking alcohol).

      alkol ji -- (French) surgical alcohol. (I'm certain this is also used for the type of alcohol you drink -- but sangara is probably the most used term).

      https://www.youtube.com/watch?v=SsUjvAItysA

    4. Sama nijaay aj na ñaari yoon.

      Mon oncle a effectué deux fois le pèlerinage à La Mecque.

      sama -- my.

      nijaay ji n. -- maternal uncle; term of reference and address to designate the husband, in conservative circles.

      aj (Arabic) v. -- make the pilgrimage to Mecca. 🕋; deceased ☠️ (for a religious personality).

      na -- he (?).

      ñaar+i (ñaar) -- twice; two. 2️⃣

      yoon wi n. -- lane, path, track 🛤; law, regulation, legislation; times.

    1. In production, you will never trigger one specific callback or a particular validation, only. Your application will run all code required to create a Song object, for instance. In Trailblazer, this means running the Song::Create operation, and testing that very operation with all its side-effects.
    2. Run the complete unit with a certain input set, and test the side-effects. This differs to the Rails Way™ testing style, where smaller units of code, such as a specific validation or a callback, are tested in complete isolation. While that might look tempting and clean, it will create a test environment that is not identical to what happens in production.
    1. This is the story of how a bill to save the vote and preserve a semblance of democracy for millions of Americans died at the hands of an intransigent, reactionary minority in the Senate, which used the filibuster to do its dirty work

      The author starts off by personifying "the bill" as something that was supposed to save millions of Americans, but rather was killed by Senators. He immediately provides a brief overview of the claim of his essay before developing his narrative. This way, the audience gets a glimpse of the issue that the author will tackle. Also, by using words such as "intransigent and reactionary", the audience already understands that the author is going to be criticizing the senators for their action.

  5. Feb 2021
    1. For branching out a separate path in an activity, use the Path() macro. It’s a convenient, simple way to declare alternative routes

      Seems like this would be a very common need: once you switch to a custom failure track, you want it to stay on that track until the end!!!

      The problem is that in a Railway, everything automatically has 2 outputs. But we really only need one (which is exactly what Path gives us). And you end up fighting the defaults when there are the automatic 2 outputs, because you have to remember to explicitly/verbosely redirect all of those outputs or they may end up going somewhere you don't want them to go.

      The default behavior of everything going to the next defined step is not helpful for doing that, and in fact is quite frustrating because you don't want unrelated steps to accidentally end up on one of the tasks in your custom failure track.

      And you can't use fail for custom-track steps becase that breaks magnetic_to for some reason.

      I was finding myself very in need of something like this, and was about to write my own DSL, but then I discovered this. I still think it needs a better DSL than this, but at least they provided a way to do this. Much needed.

      For this example, I might write something like this:

      step :decide_type, Output(Activity::Left, :credit_card) => Track(:with_credit_card)
      
      # Create the track, which would automatically create an implicit End with the same id.
      Track(:with_credit_card) do
          step :authorize
          step :charge
      end
      

      I guess that's not much different than theirs. Main improvement is it avoids ugly need to specify end_id/end_task.

      But that wouldn't actually be enough either in this example, because you would actually want to have a failure track there and a path doesn't have one ... so it sounds like Subprocess and a new self-contained ProcessCreditCard Railway would be the best solution for this particular example... Subprocess is the ultimate in flexibility and gives us all the flexibility we need)


      But what if you had a path that you needed to direct to from 2 different tasks' outputs?

      Example: I came up with this, but it takes a lot of effort to keep my custom path/track hidden/"isolated" and prevent other tasks from automatically/implicitly going into those steps:

      class Example::ValidationErrorTrack < Trailblazer::Activity::Railway
        step :validate_model, Output(:failure) => Track(:validation_error)
        step :save,           Output(:failure) => Track(:validation_error)
      
        # Can't use fail here or the magnetic_to won't work and  Track(:validation_error) won't work
        step :log_validation_error, magnetic_to: :validation_error,
          Output(:success) => End(:validation_error), 
          Output(:failure) => End(:validation_error) 
      end
      
      puts Trailblazer::Developer.render o
      Reloading...
      
      #<Start/:default>
       {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model>
      #<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model>
       {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
       {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=save>
      #<Trailblazer::Activity::TaskBuilder::Task user_proc=save>
       {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
       {Trailblazer::Activity::Right} => #<End/:success>
      #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
       {Trailblazer::Activity::Left} => #<End/:validation_error>
       {Trailblazer::Activity::Right} => #<End/:validation_error>
      #<End/:success>
      
      #<End/:validation_error>
      
      #<End/:failure>
      

      Now attempt to do it with Path... Does the Path() have an ID we can reference? Or maybe we just keep a reference to the object and use it directly in 2 different places?

      class Example::ValidationErrorTrack::VPathHelper1 < Trailblazer::Activity::Railway
         validation_error_path = Path(end_id: "End.validation_error", end_task: End(:validation_error)) do
          step :log_validation_error
        end
        step :validate_model, Output(:failure) => validation_error_path
        step :save,           Output(:failure) => validation_error_path
      end
      
      o=Example::ValidationErrorTrack::VPathHelper1; puts Trailblazer::Developer.render o
      Reloading...
      
      #<Start/:default>
       {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model>
      #<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model>
       {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
       {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=save>
      #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
       {Trailblazer::Activity::Right} => #<End/:validation_error>
      #<Trailblazer::Activity::TaskBuilder::Task user_proc=save>
       {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
       {Trailblazer::Activity::Right} => #<End/:success>
      #<End/:success>
      
      #<End/:validation_error>
      
      #<End/:failure>
      

      It's just too bad that:

      • there's not a Railway helper in case you want multiple outputs, though we could probably create one pretty easily using Path as our template
      • we can't "inline" a separate Railway acitivity (Subprocess "nests" it rather than "inlines")
    2. step :direct_debit

      I don't think we would/should really want to make this the "success" (Right) path and :credit_card be the "failure" (Left) track.

      Maybe it's okay to repurpose Left and Right for something other than failure/success ... but only if we can actually change the default semantic of those signals/outputs. Is that possible? Maybe there's a way to override or delete the default outputs?