And this is what I believe is happening with students and reading, at least in part. They have convinced themselves that they aren’t readers. They have convinced themselves that reading old books, especially difficult old books, is just too arduous, too boring, too pointless. They have convinced themselves that even if the books are good and soul-enriching, there are better things to be doing with their time.

Doing free work for a company to make THEIR place a better one, only because you were gamed into doing that. The solution is never contribute to anything that is controlled by private company.

Don't think that I just naturally perfectly segment these commits when creating the feature. I heavily rebase and edit the commits before creating a PR.

Abstract

The GOP has threatened to weaponize a potential second Trump term

other nations are wary of what a second Trump presidency could portend,

so 00:40:49 there would be a mixture and my feeling is if you can't use the tool every single time it gets to be a bit of a hassle that oh today I'm using it tomorrow I'm not using it you you you 00:41:01 you sort of it becomes a cognitive effort to work the tool because you're not working the tool every day it'd be like changing from Mac to Windows every two days it's like oh c how do I do it 00:41:15 how okay it's there and that's not the sort of question you need to ask you don't want to ask yourself that sort of question in the booth you don't have time so you want everything to be very quick

Premium MOC tax support. Yaay, taxes. I think this one takes the award for most effort required to implement a feature that no-one really wants.

If this MR had been merged it would have saved us a lot of time and trouble.

The amount of time wasted on this is ridiculous. Thanks. This is about the only thing that worked. Why in the world this wouldn't "just work" by defining the default url options in Rails config/environments/test.rb is beyond me.

The goal of this project is to have a single gem that contains all the helper methods needed to resize and process images. Currently, existing attachment gems (like Paperclip, CarrierWave, Refile, Dragonfly, ActiveStorage, and others) implement their own custom image helper methods. But why? That's not very DRY, is it? Let's be honest. Image processing is a dark, mysterious art. So we want to combine every great idea from all of these separate gems into a single awesome library that is constantly updated with best-practice thinking about how to resize and process images.

By dropping or reducing or postponing the least importantparts, we can unblock ourselves and move forward even when timeis scarce.

If we overlay the four steps of CODE onto the model ofdivergence and convergence, we arrive at a powerful template forthe creative process in our time.

the research says is that students often

“If practicing feels easy, you’re probably not doing it right.

So when we struggle – like when we have difficulty making sense of a math review problem, or when we can’t seem to get a note to speak in quite the right way in a run-through – it appears that we misinterpret greater effort as an indication of reduced learning. And that this is why we tend to gravitate to activities like re-reading the textbook, which feels easier and more productive than struggling for five minutes to solve a review problem and still getting it wrong. 

the more effortful strategy is the one that often leads to more effective learning.

Well, for one, there was a clear preference for the blocked study schedule, with 68% of participants reporting that they would choose the blocked strategy to study for a test, while only 32% chose the interleaved strategy. Which is interesting, because the research on blocked vs. interleaved practice suggests that in many cases, interleaving is actually the more effective strategy (here’s a great summary of the research on interleaved practice, why and how it works, guidelines for use, and examples of times when blocked may be better).

the more effort they had to put into the study strategy, the less they felt they were learning.

Yes, precisely because I've been involved in maintaining codebases built without real full stack frameworks is why I say what I said.The problem we have in this industry, is that somebody reads these blog posts, and the next day at work they ditch the "legacy rails" and starts rewriting the monolith in sveltekit/nextjs/whatever because that's what he/she has been told is the modern way to do full stack.No need to say those engineers will quit 1 year later after they realize the mess they've created with their lightweight and simple modern framework.I've seen this too many times already.It is not about gatekeeping. It is about engineers being humble and assume it is very likely that their code is very unlikely to be better tested, documented, cohesive and maintained than what you're given in the real full stack frameworks.Of course you can build anything even in assembler if you want. The question is if that's the most useful thing to do with your company's money.

It is also why it's implementation in firefox is completely useless, considering that windows/osx/most linux distros plan to add support for DoH/DoT/DNScrypt resolvers in the near future, so firefox doing it itself will provide no additional benefit.

Webpacker used to configure Webpack indirectly, which lead to a complicated secondary configuration process. This was done in order to provide default configurations for the most popular frameworks, but ended up creating more complexity than it cured. So now Webpacker delegates all configuration directly to Webpack's default configuration setup.

Unfortunately, it's too late to make the question more specific as this would invalidate some of the (good) answers.

One reader is better than another in proportion as he is capable of a greater range of activity in reading and exerts more effort. He is better if he demands more of himself and of the text before him.

Luisa: I do. I remember my dogs. I remember my mom. I remember my dad. I remember my grandparents. I remember everything, and they didn't remember anything. Their entire life was over there, so that's just my bitterness. We moved back and I was so depressed. I don't think I've ever been that depressed in my life. I had to go back to high school because … even with the IB program. I killed myself. What was that worth, all that effort, and all that [Chokes up]? What was it worth? Nothing. I had to go back to this broken education system in Mexico which I could run laps around the fucking curriculum and I had to redo it in order to go to university, and fuck, that sucked.

It will be useless work when gvfs-open will solve the bug, but in the meantime...

There used to be other backends in addition to C: Java, CSharp, and Javascript but those suffered from bitrot and have been removed.

much software requires continuous changes to meet new requirements and correct bugs, and re-engineering software each time a change is made is rarely practical.

OpenFaaS® makes it easy for developers to deploy event-driven functions and microservices to Kubernetes without repetitive, boiler-plate coding.

Personally, I'm starting to think that the feature where it automatically adds xray.js to the document is more trouble than it's worth. I propose that we remove that automatic feature and just make it part of the install instructions that you need to add this line to your template/layout: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %>

Now that I've thought more about it, I honestly think the auto-adding the script feature is overrated, over-complicated, and error-prone (#98, #100), and I propose we just remove it (#110).

now that I've thought more about it, I think the auto-adding the script feature is overrated, over-complicated, and error-prone (#100), and ought to just be removed (#110).

now that I realize how easy it is to just manually include this in my app: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %> I regret even wasting my time getting it to automatically look for and add a nonce to the auto-injected xray.js script

Wasted too much time getting it to work with old Rubies/Rails, when I think the correct path should be to just remove support for them going forward

Frankly, if the Ubuntu Desktop team “switch” from making a deb of Chromium to making a snap, I doubt they’d switch back. It’s a tremendous amount of work for developer(s) to maintain numerous debs across all supported releases. Maintaining a single snap is just practically and financially more sensible.

This example of the chromium really shows that unless snaps or other similar format was used, applications would have to be sometime very heavily patched to work on older versions of systems to the point that it generates so much work that it would not be worth do to it otherwise, or at least not worth when the snap option exists and doesn’t require that much more work.

Saving form data across sessions — what do people hate more than filling out a form? Filling out a form twice!

it’s a volunteer effort There’s no full-time team supporting Svelte — its developers are part-time volunteers. Bugs get fixed, features get added, and many professionals rely on it in production, but unlike other major frameworks, nobody is being paid to work on it full-time.

and by the way, Rick Harris is just the public face of Svelte, the team is bigger and solid with a good growing community.

This sort of library probably should be communitized so there's really just a single library.

I agree, it would be great to join forces and speed up development... Svelte really needs one safe material library option.

We don't have clear visibility on which issues the VSCode team is planning on fixing & we would like to avoid duplicating work.

Please don't copy answers to multiple questions; this is the same as your answer to a similar question

Once again, this isn’t good or bad, it’s just the most efficient way to create something that is similar to something else

Of all the compile-to-languages, the one that strikes me as having the least merit is JSX. It's basically a ton of added complexity for the sake of what boils down to syntax. There are no real gains in terms of language semantics in JSX.

Other frameworks, which use a template syntax built atop HTML — Svelte, Vue, Ractive, Glimmer etc — have historically been fragmented, meaning those tools need to be reinvented many times.

Every new variation to the view requires updating both the view model and the template. This holds true even for simple variations.

I’d still be interested in Svelte making things easier so I’ve opened a feature request for Reactive statement cleanup functions.

This leads to web developers at every company needing to rebuild every control from scratch. This represents millions of dollars of investment for each company to duplicate work that many other companies are also doing.

Modern view libraries like React allow teams to build and maintain these components more easily than ever before, but it is still extraordinarily difficult to do so in a fully accessible way with interactions that work across many types of devices.

First class TypeScript support means that both of these two systems do a good job of handling TypeScript code.

predicted that over time, effort in the gamified course would be lower than the non-gamified course. The Mauchly's test was notsignificant. Video game use was not a significant covariate. Time was a significant factor,F(2,132)¼28.92,p<.001, partialh2¼.31. For bothconditions, effort increased significantly at each time point. Condition was not a significant factor,F(1, 66)¼.10,p¼.75, partialh2<.01. Theinteraction effect was not significant,F(2, 132)¼1.36,p¼.27, partialh2¼.02.H4was not supported.

These seem to be better reasons to support sub-nanosecond resolution. I think either storing picoseconds or storing sec fraction as 64-bit integer are better approaches than storing a rational. However, either change would be very invasive, and it seems unlikely to be worth the effort.

The app was still stuck in beta testing years after its debut, and the creators had to ignore bug reports and feature requests due to the limited resources.

This policy allows the test suite to stay green while letting individual teams decide when they would like to put in the effort to write more deterministic tests. They may choose to do so right away, or delay until they work on the feature again.

This also ties in the "Single Source Of Truth", where even if I craft descriptive commit messages I will probably have to describe what I did in the MR comments anyways, so that feels like duplicate work.

Good commit hygiene in general is a tough thing to enforce. It requires manual labor and descipline, from both the author and the reviewer.

Other sites could absolutely spend time crawling for new lists of breached passwords and then hashing and comparing against their own. However this is an intensive process and I'm sure both Facebook and Google have a team dedicated to account security with functions like this.

Before embarking on the effort to scrape the web for new password breaches and compare against your entire user database you also need to consider the ROI. The beauty of the pwned passwords API and this, and other, implementations of it is that you can get a good improvement in your account security with comparatively little engineering effort.

But, let’s be pragmatic for a second, the 80/20 rule states that you get 80% of the value from 20% of the work and a couple of simple tests are vastly better than no tests at all. Start small and simple, make sure you get something out of the testing first, then expand the test suite and add more complexity until you feel that you’ve reached the point where more effort spent on realism will not give enough return on your invested time.

This means that teachers spend a lot of time adapting and creating their own materials

ConclusionsThis paper finds that the effort grade affects theknowledge grade positively and significantly across allspecifications. This is strong evidence that more studenteffort does lead to increase learning

Agreementis the good stuff in science; it’s the high fives.But it is easy to think we’re in agreement, when really we’re not. Modeling ourthoughts on heuristics and pictures may be convenient for quick travel down the road,but we’re liable to miss our turnoff at the first mile. The danger is in mistaking ourconvenient conceptualizations for what’s actually there. It is imperative that we havethe ability at any time to ground out in reality.

Lyubomirsky makes the simple but important point that increasing your level of happiness takes sustained effort and commitment over time, just like achieving any other important goal in life.

Research has also shown that the amount of effort someone puts into increasing their happiness has a large effect on whether or not an activity works. In several studies, researchers found that people who reported that they put a lot of effort into their activities saw the greatest gains in well-being. Other methods are also used to evaluate effort, such as how many characters someone writes in his or her gratitude letters.

Streamline helping opportunities to make them seem less costly. After the tragic earthquake and tsunami in Japan, the Red Cross encouraged people to donate $10 by simply texting the term “REDCROSS” to a pre-specified number from their smartphones. By making pro-social behavior as simple and quick as the press of a button, Red Cross was able to increase compassion and helping for many people. These efficient helping opportunities could be embedded into various social media sites—such as Facebook—to provide low-effort conduits for compassion and helping.

But this is only part of the truth. Much intellectual property is produced only after considerable financial investment, whether it be in the research laboratory or in the graduate education of the scientist using the facility.

Responsibility, myself versus others. It may appear that responses to the question of responsibility are bifurcated between "Myself" and all other parties combined. However, respondents who identified themselves as being responsible were more likely than not to identify additional parties that share that responsibility. Thus, curatorial responsibility is seen as a collaborative effort. (The "Nobody" category is a slight misnomer here as it also includes non-responses to this question.)