Meeting Purpose Explore the potential of Fair Shares Commons and strategize on implementation in Kansas/Missouri region.

Peel the masking tape off and install some 2 mm EVA craft foam is what I'd do with it. Or if originality is desired, you can get a pretty good match on that cloth tape they used.

Your application code should not be dealing with PID files, log redirection or other low-level concerns.

Let your operating system handle daemons, respawning and logging while you focus on your application features and users.

This makes developing a modern daemon much easier. The init config file is what you use to configure logging, run as a user, and many other things you previous did in code. You tweak a few init config settings; your code focuses less on housekeeping and more on functionality.

Less system administration, easier debugging, simpler code, all because you leveraged the init system to do the work for you!

And if I need for simple service object without validation? You can use Formalism::Action, a parent of Formalism::Form.

don't do this experiment philosophically do it experientially it's like undressing at night we take off everything that can be taken off

reality lies behind the multiplicity and diversity of appearances and is concealed by them

My tongue, every atom of my blood, form'd from this soil, this air, Born here of parents born here from parents the same, and their parents the same, I, now thirty-seven years old in perfect health begin, Hoping to cease not till death.

we go from not  understanding it to apathy in the span of an afternoon which is another issue. Um, so so  what should we do?

it's  only in 2023, it's only last year, that we for the first time quantify all the  nine,

we are on course for AGI by 2027 and that these AI 00:19:25 systems will basically be able to automate basically all all cognitive jobs think any job that can be done remotely

Putin Mafia style autocratic environment um wherever he can

Clarity is key: Provide crystal-clear instructions for assignments and grading criteria. Avoid confusing instructions. For example, students expressed frustration with assignment details being posted in the LMS but professors requesting submissions via email. Stay in the loop: Communicate with students by offering due dates, announcements, and calendar reminders. Timely and clear feedback on grades on the LMS empower students to track their progress effectively.

Post everything: Make sure all relevant course materials, such as the syllabus, grading scales, study guides, lecture slides, assignment instructions, and rubrics, are readily available on the LMS.

Structuring course materials in a clear and consistent manner is paramount. Use folders and course menus to group related materials, ensuring that everything is easily accessible. For example, some of our instructors have folders for each week with readings and assignments, while others choose to organize by chapters or units.

shown in Table 5. Overall, participants in theChronological group were more successful at finding thelocation for completing the prescribed instructional activities,than those in the Functional grou

As shown in Figure 3, participants reportedthat submitting assignments and checking their grades werethe most common activities, followed by reviewing classannouncements and completing quizzes or tests

One area that is typically not discussed in faculty training ishow to design a course in the LMS. Without sufficient training,courses tend to suffer from a lack of attention to design (R.Oliver, 1999) and design plays a key role in how learnersinteract with the LMS

such, it is reasonable to infer that if a student cannot interactwith the LMS or find the content required, then the student’ssatisfaction would decrease (Green, Inan, & Denton, 2012;Inversini, Botturi, & Triacca, 2006) or performance wouldbe hindered (Wang, 2010). Thus, faculty learning how todesign an intuitive user interface in an LMS is necessary inorder to ease the interaction between the learner and thecontent

Students in the Functional group completed a set of typical instructional activities slightly faster overall than participants in the Chronological group. However, students in the Chronological group reported a higher ease of use and needed less help completing the activities.

The lines between the design of content and the design ofthe functionality in future learning systems is becomingmore blurred. With ambitions of providing adaptive andcustom-designed learning experiences, even in face-to-facesettings, more and more instructional activities are delivereddigitally. It seems timely for the fields of education and userexperience (UX) to be integrated for the benefit of studentsacross all levels in all disciplines.

the ideal course layout is a balance of both functional andchronological elements. The findings directly apply to instruc-tors at universities and colleges who teach using an LMS, byway of possibly helping instructors design their course sites inan informed, intuitive way for students.

robust theme in the reasons given for preferringface-to-face delivery formats is the perceived lack of interactionwith an instructor in online courses.This was evident in statementsthat suggested that students believe they would have to “teachthemselves”, or that they would prefer a course taught by a “hu-man” or a “real teacher”.

All roads lead to progress.

The lonesome cat isn’t useless.  UUOCs are typically characterized by having exactly one filename argument; this one has none.  It connects the input to the function (which is the input of the if statement) to the output of the if statement (which is the input to the base64 –decode statement)

Some

Something of the sort was at-tempted years ago with the utmost se-riousness by a Mr. Quilter of Florence,Whistler's "Harry QUilter"; if I remem-ber rightly it was called All About Every-thing, and some of it was quite uninten-tionally very amusing reading.

we are certainly special I mean 00:02:57 no other animal rich the moon or know how to build atom bombs so we are definitely quite different from chimpanzees and elephants and and all the rest of the animals but we are still 00:03:09 animals you know many of our most basic emotions much of our society is still run on Stone Age code

curl -v -X POST \ -H "Accept: application/json" \ -H "Content-Type: application/json" \ -H "User-Agent: Mozilla/5.0 (${systemInformation}) ${platform} (${platformDetails}) ${extensions}" \ -H "Authorization: SSWS ${api_token}"

Yeah, I agree that lib (or app/lib

The real fundamental problem is that lib is a kitchen sink

Everything has a place so do better and find it. There is a certain belief that everything within app should be organized into functionally-named directories and any files placed in app/lib actually belongs in app/services or app/interactors or app/models or someplace if the developers just tried harder. The implication is that developers are bad developers if they don’t yet know what kind of constant they have and where its forever home should be. I reject this. Over the lifespan of an application, there will be constants that have not yet found their functional kin, if those kin ever come to exist at all; sometimes you simply need some code and a place to put it. app/lib can be the convention for where those constants can live temporarily or as long as necessary. Autoloading is really nice, let’s treat them to it.

Have you thought about citing the quote directly here, together with several summary points about why it provokes such questions, instead of creating just clickbait for your substack service? I believe that interested readers would click on your link in any case. Not interested will not be annoyed by having to click on the link to get to know that they are not interested. (It applies also for other areas of (self)marketing, by the way :-)

We would not have it again. Sometimes we think of the nations lying asleep, Curled blindly in impenetrable sorrow, And then the thought confounds us with its strangeness. The tractors lie about our fields; at evening

ISO 8601 specifies the use of uppercase letter T to separate the date and time. PostgreSQL accepts that format on input, but on output it uses a space rather than T, as shown above. This is for readability and for consistency with RFC 3339 as well as some other database systems.

but Government, even in its best state, is but a necessary evil…

As a result, hisindex is simultaneously a relic of research and a reminder of the pitfalls of all such effortsto create systematic knowledge, regardless of the underlying technology – paper, digitalor otherwise.

Beyond the realm of historians, advocates called card indexes ‘the only portable,elastic, simple, orderly and self-indexing way of keeping records’, and the practice wascommon enough that Gustave Flaubert parodied the unending and ultimately futilepursuit of all knowledge in his 1881 satire Bouvard et Pe ́cuchet (Dickinson, 1894).

In the building is an altar to all the gods in common. Now return back again to the Altis opposite the Leonidaeum.

the first things that I think is important to understand from our perspective we've been taught Through the Ages that every life form on the face of the planet has its proper place as divinely ordained by our Almighty 00:31:03 Creator when one looks to the human body and the complexities every so has an importance and Chief Seattle taught us that all things are connected what we do 00:31:15 to the Earth we do to ourselves we are but one strand in a very complex Web of Life and our ancestors also foretold of a Day of Reckoning and we are in that 00:31:27 Day of Reckoning right now

there are some sources of energy which  which create a negative value because of   00:48:39 of of global climate change and climate working  and warming and you know all the negative   external effect of using some energy so we have  some to make some of the energy uh sources just   illegal you know we have to keep some of the oil  in the ground we have to stop looking for new oil   and gas so you know so the solution to some of  the of the energy questions we have is just to to   00:49:04 to make illegal you know the use of certain energy  and to to to move to other energy so that's part   of the answer now if we if we have done that  and we deal with with energy that don't have the   the negative this much bigger negative impact  on mankind than their positive productive impact   then you know redistribution of wealth must be  about all forms of wealth you know whether it's   00:49:32 rent or energy or financial assets or i  was seeing you know we we need to have a   permanent circulation of wealth and power so you  know that's the way i i view you know taxation of   wealth is will be a permanent you know progressive  tax on net wealth which in effect will will will   wipe out all the biggest uh wealth right away you  know say up to 90 percent tax per year for you   00:49:59 know for for billionaires but among you know there  will still be some people who want 100 000 dollars   some people who earn 1 million or 2 million but  there will be a permanent circulation of wealth   holdings within within this limited uh wealth  gap that that will still exist and this should   be for all forms of wealth you know whether it's  land or housing or whatever whatever the origin

to get rid   of monopoly rent you have to return basic key  uh infrastructure to the public domain where   it was before 1980 so that uh basic needs can be  supplied at low prices not uh creating monopoly   for uh the one percent uh and i guess i'm saying  you have to realize that finance has used as well   00:25:12 to take over the economy and this has to  be reversed uh because uh once you have   uh wealth taking the form of uh claims uh  loans and claims on other people's debt   we'll count you up compound interest any rate of  interest is a doubling time and compound interest   is always going to grow faster than the economy's  real growth and the only way to prevent this isn't   00:25:37 simply to lower the interest rate which you've  done today 0.1 uh the only solution is to wipe out   the overall debts that are stopping economic  growth and these debts are the savings of the   one percent the good thing about cancelling debts  is you cancel the savings of the one percent   and as long as you leave these savings in  place there's not going to be a solution

We will also run into some issues when we consider adding new channels to Service Desk like an API. We should have a streamlined process of rendering notes (messages) etc. Having a base64 image (or even attachment) in mail but not in the API might be inconsistent and also adds a lot of code that needs to be maintained.

The pencilled dots in the margin of many books in the Codrington Library at All Souls are certain evidence that A.L. Rowse was there before you.

opts = method(__method__).parameters.map(&:last).map { |p| [p, eval(p.to_s)] }.to_h SomeOtherObject.some_other_method(opts)

that's right, we don't want to do params = { ... } because then we're hardcoding the implementation and it becomes very coupled. The benefit of doing it like in my examples is that you can change the method signature and still automatically capture all keyword parameters.

and then the deepest level is what's maybe more relevant for our discussion 00:27:04 we call it we call it all pervasive it's a conditioned kind of suffering and it's conditioned by ignorance the ignorance that does not understand reality correctly okay and that's really 00:27:17 what we're that's the opposite of what we're talking about when we talk about you know shunyata or emptiness uh this ignorance is 100 180 degrees opposite um so in that last level of suffering is 00:27:32 really the underpinnings of all the other sufferings okay so if we can address and remove that level of ignorance then all the other sufferings fall away 00:27:43 and you could also see it as all of our attachments that get us into trouble our aversions that can end in anger hatred and now we see so much violence in the world all that and 00:27:55 and our selfishness and our greed and you know on and on all that just falls away when we begin to get rid of this ignorance and we begin to not only intellectually understand emptiness but 00:28:08 we put it into our lives it percolates down and it starts to be part of our attitude the way we think the way we feel it permeates every aspect of our sleep and wake life and when that happens it's 00:28:22 it's like a revolution i don't speak from personal experience because i don't have that but according to the great saints and masters who have it's like a total revolution it's full of joy it's complete love and compassion 00:28:36 there's no moment where there isn't and it's always bathed in this wisdom of emptiness taking things as you said so beautifully in the beginning of your remarks carlo that everything is 00:28:48 in relation there are no discrete entities at all there's no independent existence i think those are the words that were used by david bohm who was a very close friend of his holiest the dalai lamas and as 00:29:01 you know a well-recognized quantum physicist um so those are just some contextual opening remarks to put us in in the in the right ball field if you will uh as a 00:29:15 with an american background baseball field right could be a soccer field

I think RSpec should provide around(:context)/around(:all). Not because of any particular use case, but simply for API consistency. It's much simpler to tell users "there are 3 kinds of hooks (before, after and around) and each can be used with any of 3 scopes (example, context and suite)". Having some kinds of hooks work with only some kinds of scopes makes the API inconsistent and forces us to add special case code to emit warnings and also write extra documentation for this fact.

Organizations as varied as Y Combinator, MIT’s Radiation Lab, and ARPA have astonishing track records in catalyzing progress far beyond their confines.

Easy Star All-Stars

today I'm here to describe that everything really is connected, 00:02:02 and not in some abstract, esoteric way but in a very concrete, direct, understandable way. And I am going to do that with three different stories: a story of the heart, a story of the breath, and a story of the mind.

Of course, we can always add more special cases to the type system to detect the specific case of iterating over a known-bounded object literal, but this just leads to the "Why does this code not behave like this other nearly-identical code?" problem when we fail to properly exhaust all the special cases.

or maybe it was how he used fire 15 to describe the trees.

You can help make Node.js and browsers more unified. For example, Node.js has util.promisify, which is commonly used. I don’t understand why such an essential method is not also available in browsers. In turn, browsers have APIs that Node.js should have. For example, fetch, Web Streams (The Node.js stream module is awful), Web Crypto (I’ve heard rumors this one is coming), Websockets, etc.

Run the Rails server (bin/rails s) and the Webpack Dev Server (bin/webpack-dev-server) via your preferred method. Two terminal tabs will work or create a Procfile and run via overmind or foreman.

Epics can contain both issues and epics as children

It also makes your code harder to follower because you are using SCREAMING_SNAKE_CASE instead of nice, readable methods.

This style of testing is used to exercise one piece of code with a comprehensive range of inputs. By specifying the test case once, alongside a table of inputs and the expected output for each, your tests can be made easier to read and more compact.

All The People

With every other change I make, I have to test in a dozen clients and make sure it looks fine. Why is there so much variation in email style implementation amongst different clients?

I've worked with people at companies where this was their only responsibility. Setting up emails for clients, making sure they pass a battery of tests and look great in all browsers and clients. It's an incredible PITA and it's not a set it and forget it thing. Clients can change month to month; spam filters change, etc...

STREAMS originated in Version 8 Research Unix, as Streams (not capitalized).

Valleyspeak

I think the issues/problems specified in the comments are not present with a Hash-only implementation. :) I would be supportive of re-considering this feature just for use with a Hash, where I believe 80% of the real-life use cases would (and do) exist. I have encountered this need before in the wild, but not with Arrays.

It would be very nice if that was consistent across every application.

Trying to force this one thing to work for everyone is the worst way to do that.

The elimination of what is arguably the biggest monoculture in the history of software development would mean that we, the community, could finally take charge of both languages and run-times, and start to iterate and grow these independently of browser/server platforms, vendors, and organizations, all pulling in different directions, struggling for control of standards, and (perhaps most importantly) freeing the entire community of developers from the group pressure of One Language To Rule Them All.

I would much rather have a "cosine" module than a "trigonometry" module because chances are good I only need a small fraction of the utilities provided by the larger trig module.

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.

Onceability can be the result of the exaggerated demand for un-memorable passwords.

I'd suggest there ought to be config to disable source maps specifically, and specifically for either CSS or JS (not alwasy both), without turning off debug mode. As you note, debug mode does all sorts of different things that you might want with or without source maps.

There's not a way to do it at the moment without enabling all debug features.

Notice that the HTML elements (BUTTON, DIV, etc.) are in CAPS. We know this is bending the standard Ruby style rules slightly, but we think it reads better this way.

Knowing what your elements are lets browsers use sensible defaults for how they should look and behave. This means you have less customization work to do and are more likely to get consistent results in different browsers.

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