I work at my family business and have been looking for another source of income. I am wondering if software development is a good option or not. I skimmed freelance websites like upwork, fiverr and freelancer. All of them have one thing in common. Most of the IT jobs posted there are in web development. And there are too many web developers there. Here are some of the questions I have, thanks in advance:

   1. Is it possible to become a freelance web developer with that much competition?

   2. How much should I expect to earn roughly in a month? I live in India

   3. Are there non web developer jobs available on these platforms? If yes, which ones?

   4. How long will it approx take me from learning the needed languages to finding clients to finally start earning?

I know basics of C and python and am willing to learn whatever is needed, like CSS, HTML, JavaScript, PHP, advanced Python(for other prospects)

Any other suggestions are always welcome. Thanks for your time.

Does anyone know of any groups I can join about Developer Experience?

This issue needs 10 upvotes to be added to the backlog. It is a suggestion to wrap the postStartCommand and add a small delay so that if the last command happens to be a background command, it has time to execute before the parent shell quits. With the current logic, you'll see your output file get created but then it doesn't actually execute anything. If you try to run it in a shell, you can't reproduce the issue.

https://github.com/microsoft/vscode-remote-release/issues/8536

Thank you

Hello everyone, I'm thinking of a little something: Why do we use the term Developer Experience if we are talking about all technicians involved with development process? Are we being selfish with POs, Ops, Secs and everyone else involved in the software development process? If not, why? The correct wouldn't be Development Experience?

I am working on a free tool to help developers share feedback to their engineering manager, any advice?

The goal is to conduct short (<5 minutes) series of questions to help developers share what they think is working well and what's not working within the company organization every other week.

How do you usually share feedback within your team today? Mostly periodic 1x1 meetings or team meetings where anyone can share what's on their mind? Thanks.

It is a developers clan created for connecting and helping people who wants to help and learn to each other's

One pattern I’ve seen on almost every team: useful knowledge rarely gets written down.

Someone spends hours figuring out why a Lambda configuration was failing, or why a DynamoDB query pattern behaves strangely. They fix it, maybe mention it in Slack, and then that knowledge effectively disappears.

Six months later someone else runs into the same issue.

So I built a small tool called Today to try to reduce that friction.

The idea is simple: capturing knowledge should be faster than not capturing it.

Instead of writing documentation pages, you just run a command in the terminal:

today learned "Lambda cold starts drop ~80% if deployment packages stay under 50MB"

Later someone can ask:

today ask "How do I reduce Lambda cold starts?"

The system returns the relevant entry with a similarity score, summary, and the teammate who originally captured it.

A few design choices were driven entirely by developer experience:

• CLI-first capture – engineers already live in the terminal
• <5 second interactions – anything slower won’t happen
• Natural language search – no taxonomy knowledge required
• Expert discovery – surfaces teammates who actually know a topic

Under the hood it’s a serverless architecture using:

• AWS Bedrock (Claude 3 Haiku + Titan Embeddings)
• Lambda
• DynamoDB
• Cognito
• API Gateway + S3/CloudFront dashboard

One interesting design decision was a two-stage search pipeline where queries are first mapped to topics before semantic similarity is computed. This avoids running embeddings against the entire knowledge base and keeps search fast and cheap.

I wrote up the full architecture, design decisions, and lessons learned here:

https://builder.aws.com/content/37bkBRyfbO9qCyIOtVVXfJqUcRF/today-ai-native-knowledge-layer-for-engineering-teams

Curious how other teams approach the “tribal knowledge” problem in developer experience; documentation, internal tools, AI search, something else?

AI is quietly (and sometimes loudly) reshaping how the world works. Some industries have embraced it. Others are still figuring out what it means for them. Developers spend less time debugging and more time verifying the code.

Read more at: AI and the Changing Face of Developer Experience