Something to experiment in 2018 🔥

@selfmadecoder

I read this somewhere lol 😁 "Analyses of startup post-mortems find that about 42% of failures occurred because the
founders “built a solution looking for a problem,” i.e. they lacked a scalable market need."

Books of z week
AI utopian acceleration vs existential caution
• The Singularity Is Near (Ray Kurzweil) — Rapid AI progress will lead to transformative and mostly positive superintelligence.
• Superintelligence (Nick Bostrom) — Advanced AI poses severe existential risks that must be mitigated before widespread deployment.

Progress doesn’t need approval
it needs persistence.

"I’d rather fall short of a big goal and see myself as a failure than lower my goals to a level where I can easily accomplish all of them just to feel like a success."

@selfmadecoder

One thing I’ve learned over time is how silly it is to obsess over your tech stack. Just use whatever works for you and whatever works best for the product you’re building. JS, TS, Rust, PHP, even COBOL 😁 .. it really doesn’t matter. Most of the time you’re either working on someone else’s product (where the CTO picks the stack anyway), or you’re building your own, and you definitely don’t need to write your todo app in Assembly just to feel “performant and scalable.” Get your first users first.

I’m not saying write spaghetti or vibe coded, unmaintainable and unscalable stuff, but we really stress over the silliest things sometimes.. like “is PHP dying?” or “is Ruby dead?” Who even decides that? If you’re learning for fun, cool. But if you’re building a product, overthinking the stack just wastes your time and usually ends with the project half finished and abandoned.

@selfmadecoder