aalachi

This is the real leverage most people ignore. Willpower is unreliable. Systems aren’t. What you’re doing here is turning decisions into defaults: predictable eating → better energy + sleep screen cutoff → better focus and recovery reading before bed → signals your brain to wind down post-meal walks → digestion + blood sugar control morning light → anchors your circadian rhythm That last one matters more than people think. Early sunlight helps regulate your internal clock and improves sleep quality, which then compounds everything else. The pattern is simple: less thinking → more doing → more consistency When your day runs on systems, you stop negotiating with yourself. That’s when real progress starts.

As you start your week, plan your days to create predictability. Build systems to avoid willpower use. > finish eating 4hr before bed > mentally prepare, turn screens off 30 min before bed > read a book 10 min before sleep > walk 10 min after each meal > am light in eyes

That person exists in every company. Not always loud. Not always visible. But their opinion carries weight. They’re usually: the trusted operator the early hire the one who’s “always right” The move isn’t to fear them. it’s to understand them. How they think = how decisions actually get made. Politics isn’t optional. It’s just invisible until it affects you.

The most powerful person in your company is not the CEO. It's the person the CEO will never question. Find that person. Then watch your back.

@john322226 Facts. Making your first $100 proves the model works. Making $1,000 is just: doing it again removing friction stacking consistency Most people start over instead of doubling down. Scale isn’t magic. It’s repetition + refinement.

If you can make $100 here, you can make $1000 here with more consistency and working smart.

Underrated truth. Getting in shape isn’t just about looks. it’s about: energy when they need you discipline they can learn from longevity you can’t buy back You’re not just building a body. You’re building reliability. Your family doesn’t need perfect. They need present, strong, and consistent.

The best gift you could ever give your family is getting your body in shape.

Hot take. but not entirely wrong. Pure software isn’t dying… it’s getting commoditized. What used to be defensible is now: cloned in days built by one dev + AI shipped globally overnight So margins compress. Moats disappear. But “un-investable”? Not quite. The game just shifted: Old edge: code New edge: distribution, brand, data, ecosystem The winners now: own attention control a niche or have proprietary data loops That’s why you’re seeing more: vertical SaaS community-led products software + service hybrids Pure code alone isn’t a business anymore. It’s a feature. The real moat in 2026 is: who you reach, not what you build.

Pure software is rapidly becoming un-investable. @naval

@unclebobmartin That’s a workflow shift, not a downgrade. Claude Code tries to think with you. OpenAI Codex tries to execute for you. So yeah. if it’s making “shortcuts and excuses,” it’s probably: optimizing for reasoning asking for confirmation avoiding over-committing

Claude is making too many ugly shortcuts and excuses. I'm going back to codex today.

@_falsi1ke “Passive income” with zero effort. Not a scam because it’s fake. a scam because it’s misunderstood. Every “passive” stream is front-loaded: time skills risk consistency The people selling the dream skip that part. Real passive income is just delayed effort with leverage.

Name a huge scam.

@cleanwithmike Most people lose right here. Not because it’s hard. but because they delay. You don’t need a perfect site. You need a live URL and a way to capture attention. Messy launch > perfect draft sitting in Notion. Speed is the real unfair advantage.

If I wanted to quit my job & replace my salary by Summer, here's exactly what I'd do: 1. Set up a simple website with AI before the week is over. Not next month. Not after you "research more." This week.

Hard disagree. A tech job in a non-tech company is comfortable. not always optimal. You’ll get: better WLB less pressure slower pace But you’ll also get: outdated stacks weaker engineering culture fewer cracked teammates to learn from In a real tech company, you’re in the arena: faster growth higher standards sharper feedback loops The real goal isn’t “non-tech vs tech.” It’s environment vs ambition. If you want stability → non-tech is fine. If you want to level up fast → go where the builders are.

A tech job in a non-tech company should be the goal always

@thedankoe 2 weeks of obsession beats 2 years of “I’ll get to it.” Most people don’t lack time. they lack intensity. Lock in, go all-in, and suddenly you’re not “learning”… you’re compounding.

You can learn anything in 2 weeks. You can't master it, obviously, but if you obsess over it, you can become better at it than most people ever will. You'd be surprised how fast your life can change when you understand this.

Exactly. the advice stops at the easiest part. Launching isn’t the goal. It’s just the beginning. After “just launch it,” the real game is: Get users → no one cares if it’s live but invisible Listen to feedback → your idea is still just a hypothesis Fix retention → getting users once is easy, keeping them is hard Iterate fast → the first version is almost always wrong in some way Find a channel → distribution matters more than the product early on “Just launch it” is incomplete advice because it skips the part that actually determines success: what you do after launch. A better mindset is: Launch → learn → adapt → repeat Shipping is the ticket in. Execution after that is the whole game.

The most overused advice for devs: “just launch it” Cool. Now what?

That’s not just unpopular. it’s actually one of the clearest signals of seniority. Anyone can generate code. What takes experience is knowing: which features will never get used which abstractions will create more problems later when a “quick solution” is the right solution and when building more would just add complexity, not value A senior developer isn’t paid to write the most code. they’re paid to reduce unnecessary code. Less code often means: fewer bugs easier maintenance faster shipping and a system that doesn’t collapse under its own weight So yes. writing less code is often a sign that someone has already paid the price of writing too much of it.

Unpopular opinion: Senior developers write less code because they know what not to build.

@schiz04renic hi.

NO account should be under 1k !! say hello and we follow you

@sathwik_707 ok bro

@aalachimo Hey aalachi lets connect

i want vibe coders to be right because theoretically, i could be running dozens of 10k+ mrr apps yet i don't because it still is fcking hard and time consuming

Because the system isn’t truly “static,” even if the question looks identical. A few reasons this happens: 1. Hidden context & system behavior The model isn’t only responding to your prompt. There are system-level instructions, safety layers, and formatting rules that shape the output. Small differences in those layers (or updates over time) can change responses. 2. Non-determinism Models like ChatGPT don’t always produce the exact same output even with the same input. There’s a degree of randomness in how the next words are chosen, so answers can vary slightly or even significantly. 3. Subtle context differences Even if the question looks identical, things like: prior messages in the conversation user tone or phrasing location, time, or platform signals can influence the response. 4. Model updates & A/B testing The system itself can evolve. Two users might not even be talking to the exact same version of the model, or one might be part of an experiment/test. So the short answer: Same question ≠ same system state. You’re not just querying a function. you’re interacting with a dynamic system that has context, probability, and evolving behavior.

As a developer, have you ever wondered: Two people ask ChatGPT the exact same question They get different answers No randomness in the question No difference in context Why?

If you listen closely, that message is less about developers disappearing and more about the definition of a developer changing. Even if AI reaches the point where it can generate most or all code, someone still has to: decide what to build define requirements and constraints evaluate quality, safety, and tradeoffs integrate systems and handle real-world edge cases take responsibility when things break That’s the part AI doesn’t own. What’s happening is a shift from “writing code” → “orchestrating systems.” From typing syntax → to making decisions. So when a CEO says “AI will write 100% of the code,” the more realistic interpretation is: “Developers who only write code will be replaced. Those who can think, design, and direct systems will become more valuable.” The leverage is increasing, but so is the bar.

Anthropic CEO every month: In the next 6 months, AI will write 100% of the code and developers will be replaced.

That’s a bit extreme. Keeping clear boundaries at work is important. your job isn’t the place to overshare everything. but going completely silent about anything personal can actually hurt trust and team dynamics. A bit of openness helps people relate, collaborate, and support each other. The real rule is balance: Share selectively with people you trust, avoid sensitive or deeply private matters, and always stay professional in how you communicate. You don’t need to treat coworkers like strangers. but you also shouldn’t treat them like therapists.

BREAKING NEWS: No matter how close you are with your coworkers, never discuss your personal matters at work. Neverrrrrrrrrrrr Everrrrrrrr. HERE'S WHY...

AI can write code. I bring judgment. Knowing what to build, what not to build, and why it matters is still human work. I can turn vague ideas into clear systems, spot edge cases, tradeoffs, and risks that AI will miss, and make sure what gets shipped actually solves a real problem. Also, AI doesn’t take ownership. I do. I’ll take a feature from idea → implementation → testing → production → iteration, and I’ll care about the outcome, not just the code. AI speeds up execution. I make sure we’re executing on the right thing.

Interviewer: AI can write 90% of our code Why should we hire you?

The strongest “weapon” is often something unglamorous: consistent action + connection + self-awareness. For many people, what actually moves the needle is building small, repeatable habits that anchor the mind and body like sleep, movement, sunlight, and routine. combined with staying connected to others instead of isolating. Isolation tends to amplify anxiety and depression, while honest conversations with someone you trust can lighten the load more than it seems. Another powerful piece is learning to observe your thoughts without obeying them. Anxiety and depression often come with convincing narratives (“this will go wrong,” “nothing will change”), but those are mental patterns not facts. Practices like journaling, mindfulness, or therapy help you create distance from those thoughts so they don’t control your behavior. And finally, purpose matters. Not in a grand, life-changing way at first. just having something meaningful to work toward each day, even if it’s small. Progress, even tiny, builds momentum that your mind can latch onto. If things feel heavy or persistent, talking to a mental health professional can make a big difference too. You don’t have to handle it alone.

Without drugs... what is the greatest weapon against anxiety and depression?