Give your portraits a professional, polished glow in just a few minutes

The pitas you make at home are worlds apart from the stuff you buy in stores, and watching them puff to glorious heights in your oven or on your stovetop is culinary magic at its best. Here’s how we do it.

SVG to EMF Converter - CloudConvert is a free & fast online file conversion service.

https://graphicdesign.stackexchange.com/questions/60996/illustrator-emf-export-loses-precision

Looking for an easy DIY project? You won't believe these before-and-after spray paint photos!

A skeleton boilerplate built with Eleventy. Contribute to josephdyer/skeleventy development by creating an account on GitHub.

Why they don’t read it

I’m a bit of a perfectionist. Several years ago, I believed the best documentation should be nicely formatted, concise, well-illustrated, and written in clear language — and this is not wrong. But all these features make little sense if the documentation isn’t regularly used by those for whom it has been created.

If the team doesn’t react to anything you publish, I have bad news: this documentation (specs, reports, guidelines, etc.) might be already “dead.” Here are several typical scenarios of what may have gone wrong:

1. “Approved and forgotten” — design guidelines were created without team involvement and then approved by stakeholders. After the official presentation, someone checked them out, while others didn’t. Since the guidelines were comprehensive, they looked like a huge reading that would take a lot of time.

2. “A perfect monolog” — amazing design knowledge base inspired lots of team ideas and questions, but commenting was either absent in the tool or disabled. As a result, the discussion occurred elsewhere, in Slack or MS Teams, and soon this chat became a more valuable “source of truth” than the knowledge base itself.

3. “Lone warrior” — design system documentation was detailed and well-structured but didn’t include any links to what other team members (engineers, QAs, UX researchers, etc.) were doing. As a result, it remained just the designers’ resource, and designers had to answer the same repeated questions in the chat or team meetings.

Documentation is a digital product no less than the actual product you are designing and being paid for.

Earlier this year, I pushed out a tweet about my desire to be a beginner again, learn something new and took a particular interest in…

All the tips you need to prevent running injuries, including form tips, strength and mobility moves, and more.

Task Write a program that prints the integers from 1 to 100 (inclusive). But: for multiples of three, print Fizz (instead of the number)...

From its start, Perl comes with most (Unix) core operating system trickery like forks, events and signals. So, you can implement real performing daemons for interesting tasks.

We will get into various features which show how straight-forward it is to implement an Apache-like webserver, with VirtualHosts, proxies, etc.

But we start by discussing many options how to set-up servers: processes, event-loops, and so on... before we reach to HTTP-servers processing requests.

Any::Daemon

• Use Apache as your front end ~30:00

Example based guide for text processing with perl from the command line - GitHub - learnbyexample/learn_perl_oneliners: Example based guide for text processing with perl from the command line

Mojo one-liners are just Perl one-liners. You will use -E (or -e) to write the program. You might use -n to loop over input, or -p to do the same while printing $_ after each item, just like normal one-liners.

To get the extra Mojo goodness, add -Mojo. The name itself is a cute hack. Since -M is what loads a module on the command line, the module name is therefore ojo.

Command-line interactive multitool for tabular data.

VisiData is an interactive multitool for tabular data. It combines the clarity of a spreadsheet, the efficiency of the terminal, and the power of Python, into a lightweight utility which can handle millions of rows with ease.

Dieter Rams, Vitsœ's furniture designer. Ten principles for good design (sometimes referred to as the ‘Ten commandments’).

Iconduck lists 302,680 free open source icons, illustrations, emojis and graphics. They can be used for personal and commercial projects.

Enter fzf.vim by the legendary Junegunn, which is a wrapper for the command line fuzzy finder with the same name, fzf. On the surface it seems like a just another fuzzy finder, but it's much more than that! Let me show you some of my mappings and how I have been using it...

BTW, if you had similar end points that supported batch requests (i.e. lists of ids or lists of emails), that would help significantly for my use cases (though still not be as ideal as a performant list endpoint with basic querying).

GET /api/v2/users/{user-id} and GET /api/v2/users-by-email offer immediate consistency in their results.

A UI design case study to redesign an example user interface using logical rules or guidelines

Use space to group related elements
Be consistent
Ensure similar looking elements function similarly
Create a clear visual hierarchy
Remove unnecessary styles
Use colour purposefully
Ensure interface elements have a 3:1 contrast ratio
Ensure text has a 4.5:1 contrast ratio
Don’t rely on colour alone as an indicator
Use a single sans serif typeface
Use a typeface with taller lower case letters
Limit the use of uppercase
Use regular and bold font weights only
Avoid pure black text
Left align text
Use at least 1.5 line height for body text

Illustration placeholders for developers. Powered by Blush