Skip to main content

The Pause Was Unplanned. The Return Is Intentional

 Why I stepped away, what I learned, and where this blog goes from here.

Returning After a Long Absence — And Why It Matters

It has been quite some time since I last published here, and I think that deserves a straightforward acknowledgment before anything else.

Over the past years, my attention was pulled in several directions — professional commitments, ongoing projects, and the kind of sustained workload that quietly pushes non-urgent priorities to the back of the queue. Writing, unfortunately, became one of them.

What I did not anticipate was how much I would miss it.

This space was built on a simple premise: to share ideas, perspectives, and insights worth putting into words. That premise has not changed. If anything, the time away has given me a clearer sense of what I want this blog to be — more intentional, more focused, and more consistent.

I am not returning with a promise of a rigid posting schedule or a dramatic reinvention. What I am returning with is a renewed commitment to showing up here regularly and contributing something genuinely worth your time.

There is no shortage of topics I have been meaning to write about. Consider this post the first step toward doing exactly that.

Thank you for your patience, and welcome back.

— Dhaval Parmar

Comments

Post a Comment

Popular posts from this blog

Why Domain-Specific AI Agents Beat One Big Agent

Everyone is building agents right now. Real estate firms. Independent insurance brokers. Fortune 500 companies with budgets big enough to hire an army of consultants. Ask around and you'll hear the same story everywhere: "we're building our own agent." And yet almost nobody is asking the obvious question: why does the default approach keep failing? One large, general-purpose agent gets wired up to every tool the business owns. It impresses in the demo. Then it quietly stalls before production. There's a gap between what businesses want and what they're actually getting. They want AI woven into their data, their workflows, their day-to-day operations. What they get instead is one oversized agent trying to be a sales rep, a compliance officer, and a customer support line, all at once. That gap is an architecture problem, not a model problem. Key Takeaways The default "one big agent" pattern breaks down on context bloat, cost, fragility, and portability...
Post a Comment
Read more

Stop Babysitting your AI Coding Agent Every Single Session

  Watched a video by DSquaredLabs on " No more re-explaining: Give your AI agent a memory graph " — here's what stuck with me and why I think this three-tool system is worth your attention If you work on a large codebase with AI coding tools, you already know the ritual. Open a new chat, paste your file structure, explain your stack, describe how the modules connect — and repeat the whole thing tomorrow. It is not a minor inconvenience. It is a compounding productivity tax that gets worse as your project grows. This article breaks down a three-tool system designed to fix exactly that. If you want the full walkthrough with a live demo on a real monorepo, the video at the bottom covers everything in depth — but the core concepts are worth understanding before you dive in. The Problem With How Most Developers Use AI Today Most AI-assisted coding workflows are missing three things that every good engineering team actually has: A map of the codebase A process for how w...
Post a Comment
Read more

ANDROID - update status Linked-IN

jars: 1. linkedin-j-android.jar 2. scribe-1.3.1.jar MainActivity: package com.testshare; import java.util.EnumSet; import org.scribe.oauth.OAuthService; import android.app.Activity; import android.content.Intent; import android.os.Bundle; import android.util.Log; import com.google.code.linkedinapi.client.LinkedInApiClient; import com.google.code.linkedinapi.client.LinkedInApiClientFactory; import com.google.code.linkedinapi.client.enumeration.NetworkUpdateType; import com.google.code.linkedinapi.schema.Network; public class TestshareActivity extends Activity { private int LINKEDIN_OAUTH_RESULT_CODE = 4000; private OAuthService service; private static final String PROTECTED_RESOURCE_URL = "http://api.linkedin.com/v1/people/~"; /** Called when the activity is first created. */ @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(...
9 comments
Read more