21–30 of 30 posts
I honestly read "Postgres beat perfect" and imagine an article about just using PostgreSQL for all your early features. Features like Full-text search, Documented DB, distributed tasks running, etc., and not worrying about scale and always know that is better to have it ready for customers than keep them waiting for the best tool for the work
Earlier quoted context omitted.
Adding to this, it’s hard to know if you are actually getting “better” because it’s so hard to measure. My approach is to try to get better between reflection periods while also scheduling days for self reflection on that goal.
I am 50/50 on if a conscious self-reflection will give you the birds-eye view. For some it might work, for me it doesn't. Meditation definitely achieves that for me however.
This is all a big problem with unrealistic expectations. > If I get one percent better each day for one year, I'll end up thirty-seven times better by the end of the year. This, too, is an unrealistic expectation. To get better every day (or even most days!) is very hard to do and can put you on the defensive as much as the quest for perfection.
"We evolve beyond the person we were a minute before! Little by little, we advance a bit further with each turn. That's how a drill works!"
This is all a big problem with unrealistic expectations. > If I get one percent better each day for one year, I'll end up thirty-seven times better by the end of the year. This, too, is an unrealistic expectation. To get better every day (or even most days!) is very hard to do and can put you on the defensive as much as the quest for perfection.
> This, too, is an unrealistic expectation. To get better every day (or even most days!) is very hard to do and can put you on the defensive as much as the quest for perfection Not just getting better every day (which already is very hard) but getting exponentially better every day! That is just plain ludicrous idea.
Best thing my first boss ever told me and I find my self repeating to my self all the time - “perfection is the enemy of good”
Loads of people are on quickfire mode, judging every little "but we could do better" as "perfect" and throwing out that phrase. It is really annoying. When you want to invest a little more time, because you already know, what problems will bite you in your behind later, and then you hear that phrase. Whoever outputs that phrase should first think about whether they are stopping improvement, by labelling it as "perfec…
Then maybe you could reply: "yes but at least it has to be good enough. It isn't, yet -- this and that and that will come back and bite us"
Best thing my first boss ever told me and I find my self repeating to my self all the time - “perfection is the enemy of good”
"don't let good be the enemy of what is actually needed"This is all a big problem with unrealistic expectations. > If I get one percent better each day for one year, I'll end up thirty-seven times better by the end of the year. This, too, is an unrealistic expectation. To get better every day (or even most days!) is very hard to do and can put you on the defensive as much as the quest for perfection.
nkozyra: This is all a big problem with unrealistic expectations. > If I get one percent better each day for one year, I'll end up thirty-seven times better by the end of the year. OP also seems to assume that 1% improvement today is same effort/as easy as 1% improvement yesterday. it becomes harder to improve by 1% as time goes on, just coz your baseline is compounded too but absolute effort/difficulty may not. 3.65…