in stasis pending unPAUSE @beadsland@mastodon.social

📢 A Maker Manifesto

https://wiki.hackmanhattan.com/User:Beadsland/Manifesto

Imposter syndrome is the belief that because you are capable of the virtue of doubt, you're somehow less prepared for the challenges of life than the many hubristic arseholes who lack the sense to recognize any consequences of their own poor judgment.

The world doesn't need more overconfidence. It needs more folk comfortable with doubt, of themselves, of their practices and institutions. Questioning our ability or preparedness to do a thing is not the same as being unable to do that thing.

Making is all about screwing up.

It's about having the confidence to screw up in increasingly creative ways.

It's the art of getting it wrong with such flair and panache that you can't help but be entertained by your own ineptitude.

It's the ability to foil so many of your own plans that you are left with no option but to stumble into a solution that works.

A solution, that when found, leaves you awestruck by what you have accomplished.

And it is in pursuit of that awe that the Maker makes.

Programming, a story:

"I want to create X." *start creating X*

"Oh, no. I'll need to create Y to properly do X." *start creating Y*

"Oh, wait, Y really would make better sense with Z." *start developing Z*

"Meh, I'm sick of doing this work without Ω." *start putting together Ω*

"This would all work better if only I had ß." *start building ß*

Jack, ✓. House, ✓. Malt, ✓. Rat, ✓. Cat, ✓. Dog, ✓. Cow, ✓. Turtle, ✓. Turtle, ✓. Turtle, ✓. Turtle, ✓...🐢↓ 🐢↧ 🐢↯

When developing, we begin with a standard model and choose a stack tailored to building variations on that model up from such stack. Through experience on multiple builds, we develop familiarity with navigating the pitfalls and limitations of said stack.

When programming, we begin with a problem non-standard to the stack we've chosen. Like a 4X gamer, we then explore, expand, exploit the sedimented layers of our stack, perhaps even replacing layers entirely with our own handcrafted solution(s).

When developing, we begin with a standard model and choose a stack tailored to building variations on that model up from such stack. Through experience on multiple builds, we develop familiarity with navigating the pitfalls and limitations of said stack.

When programming, we begin with a problem non-standard to the stack we've chosen. Like a 4X gamer, we then explore, expand, exploit the sedimented layers of our stack, perhaps even replacing layers entirely with our own handcrafted solution(s).