Protect Yourself/Protect Others

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.

Better yet, send them a link to this page to help them understand why and how to make an example app:

In the classroom, I delegate responsibilities to my students at a rate that astounds people. There is almost nothing that I will not allow my students to do, including teaching my lessons whenever possible. My students take full and complete ownership of the classroom, whether they like it or not, and as a result, they possess great ownership of their learning.

They fail to understand the importance of autonomy when delegating responsibilities.

They lack faith in the capacity of others.

I learned to “let go” and simply trust others to maintain certain gem suites.

I do think it's a common pattern that should be solved, and I am probably going to try and solve it as a Gem as opposed to simply writing code that we use in our code base

cultural capital

Systemd problems might not have mattered that much, except that GNOME has a similar attitude; they only care for a small subset of the Linux desktop users, and they have historically abandoned some ways of interacting the Desktop in the interest of supporting touchscreen devices and to try to attract less technically sophisticated users. If you don't fall in the demographic of what GNOME supports, you're sadly out of luck.

I wanted to use GitHub Gists which are a wonderfully low friction way of sharing code

You should default to the most permissive option imo and there really is no reason to check anything until you really need to If it were left to me I'd just use optional chaining, as it also eliminates the need for no-ops

In other words, programs that send messages to other machines (or to other programs on the same machine) should conform completely to the specifications, but programs that receive messages should accept non-conformant input as long as the meaning is clear.

be conservative in what you do, be liberal in what you accept from others

The benefits for developers do reflect on benefits for users, with more software delivered faster and more securely.

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.

I clearly understand why snap is a safety progress on server and IoT but in my « human » usage snap is just restricting how I use my data and computer.

Treating the web as a compile target has a lot of implications, many negative. For example “view source” is a beloved feature of the web that’s an important part of its history and especially useful for learning, but Svelte’s compiled output is much harder to follow than its source. Source maps, which Svelte uses to map its web language outputs back to its source language, have limitations.

Better community building: At the moment, MDN content edits are published instantly, and then reverted if they are not suitable. This is really bad for community relations. With a PR model, we can review edits and provide feedback, actually having conversations with contributors, building relationships with them, and helping them learn.

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

When you email me, please include a minimal bash script that demonstrates the problem in the body of the email (not as an attachment). Also very clearly state what the desired output or effect should be, and what error or failure you are getting instead. You are much more likely to get a response if your script isn't some giant monster with obtuse identifiers that I would have to spend all afternoon parsing.

I realise this is old, but as it isn’t a forum i see no problem in replying

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

Library author here. I'm always fascinated by new ways people can invalidate my assumptions. I mean that in a sincerely positive way, as it results in learning.

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.

I know where you're coming from, and to a degree, I think you're right.

And as an aside, I’m definitely in favor of more debates than sessions in future conferences, since we actually learn more by hearing multiple viewpoints.

I'm suggesting there should be a way to write lifecycle related code that also responds to changing props, like how useEffect works. I think how React handles this could be a good source of inspiration.

If Svelte came up with some kind of hooks like API maybe it could solve both these issues at once.

I think Svelte has some things to learn from React hooks.

I started Solid years ago before I thought anyone would be interested in using it. I only started promoting it because it had already achieved the goals I had set out for it.

I'll work on a preliminary PR (which I expect will need some love from maintainers, sorry!)

If you are a senior, try talking to a junior or someone less experienced than you. Many companies are running what is called ”reverse mentoring” programs where juniors coach senior members of a company. Senior’s experience is traded for a fresh perspective from a junior. You’d be amazed at how much you could learn and share.

But it's easy to imagine that the caption was incorrect for too long because those who know the language, know where the mistake is, and those who don't, think that it's the correct way to spell it.

Can't upvote this enough. It is highly irritating to see language destroyed (and we wonder why kids bastardize the language..).

Don’t go to code academy, go to design academy. Be advocates of the user & consumer. It’s not about learning how to code, it’s about translating real-world needs to technological specifications in just ways that give end users agency and equity in design, development and delivery. Be a champion of user-centric design. Learn how to steward data and offer your help.

To understand and be understood, those are among life’s greatest gifts, and every interaction is an opportunity to exchange them.

Studying the masters will help you understand how all copywriting elements fit together.

Don’t worry, I’m not judging you, at least as far as you know.

there's no reasonable way to communicate effectively with the less technically minded without acquiescing to the nontechnical misuse of the term "hacker"

The more easily relabeled of the two uses of the term "hacker" is the malicious security cracker: it is not only the more recent phenomenon to acquire that label, but also the one whose meaning is most easily evoked by an alternative term. This is why, when you read an article of mine that talks about malicious security crackers, I use the term "malicious security cracker"

Get phrasebooks to start studying basic terminology. Phrasebooks are lists of expressions made for travelers to foreign countries. These lists give you an example of the sentence structure a language uses and what kind of words are useful. Find a phrasebook in the language you wish to learn and treat it as a foundation you can build upon as you learn more.

I’m often neglecting half of my projects in order to obtain progress by leaps and bounds in just a few

Before each election, I have traditionally written up an analysis of the California ballot measures and send it to my friends. It's not always obvious what the "real" agenda is on each one, and even with clear purposes there are often competing interests at play. These writings are the result of my own analysis, which comes from a libertarian perspective, and I'm not knowingly affiliated with any party behind any ballot measure. I believe that mere lists of "vote yes" or "vote no" are not very helpful except for sheep: it's important to know why one is urged to vote in any given direction. I would rather you vote against my position because you had an opposing view than vote with my position because you flipped a coin.

This issue is already known to us since yesterday. Our engineers are now working diligently to fix this behavior. I'd recommend you contact our Customer Care team and let them know that you're one of the affected users of INV36818. That way, they will link your company to the case. You will then receive a notification via email for its updates. 

life as the reigning queen of Rupaul's Drag Race

CORRESPONDENCE

have to start searching that person's history until we begin to understand what led him or her to speak just so. Sometimes we do less well: if the history isn't there for us, we don't learn it, but instead make it up to suit ourselves.