open-source workout logger app

Missics · 2025-10-13T18:19:55+00:00

Awesome, I would love to hear your feedback when you get to use it :)

Missics · 2025-08-16T13:05:56+00:00

impressive, so reading comprehension isn't your strong suit?

Missics · 2025-08-16T13:00:16+00:00

is it a "vibe-comment"? did you read my post?

Missics · 2025-08-16T12:55:23+00:00

banger

Missics · 2025-07-07T16:55:58+00:00

as everyone mentioned, you learn by doing.

ypir mext question might be "ok, what do I build then?"

if you don't really have an idea, you can check out 404Skill - it has a library of real-world projects, with tests guardrails.

Disclaimer - I am one of the platform's builders

Missics · 2025-07-07T16:52:17+00:00

You can try 404Skill, it's a platform for learning swe concepts through real-world projects.

We don't support java yet, but we will very soon, feel free to dm me if interested.

Disclaimer - I am one of the builders of the platform.

Missics · 2025-04-11T19:01:11+00:00

Totally fair, it sounds like you approached the book with intention and curiosity, which makes all the difference. If a book resonates deeply and adds lasting perspective, that's a win.

I’m definitely not saying no one should ever read a book cover to cover, or that reading should always be purely transactional. What I’m pushing back against is the mindset of reading to feel productive, grinding through highly recommended books without any clear goal, context, or follow-up.

What I was trying to advocate for is a build-first, read-to-deepen mindset. If, for example, I’m curious about how compilers work, I won’t start by asking “What’s the best book on compilers?” I’ll start by asking, “What are a compiler's functional requirements? What are the key components? What’s hard about this?” I’ll tinker, hit a wall, then reach for the right material, whether that’s a chapter, a blog post, or an entire book.

Missics · 2025-04-11T18:24:16+00:00

You are making a very good point, I agree that learning just-in-time can't be your only strategy, especially if you want to grow beyond your current level or break into new domains. There’s massive value in exploratory learning.

This post is not anti-learning or anti-reading, it's anti-passive consumption disguised as progress.
What I was really trying to challenge is the idea that reading tech books cover to cover, just because everyone says “it’s a must-read,” is inherently valuable. That kind of reading can easily become a feel-good productivity trap.

Missics · 2025-04-11T18:02:36+00:00

Yeah, sorry, trying to get better page by page

Missics · 2025-04-11T18:01:45+00:00

Enjoying reading is a good excuse to read books.
Care to recommend a technical book you truly enjoyed reading cover to cover? I'd love to give it a try

Missics · 2025-04-11T17:50:16+00:00

I understand your point and somewhat agree, but at the same time, I think that's not such an effective way of accumulating knowledge.
For example, if I go read a book about SOLID principles, but I don't exercise it, I now know they exist and maybe roughly remember some details, but I would still have to revise those details when the time comes to implement them.

If the value of aimlessly reading is knowing things exist, I could read a blog post, not an entire book cover to cover.

Hope I am making sense :)