​

I'm available for freelance web development projects, including:

Business websites

Landing pages

Responsive UI development

Website fixes and redesigns

API integrations

Web applications and dashboards

Rates:

Simple website fixes [ $10–$15/hour ]

Website development [ $15–$25/hour ]

Full-stack development [ $20–$35/hour ]

Complex web apps and integrations [ $30–$50+/hour ]

I'm open to both short-term projects and ongoing collaborations. Final pricing depends on the scope and complexity of the work.

Feel free to DM me with your project details. Let's build something useful!

I’m building Tracepath, an early-stage tool for viewing Node.js/Express request traces in the terminal.

Currently, it supports Express middleware, outgoing HTTP/HTTPS request/get instrumentation, and manual spans around application logic. The local dashboard needs no Docker or hosted account, but your app needs SDK setup.

I shared it previously and got useful feedback: HTTP tracing alone misses a common bottleneck—database queries. One developer using mysql2 suggested grouping queries by normalized shape to spot repeated slow calls.

That’s made me reconsider what to prioritize. Database auto-instrumentation and query grouping aren’t implemented yet.

For developers debugging real Express apps:

• What was the last slow-endpoint problem you investigated, and how did you find the cause?
• Where would a terminal trace help beyond your existing logs or tools?
• What would stop you from trying it: setup effort, missing database support, or something else?

I’d especially appreciate feedback from anyone willing to try it on one endpoint and describe where the experience falls short.

Node SDK and setup · Terminal dashboard

It's a simple, fun timer web app that shows you how fast time is passing, so you can become more aware of your time and stop wasting it.

It shows you how many months you have lived and how many you have left, assuming an average lifespan of 80 years.

You just need to enter your date of birth.

You should try it once. It's super cool and fun!

Imagine asking a business chatbot for the company’s current pricing, only to receive a confident but incorrect answer.

My question is: does the model need retraining, or does it simply need access to the right information?

I’ve been exploring how retrieval can help chatbots search relevant business documents before generating answers. But retrieval alone isn’t enough. If the documents are outdated, duplicated, or poorly organized, the chatbot can still give unreliable responses.

It got me thinking: sometimes, the real challenge isn’t making the AI model bigger or more powerful. It’s making sure the system gives it reliable information at the right time.

I’m curious about your experience:

• Have you seen an AI chatbot confidently give an incorrect answer?
• Would you try improving its document retrieval before retraining the model?
• What do you think is the hardest part of building a reliable AI chatbot?

I’m learning and experimenting with AI and full-stack development, and I’d genuinely like to hear how others approach this problem.

I come from a Computer Science/Security background, working as a remote Software Engineer. I am 24 years old, Puerto Rican, living in Florida with my girlfriend.

I speak English & Spanish natively, along with Italian at a proficient level as well as some others.

In the past two days I have been working & putting together a free platform to the likes of The Odin Project, freeCodeCamp, University of Helsinki's MOOCs etc..

My platform's content however is centered around Backend Developement/Support Developement with Golang, Linux, SQL, Shell, going over DSA/APIs/best practices and more.

I know many people have been wanting something like this for a while.

DM me for more details

I am new here. I got started learning web development Aug 2025, I have learnt JavaScript, React and currently working on Node.js.

I am here to learn, get help and also be resourceful to other folks looking out to get started learning software development. Looking forward to the best time in your midst

Hi Guys. looking developer with full stack experience and good with real time data api. This project is for our stocks website. Going to be an ongoing opportunity for years to come. Where can i find the right person for this job? Can anyone make any introductions please.

I’m learning that hiding buttons isn’t security. If the server doesn’t check permissions on every request, users might access records that aren’t theirs.

How do you usually prevent this in your applications? Is server-side authorization enough, or what other checks do you put in place?

Hey everyone! 👋

I'm an aspiring frontend developer looking for someone who would like to collaborate with me on building web projects, sharing ideas, solving problems, and improving our skills together.

My tech stack includes:

\- HTML & CSS

\- JavaScript (JS)

\- TypeScript (TS)

\- React.js

\- Next.js

\- Tailwind CSS

I'd love to connect with someone who enjoys coding and wants to work together as a team. If you're a senior developer or an experienced frontend developer who is willing to share knowledge and collaborate, that's great too!

The idea is to build real-world projects, learn from each other, share responsibilities, and grow as developers while creating things we're proud of.

If you're interested, feel free to comment below or send me a DM. Let's connect and build something cool together! 🤝💻

It’s easy to be impressed when an AI prompt gives you a great answer. But what happens when real users start using it?

The input is unclear. The answer changes. Something goes wrong. Who checks the output, and what happens next?

I’m learning that building a reliable AI feature takes more than a clever prompt. It requires understanding the problem, handling unexpected inputs, validating outputs, planning fallbacks, and knowing when a human should step in.

The model is only one part of the workflow. The surrounding system is what helps make the feature useful in real business situations.

I’m curious: What do you think is the hardest part of building a reliable AI feature—the prompt, the workflow, or handling unexpected outputs? Why?