Live data from Hacker News

The curse of knowing how, or; fixing everything

notashelf.dev

281–290 of 458 posts

Re: The curse of knowing how, or; fixing everything

#281

Earlier quoted context omitted.

I have another submission for most annoying UI problem: Trying to read a thing, but it's on medium.com. The sheer amount of popups and overlays I need to click away before I can actually read your thing, geez.

Reader mode is a thing, but if you can suggest a better (ahem) medium to repost it to, I'd be happy to! (Honestly, I'm sort of with you on the medium thing, but I posted this years ago now...)

Maybe substack?

Re: The curse of knowing how, or; fixing everything

#282

This just sounds like perfectionism. I believe it is a curse, because I hate working with teammates like this. They'll spin their wheels solving some insane problem no one asked them to do because it's "better" while ignoring the larger scope and goals of the project. I've tried to coach people out of this mindset, because I used to have it very early in my career, til I realized the sheer impracticality of it. I use…

There's a difference between picking up on some esoteric detail.in your company's product and making it your only mission to solve it, ok the detriment of everything else vs taking Friday afternoons for a month to fix a Terraform provider for the world. There are two kinds of lazy. The kind that makes us good programmers and the kind that makes us bad programmers. If you're gonna be the second kind of lazy and just wait for someone else to do it for you, you might as well become a manager at work and take credit for their work while you're at it.

Re: The curse of knowing how, or; fixing everything

#283
There's a quote I learned when doing theatre, which I've seen attributed to either the stage magician Doug Henning or possibly Stanislavski, describing the process of art as taking something that's difficult and making it habit, then taking something that's habitual and making it easy, and then taking something that's easy and making it beautiful.

For example, as an actor, you learn your lines by rote (they become habit), then you gain an understanding of the character's motivations (remembering the lines becomes easy, because of course that's what your character would say), then you work to tune your performance so the audience shares in the emotion and unspoken meaning of the lines (that's beautiful/art).

As this relates to software, I think it goes something like: you learn the magic incantation to make the computer do what you want (solving a hard task becomes habit), then you learn why that incantation works (solving it becomes easy), then you figure out better ways to solve the problem, such that the original friction can be removed completely (you find a more beautiful way to solve it).

Re: The curse of knowing how, or; fixing everything

#284

This just sounds like perfectionism. I believe it is a curse, because I hate working with teammates like this. They'll spin their wheels solving some insane problem no one asked them to do because it's "better" while ignoring the larger scope and goals of the project. I've tried to coach people out of this mindset, because I used to have it very early in my career, til I realized the sheer impracticality of it. I use…

i really agree with this

Re: The curse of knowing how, or; fixing everything

#285

Earlier quoted context omitted.

Thank you for your comment, especially for this > I've written a lot of Rust. I've read less than half of the Rust book. Just knowing that there's someone out there who has worked like this or has been in the same situation gives me enough confidence to go through it!(the just write code part) I've gone through so many resources (including the book) and I never managed to finish any of them. But I think now I need to…

I've -literally- been writing Swift, every day, seven days a week, 52.4 weeks a year, since June 2, 2014 (the day it was announced), yet, I still have huge gaps in my knowledge of the language. I speak it without an accent, but not at Ph.D level. As to home projects, that's pretty much all I do, these days, ever since I "retired"*, in 2017. I'm quite good at what I do, and generally achieve every goal that I set, but…

Unrelated question since you've got the Swift experience: How would you recommend a modern day Mac utility get sold? Is grabbing some hardware ID of a device and then charging money for a license keys somehow still the way to go for some small utility (eg window management app like Rectangle) if you want to sell to users outside of the Mac app store?

Re: The curse of knowing how, or; fixing everything

#286

Hopefully the future me is able to relate to this, because I really feel like I'm in a rut when it comes to working on personal projects. I have many ideas that I want to build, but I'd have to learn new languages, yet I just can't sit and go through the documentation every day like I should. Still haven't finished the rust book. The other way is start building already, and if you come across a block, then learn abou…

You’re getting a lot of advice here, I’d just echo the sentiment of trying to give yourself permission to have fun.

In my experience the best way to learn is by doing; that “uncomfortable having gaps” is there for most folks to some degree. That mild discomfort is a good indicator that you are in the growth zone, maybe you can shift your perspective to perceive it as a positive signal.

AI is also great to ask questions and accelerate the process of learning a new language, but if you’re doing this for the craft then you are free to choose the constraints and rules that make it fun.

Re: The curse of knowing how, or; fixing everything

#288
post #153

A good part of that is a disguised sense of superiority. Life becomes way lighter when you realize other people are also smart and what you’re “fixing” can very likely be: - something so unimportant that no one felt it was worthy working on - something that was supposed to work like that, and you simply don’t agree and want to make it your way

All of programming comes from a sense of superiority. Programming is the closest humanity has ever gotten to godhood. We're creating entire structured universes out of unstructured bits. The system reflects the understanding of its creator. We're all pretending to be gods, warring over the system's design.

I wish this meme would die already. You're just writing some mumbo jumbo that you've learned (at least most of it) in a couple of years, chill out.

Re: The curse of knowing how, or; fixing everything

#289
post #266

One of the ways psychologists classify people is between those who are maximizers/optimizers and those who are satisficers/stop when things are "good enough." As someone who is very much on the optimizer side of things, and experiences the struggles described in this article, the lesson I take to heart is that while satisficers tend to be happier, optimizers get more done. Your optimizer tendencies make you into an e…

As someone who sometimes thinks of themselves as an "optimizer", I feel the opposite take away. I spend too much time "polishing" trying to make something perfect, at the cost of actually getting things done.

Re: The curse of knowing how, or; fixing everything

#290
Aargh. As someone who went into programming at ~12 after trying toys, woodwork, mechanics, electrics, electronics, .. - and stays there for 40years - i would have blessed software if it was just the software to blame. But i also knowhow all the other things before/besides that.. So it is, a total DIY-as-noone-will-fix-it-and-no-way-buying-it. Or it was but i haven't noticed things have changed?

(the saying goes that every man sooner or later grows.. into buying new socks instead of darning the holed ones. That i have accepted, but my question is, Shouldn't that apply to other things too?)

Handle of fridge broke? Well.. no-such-thing-as-buy. Fix it - or replace it - with a rope (from some gift-bag handle actually). Uncountable toys being fixed and overflowing the wardrobe.. No way Throwing (almost) working things.

Pfft. Same thing as these hudreds of Makehells^b^b^b^b^bfiles, or that proper rename tool [1] which after 10years has become a swiss-army-knife and i still find more use cases to add :/

A cage looking for a bird.. vs learning when to leave things broken...

Maybe that last one is like learning to pick your battles. Seems the hardest life lesson that can only be self-taught, sigh.

Thanks for the revelation.. maybe one day i'll write mine :/

[1] https://github.com/svilendobrev/svd_bin/blob/master/filedir/...

Post reply on HN