Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Aim, fire, scan: the 80/20 of executing on big projects

indiehackers.com

Post reply on HN
Print view View original

21–30 of 46 posts

Re: Aim, fire, scan: the 80/20 of executing on big projects

#21

Post by mcmoor »

quickthrower2 wrote: post #5

These goal escrow sites, like stickK, beeminder are not my thing but glad they help people. Here are some other hacks: 1. Set your standards ( https://www.youtube.com/watch?v=aUck-umj2WI , yes it is him, but it is good.) 2. If plausible, release something shit / half done. You will feel embarrassed and want to fix it up. 3. Just get started. Do a minute. Soon you will be in work mode, and forcing yourself to no to do…

I still don't find habit useful, at least as I interpret it as something magical that reduces pain of something you do often. If anything, pain of something I do get worse and worse the more I do it. Anything I do regularly is always because of external pressure, without that my "habit" just vanishes.

Re: Aim, fire, scan: the 80/20 of executing on big projects

#22

Post by chaosharmonic »

candiddevmike wrote: post #17
metabeard wrote: post #13

Earlier quoted context omitted.

> DDR cab Dance Dance Revolution?

Stepmania is an option along with some USB pads. Works well on Linux.

Stepmania is great. I actually built a skeleton of a workout tracker for DDR a while back using the simfiles I was already playing this on. I haven't had a space to play in that consistently in years, though, so I never bothered to bring the hosted demo back up when Heroku killed their free tier and kinda stalled the development before it got more than just fleshed out enough to be kind of useful.

That said, there's a mostly working .sm to .ssc converter (it's still got a couple edge cases around punctuation in titles), as I had to migrate the simfiles to something with named properties anyway to get reliable data out of them.

This, and the seeder script (which I wrote using a bunch of fetch requests in order to also test a bunch of my frontend logic, before Node started shipping with that) that I used to seed all the DDR arcade tracks into a db, were actually my first experience with Deno. It's been my go-to experiment tool pretty much ever since.

If anyone's curious, it's under my github (same username) at step-step-recollection. (And ...recollection-scripts, and ...recollection-ui. Annoyingly I never got to experimenting with server-side rendering on it, so that's also a separate repo.)

Re: Aim, fire, scan: the 80/20 of executing on big projects

#23

Post by RickHull »

quickthrower2 wrote: post #5

These goal escrow sites, like stickK, beeminder are not my thing but glad they help people. Here are some other hacks: 1. Set your standards ( https://www.youtube.com/watch?v=aUck-umj2WI , yes it is him, but it is good.) 2. If plausible, release something shit / half done. You will feel embarrassed and want to fix it up. 3. Just get started. Do a minute. Soon you will be in work mode, and forcing yourself to no to do…

I predicted your #1 was Jordan Peterson. Tony Robbins just made an appearance on Theo Von's podcast, This Past Weekend. I haven't watched it yet, but Theo is fantastic at getting his guests to open up. I am deeply skeptical of Tony Robbins overall, but I'll probably queue up the podcast soon.

Re: Aim, fire, scan: the 80/20 of executing on big projects

#24

Post by Leo_Germond »

etrautmann wrote: post #15

I like this post and find some of it quite helpful as a framework, but certain pieces are sufficiently vague that I actually have no idea what's being said: "As a rule with few exceptions, you want to move forward through iteration loops, not backward. (Too often, moving backward is a sign of problems with doing, not problems with planning.)" What does that mean? a short example here would help. How do I know if repr…

I guess it means for some "plan do check act" loop, you want to avoid doing a plan, a do, then to plan again (because you have something important to note), then do a bit etc... This kind of back and forth were you subvert the principle by turning the loop into a 2 step pseudo-iteration.

Re: Aim, fire, scan: the 80/20 of executing on big projects

#25

Post by pbkompasz »

quickthrower2 wrote: post #5

These goal escrow sites, like stickK, beeminder are not my thing but glad they help people. Here are some other hacks: 1. Set your standards ( https://www.youtube.com/watch?v=aUck-umj2WI , yes it is him, but it is good.) 2. If plausible, release something shit / half done. You will feel embarrassed and want to fix it up. 3. Just get started. Do a minute. Soon you will be in work mode, and forcing yourself to no to do…

Gym is fun!

Re: Aim, fire, scan: the 80/20 of executing on big projects

#27

Post by DeathArrow »

Why complicate things? Make a plan, start executing it, review and adjust. There's all there is to it.

If you put down hours in a mindful way towards your objective, you will progress, regardless if you want to learn to play piano, discover a revolutionary drug or get rich.

Re: Aim, fire, scan: the 80/20 of executing on big projects

#28

Post by TeMPOraL »

quickthrower2 wrote: post #5

These goal escrow sites, like stickK, beeminder are not my thing but glad they help people. Here are some other hacks: 1. Set your standards ( https://www.youtube.com/watch?v=aUck-umj2WI , yes it is him, but it is good.) 2. If plausible, release something shit / half done. You will feel embarrassed and want to fix it up. 3. Just get started. Do a minute. Soon you will be in work mode, and forcing yourself to no to do…

> 5. Habits are very powerful. Your brush your teeth, right?

You'd be surprised. For some, brushing teeth is an explicit act of will every day, that never seems to habituate. ADHD perhaps?

Post reply on HN