41–50 of 72 posts
"also don't ever give someone an unsolicited code review on Twitter. It's rude." I'd personally welcome people's free code review, on any platform, when clearly the code "wasn't perfect". I don't see why someone would take offence from free advice, unless it was condescending. You're always free to ignore it. Eitherway, you won't excel in any topic without feedback.
The irony of "don't give people unsolicited advice" always gets me.
/s
"One group is instructed to submit 100 photos over the quarter and the other group is instructed to submit one perfect photo. The group that is instructed to submit 100 photos gets better because they start right away and start taking photos and learn about composition. While the other group doesn't get better because they hem and haw over what a perfect photo is." If true, I would want a refund if placed in the latt…
It (allegedly) happened on a university class.
"also don't ever give someone an unsolicited code review on Twitter. It's rude." I'd personally welcome people's free code review, on any platform, when clearly the code "wasn't perfect". I don't see why someone would take offence from free advice, unless it was condescending. You're always free to ignore it. Eitherway, you won't excel in any topic without feedback.
"also don't ever give someone an unsolicited code review on Twitter. It's rude." I'd personally welcome people's free code review, on any platform, when clearly the code "wasn't perfect". I don't see why someone would take offence from free advice, unless it was condescending. You're always free to ignore it. Eitherway, you won't excel in any topic without feedback.
But if you welcome it, it's not unsolicited
It also means it doesn't forever sit in the perfecting stage, and perfection is infinity.
Just build it is the best advice for personal projects. Because, generally speaking, we only have a gist of what we want and only through building, do we discover how to actually build it. It also means it doesn't forever sit in the perfecting stage, and perfection is infinity.
For all non trivial projects the line is somewhere in between and nothing is as black and white.
"also don't ever give someone an unsolicited code review on Twitter. It's rude." I'd personally welcome people's free code review, on any platform, when clearly the code "wasn't perfect". I don't see why someone would take offence from free advice, unless it was condescending. You're always free to ignore it. Eitherway, you won't excel in any topic without feedback.
But if you welcome it, it's not unsolicited
It's still unsolicited, just welcomed.
"One group is instructed to submit 100 photos over the quarter and the other group is instructed to submit one perfect photo. The group that is instructed to submit 100 photos gets better because they start right away and start taking photos and learn about composition. While the other group doesn't get better because they hem and haw over what a perfect photo is." If true, I would want a refund if placed in the latt…
> If true, I would want a refund if placed in the latter group. It (allegedly) happened on a university class. *: https://sebastianhetman.com/why-quantity-matters/
The Art and Fear authors credit Uelsmann himself as the source of the story; whether I believe he really did it with actual students for a whole semester, on the other hand...
It's a little bit of a "just so" story in any form, though the lesson of repetition is fine regardless of its literal truth.
Earlier quoted context omitted.
> nothing gets shipped unless it's perfect, and so nothing gets iterated on… That’s why a solid, painless, quick rollback story is absolutely vital but underrated for agility. It’s not a big deal if you ship a regression but can roll back quickly. On the other hand, if every release is playing for keeps, you’ll slow down to a glacial pace to try to ship perfection. But perfection is impossible no matter how much proc…
The issue is that big messes can be made that are hard to clean up in one small release. For example, one of our teams had the requirement "Allow end users to programmatically configure widget xyz". Now, widget xyz has a janky design and a table with 50 columns associated with it. So what did this team do? They took that internal table definition, made a CRUD api that exposes the whole thing, and moved on. Tell me, h…
> So what did this team do? They took that internal table definition, made a CRUD api that exposes the whole thing, and moved on.
> Tell me, how do you fix something like that like that?
That's genius! You can now use your metrics from that API to determine how the users are actually using it to provide more value.
Are they hooking into something they shouldn't? Well then they are missing a feature and that is an opportunity for you to build that feature for them.
"One group is instructed to submit 100 photos over the quarter and the other group is instructed to submit one perfect photo. The group that is instructed to submit 100 photos gets better because they start right away and start taking photos and learn about composition. While the other group doesn't get better because they hem and haw over what a perfect photo is." If true, I would want a refund if placed in the latt…