r/devworld

Curious to know what the most useful marketing tip is for everyone. Would be great to combine the knowledge of everyone. Obviously we all build something amazing, but how we get it to the right users is the most difficult task.

I typically use ChatGPT for developing ideas, brainstorming, and planning, and then take the concept to Codex to implement.

However, the context switching was always lossy because there was never an easy way to export my entire convo.

So, to solve this, I created a simple utility that takes in a conversation share link and outputs an md and/or json files, or you can one-click copy the entire conversation.

It’s stateless so none of your data is saved or used for anything.

Check it out!

Try to describe your app/website in one sentence in this format: App/Website name - Description

I will go first

Tructivity - helps students organize their academic and personal lives in one platform without the cognitive drain of app-hopping

Learned this one the painful way.

Heroku rotates DATABASE_URL during certain maintenance events.

If you've hardcoded that value anywhere instead of reading it from the environment, your app can randomly stop talking to the database after maintenance.

Nothing's "broken."

Your code is.

It's one of those infrastructure gotchas you only learn after losing a few hours debugging.

What's the most expensive infrastructure lesson you've learned the hard way?

Mine was this.

I'd love to hear yours.

Hey everyone,

I’ve been building Linxalium — a curated directory for tools, apps, SaaS products, dev utilities, and useful online projects.

The idea is simple: most makers know they need visibility, but big directories often feel noisy. You submit once, get buried, and the listing becomes another dead profile page.

I wanted to build something smaller and manually reviewed, where each project gets a clean public record with:

• category
• description
• logo / screenshots
• project link
• backlink
• optional project story / blog-style page

Current status:

• registration is open
• creating a project listing is free
• every submission is reviewed manually
• the domain has already reached DR 16 in Ahrefs
• approved projects get a public listing page
• I’m still improving categories, review rules, and discovery

I’m keeping submissions free during this early stage while I grow the directory and learn what founders/developers actually need. Some faster publishing / featured options may become paid later once the review queue grows, but right now builders can register and submit for free.

Site: https://linxalium.com

Would love feedback from other developers and indie builders:

Does this feel useful, or does it still look too much like “just another launch directory”?

I've been building an AI contract review tool over the last few weeks.

The goal isn't to replace lawyers. It's simply to help people understand what they're agreeing to before clicking "I Agree" or signing a contract.

Recently, a Reddit user tested it with a real contract and gave feedback that completely changed my roadmap. They pointed out that:

• My product name wasn't unique, so I rebranded it to Trothix.
• The current text limit is too small for many real-world contracts.
• PDF upload is far more important than I originally thought.

I've already shipped the rebrand and I'm working through the remaining feedback.

Now I'd love some developer perspectives before I keep adding features.

A few questions:

• Does the UI feel trustworthy?
• Is the workflow obvious from the homepage?
• What would you improve before I build more features?
• If you were building this, what would you prioritize next?

If anyone wants to try it, I'm happy to share the demo in the comments rather than putting a link in the post.

I'd genuinely appreciate honest feedback, whether it's about the product, UX, or technical direction.

First I hate the word 'Engineering' but this what everyone is calling themselves nowaydays but it's innacurate, or real career was always called "Programming" - but that's another topic.

I have around 10 years of exp in the industry.

There's tremendous signs that this career will die, maybe not soon, but it is obvious, and all counter-arguments are not convincing to me.

Sign 1:

• CS major enrollments are in decline, just google it, it's collapsing.
• Cope: "But this is a good thing, it means that the industry is re-aligning itself".
• My anti-Cope: Nope, it's a sign that this industry is very scary now.

Sign 2:

• Companies not hiring juniors anymore.
• Cope: "Yes, but the demand on seniors now is more than ever!"
• My anti-cope: First, this is ***** selfish, second, half of you seniors will be next not to be hired.

Sign 3:

• Historical layoffs.
• Cope: "IMAO LOLLOL, these layoffs have nothing to do with AI, it's because of Covid hire inflation"
• My anti-cope: Sure bro, keep lying yourself, even the big corporates themselves are admitting they're laying off for AI, either as replacement or for further investment, but the end result is the same.

More coping arguments:

• "Yeah, but eventually corporates will wake up and realize how much vibecoding/Ai-driving programming is prone to disasters, and programmers will be in demand more than ever, VICTORY WILL BE FOR US".

My anti-Cope: Yeah, sure, do you really believe that c-suite people really care about code quality? They care about promising clients and delivering too fast no matter what. And even if this eventually happens, it will be too late already, how long it will take for these corporate to "wake up"? 10 years? 15 years? By this time, many seniors would be retired already, and juniors never even had the chance to acquire the know-how to fix those problems; it's like the moon-landing, the humanity is struggling to do the moon landing again because the know-how hasn't been transfers to the next 2 generations, a lot of things lost forever, this what may happen to programming. Besides, there's no guarantee that the AI "tools" will never get so much better to the point that this will no longer be a problem - I mean, everyone was laughing 2 years ago at the idea that manual coding will be taken over by AI, but here we are.

• "Yeah, but bruuuh, maybe only manual coding is dead, but SYSTEM DESIGN, and SOFTWARE ENGINEERING (roar, engineering), and CODE REVIEWING, and collecing and writing requirements are still important skills tha will never be taken by AI.

My anti-Cope: Stop lying to yourself, it's not only the manual coding which is dead (which is the most fun part); but everything else is dying too, due to the higher expectation in deadlines, NO ONE has time to do manual PR Reviewing, NO ONE has dtime to do manual System Design, or any sort of "software engineering"....hell, I come across many stories all the time on Jira/Clickup all filled with long dashes; purely generated by AI; nothing is being done without AI; and there's no guarantee in the future that the AI will get so good in listening as well, the CEO just talks to him and gives him vague orders what to do, and will give resuls.

"Before I build anything, I want to understand your real frustrations first"

I'm at the beginning of my journey of building software. I know I want to build something meaningful, but I don't want to just pick a random idea out of thin air I want to start with a real problem that real people actually face.

So before I write a single line of code, I want to ask you directly:

What's something in your workflow that wastes your time every week? Maybe no good tool exists for it, or the ones that do are too expensive, too complicated, or just don't quite fit how you actually work.

Could be something tiny and repetitive. Could be something that's been annoying you for years. Doesn't matter I want to hear it.

And if your problem resonates with me and feels like something I can genuinely solve I'd love to have a quick casual conversation with you, just a few messages or a short chat, so I can understand it better from your perspective. The goal is to build something that actually fits your situation, not just a generic solution.

No pitch. No agenda. Just someone trying to start their journey the right way by listening first.

What's frustrating you?

I built a Swagger-like Developer Portal for Frappe 🚀

https://github.com/raisulislam0/frappe\_doc

One thing that always frustrated me while developing in Frappe/ERPNext was API discovery.

Need to call a whitelisted method?

Search through source code

Figure out the full module path

Guess parameter names

Check if it expects GET or POST

Open multiple tabs to inspect DocTypes and child tables

So I built frappe_doc.

It's a Frappe app that automatically scans all installed apps and generates a live developer portal from your codebase.

Features

✅ Discover all @frappe.whitelist() APIs automatically

✅ Parse Python type hints and Google-style docstrings

✅ Search APIs by app, module, route, arguments, DocType, etc.

✅ Generate ready-to-copy frappe.call() and curl examples

✅ "Try It Out" functionality to execute API calls directly from the UI

✅ Explore DocType schemas with expandable child-table trees

✅ AST-based scanning (doesn't import or execute your code)

✅ Works with custom apps and ERPNext out of the box

Example

Instead of searching through code to find:

@frappe.whitelist() def apply_for_leave(...): ...

frappe_doc automatically generates:

API route

Parameter documentation

Return information

Example requests/responses

Interactive testing form

Frappe JS snippet

cURL snippet

DocType Explorer

One feature I'm particularly happy with:

Child tables are displayed as expandable trees, so instead of jumping between multiple DocTypes, you can inspect the entire document structure in one place.

Example:

Sales Order └── Items ├── item_code ├── qty ├── rate └── warehouse

Why AST?

The scanner uses Python's ast module rather than importing modules, which means:

No code execution

Safe on production servers

No side effects during scanning

Looking for feedback

Would this be useful in your workflow?

I'm interested in hearing:

Features you'd like to see

Limitations you encounter with Frappe APIs today

Whether you'd use something like this in production

GitHub: https://github.com/raisulislam0/frappe\_doc

Feedback and contributions are welcome!

Hi guys!! I have a personal website for my extremely small team of 3 members.

I dont have any serious comission or professional work in mind so far so its abit unprofessional and undone for now!!

its https://xtrcom.xyz

rate it and let me know what do you think!!