Americans deserve a campaign that tests the strengths and weaknesses of the candidates; that highlights their differences and allows scrutiny of their plans; that motivates people to vote by giving them a clear account of how their choice in this election will affect their lives.

We should also insist that every piece of technology is, by essence, political. That you cannot understand technology without understanding the people. And you cannot understand people without understanding politics. Every choice you made has an impact on the world.

Introducing relationships between issues will considerably increase the complexity of GitLab. That is not a reason not to do it. But it is a reason for us to be strategic in when we do it, and ensure we have a good design that is scalable and aligns with our other initiatives.

If you have studied the historical campaign, you may wonder if the same operational plan can be duplicated in the game—with the same results.  The answer is yes.  The unit capabilities and game mechanics allow for a repeat of history, but there is always the other player to consider.  As with history, the two sides have nearly the same number of infantry divisions, tanks, mobile units and artillery.  The German advantage is most evident in airpower—the Luftwaffe dramatically outclassed the Allied air forces in the campaign (and so it is with the game).  Only the German player who knows exactly how to employ their units with careful attention to the movement and combat sequences, event card use, the hidden unit dynamic, and especially the air rules—will be able to duplicate the historic success of the 1940 Wehrmacht.  And even then, the historic result was only possible because the Allied response played almost perfectly into Germany’s hand.  But there is more than one path to a decisive result, and the game allows for multiple campaign plans for both sides.  The rules are set up to mirror the operational, command, and doctrinal differences between the two opposing sides, but the contest is designed simply to re-create the same historic “canvas” upon which both players may then paint—the issue will be decided by a combination of player decisions and the fortunes and fog of war.

When building the Droplet Console, we had a few options to support SSH keys-based authentication. The most straightforward way would be to directly allow the customer to specify a private key that is already set up for accessing the Droplet. However, there are some problems with this solution:

You can no longer create accounts with Yahoo domains other than "@yahoo.com",

Auto-update aside, you might also have found it hard to find a Chrome binary with a specific version. Google intentionally doesn’t make versioned Chrome downloads available, since users shouldn’t have to care about version numbers—they should always get updated to the latest version as soon as possible. This is great for users, but painful for developers needing to reproduce a bug report in an older Chrome version.

This simple approach to avoiding bad decisions is an example of second-level thinking. Instead of going for the most immediate, obvious, comfortable decision, using your future regrets as a tool for thought is a way to ensure you consider the potential negative outcomes.

This visualisation technique can be used for small and big decisions alike. Thinking of eating that extra piece of cake? Walk yourself through the likely thoughts of your future self. Want to spend a large sum of money on a piece of tech you’re not sure yet how you will use? Think about how your future self will feel about the decision

Instead of letting your present self make the decision on their own, ignoring the experience of your future self who will need to deal with the consequences later, turn the one-way decision process into a conversation between your present and future self.

Nobody ever says rubber ducky debugging involves writing memos to your preferred duck, after all.

Can you refactor your code so that instead of returning from within the transaction block you set a variable and then return outside of the block?

An adviser should have their students explicitly practice decisions 25 and 26, test their solutions, and try to come up with the ways their decisions could fail, including alternative conclusions that are not the findings that they were hoping for. Thinking of such failure modes is something that even many experienced physicists are not very good at, but our research has shown that it can be readily learned with practice.

The third and probably most serious difficulty in making good reflective decisions is confirmation bias.

To be a successful physicist requires mastering how to make all 29 decisions, but the reflection decisions (decisions 23–26) are arguably the most difficult to learn.

We observed an overall increase in the amount of negative information as it passed along the chain—known as the social amplification of risk.

McConnell said it’s up to the Republican candidates in various Senate battleground races to explain how they view the hot-button issue.   (function () { try { var event = new CustomEvent( "nsDfpSlotRendered", { detail: { id: 'acm-ad-tag-mr2_ab-mr2_ab' } } ); window.dispatchEvent(event); } catch (err) {} })(); “I think every Republican senator running this year in these contested races has an answer as to how they feel about the issue and it may be different in different states. So I leave it up to our candidates who are quite capable of handling this issue to determine for them what their response is,” he said.

governance rather encompasses all localdecision-makers as well, as it is actually almost entirely within their own respective dominions ofcontrol where the overall success or failure is determined.

For example, in respect to the goal of reducing the global emissions of carbon dioxide, the relevantsystem of governance is not limited to those who conclude that there is a global risk, those whoaccept or reject the conclusion, those who formulate objectives, those who choose to adhere to or toignore them, who conceive of regulations, who choose to implement them or not, who determineprogress, decline or failures, those who select means by which to influence the desired local industrialinvestment, or consumption choices and so on.

5.11 Convert your principles into algorithms and have the computer make decisions alongside you.

5.6 Make your decisions as expected value calculations.

5 Learn How to Make Decisions Effectively

No draft decision in the modern history of the court has been disclosed publicly while a case was still pending.

There is something nice about aligning with the platform. But it risks being a straitjacket, and I think we can provide better ergonomics when it comes to streaming.

Students should be directly involved in campus conversations and decision-making about social reading technologies.

In Rails, this is known as nested layouts, and it is a bit awkward to use. The standard Rails practice for nested layouts is complicated and involves these considerations:

In 1994, The Unix-Haters Handbook was published containing a long list of missives about the software—everything from overly-cryptic command names that were optimized for Teletype machines, to irreversible file deletion, to unintuitive programs with far too many options. Over twenty years later, an overwhelming majority of these complaints are still valid even across the dozens of modern derivatives. Unix had become so widely used that changing its behavior would have challenging implications. For better

How can we help your business? See how we help you address today’s digital challenges with real-world enterprise use cases.

Find and build extensions in the Adobe Exchange. Adobe Experience Cloud now includes integrations from partners like Acxiom, AppDynamics, Dun & Bradstreet, Facebook, Mastercard, and Microsoft — all available in the Adobe Exchange. The AppDynamics integration, for example, helps marketers see when and why a customer is having a poor experience and automatically triggers an event like a personalized offer. And Mastercard’s integration combines behavioral data with analytics data to help marketers build smarter profiles to reach more likely buyers. And our integration with Microsoft includes joint solutions that integrate Adobe Experience Cloud with Microsoft Azure, Microsoft Dynamics 365, and Power BI. Find these integrations and hundreds of others in the Adobe Exchange.

Calling a software convention "pretty 90s" somewhat undermines your position. Quite a lot of well-designed software components are older than that. If something is problematic, it would be more useful to argue its faults. When someone cites age to justify change, I usually find that they're inexperienced and don't fully understand the issues or how their proposed change would impact other people.

If you dig into the details, you will see that the TypeScript team take breaking changes very seriously and with consideration.

There are many projects that does not use the master branch as default. For example, Next.js uses the canary branch, the npm CLI and many more other projects uses stuff like prod, production, dev, develop, release, beta, head.

He was just ruthlessly decisive, always willing to make the hard call.

I've been thinking more about how to best do this. The preferred way might be to use the same domain and have an application load balancer like nginx split traffic on the URL path (e.g. /api). This is for two reasons. Firstly, you might not necessarily want to cookie the primary/apex domain and have the cookie shared across all subdomains. You also might not want to do CORS because preflight requests add latency and CORS adds complication.

Prettier intentionally doesn’t support any kind of global configuration. This is to make sure that when a project is copied to another computer, Prettier’s behavior stays the same. Otherwise, Prettier wouldn’t be able to guarantee that everybody in a team gets the same consistent results.

I don't believe the sprockets and sprockets-rails maintainers (actually it's up to the Rails maintainers, see rails/rails#28430) currently consider it broken. (I am not a committer/maintainer on any of those projects). So there is no point in "waiting for someone else to fix" it; that is not going to happen (unless you can change their minds). You just need to figure out the right way to use sprockets 4 with rails as it is.

Too new to comment on the specific answer

“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!).

Carcassonne just gets on my nerves because I just don't view selecting between so many placement options to be that interesting.

Few real decisions to make....Not in my experience, either in tile placement or in disk placement. Of possible interest is the thread:Informal experiment: how easy to find "the optimal disk placement" in various positions?wherein we see that even in the second phase, which people often complain is "automatic" or "obvious", the decisions are not necessarily obvious.

Incidentally, I like both these games more than Fjords because they offer up a wealth of decisions on each turn even if you have drawn an unlucky hand of cards.

Luck is a major factor. As discussed above, sometimes the map seems to build itself and you draw tiles which you HAVE to place even though they are aiding your opponent.

Otherwise, it plays out fairly predictably and very quickly. This is a shame because this is the point that it starts to feel like a real contest.

Sometimes it feels like the map builds itself - there is often only one viable placement, so it starts to feel like a jigsaw, searching for that available position. Surely placing a single tile shouldn't be this difficult!

This is a Rails change of behaviour and Rails is not going back.

But so far everything brought up has just been about the relative advantages of checked exceptions, and that issue is closed. We won't do it.

provide interfaces so you don’t have to think about them

A second trap is thinking that you just need to work on yourself in order to grow your career. For example, "To progress, I just need to get better at [insert skill.]" But you are only one part of the equation.There is a whole other part of the equation, which is your environment. Your environment either limits or amplifies your own ability to get better at a skill.

Evaluating impact isn't easy. It is complicated by a few factors:Impact is the result of multiple other variables.Those variables are interrelated and have confounding factors.Impact can be subjective to the individual.A lot of times you aren't even aware of what is holding you back, or what to evaluate on.

"Should I leave my current role?""How do I compare or choose between two or more opportunities?""What is preventing me from moving forward?"

If you don't understand both sides of an issue, you cannot make an intelligent choice; in fact, if you don't understand all the ramifications of your actions, you're not designing at all. You're stumbling in the dark.

Consequently, you act irresponsibly when you adopt any programming practice simply because "that's the way you're supposed to do things."

My point is that you should not program blindly. You must understand the havoc a feature or idiom can wreak. In doing so, you're in a much better position to decide whether you should use that feature or idiom. Your choices should be both informed and pragmatic.

With the introduction of CPUs which ran faster than the original 4.77 MHz Intel 8088 used in the IBM Personal Computer, programs which relied on the CPU's frequency for timing were executing faster than intended. Games in particular were often rendered unplayable. To provide some compatibility, the "turbo" button was added. Engaging turbo mode slows the system down to a state compatible with original 8086/8088 chips.

It makes me happy to see people actually think about things and not just accept a shitty API.

Trust me, I thought a lot about #validate and its semantics, and I am gonna make it even more "SRP" by making Form#errors and #valid? semi-public. All that happens via #validate reducing the possible wrong usage for users.

I use <b>s for the decorative portions of the layout because they’re purely decorative elements. There’s no content to strongly emphasize or to boldface, and semantically a <b> isn’t any better or worse than a <span>. It’s just a hook on which to hang some visual effects. And it’s shorter, so it minimizes page bloat (not that a few characters will make all that much of a difference). More to the point, the <b>’s complete lack of semantic meaning instantly flags it in the markup as being intentionally non-semantic. It is, in that meta sense, self-documenting.

2021

Your people and your workplace are your greatest assets and they are underutilized. Steelcase research shows us that on average: only 54% of office space is used throughout the day over 37% of employees are not engaged at work We equip organizations with the tools to measure the places where people work on a continuous, periodic, or trial basis.

Think first: why do you want to use it in the browser? Remember, servers must never trust browsers. You can't sanitize HTML for saving on the server anywhere else but on the server.

In my opinion, it can sometimes look odd. Very interestingly, this is by design and is part of the Material design specification. This article isn’t to argue whether it should be this way or not, though; it’s just to change yours such that your MenuItem(s) show below the menu selection, like so:

Give the user as much information as you can to help inform them on what’s about to happen. Anticipating and answering the following questions can help

But this post is in part a plea to consider what you’re invoking visually and the expectations surrounding it.

Now they have what they need to make an informed decision, with a little intentional ambiguity to temper expectations.

Some of these are absent-by-design

Like most frameworks that abstract the DOM, Svelte has incompatibilities like the inability to name a prop class because it’s a reserved keyword in JS, and you’ll use on:click not onclick, but these quirks are few in number and reflect carefully chosen tradeoffs. Svelte does its best to harmonize with the web platform, welcoming both experienced developers and newcomers with whatever web knowledge they have.

It is intentionally very minimal

Secondary buttons are the alternative we give users to the primary action.

I think a casual look at the game could be quick to take fault that some moves are scripted, and perhaps they are.  If play passes to you and there is a stock to be had for free…why _not_ take it? For me, it’s a distraction. The player before you likely considered the options and found the game state to be worth tempting you with that. Those free, or even cheap, stocks won’t gain you the influence in any companies that can make your personal cache more valuable.

Ultimately, I’m an “are there tough decisions?” kind of gamer, and on that matter I’m torn. There are some turns and some positions and some situations that will play themselves. Sometimes obviously so, and sometimes after you think it out.

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.

To ensure there is enough space for both content and navigation, Reply uses different navigation patterns for desktop, tablet, and mobile.

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.

Doing a HOC properly, as a library should, with hoisted statics and displayName and ref, etc., is a hassle and would add unnecessary bulk.

Adding checks for bracket[3] syntax as opposed to dot.3 syntax adds a lot of complexity, and has consciously been avoided.

Typically, platform accessibility APIs do not provide a vehicle to notify assistive technologies of a role value change, and consequently, assistive technologies may not update their cache with the new role attribute value.

// Use `noConflict` to restore the pre-fp variant. var fp = _.noConflict();

While react hooks were one of the catalysts for v3 we don't agree with with the APIs or the model and won't be emulating it.

The misspelling of referrer originated in the original proposal by computer scientist Phillip Hallam-Baker to incorporate the field into the HTTP specification.[4] The misspelling was set in stone by the time of its incorporation into the Request for Comments standards document RFC 1945; document co-author Roy Fielding has remarked that neither "referrer" nor the misspelling "referer" were recognized by the standard Unix spell checker of the period.

Determining this exact byte position within one massive mdat in each respective file is not trivial.

The Moov atom can only exist after recording is complete when the relevant metadata can now be created for the stored data.

Modules using code that doesn’t exist in browsers such as process.env.NODE_ENV and forcing you to convert or polyfill it.

TBH It is a bit disheartening to see this issue closed when all proposed solutions do not sufficiently solve the issue at hand, I really like svelte but if this is how feature requests are handled I am probably not going to use it in the future.

There are tools in Svelte that break this expectation to a degree, but they are a bit annoying to use, which makes it an active decision on the part of the developer. The API hints at the way we want you to do things because we feel that this will give the better experience.

I think that we should be willing (taking the risk) to make bold changes, as long as they fit in the direction we see the community going in the long term (with Material-UI empowering it).

Force everything to the git root per NPM lameness

For a non-monorepo package you can simply point directly to the Github repo. This case is similar, but you want to scope it just to a single package within the repo. For those that make monorepos they don't necessarily need this feature. It's for those that use projects that use monorepos. Telling them to not organize their projects into monorepos doesn't help people who make use of these projects.

npm's inability to handle monorepos then i'd have designed my repos accordingly

Amazon pushes teams to escalate one-way door decisions – those that can’t be reversed and may have long-term consequences.  However, with “two-way” decisions, managers are coached to make these decisions themselves.

This impacts monetization and purchasing at companies. Paying for a new design tool because it has new features for designers may not be a top priority. But if product managers, engineers, or even the CEO herself think it matters for the business as a whole—that has much higher priority and pricing leverage.

I could add .json on the end, but that would mean hacking away at angularjs, which is doing the right thing. I would rather find a good solution and hack away at rails, which is doing the wrong thing :)

In that case I would suggest to use .xml or .json format to eliminate accept header parsing issue.

Safari sends following order application/xml (q is 1) application/xhtml+xml (q is 1) image/png (q is 1) text/html (q is 0.9) text/plain (q is 0.8) \*/\* (q is 0.5) So you visit www.myappp.com in safari and if the app supports .xml then Rails should render .xml file. This is not what user wants to see. User wants to see .html page not .xml page.

Oracle didn’t seem very interested in OpenOffice.org, and the community of volunteers developing it formed The Document Foundation back in 2010. They called on Oracle to participate and donate the OpenOffice.org name and brand to the community. Oracle never did, and the resulting forked office suite has been named LibreOffice since then.

In 2011, Oracle laid off OpenOffice’s paid developers and donated the OpenOffice software to the Apache Foundation, rather than The Document Foundation. It’s remained there since, a project in slow but steady decline.

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.

JSON parsing is always pain in ass. If the input is not as expected it throws an error and crashes what you are doing. You can use the following tiny function to safely parse your input. It always turns an object even if the input is not valid or is already an object which is better for most cases.

I been using turbo tax for like 5 years now.. Every year the predatory UI gets worse and worse. It constantly badgers you for more service for simple returns, it locks you in to benefits when you are just trying to see if one tax stance is better than another, IT NEVER LETS you go back and undo any PRODUCTS unless you want to delete your whole return. I think part of my frustration is the terrible tax laws we have in this country but for petes sake if you cant let me add up itemized deductions and compare them to a standard deduction WITHOUT locking into a product, you honestly have a terrible product. Just be honest with your pricing instead of trying to trick people into these products and HOLDING THEIR HOURS OF CLERICAL WORK HOSTAGE. WHAT A JOKE.

Are you angry now? Because I’m angry.

Buridan's ass is an illustration of a paradox in philosophy in the conception of free will.

and eventually waste away and die never having taken either path.

However, a ActiveRecord::Rollback within the nested transaction will be caught by the block of the nested transaction, but will be ignored by the outer transaction, and not cause a roll back! To avoid this unexpected behaviour, you have to explicitly tell rails for each transaction to indeed use proper nesting: CopyActiveRecord::Base.transaction(joinable: false, requires_new: true) do # inner code end This is a safer default for working with custom transactions.

The words that you have not spoken; you are their owner. The words you have spoken, they own you.

The data that organizations and individuals have committed to digital memory stands to ultimately control them.

Remember that tech decisions are political decisions

by practicing data minimalism and actively considering your data decisions

I dismissed the idea, though, because I thought that cloning even part of a repository with git-svn required scanning every commit in the entire repository, in order to build the local history. With almost 1.5 million commits in the plugin repository, that would take roughly 4 hours to clone a plugin.

Many of them have made poor password choices stretching all the way back to registration, an event that potentially occurred many years ago.

Ruby's current handling of Dates and Times is all over the map. We have Date, Time, DateTime, ParseDate, and more, not to mention all the other common extensions running around out there. Ruby needs an improved class that incorporates them all.

referrer (note spelling)

Make two-way door decisions Most decisions are easy to reverse, have the directly responsible individual make them without approval. As Jeff Bezos describes only when you can't reverse them should there be a more thorough discussion.