Josh Ponelat

Coffee | Code | Creative.
In an order that would surprise you.

[Josh Ponelat @jponelat]

@robj3d3 Been tinkering with this, execution will be the main thing!

[Josh Ponelat @jponelat]

Goodness, vibe coding can be frustrating. Two steps forward, five backwards.

[Josh Ponelat @jponelat]

@boyney123 That’s a cool flex 💪😄

[Josh Ponelat @jponelat]

@_catwu That's a cool UI trick! Nice.

[Josh Ponelat @jponelat]

@aidandcunniffe It’s a better package manager cli name to be fair

[nate parrott @nateparrott]

direct manipulation

[Blair Dulder CPA™ 🧃 @runaway_vol]

@levelsio i always put an empty 8gb file in the server root. in case something happens you have quick relief to fix things

[Josh Ponelat @jponelat]

@code_star Gonna keep an eye on this thread, thanks ! I’m building a journaling app based on time view. Even without AI it’s super useful to record your work

[Josh Ponelat @jponelat]

Are you almost agentic? I wrote something up on it... https://t.co/stSnn0E7vf

[Geoffrey Litt @geoffreylitt]

# the nightmare bicycle

imo, the most important idea in product design is to avoid the "nightmare bicycle".

imagine a bicycle where the product manager said "people don't get math so we can't have numbered gears - we need to have labeled buttons for gravel mode, downhill mode, ..."

this is a hypothetical "nightmare bicycle" that Andy diSessa imagines in his book Changing Minds.

as he points out: it would be terrible! we'd lose the intuitive understanding of how to use the gears to solve any situation we encounter. which mode do you use for gravel + downhill??

turns out, anyone can understand numbered gears totally fine after a bit of practice. people are capable!

along the same lines - one of the worst misconceptions in product design is that a microwave needs to have a button for every thing you could possibly cook: "popcorn", "chicken", "potato", "frozen vegetable" bla bla bla.

you really don't! you can just have a time (and power) button. people will figure out how to cook stuff.

good designs expose systematic structure; they lean on their users' ability to understand this structure and apply it to new situations. we were born for this.

bad designs paper over the structure with superficial labels that hide the underlying system, inhibiting their users' ability to actually build a clear model in their heads.

[Josh Ponelat @jponelat]

@boyney123 @addyosmani That’s so cool! Does look like a super power 🦸‍♂️

[Josh Ponelat @jponelat]

@topSimpa Business first. User second. Product/API third.
It's a tradeoff. How much energy you spend considering these, vs how much time you have to build it. Account for as much as you can, knowing that you're likely wrong (we all are) and that testing will help prove things.

[Josh Ponelat @jponelat]

@topSimpa Functional requirements are what the thing will do. If the business requirement is to "get more users". Then the functional req might be "build a box that makes people laugh when they push a button". It's a thing, users can interact with it. It is functional.

[Josh Ponelat @jponelat]

@topSimpa Yes there is a difference. The business requirements are how this thing will impact the business. Is it meant to get more users, engage them more? How will this translate into more money ultimately.
The initial requirements should definitely consider this.

[Josh Ponelat @jponelat]

@topSimpa @OyabureZakari Thanks for the feedback @topSimpa ! @LukasRosenstock wrote the section on Function/non-Functional, but I'll throw in my thoughts...

[Josh Ponelat @jponelat]

@heynibras As someone who's played around with walking-and-talking, it can actually be super exhausting to work while on foot. Not every walk should be productive! I'm playing around with prototypes to bring order to notes, an Infinite Journal, if you will :)

[Josh Ponelat @jponelat]

Bret Victors principle of Immediate Connection, drives much of my thinking today, had to write about it…
https://t.co/D4CQ0s85Dr @Dynamicland1

[Stammy @Stammy]

now this is a side project

[Josh Ponelat @jponelat]

My first post on Substack! Just something to get going with... Marketing jargon on landing pages https://t.co/sdYcUFJ5JQ

[Josh Ponelat @jponelat]

Fun!

[Lukasz Gornicki @derberq]

Reading about AsyncAPI and learning its structure should be much easier now thanks to this great feature from @_acebuild that is now part of AsyncAPI website

The beauty is that it is not hardcoded. The whole explorer is generated from @jsonschema

https://t.co/fP5VdeMv9z