Tell HN: I made $1000 with my app and now making $500/mo

I agree with your point. However, I think I look at it from a slightly different perspective.

When it comes to any code I produce (with the exception of some learning projects), I try to keep it: effective, efficient and simple. In that order.

Effective is essentially what you were saying about correctness and usability from the user perspective. Peter Drucker would say to be effective is to "do the right thing." This is always an outward focused item. Does it impact the user in the right way? Does it solve the right problem? Etc. This is hands down the most important thing. Nothing else matters if you're doing the wrong thing.

In contrast, efficiency is to "do the thing right." Once you're doing the right thing, minimizing your costs, increasing your quality, making it so your code doesn't "consume the whole world" all fall under this category. Poor efficiency can negatively impact the effectiveness of your code. "It does this really cool thing, but it takes far too long to load so I can't use it."

Then lastly, keep it simple. That is not to say ignore the natural complexity of the problem, but rather to keep the solution to the essential complexity of the problem. Keeping things only as complex as they need to be covers a whole lot of dimensions in software. It makes things more explicit and understandable, it helps with code readability, and code re-usability. It decreases the surface area of what needs to be maintained. All good things for the health of the dev and the project.

It's all in that order for specific reasons. They move outside in. As the dev, I'm not the most import person with respect to the code I'm writing. The user is, and so the code needs to be purposeful to them (efficacy). Efficiency is more about the product, making sure it works properly. Keeping things simple, although it impacts efficacy and efficiency, is largely a positive for me and helps me maintain sanity.

I think it's important to note that it's all of these things, not just one of them. We'll approach tradeoffs in a prioritize way, but we're striving for the three of them. Obviously a very difficult task. But I find that approaching engineering this way has helped me grow a lot as an engineer.

Anyway, first time post here. Your comment made me think of this. Thanks for coming to my tedtalk.

That’s really good to know. To you mind expanding on why?

> It's easy to go on Instagram and forget how long you've been resting for. Don't worry, we'll notify you once your rest is over.

Will this notify through a connected Apple Watch? So that I can just get up and take a breather and get a vibration on my wrist when it's time for my next set? That'd be awesome.

A thought- the notification in the screenshot tells you your next weight, but it seems that it's telling you after your rest- not after your last set. A notification to set your next weight before you rest would be helpful, so that you're ready to go when rest is over.

I don't even know what 5/3/1 is but I was planning on joining a gym this month, so your getting my signup.

For the SEO could you go after Gym Noobs like me who know nothing about different programs, teach them what 5/3/1 is and then lead them to your app? Or is that too crowded and difficult?

Wow, that's frankly way less than I would have guessed for an apartment within an urban area, particularly given what my brother in TN is paying.

(And yeah, SWE, but no longer at a FAANG. I've found my fit is more in smaller companies, though I've worked at some larger corps since too. And while a SWE pay is — relatively speaking — nice, rent is such that it often makes me wonder how anyone who isn't is even supposed to manage it. The housing market needs a lot more supply, IMO, if the price is ever to be sensible. But, it is good that you've found a cheap place, and more importantly, hopefully a friendly place.)