Harith M

Tech enthusiast & curious generalist. Always exploring the latest in tech & sharing my findings. Let's discover the future together!

[Harith M @harith_m1999]

@manoj_ahi Congratulations, Manoj! Beautiful concept, polished execution, and a strong focus on user privacy. Wishing Orbl an amazing journey ahead!

[Harith M @harith_m1999]

@jspujji GA

[Harith M @harith_m1999]

@bryan_johnson @jain_harshit Mid session sleep really helps to rewrite brain!

[Harith M @harith_m1999]

@pbteja1998 @ayushtweetshere Can we run openclaw on windows?

[Harith M @harith_m1999]

@pbteja1998 I tried codex recently with the app version.
I mapped my local folder to it, all the code changes got reflected in my local

[Harith M @harith_m1999]

@jspujji ONBOARD

[Harith M @harith_m1999]

An insightful eye of looking how next jobs are being shaped!

Writing code is no longer a unique proportion to have.

People in all aspects should be able to leverage the AI capabilities and build things for their needs!

[Aakash Gupta @aakashgupta]

The CEO of Postman just described what the best PM job in the world looks like right now.

Postman has 30M+ developers on its platform. Abhinav built the tool that made API collaboration mainstream. So when he says "PMs are building APIs and prototyping in Claude instead of writing PRDs," that's not a hot take. That's a field report from Anthropic's actual org chart.

And the details matter.

PMs prototyping in Claude means the feedback loop between "idea" and "working thing" collapsed from weeks to hours. You don't write a spec and wait for engineering to interpret it. You build the first version yourself, put it in front of users, and iterate before a single engineer touches it.

Designers shipping PRs through Cursor means the handoff is gone. The gap between "what it should look like" and "what it actually looks like in production" used to be where 30% of product quality died. That gap is closing.

Staff engineers leading projects with high agency, seeing across the board and deep in the stack. That's the new PM partner. Not a junior dev waiting for a ticket. A senior builder who owns the entire problem.

This is a harder job. You need taste, technical instinct, and the ability to build a prototype that's good enough to learn from. But it's also a way better job. You're in the code. You're in the product. You're three steps closer to the user than a PM writing Jira tickets ever was.

The PRD era is fading at the best companies. What's replacing it is more fun and more impactful. But it requires a different skillset. The PMs who build that skillset now will have their pick of the best roles in tech for the next decade.

[Harith M @harith_m1999]

@techxutkarsh Hi, can you pls share this document

[Harith M @harith_m1999]

@pbteja1998 Hi Bhanu, I have not built any agents as of now.
I bought few credits from claude can you share any resources or steps which I can follow to build agents and further orchestrate them!

[Harith M @harith_m1999]

@TommiPedruzzi AI

[Ankur Nagpal @ankurnagpal]

I wrote a 30,000 word Notion guide on every single tax saving strategy I wish I knew 3 years ago

Includes strategies for startup founders, business owners, freelancers, W-2 employees, side hustlers

Want a free copy? Like / RT and leave a comment and I'll DM you

[Harith M @harith_m1999]

@manoj_ahi Is this organic through SEO ?

[Harith M @harith_m1999]

@staticmaker1 How does it get traffic

[Arpit Bhayani @arpit_bhayani]

Knowing when to switch roles or companies significantly impacts your career growth and trajectory, and I have a simple 3P formula that can help you find the right time to switch.

1. Paisa (money)
2. Power (core competency growth)
3. Position (ladder growth)

At any company you are working at or switching to, you should get at least two of the three Ps. If you are getting fewer than two, it is time to switch.

1. Paisa (Money)

Monetary compensation is often a primary motivator for a job change. Consider a switch if your current role does not provide enough or if the increments do not keep pace with industry norms. If the other two Ps outweigh your average salary, it might be worth staying at the current company.

2. Power (Core Competency)

Power in this context refers to your growth in core competency and how close you are to becoming a subject matter expert in the domain in which you operate. Aim to become a really good engineer, and a good job will always present you with opportunities to become one.

Assess whether your current role challenges you, introduces you to new technologies, methodologies, or projects, and ultimately contributes to your professional depth and breadth. Again, if the other two Ps outweigh the lack of core competency, it might be worth staying at the current company.

3. Position (Ladder Growth)

The third P, Position, involves your upward movement in the org ladder. Your official title matters, and it dictates the roles and responsibilities you have handled. Hence, an important criterion to decide if it is the right time to switch or not.

Assess if your current job provides a clear and actionable path for promotion and increases in responsibility. Stagnation can often lead to your future employer doubting your abilities and will negatively impact your career growth.

Again, if the other two Ps outweigh the lack of ladder growth, it might be worth staying at the current company. Most people remain at an L5 at Google is an example of this.

I always evaluated my situation every six months and over-optimized for two of the three Ps. For example,

1. at Practo, I optimized for Power and Paisa
2. at Amazon, I optimized for Position and Paisa
3. at Unacademy, I optimized for Position and Power
4. at Google, I optimized for Power and Paisa

My entrepreneurial stint has been about optimizing for Position and Power with a hope for a high gain in the third P in the coming years.

To me, this has been a pretty structured framework to guide my thinking process, ensuring that my career decisions are both strategic and beneficial in the long run. Hope it helps you as well.

[Harith M @harith_m1999]

I first came across system in "Atomic Habits" but never got more out of it as I did not put in a actionable plan.

Hope this thread helps you to build your system!

https://t.co/xVq4WQNzbH

[Harith M @harith_m1999]

Just watched @DrJustinSung’s video on "How to Build Systems to Actually Achieve Your Goals."
Knew systems mattered — but his approach was a game-changer!
Here are my key takeaways:
🧵👇

[Harith M @harith_m1999]

3. Peel the Band-Aid
- You always have a approach to fast track the system you have laid out, avoid using it.
- The bypass that you take, does not help you in longer run.
- Anything that is a hindrance, create a new system to overcome it.

[Harith M @harith_m1999]

https://t.co/tpLjI2jLvX

[Harith M @harith_m1999]

Watched a 🔥 podcast this morning on @myfirstmilpod
"I was $15m in debt....now I'm rich"
Here is my notes:
- Profit is made on the buy, not the sell (selling = speculation)
- Make one thing work, then move on
- Persist don’t throw in the towel

[Harith M @harith_m1999]

- Those who’ve failed often persist longer than those who succeed early
- Find a strategy that works and position your business around it.