Always With Honor is a graphic design and illustration studio in Portland, Oregon

https://veerle.duoh.com/inspiration/animal-aid

Emulate the sound of Roland's most famous and influential musical instruments from Yuri Suzuki and Roland.

Simple CSS Spinners

2nd selection

See issues for defaults to work in IE11

You should write your own debugger!

~25:00

https://speakerdeck.com/rjbs/1-dot-21-gigawatts?slide=174

This bright, jewel-toned condiment offers a zesty tang to countless dishes and adds a lovely splash of color as well. It takes about 10 minutes to assemble and lasts for weeks in the refrigerator.

1 medium red onion, about 5 ounces
1/2 teaspoon sugar
1/2 teaspoon salt
3/4 cup rice vinegar, white vinegar, or apple cider vinegar

• In the container you will be using to store the onions, add the sugar, salt, vinegar, and flavorings. Stir to dissolve.
• Boil 2 or 3 cups of water in a kettle. Par-blanch the onions: Place the onions in the sieve and place the sieve in the sink. Slowly pour the boiling water over the onions and let them drain.

During the pandemic, I didn’t do a ton of actual writing. I barely blogged. I don’t think I did more than 1 or 2 publication, popular or academic. Even worse, I didn’t do a ton of actual reading. At first, I thought it was the pandemic itself. This is stressful stuff, my work life had been through into complete chaos, and my daily living routine was in tatters.

Over the past year or so, however, I slowly realized it was something bigger: I was having trouble concentrating, especially for the 3 or 4 hour blocks of time it took to write well. Or to blow through a book. Or to really study bridge defense. At first I thought I was just getting old. Doesn’t this happen to everyone when they hit their mid-40s? But the more I examined it, the more I started to believe it was a function of how I was consuming information. I was massively multi-tasking, almost full-time. And the two biggest culprits were my email inbox and my twitter feed.

Workers now inherently multitask, because they build their work world around their inbox, which is constantly delivering them different streams of work.

Give tired plants a wake-up call with a little leftover coffee

Thus, I began pouring coffee for my fig tree a couple of times a week. I made sure the liquid was room-temperature to avoid burning the roots. And because coffee is quite acidic, I diluted it half-and-half with tap water. My tap water is hard (alkaline - pH over 7), so the mixture's pH should be about neutral.

OH no Type Co. Retail and custom typefaces. Life’s a thrill, fonts are chill!

95% of all debugging is print statements, but once or twice a year, a problem shows up that is best attached with perl5db.pl, the venerable core Perl 5 debugger. Like a light saber, it dates back to a forgotten time and its operations are poorly understood. Unlike a light saber, it is not elegant, and nobody aspires to use it. Also, it can cut limbs right off. Still, it’s a very useful multi-purpose tool, and if you learn how to use it, it can save a lot of time and clear up a lot of mysteries.

This talk will cover what the debugger is, how to use it at a basic and intermediate level, how to customize it, and at least one or two stories about how it is very, very awful.

If you don't need any templating languages and just need to get a simple site built plus Sass, use this as the contents of a fresh package.json:

npm start - copies src files to public and starts Browsersync server at localhost:3000
npm run build - copies files to public and autoprefixes/minifies css

One of the more difficult problems with writing systems that communicate over the network is managing input and output—that is, the reading and writing of data to and from the network and hard drive. Moving data around takes time, and scheduling it cleverly can make a big difference in how quickly a system responds to the user or to network requests.

In such programs, asynchronous programming is often helpful. It allows the program to send and receive data from and to multiple devices at the same time without complicated thread management and synchronization.

Git has a reputation for being confusing. Users stumble over terminology and phrasing that misguides their expectations. This is most apparent in commands that “rewrite history” such as git cherry-pick or git rebase. In my experience, the root cause of this confusion is an interpretation of commits as diffs that can be shuffled around. However, commits are snapshots, not diffs! I believe that Git […]

https://www.malikafavre.com/

aspect-ratio is a great example of a humble property that fills a long-awaited need in the CSS community. It’s simple to use and behaves in a way that respects content, without the need for any extra CSS.

1. Get comfortable with 11ty’s configuration
2. Set a source folder and an output folder
3. Configure markdown for Nunjucks syntax
4. Supercharge markdown with containers and classes
5. Embrace the Data Cascade
6. Async shortcodes are for dynamic data fetching
7. Use Eleventy Navigation

Solution 5 - Path::Tiny
The solution that I currently like the best, involves the use of the Path::Tiny module

use Path::Tiny qw(path);
use lib path($0)->absolute->parent(2)->child('lib')->stringify;

A talk by Bryan Robinson during 11ties: a series of 11 min lightning talks on 11ty, recorded on 11/11, 2020 -- for Jamstack TORONTO.

Give criticism without hurting people's feelings while opening the relationship for constructive collaboration.

He was taught criticism had to tick two simple boxes. It had to be constructive, and it had to be criticism of an action or thing instead of a person.

But no one ever bothered to teach us how to criticize constructively— without making humans miserable. At least nobody ever taught me the secret.

What I didn’t get at the time was that my advice was not nearly as valuable to the receivers as I estimated in my mind.

My advice was totally unsolicited.

Radical Candor by Kim Scott — a book every “boss” should read.

After reading The Coaching Habit, I realized that the best criticism is criticism that doesn’t have to come out of your mouth, but ideally from the receiver of the criticism’s mouth.

• “What” questions drive exploration.
• “How” questions drive action.
• “Why” questions drive justification.
• “When” questions drive accountability.

Step 1: Set the stage, tone, and rules

While we dive deeper into ____, I may also say some stupid things that might make you feel like this bizarre person doesn’t know what the heck they’re talking about. I’d like to openly invite you to poke holes in my ideas whenever you can.
I’d love for this to be a space where we can collaboratively challenge each other’s thinking so that we can both leave this conversation with sharper thoughts.

Step 2: Ask curious “what” questions

Step 3: Ask “what else” questions

Step 4: Ask “how” questions

That’s excellent! How would you go about improving ____?

Step 5: Ask the first step question

That’s excellent! What would be the first tiny step to improve on ____?

6. Ask the “when”

It would surprise most people to know that my bologna-loving self is really good at making delicious salads. Even self-proclaimed salad haters have been wooed by my artfully arranged piles of leaves and stuff. As one might expect, I have many strategies, tips, and tricks for making special-tasting salads, and I would…

• don’t be afraid to get a little monosodium glutamate or nutritional yeast involved
• Use way less oil in your vinaigrettes
• A little bit of sugar (honey, maple) is all it takes make your dressings feel more finished.
• add a little vanilla

In part II on your engineering superpower (technical writing), Sophie DeBenedetto talks about how to write well.

Blogging

Try these strategies to help you get started:

• Write an outline first.
• Start with a detailed introduction.
• Write the conclusion first.

If you use the conclusion first approach, focus on what the reader should walk away from your post having learned.

Pull Requests

A good PR description has a few elements:

• A descriptive title.
• An explanation of the what, why, and how.
  • ____ What problem does the code solve?
  • ____ Why is this solution needed?
  • ____ How does the code solve the problem?
• Extras: Anything from usage instructions to info on testing/QA.

How to Write a Ticket

• What problem needs to be solved and why?
• What value does the project gain by delivering this work?

How To Ask For Help

• What is the current behavior? Describe the bug that is occurring.
• Under what circumstances does the behavior occur?
• How does the behavior differ from the expected behavior?