Your .env File Isn't Ready for AI Coding Agents

Your .env File Isn’t Ready for AI Coding Agents

I had been using Claude Code for a while when I decided it was time to audit everything that had accumulated around it: CLAUDE.md, permission rules, and the rest of the settings.

So I did what most of us would probably do. I asked Claude to help me review them.

One finding stood out:

“You have database credentials stored in your settings file.”

They were development credentials, and there had been no breach. But the way they got there exposed a flaw in my workflow.

Several times, I had asked Claude to connect to a development database and perform a specific task, telling it that the credentials were available in .env. Claude generated the command and asked for permission. I recognized the command and what it was intended to do, so I selected “Yes, always” to avoid approving the same operation repeatedly.

What I had not considered was how that approval would be recorded. The command was persisted after the credentials had been resolved, so the settings file contained the complete command—including the credentials in plaintext.

That was already a problem in development. But it immediately raised a harder question:

What happens when the issue you need help debugging exists only in production?

There will be cases where we want an AI coding agent to inspect logs, query a database, or trace an integration problem. That does not mean it should receive a production password or unrestricted credentials.

At that point, I stopped treating secrets as only a file-storage problem. Moving them from .env into another file would simply relocate the risk.

AI coding agents should be given the access they need, not the credentials that provide it.

That is the boundary this article is about.

Search Architecture Starts With Intent, Not Every Query Should Take the Same Path

Search Architecture Starts With Intent, Not Every Query Should Take the Same Path

When people talk about modern search, the focus often goes straight to the retrieval technology: embeddings, vector databases, BM25, semantic search.

But after working through the search architecture for a product catalog, I found the more important question comes earlier:

What is the user actually trying to find?

A natural-language query and a product identifier may enter through the same search box, but that does not mean they should take the same path through the architecture. That became the central design principle for us:

Search architecture should start with intent, then choose the retrieval strategy that fits it.

These two searches may come through exactly the same search box:

“waterproof black jacket for winter” vs. “JCK-4521-BLK”

But they are not the same search problem.

  1. The first is asking about meaning.
  2. The second is asking about identity.

And treating both the same way can make search worse, not better.

A working demo is only the beginning.

From “Can We Build It?” to “Will It Survive Reality?”

AI changed who can build.

It did not remove the need for judgment, it moved where judgment matters.

A few years ago, building a working application was itself proof of technical capability. Today, a non-technical person can describe an idea to an AI tool and have a surprisingly credible application running in a weekend.

That is a real shift, and architects should not pretend otherwise.

But it has also created a new assumption: if almost anyone can build software now, perhaps we no longer need the developers, architects, and specialists who used to make it possible.

I think that conclusion gets the change exactly half right.

The question is no longer whether you need an architect, but when.

AI makes experimentation cheaper and more accessible. That means more ideas can be validated, more prototypes can become real products, and more systems will eventually reach the point where architecture, judgment, and specialist expertise matter.

//ِbuild 2015 AR/ ملخص أخبار مؤتمر مايكروسوفت المدهشة. اليوم الأول – الجلسة التمهيدية

“دعم و تقوية جميع المطورين”
ساتيا ناديلا
المدير التنفيذي, مايكروسوفت
هكذا بدأ مؤتمر Build 2015 في جلسته التمهيدية. سأحاول تلخيص اهم ما تم ذكره في جلسة البارحة.

//build 2015/ Mind Blowing Summary! -1st Day keynote-

Empowering every Developer”
Satya Nadella,
CEO, MicrosoftThis is how Build15 Keynote 1st day started. Below I will summarize the most mind blowing keynote of yesterday session.

AR App with Wikitude SDK Using Cordova on Visual Studio 2013

Summary:

In this article we will see how to setup Wikitude SDK with Cordova on Visual Studio 2013.
we will use the official samples provided by Wikitude.

Make Your PC a Wireless HotSpot

Summary:Imagine this scenario:
you have wired internet connection, Your laptop connected to it and you want to connect your mobile also using wireless but you do not have wireless router?!!
There is some programs which will help you do that such as (Connectify). In this article we will see how we can do it with out any external program.

Instant Tracking Sample

 This is a sample project for using Instant Tracking.
SDK:                      Metaio
Render Software:  Unity3D
AI (Unity Plugin):   R.A.I.N AI Engine
Script Language:    C#

Marker Based Tracking Sample

 This is a sample project for using Marker based Tracking.
SDK:                      Metaio
Render Software:  Unity3D
AI (Unity Plugin):   R.A.I.N AI Engine

Microsoft Developers UAE Meetup #6 (Augmented Reality)

Augmented Reality

Recently technology is blending digital content into our real world and integrate our increasingly digitized lifestyle with our physical lives in a seamless, natural way to blur the line between what is real and what’s computer-generated by enhancing what we see, hear, feel and smell. Augmented Reality is the technic to make all that happens.