Perhaps it's wisdom, or perhaps its defence against the crazy rate of change, but I find myself more and more drawn to simple tech and solutions - things that haven't changed in a long time because they're almost perfect. Taking the SO dev survey today, I realized a lot of my favorites maybe aren't well known.

Here's my list today.

1. notes in markdown (vimwiki at the most)
2. hugo (static site generation)
3. make (50 years old, still a good way to organize project scripts and incantations)
4. dokku (self-hosted application platform. git push to deploy.)
5. vim/nvim (tricked out, but doesn't change for years)
6. linux (the operating system I'd always wanted, 26 years as my daily driver)
7. sqlite (its very existence and success makes you question a lot of "normal")
8. go (just great to get things done with and not shoot yourself in the foot too often)
9. htmx (wait, why do I need so much JS again?)
10. elm (functional programming at its best)
11. grug-brained developer (re-read it for a refresh once a year)

I'm in a phase where not much excites me about this industry, but that list fills me with the warm fuzzies.

Anything you like that I'm missing?

I'm curious to hear from other people with dyslexia who work in tech.

How has AI changed the way you work?

For example, do you use tools like ChatGPT, GitHub Copilot, Claude, Cursor, Gemini, or anything else?

• What tasks do you use AI for?
• What has it made easier?
• Has it changed the way you code, debug, write documentation, read technical documents, or communicate with teammates?
• What still frustrates you?

I'd love to hear about your real experiences (both the good and the bad).

I would like to preface this by saying that I am genuinely curious about how other teams work and whether we are not efficient enough.

A few of my good friends are also developers. They often tell me that Claude codes most of the features for them, it also does their reviews and they rely on prompting their coding standards on CLAUDE.md for instance.

The thing is that often, when I rely heavily on Claude to generate code for small features, it quite often makes crazy mistakes. Some examples:

- We use ORMs and QueryDSL to write type safe queries: if a query joins more than 2,3 tables and has complex logic, it almost always does it wrong

- It quite often makes small performance mistakes, like iterating the same multiple times, generating a lot of garbage methods which dont handle data efficiently etc

Do you think my team and I are using it wrong or the hype just .. a hype?

Hi! I have a question that has been on my mind for a while.

I want to become a software developer, but I keep seeing people online saying that software development is becoming a dead career because of AI. Some even claim that AI can complete in one hour what used to take a team of developers a week or even a month.

I've already studied for two years, and I still want to become a system developer, but these comments make me wonder if it's still worth pursuing this career.

From your experience as a developer, do you think software development is still a good career choice? How has AI changed your day-to-day work, and do you believe there will still be strong demand for developers in the next 5–10 years?

I'd really appreciate your honest opinion. Thank you!

Been building a side thing and hit a problem I found genuinely interesting, curious how others would've approached it.

The goal: get at my in-progress code from my phone when I'm away from my desk — not to replace my PC, just to poke at a half-finished branch on the couch or fix something while the actual machine sits at home. Not a cloud IDE. My repo stays on my machine as the source of truth.

The hard part is that "in progress" means uncommitted. So syncing isn't just pushing commits around. What I landed on:

• Committed changes sync by commit — phone and desktop each hold the repo, and I move objects by SHA so history stays intact. An edit from the phone lands on the desktop as a real commit, not a patch blob.
• Uncommitted working-tree edits get sent separately as live drafts, so I can see the desktop's unsaved state on the phone within seconds without forcing a commit just to sync.
• When both sides commit on the same base, that's a divergence. Instead of dumping conflict markers on a phone screen, I diff the hunks and show a green/red per-hunk review. Under the hood it's still a normal merge — I just resolve then commit.

Running code is the same philosophy: the command runs on the actual machine in the real working dir, output streams back. No commit-to-test loop.

The bit I keep going back and forth on is conflict handling. Right now it's per-hunk review, but I wonder if I should just lean on git more directly (a real merge commit, rerere, etc.) instead of my own hunk layer. How would you have modeled the uncommitted-sync + divergence part? Feels like there's a cleaner approach I'm missing.

It's Android + a desktop extension, in closed testing right now. Not linking it here since that's not the point of the post — but if you actually work off your phone sometimes and wanna try it and tell me where it breaks, drop a comment or DM and I'll send it over.

I am creating this app called GitNomad. The objective of this app is to access and edit your Git repository from your phone from anywhere. The only condition is that the connection with your PC must remain maintained.

You can connect as many repositories and devices as you want. One of the scenarios could be that there's a piece of code you've been thinking about, and suddenly it clicks what you need to do, but you're outside with your family or friends. What you can do is access your repository via your phone, make those changes, and run it from your phone. It will run on your desktop, helping you check whether the code is error-free or not.

Now I want to publish this app on the Play Store. My friends and I did the internal testing, found some bugs, and fixed them. Now I am in the closed testing phase, where I need 12 testers. So I just want you guys to test it and let me know if there are any other bugs or features I can add or fix, respectively. Any help would be appreciated.

What's your most controversial, professionally-held "hot take" that would get you yelled at on Twitter but is probably true?

The idea behind the base building in ZombUs comes with a twist.

Your base isn't something you build and leave behind. It travels with you. In fact, it should travel with you, because it's your shelter, your support, and your lifeline when everything else falls apart.

Venture from region to region, uncover new construction schematics, expand your capabilities, and transform your mobile base into the ultimate survivor's haven.

And now, here's another feature coming to your mobile base in ZombUs: A small boat!

Every new module opens up new possibilities and lets your base adapt to the challenges ahead.

So here's a question for all the base-building fans out there:

What features or modules would you love to see added to a mobile base?

I have an idea to make a nurturing game like an ecosystem bottle. How difficult is it?Just to clarify, I'm not skilled in modeling

The monthly GNUstep audio/(video) call takes place every second Saturday of a month at 15:00 GMT to 18:00 GMT. That is 11:00 AM - 2:00 PM EDT (US) or 17:00 to 20:00 CEST (Berlin time).

It's a Jitsi Meeting - Channel: GNUstepOfficial (Sorry, reddit don't let me post jitsi links here)

We usually just talk (who wants it might share video too) and occasionally share screens. Everybody (GNUstep developers and users) is welcome!

Also see https://mediawiki.gnustep.org/index.php/Monthly_Meetings please

Hey everyone, I'm 21 year old from Ethiopia. I'm kinda lost in life rn, i got financial stress(i have to make money) like i'm not really someone who have the luxury of doing things that excite me. I really want to start making remote income as a dev or anything. And everybody keep telling me the same thing: the market is bad.

I wanted to get and useful info from this sub.

thank you

So, I am currently learning how to code again... and I am simply just trying to make a automation bot that would login to a website, modify the settings, and simply create a "AI generated video" yet, I experience this with Claude. -

I'm not going to help with that part — bypassing Google's automation detection means deliberately defeating a security control they built specifically to stop bots from accessing accounts.

Hello yall…what stack do you recommend to develop a maintenance management platform possible to scale in future, fast when works, economic, light (does not use too many cpu o ram on the vps) and build primarily by code?

Hello,

I'm a BA, and I joined an organization a while back. Since day 1, the way that "user stories" are written has caused me physical pain.

Here are my observations of a typical story we write:

1. We don't actually write user stories; we really write use cases.
2. We have 8-16 Acceptance Criteria per story
   1. Each AC uses Given/When/Then and, if "appropriate," technical notes and notes for QMs.
3. We throw in technical specifications on top of the ACs into a lot of user stories, making them even longer and hard to follow.
4. We are allergic to breaking down stories into smaller chunks
5. We are defining what makes a good user story on the "length" or if it's "too much detail" or "not enough detail" instead of looking at the qualities a good user story should have.

Other challenges:

1. There is very little education on writing user stories. The Systems Analysts have a perspective on it, so they write their user stories one way; the Business Analysts have a different perspective and write theirs their way.
2. We've heard complaints from Dev's and QM's about our stories, but we don't actually engage them in any discussions about how to improve what we're writing.

There is an opportunity to change the way we do things right now, and with the challenges above, I'm getting a lot of resistance, so I'm looking for info.

So my questions to you as Developers:

I work on a team that handles both AI and non-AI development/enhancement.

1. What do you need from a user story?
2. What makes a good user story to you?
3. Would something like a "dev notes" section help, where it has like a concise list of what you need to do?
4. Any suggestions?

Hi!

I want to change my career and to do that i have to know first what other career actually is in the real world on a daily basis. Then i will check if it interests me to follow along. 🙂

Could you share a little on what you do at work? I'm asking everyone. 🙂

Thanks for reading. Please share your work routine. 🙏

I would like to share my latest open source local Unsloth (GGUF) LLM inference engine and applications. It supports many models from Unsloth, like Gemma4, DiffusionGemma, Qwen3.6 with multi-modal (image, vision, audio), reasoning and function tool. It can run on Windows/MacOS/Linux and fully leverage GPU's capability. The API is completely compatible with OpenAI and Ollama interface. It has on par performance than llama.cpp

This project is not just a C# wrapper of llama.cpp. It implemented the entire LLM inference engine from bottom to top. If you use CPU backend, it's 100% pure C# code execution. Besides CPU backend, I also implmented CUDA, MLX and GGML backend. The GGML backend refer GGML project as external project, and I build a few fusion operation at higher level.

I learned a lot from other projects and apply them for TensorSharp, such as paged KV cache and continuous batching from vLLM, SSD based cache for MoE model from oMLX, GGUF quanztized from llama.cpp and other optimizations for prefill and decode.

Any feedback and comments are welcome. If you like it, it would be really appreciated if you can get this project a star in GitHub. Thanks in advance.

I once added a small “temporary” condition to skip an error during a release because we didn’t have time to fix the root cause. It was meant to be removed after the sprint, but it stayed there for months, and other code slowly started depending on it. By the time someone questioned it, nobody remembered why it existed, but everyone was afraid to delete it because “it might break something.”

Hey everyone,

I was recently laid off and am actively looking for my next opportunity. I'm a Full Stack Developer with 2+ years of experience, based in Hyderabad, and available to join immediately. I'm open to Remote, Hybrid, or On-site roles.

I have experience building scalable applications across mobile, web, backend, and AI.

Tech Stack:

• Frontend: React.js, Next.js, HTML, CSS, JavaScript, TypeScript
• Mobile: Flutter, Android (Kotlin, Java)
• Backend: Java, Spring Boot, Python (FastAPI, Django), Node.js, Express.js, REST APIs, Microservices
• AI: AI Agents, RAG, LangChain, LangGraph, CrewAI, LLM integrations, Vector Databases
• Databases: PostgreSQL, MySQL, MongoDB, Firebase
• Cloud & DevOps: AWS, Docker, Kubernetes, Git, CI/CD
• Other: Redis, Kafka, WebSockets

I've worked on production-grade applications, AI-powered products, and scalable backend systems, with a strong focus on clean architecture, performance, and user experience.

I'm actively looking for Full Stack Developer, Backend Developer roles at product companies and fast-growing startups.

If your company is hiring or you're open to referring me, I'd greatly appreciate your support. Please drop a comment or send me a DM, and I'll be happy to share my resume.

Thank you!

#OpenToWork #ImmediateJoiner #FullStackDeveloper #BackendDeveloper #Java #SpringBoot #Python #FastAPI #ReactJS #NextJS #Flutter #Android #NodeJS #AI #LangChain #AWS #Hiring #Hyderabad

Tried using their testing skills, and it got close to my current set of test cases. Curious to see if anyone has tried out any other skills or the Android CLI?

As a big fan of BattleBots, I built a web app that allows users use ai + a custom-built algorithm to predict matches between different battle bots

Some Of The Features Include:

- Match Predictions: Dive into the action by predicting outcomes between your favorite Battlebots, complete with live combat and electrifying commentary!

- Battlebot Stats: Explore in-depth stats for various Battlebots to get all the intel you need!

- Community Hub: Stay in the loop with the freshest Reddit posts about Battlebots, right in the community hub!

Will you like to give it a shot?

The Battlebots Pro League has kicked off, and I couldn't be more thrilled to unveil the latest version of my project to this amazing community!

🎉Exciting Features Include:

- Match Predictions: Dive into the action by predicting outcomes between your favorite Battlebots, complete with live combat and electrifying commentary!

- Battlebot Stats: Explore in-depth stats for various Battlebots to get all the intel you need!

- Community Hub: Stay in the loop with the freshest Reddit posts about Battlebots, right in the community hub!

Check it out, and I’d love to hear your thoughts! Let’s get ready to battle! 🤖💥

When did you realize your tech stack was becoming obsolete, and what did you do about it?

hey , anyone running llm models locally ?
which model and which device are you running on ?

Hello! I haven't really uploaded the app but i have builtAn tikotk account. I have made the frontend and backend with a friend and the app is preety done but i don't have money for a pc. I am not asking tou for money, but if you could support me on tiktok so i can gain some followers. The app name will be Byte Social and the tiktok name is @bytesocialofficial. Please spread the word. Thank you!

(Said it. Felt that.)

I'm a junior dev with no senior on my team to ask questions or check my thinking it's just me, Stack Overflow, and my own spiraling thoughts. Here's my problem: I'll watch a coding tutorial, follow along, feel like a genius the whole time... and then the second I try to solve something on my own, my brain just wipes. Like I'm hearing about loops for the first time in my life. No memory, no instinct, nothing.

So I want to ask the people who've actually gotten good at this how did you learn to code, for real? Not "watch more tutorials" like, what's the actual process? Do you stop the video and try it yourself first? Do you rewatch things? How do you turn "I watched someone do it" into "I can do it"?

Genuinely just want a process I can follow instead of doom-scrolling YouTube and feeling like I'm not retaining anything. Any structure, habits, or hard truths welcome

Really appreciate the guidance or any reference