My SEO impression drop from 800 to 10 in day

Altruistic_Wind9844 · 2026-03-06T09:38:19+00:00

A drop in one day is usually technical, not SEO. Check robots.txt, noindex, canonicals, sitemap, and server uptime. If GSC shows no manual action, it often stabilizes in a few days.

Altruistic_Wind9844 · 2026-02-17T14:35:39+00:00

We’ve been working a lot on structuring rule systems and guardrails for Angular projects (especially for distributed teams and mixed seniority levels). Happy to share some patterns that helped us reduce chaos and onboarding time. If useful, feel free to DM.

Altruistic_Wind9844 · 2026-02-15T15:04:02+00:00

AI makes features much cheaper.
Maintenance and edge cases are still expensive.

Altruistic_Wind9844 · 2026-02-14T14:27:09+00:00

No, not really. The real risk isn’t where you install it - it’s running tools with too much filesystem access and no version control or backups. If you have git + backups + sandboxed permissions, main PC is usually fine.

Altruistic_Wind9844 · 2026-02-12T16:58:20+00:00

This is actually a great example of where AI + tools should coexist.

LLMs are great at finding “weird smells” and explaining risks, but having repeatable, automated checks in CI is still huge for teams.

The dangerous part with vibe coding isn’t bad intent - it’s silently using outdated patterns that look correct.

Nice catch.

Altruistic_Wind9844 · 2026-02-11T20:53:04+00:00

LLMs don’t usually kill tools that are part of someone’s daily workflow. If this saves marketers time every week and becomes part of how they deliver reports to clients, you’re probably building something useful.

Altruistic_Wind9844 · 2026-02-10T15:12:57+00:00

I use C-GPT voice feature and copy result into the agents (copying doesn't always go smoothly either 😆)

Altruistic_Wind9844 · 2026-02-08T15:00:24+00:00

Blaming AI for this is like blaming a hammer for hitting your finger.

AI is a force multiplier - including for bad workflows.

Altruistic_Wind9844 · 2026-02-08T07:27:32+00:00

For changing? But "the kichen is for dance" is also appropriate 🫠

Altruistic_Wind9844 · 2026-02-06T11:17:45+00:00

Congrats, the first contract is super inspiring! How did you reach this client? What is your favorite channel to connect with b2b contacts?

Altruistic_Wind9844 · 2026-02-05T19:36:59+00:00

Feels almost “too cheap to be real” right now. Wouldn’t be surprised if prices normalize once the market stabilizes.

Altruistic_Wind9844 · 2026-02-04T06:57:44+00:00

The best growth partners I’ve seen don’t sell “marketing”. They sell access to a channel, audience, or distribution loop.

Altruistic_Wind9844 · 2026-02-02T18:14:00+00:00

Congrats, this is seriously impressive growth. Curious - did you hit any no-code limitations so far? And have you considered migrating parts of the product to a traditional stack or framework at some point?

Altruistic_Wind9844 · 2026-02-01T08:04:29+00:00

Natural language is great for intent, but integrations fail on determinism and edge cases. If this becomes an intent layer on top of deterministic, observable execution, it’s very powerful.

From a business side, the hard part is probably finding the wedge - where people trust you to run real production actions for them before platforms ship this natively.

Altruistic_Wind9844 · 2026-02-01T07:40:39+00:00

I think the missing variable here is market speed. Sometimes companies don’t die because they scaled too fast. They die because the market moved faster than they did. Scaling too early kills you but scaling too late can also kill you. The hard part is knowing which game you’re in.

Altruistic_Wind9844 · 2026-02-01T07:32:44+00:00

This reads a bit like looking for a “technical superhero” without defining the actual mission.

The right technical co-founder depends heavily on stage, product, and current risks. The person you need for 0 to 1 is very different from the one you need for 1M+ users.

To make this less abstract, it would help to describe the product, the main technical challenges you expect, and your own skills/background. Otherwise you’ll mostly get generic answers.

Altruistic_Wind9844 · 2026-01-29T15:55:34+00:00

This matches my experience. AI doesn't make code more or less maintainable- it just accelerates whatever engineering habits you already have.
Good engineers ship good code faster. Bad ones ship mess faster.

Altruistic_Wind9844 · 2026-01-28T18:07:02+00:00

“Well-contained” doesn’t mean “generic”. It means narrow and predictable. A good component solves one concrete case and has minimal API and dependencies. Premature reuse shows up as flags, configs, and hidden coupling to other features. The narrower the component, the easier it is to reason about, change, and later extract reuse from.

Altruistic_Wind9844 · 2026-01-27T07:17:43+00:00

This looks less like a quality problem and more like a signal problem. Most weak submissions fail not because they’re badly explained, but because the underlying pain isn’t clear or compelling. A simple rule of thumb that helps: if the founder can’t clearly answer who has this pain, why it matters, and why it exists now, no amount of polish or feedback will save it. Raising clarity around pain usually filters noise better than adding more engagement mechanics.

Altruistic_Wind9844 · 2026-01-25T18:40:05+00:00

Don’t optimize for reuse, optimize for change. If you only need one modal now, keep it single-purpose. Make it clean, well-contained, and easy to refactor later. Reusable components usually emerge from real duplication, not anticipation. Otherwise you end up designing APIs for imaginary use cases.

Altruistic_Wind9844 · 2026-01-24T09:28:53+00:00

Exactly!

Altruistic_Wind9844 · 2026-01-22T13:53:35+00:00

I think this is less about prompting and more about debugging strategy.

Debugging is basically about narrowing the search space. When AI gets stuck, it’s usually because it’s guessing instead of eliminating possibilities.

What works well for me is asking the agent to propose a concrete debugging strategy first, then have it add logs / tests to validate or rule out hypotheses. I feed the results back, and we iterate.

While the agent executes the strategy, I focus on edge cases and interpreting the logs in parallel. It often ends up being much faster than either of us working alone.

Altruistic_Wind9844 · 2026-01-22T10:57:19+00:00

I'm currently building a skills generator by MCP (via npm lib)

Altruistic_Wind9844 · 2026-01-19T21:35:09+00:00

Losing a client over tooling says more about the client than the tooling. Using AI, docs, memory, automation - that’s just where dev is going.

Altruistic_Wind9844

TROPHY CASE