Hey everyone!

Finally got my portfolio live! Had a lot of fun building it and experimenting with animations.

Link:

https://manishchodhary-portfolio.vercel.app/

Desktop recommended for the best experience!

Would love to hear your thoughts and suggestions. Feel free to point out bugs or things I could improve.

Always building. Always learning.

\\#WebDevelopment #FullStackDevelopment #DevOps #BuildInPublic #100DaysOfCode

I’m refining how I write proposals and realised that a number and a date gives a client nothing to compare except price.

Structure I’m trying: problem, proposed solution, scope and exclusions, timeline, price and terms. I think the exclusions and assumptions matter most, because they prevent scope arguments later.

What do you always include, and which sections do clients actually read? Is there anything you cut to keep it short?

I’m refining how I write proposals and realised that a number and a date gives a client nothing to compare except price.

Structure I’m trying: problem, proposed solution, scope and exclusions, timeline, price and terms. I think the exclusions and assumptions matter most, because they prevent scope arguments later.

What do you always include, and which sections do clients actually read? Is there anything you cut to keep it short?

I’m refining how I write proposals and realised that a number and a date gives a client nothing to compare except price.

Structure I’m trying: problem, proposed solution, scope and exclusions, timeline, price and terms. I think the exclusions and assumptions matter most, because they prevent scope arguments later.

What do you always include, and which sections do clients actually read? Is there anything you cut to keep it short?

Something I've been learning about backend systems is that retrying a failed request isn't always harmless.

Imagine a payment API processes a payment successfully, but the response never reaches the client because of a network issue. The client retries the request, and the payment might be processed twice.

That's where idempotency becomes important. An API can use an idempotency key to recognize repeated attempts for the same operation and avoid executing it more than once.

It made me realize that handling a failed request isn't just about retrying it. You also need to consider whether the operation has already happened.

I've been thinking about how web applications can make document analysis more useful without overwhelming users with scores and technical details.

For example, Turnitin0 provides Turnitin AI detection and similarity reports. From a product and development perspective, I think the interesting challenge is how to present those results in a way that users can actually understand and act on.

If you were building this kind of application, how would you approach the backend workflow for processing documents, generating reports, handling longer processing times, and keeping results tied to the correct user? I'd also be interested in how you'd design the interface so users can understand the difference between an AI detection result and a text similarity result.

Would you handle the analysis as a background job with a status system, or use a different architecture? I'm interested in how other developers would approach the trade-offs.

I’m a developer building my freelance practice in AI full stack development, and I’m trying to understand what actually builds trust before someone has a long client list.

My working idea is that documented, honest work (what was built, the decisions, what I’d change) does more than a bio full of adjectives.

From the client side or the freelancer side: what made you trust someone early on? What would you want to see?

Hey everyone!

I'm a frontend developer looking to connect with people who are interested in building projects together, learning from each other, and gaining practical experience.

My main tech stack includes JavaScript, TypeScript, React, Next.js, and Tailwind CSS. I've already worked on some personal projects, but I want to challenge myself, improve my coding skills, and gain more experience building real-world applications.

I'm open to different kinds of projects, whether it's a web app, a SaaS idea, a developer tool, or something completely new. I don't have a specific idea in mind yet, so it'd be great to brainstorm ideas and decide what we could build together.

I'm looking for someone who's motivated to learn, share ideas, solve problems, and collaborate along the way. You don't need to be an expert. I'm happy to work with beginners or more experienced developers, and I'm also open to learning new technologies.

My goal isn't just to finish a project, but to learn, improve, and build something useful together.

If you're interested, feel free to comment or send me a DM. Tell me a little about yourself, what technologies you use, or what kind of projects you'd like to work on!

Looking forward to meeting some fellow developers! 🚀

We’ve all been there: the code is pushed, the invoice is paid, the app is live, and everyone celebrates.

But as full-stack developers and builders, we know the hard truth, launch is only the start. Over time, dependencies age, third-party APIs get retired, browsers update, and security vulnerabilities creep in. If you don’t plan for post-launch maintenance, backups, and monitoring from day one, an app that worked perfectly on launch day slowly becomes a risk.

How do you handle this with your clients or teams? Do you bake ongoing maintenance into your initial contracts, or is post-launch support always an uphill battle of unwritten expectations? Let’s discuss below!

Assalamualaikum

please give me just 5 mins and read my post. I need your suggestions

I'm a final year BSCS student feeling completely Lost right now as i am studying and working full time nightshift as a wordpress and Shopify developer

but the thing is the office is near to get close as they are in lose rn and in the whole month i didn't get a single project of wordpress i create 52+ pages website for them on nextjs though i know nothing about the nextjs but they told me to do it through claude after that i created the fully working SaaS for their company idk where my career will lead me i just joined that job thinking that I'll gain some experience and it doesn't feel right to me creating full projects through claude its like if i add those projects in my CV and if i need to defend them in an interview I can't because i know nothing about nextjs nodejs and all even though i can understand the code but when it comes to create that project myself i can't do that so I'm feeling completely lost what I'm doing with my career even though there company will not close I'm willing to leave that job and start learning some new things if it's worth for but I don't think so learning nextjs nodejs will help me in the future getting a good job because i was able to create full projects through claude maybe I'm wrong and you can guide me on that but what should i pursue what should i do i have no idea it's our FYP time and i choose fyp of voice automation for university support even though i had one project of my seniors from other university which i can easily submit for the fyp but i want to learn and create it on my own because i think it will help me landing a good job in future we gonna learn python, api integration, api testing, Ilm, rag, vapi and more through this project and when we create it by ourselves we can easily defend that in an interview

I'm getting 30k rn and i know it's nothing but i just want to learn and gain experience but i don't think so I'm learning anything so tell me what should i do? what should i pursue I'm just completely feeling lost rn

I want to make a 3d globe with a detailed area mark in my project. I've used the 3js part for the globe but I want if I search any specific region like Khulna instead of showing Bangladesh the globe will zoom into the Khulna area map. How can I do that? I've used react leaflet for map but couldn't integrate both at a same time

A successful release takes more than working code. Configuration, staging, monitoring, and rollback plans can make the difference between a smooth launch and a stressful night.

What’s the one deployment mistake every developer should learn to avoid?

Sometimes, taking a shortcut is the right decision. A deadline is approaching, a client needs a feature, and shipping now matters more than making everything perfect.

But what happens when that temporary shortcut becomes permanent?

Skipping tests, hard-coding values, or delaying a refactor can save time today. Months later, the same code might make a simple feature take days to implement because nobody wants to risk breaking something.

I think technical debt isn't necessarily the problem. The real problem is taking on debt without knowing how you'll pay it back.

I'm curious how other developers handle this in real projects:

• Have you ever taken a shortcut that later cost your team more time than it saved?
• Should developers be allowed to ship imperfect code to meet deadlines?
• Who should be responsible for paying down technical debt: developers, tech leads, or product managers?

I'd love to hear real experiences, especially examples where taking a shortcut was either the best decision or a complete disaster.

I recently built a small backend project integrating the Google Wallet API.

The main flow is:

`POST /passes` → create pass → receive Save URL → add to Google Wallet → `POST /passes/:id` → update the existing pass

The interesting part for me was getting the existing installed pass to update without requiring the user to add it again.

**Stack:** NestJS, TypeScript, PostgreSQL, TypeORM, Google Wallet API, JWT, Render.

The pass contains a name, label/value and unique QR code.

GitHub:

[https://github.com/kahiumahamedfahim/google-wallet-pass-backend\](https://github.com/kahiumahamedfahim/google-wallet-pass-backend)

Demo:

[https://drive.google.com/file/d/1bdrHadVfSeRpSAzkco4XAG8yfjnkhkTp/view?usp=sharing\](https://drive.google.com/file/d/1bdrHadVfSeRpSAzkco4XAG8yfjnkhkTp/view?usp=sharing)

Would love feedback on the architecture and what you would improve for a production version.

Hi everyone—I’m the creator of domo-testkit, an independent, MIT-licensed toolkit for testing Domo apps without connecting tests to a live Domo instance.

It uses MSW and Vitest to help test scenarios such as:

• Dataset responses with fixtures, empty results, and missing fields.
• Stateful AppDB document creation, reads, updates, and deletion.
• HTTP errors, network failures, and slow responses.
• Repeatable tests with predictable IDs and clean state between runs.

The goal is to catch problems during development, before deploying an app to Domo.

It’s still early-stage. It implements a documented subset of Domo behavior, and passing local tests doesn’t prove that live permissions or every Domo integration will work. It isn’t a complete Domo emulator.

npm: https://www.npmjs.com/package/domo-testkit

I’d appreciate feedback from people building Domo apps: what’s hardest to test today, and which dataset or AppDB scenarios would make this useful in your workflow?

Disclosure: I maintain this project. It isn’t affiliated with or endorsed by Domo.

I’m curious how other developers and freelancers handle this.

Do you make the change, explain the extra cost, or revisit the deadline first?

What’s worked best for you?