Workaday Readings are the droll, dry, and dear pages I continuously tick through during my day.

This is shop talk, not for general consumption! (lest you want to fall asleep 😉 )

Workaday Reading

The Wrong Abstraction — Sandi Metz



"I originally wrote the following for my Chainline Newsletter, but I continue to get tweets about this idea, so I'm re-publishing the article here on my blog. This version has been lightly edited. I've been thinking about the consequences of the "wrong abstraction."

read »

Workaday Reading

Understanding the Hidden Powers of curl



"curl is exceedingly powerful – unfortunately, much of this power is somewhat hidden in the purposeful non-verbosity and the underlying complexity of its numerous flags, configurations, and options. Once understood, curl boasts a wide range of powerful options."

read »

Workaday Reading

htop explained

"For the longest time I did not know what everything meant in htop. I thought that load average 1.0 on my two core machine means that the CPU usage is at 50%. That's not quite right. And also, why does it say 1.0? I decided to look everything up and document it here."
read »

Workaday Reading

Awesome Design Tools



"The best design tools for everything. Curated by Lisa Dziuba & Valia Havruliyk from Flawless team. Accessibility is the practice of creating websites and apps usable for all people, including individuals with visual, motor, auditory, speech, or cognitive disabilities."

read »

Workaday Reading

Events API



"This event does not require a specific OAuth scope or subscription. You'll automatically receive it whenever configuring an request URL. The attributes Slack sends include: Careful, response URLs are case sensitive."

read »

Workaday Reading

Google Maps API links



"Using the Google Maps API v3 Links to examples of various useful things and documentation Using the Google Maps API V2 Links to examples of various useful things and documentation"

read »

Workaday Reading

"Most serious software development projects use coding guidelines. These guidelines are meant to state what the ground rules are for the software to be written: how it should be structured and which language features should and should not be used. Curiously, there is little consensus on what a good coding standard is. Among the many that have been written there are remarkable few patterns to discern, except that each new document tends to be longer than the one before it."
read »
1 17 18 19 20 21 31