> Making a to-do list for the thing isn't doing the thing.
Clearly defining and understanding the thing or, as they say, understanding the problem is half the solution. Real life experiences totally crash the OP statements.
81–90 of 220 posts
> Making a to-do list for the thing isn't doing the thing.
Clearly defining and understanding the thing or, as they say, understanding the problem is half the solution. Real life experiences totally crash the OP statements.
I see this as a kind of inspiration / perspiration thing, and I’m on Tesla’s side that you perspire less if you think more. I like to not do the thing for a really long time, and then do it quickly, having thought it through. I see some people that jump into things without thinking, and take what is imo the more difficult route, with worse results. I know there are some things you need to start to really understand w…
B: Isn't that just the wrong way?
A: Yes! But faster!
Right but I see this taken too far. Getting side eyed for creating a Jira ticket not doing it now. Dude, I am creating a Jira ticket because I have 100 things to do and need to actual priorise this! If I do stuff in the order of serendipity I will definitely be inefficient.
1. Ticket
2. Feature branch
3. Write unit test
4. Periodically merge from main.
5. Implement to get tests to pass
6. Push changes
7. Create PR
8. Wait for PR feedback
9. Address feedback and repeat
10. Close and merge PR
11. Automated CI deploy
12. Integration testing as needed
13. Close ticket
14. Include in next prod release
All of these are good things. But the overhead is significant. And there may be times when you want to do spikes that forgo some of these.In the Viable System Model[0], "doing the thing" is System 1. Yes of course you need System 1 or the thing won't get done. But in any viable system, you also have the "meta-systems", Systems 2-5: - System 2: coordination between multiple Systems 1 (which includes prioritization, communication, and exceptional conditions) - System 3: resource allocation and process development - System 4: strategy and risk management…
I see this as a kind of inspiration / perspiration thing, and I’m on Tesla’s side that you perspire less if you think more. I like to not do the thing for a really long time, and then do it quickly, having thought it through. I see some people that jump into things without thinking, and take what is imo the more difficult route, with worse results. I know there are some things you need to start to really understand w…
A: There's the right way, the wrong way, and THEN THE MAX POWER WAY! B: Isn't that just the wrong way? A: Yes! But faster!
I wonder what thing the author was avoiding when they published this thing ;)
There is nothing wrong with planning/scheduling/marketing/whatever. But a LOT of people use all that as excuses and never actually do the thing.
If you are the kind of person for whom which those are useful, great. Or if you have the self-displine/self awareness to do all that stuff and still follow through, great. But some people just need to do the fucking thing or they never will.
Source: I'm one of those people.