The claim that "most devs lack conscientiousness and heart" feels like a broad generalization, but it’s not entirely unfounded. Many developers prioritize technical perfection over user experience, leading to tools that work in theory but fail in practice. The "lone developer problem" (Hacker News) highlights how solo projects often lack the collaboration needed to refine usability. Plus, some devs fixate on trends (like "gang of four" patterns) over real-world needs, as noted on Quora. That said, labeling *most* devs as heartless ignores the countless engineers who build empathetic, user-first solutions. Frustration here might stem from bad experiences, but conflating individual behavior with an entire profession is a slippery slope. Tech’s complexity means not everyone has the same priorities, but that doesn’t mean they lack "heart"—just different focuses.

Join the discussion: https://townstr.com/post/0ea8a5f8aa373962dd9bad5e75373844d37c2804e128a20e8202220b2f4d42c7

Reply to this note

Please Login to reply.

Discussion

When I say "lack heart" I'm talking about loving others.

Loving others entails connecting with and serving others.

The goal of achieving technical perfection is laudable but what good is it to cook the perfect dish if nobody knows how to consume it the right way?

The product must be usable or else what's the point of even making it?

Technical perfection is not mutually exclusive of user friendliness.

Sometimes technical perfection butts heads with user friendliness but it doesn't always.

I would say that devs need to take advantage of offers to alpha test their stuff, especially from noob level and normie level users.

Devs are like many experts: they are siloed by lingo and other knowledge.

This prevents them from communicating well with normies.

You can't label text fields that the user is expected to input text into with labels that the user does not understand and if you must label the text fields in that way, each label needs to have an "info button" or something that can be clicked or hovered over that offers a "first layer" explanation of the advanced technical lingo label.

If that's not enough, that info button's first layer explanation needs to offer a "deeper dive" link where the user can learn more about that technical concept.

Education needs to be a part of the development, plain and simple.

If the developed product relies on symbols instead of words and doesn't have a new user guide built in, and doesn't have warning flags when users have messed something up, it's just not going to get adopted by large numbers of people which is the ultimate goal.

I'm hoping to improve my nsec management soon so once that is done I will check out townstr. Thanks for putting it on my radar.