How long do you spend on product research before you start building?
Do you thoroughly study the product first, or do you start building immediately and keep iterating as new ideas come up?
Doing the work is hard, but what's even harder is not doing the work and spending the rest of your life coping with unrealized potential. The fatigue from hard work is surface-level; the regret from inaction runs deep.
@1960dude@RizwanHamisi I've always said I can tolerate such if the pay is worth it. I clock in more hrs than needed cos I love what I do & my employee compensate quite well
@RizwanHamisi Finally someone has said it out loud. I confronted one tutor last month on the same! Do not include AI &ML and you know very well your curriculum touches nothing on those two. We need to put an end to this behavior
@StanleyMasinde_ Agree on โdo more with less.โ
But ISO size isnโt proof of bloat.
Bloat is what runs: services, RAM, daemons, disk churn, login cost.
Measure runtime cost, not installer size.
@StanleyMasinde_ The stronger criticism of Omarchy is not โthe ISO is big.โ
It is whether the opinionated defaults create unnecessary runtime cost, hide complexity from users, or make debugging harder than a clean Arch install.
@StanleyMasinde_ A large ISO can still produce a lean runtime if most of the bundled stuff is dormant after install.
Arch is not efficient simply because you installed fewer packages by hand. It is efficient when the final dependency graph, enabled services,compositor, kernel config r controlled.