I’d go as far as saying that you should not expect any traction until you have put out (published, shipped) at least three hundred great pieces of work.

It is this level of quantity that leads to:

Refinement and mastery of your skills;
Being faster, more efficient and better at flow;
A growing sense of momentum and energy;
Getting a better sense of what people WANT;
More ‘nodes’ through which to attract attention online and elsewhere;
More ideas and more ‘aha’ moments that lead to more electric, more emotional output;
Others believing in you because you believe in yourself, by showing up often or every day.

Interested in writing an article for Perl.com? Perhaps you want to get the word out about your new startup, provide a tutorial on your favorite module, or have community news to share. This document is for you.

The following will be a short explanation, along with some solutions, of a popular JavaScript question that tends to get asked in developer interviews.

This question deals with the topics: closures, setTimeout, and scoping.

As some of the finest fictional world-builders have understood, few things excite the imagination like a map. And despite the geographical limitation implied by its title, National Geographic’s maps have surveyed the entire globe and beyond. The magazine’s articles have not always presented an enlightened point of view, but for all its historical failings, the richly-illustrated monthly has excelled as a showcase for cartography, over which readers might spend hours, projecting themselves into unknown lands, journeying through the carefully-drawn topographies, cityscapes, and celestial charts.

The pistol squat takes balance, flexibility, mobility, and strength. It even helps with vertical explosivity when combined with jumping exercises. Also, quite importantly, it helps even out the imbalances between your legs. People typically have one leg that is stronger than the other and/or one leg that is more flexible than the other—the pistol squat helps to address this imbalance.

This your chance to make a lasting impression on your interviewer. Don’t squander it by not having a thoughtful question or two. It’s an opportunity to show your prospective employer that you can see a bigger picture beyond scribbled code on a whiteboard. That you care about the humans at the opposite end of the tech stack.

It’s also a chance to learn something about how your prospective employer operates. Maybe there’s some pain point you can help address, or a process gap you can help fill. Maybe you’ll see some patterns that indicate how happy or miserable you’ll be if you accept an offer.

• What’s your worst day like? How do you manage it?
• If you could change one thing about your tech stack, what would it be? What’s blocking you from implementing this change?

Essential reading: the “Shitty First Drafts” chapter of Anne Lamott’s Bird By Bird:

Almost all good writing begins with terrible first efforts. You need to start somewhere. Start by getting something — anything — down on paper. A friend of mine says that the first draft is the down draft — you just get it down. The second draft is the up draft — you fix it up.