It can be a quick conversation on what’s working and not working. Having these conversations throughout the year will improve your performance and help you work more effectively with your team.

Metrics make your work impact real.

If you’re like me, you might be washing the dishes and still be debugging code in your head.

# +devise_for+ is meant to play nicely with other routes methods. For example, # by calling +devise_for+ inside a namespace, it automatically nests your devise # controllers: # # namespace :publisher do # devise_for :account # end

find_field finds by id, name or placeholder text - so find_field('Prefix') should find the element with matching placeholder text rather than needing xpath.

Currently, I’m working on designing the interfaces and it’s real fun!

Writing documentation for the new website has been fun. Yes, fun!

easily exploited by a bullshitter. To counter this,organizations should only establish committees andhave meetings when there are clear terms ofreference, a value-adding agenda, and the rightattendees who can contribute to the desiredagenda. More simply, the need for a meeting shouldbe questioned unless an important decision needs tobe made.

When bullshit is legitimized and codified, itspreads more easily and is likely to be moreinfluential. This in turn fosters the future produc-tion of more bullshit.

Finally, any approach to evidence-based man-agement should ensure that the practices suit theindustry and functional context. For example,professionals in a biotechnology company would beexpected to follow and use industry-appropriateevidence-based practices that are likely to bemore rigorous and extensive than those adopted bya fashion-clothing company. Such practices includeencouraging or even requiring their employees todo the following four things (seePfeffer & Sutton,2006): (1) demand evidence for statements thatseem implausible; (2) examine the logic or cause-and-effect reasoning between the evidence andthe statement; (3) as needed, encourage experi-mentation to test the confidence of data and val-idity of statements; and (4) continually repeat andbuild on the first three activities to create anevidence-based learning culture that stifles theproduction and spread of bullshit.

Furthermore, to help encourage and value evi-dence over opinion, managers should be carefulwhom they consult. While they should seek sub-stantive debate about statements and supportingevidence, they should only involve well-informedand value-adding experts. Social media andcrowdsourcing initiatives regularly remind us thatthe wisdom of the crowd is not as judicious as wethink.

Colleagues throughout the organization, andespecially those in administrative and leadershiproles, should also practice it so that evidence canguide key decisions. This is also true in the areas ofmarketing and sales, which thrive on the creationand circulation of bullshit.

Research byPennycook, Cheyne, Barr, Koehler,and Fugelsang (2015)suggests that an organiza-tion’s capacity to produce and accept workplacebullshit decreases with the prevalence of andvalue placed on critical thinking in that organiza-tion. They outline how individuals have differentsensitivities to bullshit: Those who have the abilityto stop and think analytically about the substanceof statements are less receptive to bullshit, whilethose with lower cognitive skills and less insightare more receptive.

The first three steps in the C.R.A.P. framework areused to understand the nature of workplace bullshitand how to identify and deal with it. Building on thisknowledge, the final step in the framework outlineshow to prevent the creation and spread of work-place bullshit in the first place. In the long term,this step may be of the greatest benefit in dealingwith workplace bullshit. Effective prevention willminimize the need for, and costs associated with,recognizing and acting against workplace bullshit.

When you seek advice, first write down everything you’ve tried.

If you’re stuck for over an hour, seek help.

Now, if you also want deskopen to pass through any command-line parameters, you can instead use this slightly-modified version: #!/bin/sh desktop_file=$1 shift `grep '^Exec' "${desktop_file}" | sed 's/^Exec=//' | sed 's/%.//'` "$@" &

A solution is almost indicated in the question: hinder xdg-open from choosing exo-open. A brute-force approach is to copy /usr/bin/xdg-open to /usr/local/bin (/usr/local/bin is earlier in PATH unless PATH has been modified) and to patch it to use open_generic instead of exo_open (unlike the XFCE4-specific exo-open, open_generic does honor xdg mime types)

“As humans we resist change,” says Twitter and Square’s Dorsey. “It’s scary and something we can’t necessarily control. You hear that Twitter is important or Facebook is important or HTML5 is important, but how do you actually begin? There’s no easy way. It’s not fun to be self-reflective or self-aware. “In many cases it means we have to do more work,” he adds. “So we have to do more work.”

Money could be good if it is spent to provide some of the above things. Money on it's own is hard because then it means I would have to spend time book-keeping and managing instead of programming.

There's no release of sprockets 4 so there's nothing to revert. Master branch is a WIP. I would recommend using Sprockets 3.

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

On the “lows” side, I’d say the worst thing was the impact of not being present enough for my family. I was working a full-time job and doing faastRuby on nights and weekends. Here I want to give a big shout out to my wife. She supported me through this and didn’t cut my head off in the process.

Before a bug can be fixed, it has to be understood and reproduced. For every issue, a maintainer gets, they have to decipher what was supposed to happen and then spend minutes or hours piecing together their reproduction. Usually, they can’t get it right, so they have to ask for clarification. This back-and-forth process takes lots of energy and wastes everyone’s time. Instead, it’s better to provide an example app from the beginning. At the end of the day, would you rather maintainers spend their time making example apps or fixing issues?

Minimize the face sizes of attendees into grid view, and sit back a bit to allow yourself more personal space.

Demokratisierung, Digitalisierung und Dezentralisierung der Arbeitswelt

By 2021, the total electric waste is estimated to reach 52.2 million metric tons, and the majority of the waste cannot be appropriately recycled

CHILD DEVELOPMENT PERSPECTIVES

Ecoflex, unlike the materials used in commercially available flexible electronic displays, has a Young’s modulus that is compatible with the flexible bodies

The translucency of Ecoflex also helped the machines blend in with their surroundings

Although there are technologies, such as electrowetting (25) and electrofluidics (26), that use microfluidics to tune color, they rely on electric fields to move fluid and are not immediately compatible with our compressed-air power source.

Semiconductor technology has expanded our ability to see into the IR (24), and we explored techniques for camouflage or display in the IR

initial approaches to change the color, contrast, pattern, apparent shape, luminescence, and infrared (IR) emission (that is, surface temperature) of soft machines fabricated from elastomers and flexible reinforcing sheets (6–8)

These animals typically change color using specialized cells, such as chromatophores or iridophores (4, 9, 10), not simple microchannels

Although specific demonstrations of camouflage vary among species, the strategies used have common themes: background matching, disruptive coloration, and disguise (3, 11, 12)

oicing can alsoentail publicly calling ‘bullshit on bullshit’ orseeking help from an outside agency, such as aunion or government office. Employees are morelikely to choose to voice when they perceive thatthe organization offers sufficient psychologicalsafety; that is, when employees sense that theywill not be embarrassed or punished if they speakup (Frazier, Fainshmidt, Klinger, Pezeshkan, &Vracheva, 2017). The propensity to voice also de-pends on the extent to which employees haveorganizational commitment; that is, whether theycare for and believe in the organization enough towant to counter the harm of bullshit, combinedwith their perceived ability and capacity to make adifference. Such conditions are necessary foreffectively confronting bullshit. A principle knownas Brandolini’s Law states that the amount of en-ergy needed to refute bullshit is an order ofmagnitude larger than is needed to produce it(“Brandolini’s Law,” 2014).

Voicing is the act of employees speaking up toconfront what they consider to be bullshit. Em-ployees may ask to see evidence that supports thesuspected bullshit. They may themselves providebullshit-challenging evidence along with alterna-tive statements, and when doing so should becognizant that simple and coherent bullshit willtend to be more appealing than intricate andcomplex truths. Employees may also voice bylaughing at and mocking bullshit. This is a way to“informally show up its emptiness without havingto risk a full-frontal face-off with powerful bullshitartists” (Spicer, 2017, p. 167).

When employees correctly conclude that a state-ment is bullshit, they may react in a number ofdifferent ways. To illustrate these reactions, wedraw onHirschman’s (1970)exit,voice,loyaltyframework, which he initially formulated to illus-trate how employees react to organizations indecline or when the sky was falling. Scholars lateraddedneglect(Farrell, 1983; Withey & Cooper,1989) and successfully applied the framework tohelp understand employees’ responses to negativeworkplace experiences (Rusbult, Farrell, Rogers, &Mainous, 1988; Turnley & Feldman, 1999). Weapply this framework here to employees’ reactionsto bullshit.When employees act by exiting, they are tryingto escape from the bullshit and the bullshitter.This can involve quitting the organization orseeking a transfer to a different unit of the orga-nization so as to avoid the influence of the bull-shitter. Exiting is a likely reaction when employeesare so appalled by the bullshit that they cannotstay with the organization or unit, or when theyare already disillusioned, and the bullshit (possiblythe latest bout in a stream of bullshit) is the laststraw. For exiting to happen, employee dissatis-faction with the situation must rise to such a levelthat the disadvantages of remaining and facingbullshit in the workplace are greater than thedisadvantages of leaving. Or alternatively, thepersonal costs of leaving should be low enoughrelative to the costs of the two other responses inwhich workers remain and either contest thebullshit (i.e., voice) or disengage from the work-place bullshit (i.e., neglect).

Remember that bullshitters, unre-stricted by truth, have more freedom to frametheir statements. They are at liberty to deviseappealing bullshit with three significant charac-teristics. First, the bullshit may offer personalbenefits to the audience. For example, if a scien-tist in a research and development (R&D) depart-ment hears some bullshit from their boss thatsuggests the company is about to double the R&Dbudget, the scientist is likely to find this bullshitappealing. In addition, some employees may alsorelish or need workplace bullshit so as to flourish intheir jobs. They view bullshit as a necessary aspectof organizational life. Trendy jargon, flaky logic,and shallow arguments can be so appealing tosome that they provide them with direction andenergy.

Furthermore, abullshitter’s statements may never have beenintended to be believed or even to garner muchattention. They are intended to misrepresent bybeing appealing or convincing, or by distracting,exhausting, or disengaging colleagues, so thatagendas can be pursued with little or no resis-tance. This lack of awareness of the true nature ofworkplace bullshit is one of the reasons why thereis such an abundance of it (Fredal, 2011).

The bullshitter makes adecision to further that agenda through commu-nicative acts and decides on a message and amedium that will help them to achieve thatagenda. Crucially, while doing so, they disregardthe truth, in the sense that they are not concernedwith the truth, inaccuracy, or falseness of theirmessage but only in its efficaciousness in promot-ing the desired agenda

when we engagein work, we must distinguish between this type ofsocial bullshit, which can be harmless or evenhelpful to the organization (because it can enablethe development of normal interpersonal re-lationships), and other types of bullshit that canhave damaging impacts on the organization.

AbstractMany organizations are drowning in a flood of corporate bullshit, andthis is particularly true of organizations in trouble, whose managers tend to makeup stuff on the fly and with little regard for future consequences. Bullshittingand lying are not synonymous. While the liar knows the truth and wittingly bendsit to suit their purpose, the bullshitter simply does not care about the truth. Man-agers can actually do something about organizational bullshit, and this ExecutiveDigest provides a sequential framework that enables them to do so. They cancomprehend it, they can recognize it for what it is, they can act against it, and theycan take steps to prevent it from happening in the future. While it is unlikely thatany organization will ever be able to rid itself of bullshit entirely, this article arguesthat by taking these steps, astute managers can work toward stemming its flood

let's be honest, print-and-play is A LOT of work (printing, cutting, laminating, sleeving, etc) and it is not everyone's cup of tea.

If you ask my former students, they will tell you that as a teacher, my goal is to do nothing. I dream of the day when I can sit at my desk, feet propped up, reading a book, while the classroom bursts with activity and learning around me.

And yes, at TRB GmbH, we do pay people to work on OSS

It’s so simple that I sometimes wonder why it took years to develop it!

The LGPL allows users to use and integrate LGPL software components into their own software without being required to release the source code of their own software components. However, if users modify LGPL software components (“derivative work”), they are required to make the modified software component available under the same LGPL license. To avoid the latter with TRB, users have to comply with para. 5 LGPLv2.1: A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a “work that uses the Library”. Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. In other words: if you use the TRB libraries in your commercial applications or Open-Source projects, you’re not creating a derivative work of Trailblazer. Your software can be distributed under any terms.

Trailblazer (TRB) is an Open-Source project. Since we want to keep it that way, we decided to raise awareness for the “cost” of our work - providing new versions and features is incredibly time-consuming for us, but we love what we do.

This didn't work for me. Answering "y" somehow causes the script to finish immediately, rather than letting children continue sleeping. (Same thing if I make the signal handler function an empty no-op.) Does anyone know why it doesn't work for me or how to get it to work? It's as if the interrupt gets propagated to the child processes too so that it's no longer waiting for them.

A “warning” signal is sent first, then, after a timeout, a “kill” signal, similar to the way init(8) operates on shutdown.

if the process does not react on a normal kill, you may want to add an additional kill -9 a few seconds afterwards.

We can ask timeout to try to stop the program using SIGTERM, and to only send in SIGKILL if SIGTERM didn’t work. To do this, we use the -k (kill after) option. The -k option requires a time value as a parameter.

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

As schematically illustrated in Fig. 1D, the cross-linked polyimine functions are based on the dynamic covalent chemistry principle

Among all the exciting applications, wearable electronics represents one of the most important, as it is the most accessible to people, and can be integrated onto the surface of human body to provide many useful functions, including physical activity tracking

It can be applied in places that are not accessible by traditional rigid printed circuit boards

Stretchable/flexible electronics has attracted tremendous attention in the past two to three decades due to the combination of its superior mechanical attributes and electrical performance

Teaching is my passion

my transition to working on RailsCasts full time is the primary cause for me burning out.

Take 3, Previously attempted in 2012 (#8189) and 2015 (#19709). This new version uses ActiveModel Attributes API.

Bowline will bind up Ruby and HTML - letting you concentrate on the more interesting things

The office door is locked at 5pm. We work hard, but at 5 it's time to go home!

I will continue to use form objects and push changes into the repo when I feel they are universally relevant and valuable.

I apologize for the slow development of Reform after the "explosion" when I released it initially. The reason for this is I changed jobs and didn't use Reform (yet).

Action research also distinguishes itself from other research in that its purpose is to create change on an individual and community level. Kristin Esterberg puts it quite eloquently when she says, “At heart, all action researchers are concerned that research not simply contribute to knowledge but also lead to positive changes in people’s lives” (2002, p. 137).

when it comes to personal machines, I expect them to just work so I can work.

And honestly, most people prefer the no hassle, especially after wasting too much time dabbling with distros that are "for advanced users" troubleshooting all kinds of dumbass problems that just worked out of the box in many other distros.

I chose 18.04 because it's the latest LTS version, and I'm not keen on updating my OS every year or so. (I like getting things stable and not having to worry for a while)

SankeyMATIC builds on the open source tool D3.js and its Sankey library, which are very powerful but require a fair amount of work & expertise to use.

Its not too complicated but it is an annoyance. I want /etc/hosts, /etc/resolv.conf, /etc/nsswitch.conf, /etc/rc.local and all the standard stuff to work. The heavy lifting is done in the kernel. All they need to do is leave it alone. Its getting harder to make Ubuntu behave like Linux.

We also have an “anti-overtime” rate: past twenty hours a week, people can continue to work at an hourly rate of 50 percent. This allows us to have a high hourly rate for the highest leverage work and also allows people to work more per week if they wish.

Most users frankly don’t care how software is packaged. They don’t understand the difference between deb / rpm / flatpak / snap. They just want a button that installs Spotify so they can listen to their music.

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.

What’s the use of ie. snap libreoffice if it can’t access documents on a samba server in my workplace ? Should I really re-organize years of storage and work in my office for being able to use snap ? A too high price to pay, for the moment.

I - we all - totally agree about the benefits of snap for developers. But the loss of comfort and flexibility for end user is eventually a no-go option.

Users want work be done. Not struggling about how allowing access to removable medias or such a file on another partition… Not breaking their habits or workflows each time a snap replaces a deb.

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

People really don't stress enough the importance of enjoying what you're programming. It aids creativity, makes you a better teammate, and makes it significantly easier to enter a state of flow. It should be considered an important factor in choosing a web development framework (or lack thereof). Kudos!

May I ask what is holding this back?

Making UIs with Svelte is a pleasure. Svelte’s aesthetics feel like a warm cozy blanket on the stormy web. This impacts everything — features, documentation, syntax, semantics, performance, framework internals, npm install size, the welcoming and helpful community attitude, and its collegial open development and RFCs — it all oozes good taste. Its API is tight, powerful, and good looking — I’d point to actions and stores to support this praise, but really, the whole is what feels so good. The aesthetics of underlying technologies have a way of leaking into the end user experience.

And then it will help you choose a specialization in the field that you like.

Find Your Passion, Then Monetize It The

Try a little of everything, and then choose a specialization. Money is not the most important thing. You need to LOVE your activity! But you don't know what you like until you try it.

I personally think that starting from google's components makes easier to keeping update to material specs updates.

If you want a reference to the global object that works in any context, you can read this from a directly-called function. const global = (function() {return this})();. This evaluates to window in the browser, self in a service worker and global in nodejs.

I open this issue to announce that i'm actively working on a rewrite of this library to accomplish these goals:

Microbundle also outputs a modern bundle specially designed to work in all modern browsers. This bundle preserves most modern JS features when compiling your code, but ensures the result runs in 90% of web browsers without needing to be transpiled. Specifically, it uses preset-modules to target the set of browsers that support <script type="module"> - that allows syntax like async/await, tagged templates, arrow functions, destructured and rest parameters, etc. The result is generally smaller and faster to execute than the esm bundle

The use of __proto__ is controversial and discouraged. It was never originally included in the ECMAScript language spec, but modern browsers implemented it anyway. Only recently was the __proto__ property standardized by the ECMAScript 2015 specification for compatibility with web browsers, so it will be supported into the future.

Since I closed down the Dish, my bloggy website, five years ago, after 15 years of daily blogging, I have not missed the insane work hours that all but broke my health.

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

Throughput in Planned vs Unplanned Work: The graph to the left is even more interesting as it contains the initial hints at what’s actually happening. That graph measures throughput with an emphasize on unplanned work. Now, what’s unplanned work? Typically, everything related to features or improvements is planned, whereas bugs, re-work, and service interruptions are unplanned. Let’s see why unplanned work is relevant.

I've only done components that need to/can be Svelte-ified. For some things, like RTL and layout grid, you can just use the MDC packages.

This is Sass based, and therefore doesn't require Svelte components

There are a few intentional behavioral differences between Dart Sass and Ruby Sass. These are generally places where Ruby Sass has an undesired behavior, and it's substantially easier to implement the correct behavior than it would be to implement compatible behavior. These should all have tracking bugs against Ruby Sass to update the reference behavior.

In principle, this information is already available through other means, but it is actually a fair amount of work to gather it in this form, and I think it could be useful to open it up to programmatic consumption.

anything that makes you lighter helps create the balance which keeps you going.

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

Focus on your application: forget about forms details like I'm dirty, field touched...

You can try to build a solution to tackle these issues on your own, but it will cost you time and money... why not use a battle-tested solution to handle all this complexity?

If you want to implement a form with a superb User Experience, you have to take care of many variables:

Form validation can get complex (synchronous validations, asynchronous validations, record validations, field validations, internationalization, schemas definitions...). To cope with these challenges we will leverage this into Fonk and Fonk Final Form adaptor for a React Final Form seamless integration.

Managing Form State (holding field information, check if a control has been touched, if the user has clicked the submit button, who owns the current focus...) can be tedious and prone to errors. We can get help from React Final Form to handle these challenges for us.

This implementation is based upon following sources: JavaScript Debounce Function by David Walsh Lodash implementation

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

I'm okay with an overall design that allows people to plugin the parts they need in order to be able to generically support a compile-to-javascript language, but to bake in support for one singular solution because its popular is simply bad engineering.

This is the problem with baking in support for frameworks with special cases in the codebase. You can never support all the frameworks. :-(

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.