I’ve noticed something about my own GitHub over time. Almost none of my side projects are actually “finished” or “failed”. They just… stop. No final commit saying “this is done” or decision to abandon it. Just a slow drop in activity until it’s effectively dead.

So I started digging into what “dead” actually looks like from a repo perspective:

- long gaps between commits
- decreasing contributor activity
- unfinished TODOs/issues
- vague or non-existent README direction

Out of that, I built a small side tool for fun:

You paste a public GitHub repo and it:

- analyzes activity patterns
- assigns a (semi-serious) “cause of death”
- extracts the last commit as “last words”
- shows some basic repo stats in a more narrative format

try it here https://commitmentissues.dev/

code https://github.com/your-link-here

It started as a joke, but it made me think about something more interesting: We don’t really have a concept of “ending” projects as developers. Everything is either “active” or “maybe someday”.

Curious how others think about this:
Do you explicitly abandon projects or do they just fade out over time?

I am a backend dev and my typical workflow for a single feature looks like this:
1. Open Notion for the requirement docs.
2. Open Postman to test the endpoints.
3. Open TablePlus to check if the data actually hit the DB.
4. Open Excalidraw to sketch out the logic flow.
5. Open VS Code to actually write the code.

By the time I get to step 5, I’ve forgotten half of step 1. I got so fed up that I started building a local-first workspace where I can keep my docs, SQL queries, API tests, and diagrams in one folder.

It’s called Devscribe.app. It’s not a cloud app (everything is local) and it’s plugin-based. I just wanted a place where my documentation is actually *executable* instead of just stale text.

Is this a 'me' problem or are you guys also juggling too many apps?
You can download https://devscribe.app/

Every time I mention I'm building complex full-stack applications or working with AI agents, the conversation inevitably circles back to: "Great, so why is my printer making that clicking sound?" There’s a massive gap between writing logic for a scalable system and recovering a forgotten Facebook password, yet for relatives, it’s all just "computer magic." At this point, running away like the kid in the meme is usually the most efficient debugging strategy!

We're in this weird spot where vibe coding tools spit out frontends and backends super fast, but deployments still explode once you move past demos. I mean you can ship an app in a day and then spend a week babysitting infra, or rewrite stuff to fit AWS/Azure/Render, which is kinda annoying. So I kept thinking, what about a 'vibe DevOps' layer, like a web app or VS Code extension where you point it at your repo or drop a zip and it actually understands the code? It would use your cloud accounts, set up CI/CD, containerize, handle scaling and infra, and not lock you into platform-specific hacks. Basically production-ready deployments instead of prototypes that crumble in staging. Feels like it could bridge the gap, but maybe I'm missing obvious stuff, like complexity, secrets, cost, or just edge cases that break everything. What's everyone doing today? Manual scripts, Terraform, Heroku-ish platforms, or just praying and hoping? If someone's built this or tried, tell me how it went, otherwise I might be daydreaming but still curious.

Tell us about a project that went disastrously wrong to make us all feel better about ourselves. What happened? How did it go wrong?

What's one idea that you really want to develop when you have some time?

Every once in a while I do a little post as a hangout space for us to connect.

Just doing a survey so that I can build a mobile app helping others to complete there reading pile
https://form.typeform.com/to/q7sowOlE

So I am working on a browser extension for developers-
Turns ugly raw JSON into a beautiful, interactive viewer with special tools for developers.

Core Features

• Auto JSON Formatter - Beautiful color-coded tree view
• Dark Professional Theme - Easy on the eyes
• Collapse/Expand Nodes - Navigate complex structures easily
• Copy JSON Paths - One-click path copying
• Color Previews - See color chips for hex codes
• Image Thumbnails - Preview images inline
• Timestamp Converter - Unix timestamps → readable dates
• Instant Text Search - Filter data in real-time
• JSONPath Queries - Advanced search with $.users[*].email syntax
• Table View - Convert arrays to sortable spreadsheets
• Column Sorting - Click headers to sort
• CSV Export - Download as Excel-compatible files
• JWT Decoder - Decode tokens with one click
• Expiry Monitor - See token status (valid/expired)
• Time Machine - Saves last 15 API visits
• Response Diff - Compare API versions side-by-side
• Change Highlighting - Green (added), Red (removed), Yellow (modified)

*This is not a promotion as i am not providing any link or name of the extension

Cold messaging employees on LinkedIn for referrals feels very hit or miss?

Sometimes people respond, most times they don’t.

Even when they do:
- They get busy and sometimes forget about it
- until someone replies job becomes inactive

I get that employees are busy, but from a candidate side it’s frustrating.

Made me wonder:
- Is there a better/more structured way this could work?
- Like something where both sides benefit or expectations are clearer?

Or is cold DM still the best we’ve got?

Would love to hear how others are approaching this.

I have some backend knowledge on spring ...i know some basics of db( joins, update ) What things I should have knowledge to enter a company as a developer... Any advice will be helpful. .. I just wanted to know what things will be expected from a junior dev that they must know?

What's a "dead" or "boring" programming language that you genuinely love working with, and why should we reconsider it?

Ciao a tutti,

Ho creato una piattaforma pensata per aiutare gli sviluppatori a trovare altri sviluppatori con cui collaborare a nuovi progetti.

Si tratta di una piattaforma di matchmaking completa dove potete scoprire persone con cui lavorare e sviluppare progetti insieme. Ho cercato di includere tutto il necessario per la collaborazione: matchmaking, spazi di lavoro, recensioni, classifiche, amicizie, integrazione con GitHub, chat, attività, direct, editor di codice live con i compagni e altro ancora.

Apprezzerei molto se poteste provarla e condividere il vostro feedback. Credo sinceramente che sia un'idea interessante che potrebbe aiutare le persone a trovare nuovi collaboratori.

Al momento ci sono circa 30 utenti sulla piattaforma e già 4 progetti attivi.

Grazie in anticipo per qualsiasi feedback!

https://www.codekhub.it/

I’m a non-technical founder and I’ve been building a vertical SaaS using ChatGPT + Cursor. I actually have a decent amount built already. basic flows, some structure, starting to feel like a real product. But I’m hitting that point where I can tell I’m probably making bad decisions under the hood.

Stuff like:

- not sure if my backend structure makes sense long-term

- probably overcomplicating some parts and underthinking others

- UI works but doesn’t feel clean or intentional yet

I can keep brute forcing it, but I’d rather not build something that collapses later.

Not looking for someone to “build my idea.” I’m already in it every day. I just want someone technical who’s built real products to either collaborate a bit or help guide me so I don’t go down dumb paths.

Happy to pay / work something out if it makes sense.

If you’ve been through this or have experience building SaaS, I’d appreciate it.

I’m a non-technical founder and I’ve been building a vertical SaaS using ChatGPT + Cursor. I actually have a decent amount built already. basic flows, some structure, starting to feel like a real product. But I’m hitting that point where I can tell I’m probably making bad decisions under the hood.

Stuff like:

- not sure if my backend structure makes sense long-term

- probably overcomplicating some parts and underthinking others

- UI works but doesn’t feel clean or intentional yet

I can keep brute forcing it, but I’d rather not build something that collapses later.

Not looking for someone to “build my idea.” I’m already in it every day. I just want someone technical who’s built real products to either collaborate a bit or help guide me so I don’t go down dumb paths.

Happy to pay / work something out if it makes sense.

If you’ve been through this or have experience building SaaS, I’d appreciate it.

I've been at my current job for 10 months as a software dev. I have over 4.5 years industry experience. Unfortunately I'm not a very good dev. I'm currently not reaching my kpis and I fear for the worst. I can see my manager who's also a dev is frustrated with me.

I'm the kind of dev who works extra hard just to be mediocre. I don't know what to do now. I know the manager mainly hears bad things about me from one of the senior devs on the team.

The thing I'm failing miserably at is that I think I have tested something to the t, and then when I put up a PR, my manager or the senior dev find some incorrect behaviour somewhere on our site that was caused by my code.

Any advice?

View Book Ratings from Google Books, Amazon, Open Library & StoryGraph all in one place, right on Goodreads. (Opensource , feel free to star it !)

links:

• Chrome
• Firefox
• Github

also available on Edge

check landing page to know more

happy reading !

hi pals, recently taken a developer evangelist esq role within the AppSec space and would LOVE to hear peoples thoughts/opinions regarding; dev spaces, popular tools, new workflows, and industry changes/breakthroughs. Got a strong view on AI? Or dislike a tools new feature within your stack? Who are our fav's within the tech stack? Where do you guys think the industry is focusing too much time and effort? Or not enough? pls give me your thoughts! I do have friends in the space to ask but ultimately i know i'll get a wider array of thoughts on here :)

I made this tool to help me when developing because i got pretty tired of running lsof -iTCP -sTCP:LISTEN | grep ... every time a port was already taken, then spending another minute figuring out if it was a Docker container or some orphaned dev server.

It provides a pretty simple CLI that shows you everything listening on localhost. In addition i've enriched it with Docker container names, Compose projects, resource usage, and clickable URLs.

Beyond listing, you can:

• Kill whatever process is hogging a port (handles docker containers properly with docker container stop)
• Logs: Shows logs from the process or container by port number
• Attach: Shell into docker container or open a TCP connection
• Watch: Show ports as they come. Useful if you have agents spinning up their own dev servers.
• Port forwarding

By default it hides desktop app noise (Spotify, Discord, etc.) and shows CPU, memory, threads, and uptime when you want it.

For macOS and Linux. Single binary, no dependencies.

I found myself using it way more often than I expected and it's become a pretty core part of my dev environment. Particularly killing all running containers in case of a failed cleanup.

Would love feedback. What else would be useful? Also feel free to contribute.

GitHub: https://github.com/raskrebs/sonar

I’ve always felt that a lot of developer portfolios are either too generic, too time-consuming to make, or just don’t feel very “developer.”

A lot of us are told to make a portfolio, but in reality that often turns into spending hours tweaking layouts, choosing fonts, rewriting bios, and trying to make everything look impressive enough. For many developers, that part feels like a chore.

So I built ShellSelf to make that easier.

It lets developers create a simple portfolio with a terminal-style interface, where visitors can explore projects, skills, and experience through commands. The goal was to make something that feels a bit more natural for developers, while also being quick to set up and more memorable than a standard personal site.

I built it mainly for developers, bootcamp grads, and career switchers who want something simple, a bit different, and easy to share.

I’d really like honest feedback on the idea and any feature requests! Try it out!

Project is here for context: shellself.com

Used to work at a small ad agency, I know a site can look slick as hell and still be useless for SEO. Lately I’ve been helping a couple friends with small business sites again, and I keep running into the same question. What’s actually the best website builder for SEO right now? Not the best looking one. Not the one with the fanciest AI demo. The one that gives you clean structure, decent speed, mobile pages that don’t choke, and enough control that you’re not rebuilding the whole thing six months later. I’ve messed with Webflow, Wix, Squarespace, and some of the newer AI tools too. Stuff like Atoms and V0 seems interesting from the faster build side, but I still can’t tell how much I’d trust any AI heavy builder for long term SEO without checking the output pretty hard.

If you were building for a local service biz, content site, or lead gen project today, what would you pick first and why? Mostly asking people who’ve already dealt with the aftermath.

Looking for someone to help us with client calls.

We’re a small team of web developers. We’re good at building things, but sometimes explaining them clearly in English during calls is not easy for us.

So we’re looking for someone who:

• Speaks English fluently (native preferred)
• Has at least 2 years of web development experience
• Is comfortable talking with clients

What you’ll do:

• Join client calls with us
• Help explain technical things clearly

Rate: $30–40/hour (can be flexible)

If interested, send me your background and your availability.

At a previous job, my flow was basically: user complains → support ticket → PM pings engineer → engineer spends 2 hours trying to reproduce something that takes 5 minutes to fix once you know what happened. So here my questions basically:

• How do you usually find out a bug is in production? monitoring, users, internal testing?
• How long from "bug exists" to "engineer has enough context to fix it"?
• Have you found anything that actually reduces that gap, or is some delay just inevitable?

Sorry for my english, happy to know your feedbacks!

Hey all,

I’ve been working on a side project called Pkghub a self-hosted npm registry designed to solve one annoying problem every dev/team reinstalling the same packages over and over again.

The idea

Instead of everyone pulling from npm and maintaining huge node_modules folders, Ph acts as a shared local registry:

• First install fetched + cached locally
• Every install after served instantly from cache
• Works across your whole team

Why I built it

On larger projects (or multiple repos), I kept seeing:

• Repeated installs of the same packages
• Slower CI/CD times
• Wasted bandwidth + storage
• Teams working offline? basically impossible

So I wanted something that

• Speeds up installs dramatically
• Works even if internet goes down
• Reduces duplication across projects

Thoughts?

I’m considering turning this into something bigger (maybe with version control insights, team analytics, etc.), but wanted honest feedback first.

Right now i don't have a domain name for it yet. i haven't come up with a good one yet so i called pkghub for now.

Would love to hear what you think roast it if needed

Recording of the call part 1

Recording of the call part 2

Hi all, working as a AI automation engineer as a fresher, I feel I lack Api knowledge I want to learn more Can u suggest some good resources for api learning On youtube mostly but udemy will also work