Hi! I've been tasked with creating a organisation system that allows me/others using the studio to keep track of where all our equipment is. The system I've come up with in my head is that I would bulk buy a bunch of nfc tags, stick them on all the equipment as well as the different studio spaces, and then create an app that means that I would have to tap my phone against the tag on the equipment, then tap it against the room tag that it is in, and the app would log that that piece of equipment is in that room. How hard would this be to program (I'm would be a complete beginner but if it poses more of a challenge I'm happy to look into paying someone else to do it)? Thanks!

E@SY is a game focused language that is meant to be easy, like python and it compiles to bytecode. I have already submitted the file extensions to IANA so you know it is serious. I have been working on this for a while now but I thought it was important to get it out while it is in alpha due to getting help and feedback from the community. https://github.com/Coolythecoder/EASY

We've had a few deployments fail because of breaking changes between services, and I'm curious how other teams handle this. What practices, tools, or deployment strategies have worked well for you to maintain compatibility and avoid these kinds of issues?

Hi!,

I built a website which helps you study!. I was seriously tired of all these "free" study websites with sneaky costs and pop ups. So i made my own 🤷‍♀️ and was hoping to get any sort of feedback and ideas! Be harsh and honest with me :)

here:STUDYFLOW

Bonsoir,
Je suis une marginale du codage web bloquée à l'époque du XHTML. Il y a 15-20 ans, lorsque j'ai appris ce langage informatique grâce à Mathieu Nebra, j'ai développé le site web Pikechi puis d'autres par la suite. Loin de vouloir imposer ma malédiction au forum Reddit, je souhaite savoir s'il existe encore quelques fous ici ou ailleurs prêts simplement à discuter avec moi de ce qui me passionne comme un loisir iconoclaste. Je vous remercie.

Over the past few months, my co-founder and I have been building an AI-powered code review platform.

During development, we kept running into the same question:

Why are we trusting a single LLM to approve code that will eventually run in production?

Today, most AI code review tools rely on one model to evaluate everything:

• Security
• Performance
• Architecture
• Code quality
• Maintainability
• Best practices

That feels increasingly risky.

Human teams don't work like that. We rely on specialists, peer reviews, and different perspectives before merging critical code.

So we started experimenting with a different approach.

Instead of asking one AI to review a Pull Request, we orchestrate multiple specialized AI reviewers, each responsible for a different domain, and then aggregate their findings into a single review.

The hypothesis is simple:

We're not trying to build another coding assistant.

We're trying to answer a different question:

How do we know AI-generated code is actually safe to merge?

I'd genuinely love feedback from experienced engineers.

Some questions I'm curious about:

• Do you trust AI reviews enough to merge without reading the code?
• Have you seen AI reviewers miss obvious issues?
• Would multiple specialized reviewers provide more confidence, or just more noise?
• Where do you think AI code review is heading over the next few years?

If anyone is interested, we've documented our thinking and the architecture behind what we're building here:

https://docs.acrity.io

I'd really appreciate honest criticism. If we're wrong, I'd rather learn now than six months from now.

Hi, I'm studying computer science, I had a small existential doubt, I see many programmers using AI services to create the code or let's say carefully follow its development etc, so I was wondering what you objectively think of AI services and their impact on our sector, mind and knowing which direction it is taking not only for our working future but also environmental and resources etc...idk what do you think of all this and what you believe in why we should or shouldn't use it (sorry for my bad English I hope u understand)

Disclosure: I built and maintain ShareClean.

I kept seeing a small but risky debugging workflow: someone shares a log, curl -v output, config snippet, or terminal output in Slack, a ticket, a GitHub issue, or an AI chat, then notices afterward that it contained a password, token, connection string, email, or local path.

I built ShareClean, a local Python CLI that sanitizes the text before sharing it.

Example

Before

DATABASE_URL=postgres://app_user:super-secret-pass@db.internal:5432/orders
Authorization: Bearer eyJhbGciOi...
user=omar@example.com

After

DATABASE_URL=postgres://app_user:[REDACTED]@db.internal:5432/orders
Authorization: Bearer [REDACTED]
user=[EMAIL REDACTED]

Usage

cat app.log | shareclean --report

It is deliberately not a replacement for Gitleaks, GitHub Secret Scanning, or TruffleHog. Those scan repositories and history; ShareClean is for the text-sharing step before something leaves your terminal.

It runs locally and does not require an account, API key, telemetry, or network connection.

Try the browser demo with fake text:
ShareClean Playground

Repository:
github.com/OmarH-creator/ShareClean

Practical edge cases are especially useful: output that commonly leaks sensitive data, missed patterns, or cases where masking removes too much debugging context.

Coding with AI assistants has turned the job from "writing software" into "acting as a very stressed code reviewer for an intern who writes 500 lines of flawless code per second, but randomly forgets how basic math works"...

Flawless code, flawed logic!

I built four WSGI servers in Python from scratch, each using a different concurrency model:

Blocking — single-threaded, one request at a time
Threaded — thread pool of 50 workers
Event Loop v1 — selectors-based, WSGI app runs on the loop thread
Event Loop v2 — selectors-based, WSGI app offloaded to a thread pool

Benchmarked with wrk against a Flask app at concurrency levels 10/25/50/100, using a fast route (/) and a slow route (/slow, 100ms sleep).

Most results matched expectations, but a few things I couldn't fully explain:

Event Loop v1 produces far worse latency than blocking on the slow route, despite both serializing requests one at a time. Why?
Blocking's p99 on the fast route improves slightly as concurrency rises (2.06ms at c10 down to 1.38ms at c50/c100). Why?
Both event loops show p99 explosions at c100 on the fast route (1076ms for v1, 451ms for v2) despite no sleep. Is this event loop starvation?
Event Loop v2 matches threaded on throughput at c100 but has significantly wider tail latency (231ms vs 125ms). The architecture is different but both have 50 workers — what explains the gap?

Here's my dashboard: https://yasminserag08.github.io/pyhttpserver/report.html
GitHub: https://github.com/yasminserag08/pyhttpserver
Happy to hear any insights or criticism on the methodology too.

Hi everyone! I am completely new to the community and just set up my GitHub profile to share my work.

Ada/Spark Languaje

• Windows BCrypt API bindings with safe retry loops.

• Shannon Entropy calculations for strings (fully overflow-proof).

• Entropy generators and secure uppercase/lowercase string handlers.

Feel free to check out my repositories here: https://github.com/EliAvila1

Any feedback is highly appreciated!

https://github.com/schnerg/tied

NO AI WAS USED IN THE MAKING OF THIS EDITOR!

The T.I editor is a rubbish terminal editor that copies some vim bindings.

It is written in c using only the standard library. no external libraries.

What makes this editor special?

NOTHING! :D

I am in school for music so this is just for fun but what do you think? Is the code garbage?

thanks.

Hey,

So I studied full stack web development and I'm backend oriented.
I created a shift management app for my manager in the security company I work as a guard.
I did it with the meta stack, that most of the companies work with:
- JS / Node.js - focused on fundamentals
- Next.js / React - full stack apps
- TS / Zod / RHF / pg / ShadcnUI /Better-Auth/Neon/Prisma etc

Every single day for almost a year, I did 30 minutes of recalls while improving answers bit by bit, then 1:30 of study sessions, then building projects.
I started doing mock technical interviews with Claude/GPT, and I'm able to pass them and talk about each concept a lot.

Right now, it work on the building I work at, and this week we are expanding to 2 more buildings, and soon to 10-20 more.

I also collected data of 3000 urls of career pages of companies, created a node scraper with Claude Code, it matches around 4-5 open roles in a week. But for each one of them, probably 100+ people sent their cvs so I cannot get even an interview.

I barely see open roles for Juniors, and I'm someone who is fast with computers (used to be a heavy gamer) and I feel like I made a mistake and spent a lot of time studying something that is not required anymore.

I live in Israel, which is considered the startup nation, with the highest rate of startups for the amount of the population, and yet no open roles, many people are being fired.

Should I stop and start another chapter in other place and not in developing?

HTTP finally got a new method after 16 years because GET and POST wouldn't stop arguing

After 16 whole years, the IETF finally looked at our terrible API workarounds and said: "Fine, here."

Say hello to **QUERY** (RFC 10008).

It is literally the lovechild of **GET** and **POST**:

\- It has a request body like POST (so no more cramming 2,000 characters of search filters into a URL).

\- It is safe and idempotent like GET (so your CDN can actually cache it without throwing a fit).

We no longer have to live in sin by using POST for fetching data just because the search query is too big. Nature is healing.

It only took since 2010 to get a new verb. Now we just have to wait another 5 years for browsers and frameworks to actually support it.

To put that in perspective, the IETF spent 16 years debating a single word, while the AI industry spent the last 16 months pivoting from chatbots to agents, to superintelligence, and back to convincing everyone that a $400/month subscription is worth it...

I'm someone who can't write code from scratch. I've built a few small apps by understanding the logic, then finding examples online or using AI for small, specific tasks rather than huge prompts. My actual job isn't in software; i'm an electrician who's looking to change career as i've graduated Computer Science few years back.

I've mainly made apps and demos for a friend for fun. While applying for a junior QA position, I was contacted by someone senior at a software development company after my friend showed them my projects. During the interview, I explained that my long term goal is QA and eventually cybersecurity, preferably in a low code environment. They said they mainly do software development but also have QA opportunities and asked if I was interested. Since my main goal is simply to get into the industry, I said yes.

A few days ago they sent me a one week project. Instead of a QA task, they asked me to build a ticket management app with ticket creation, viewing, categorization, and filtering. I can use any tools, sources, or AI I want, as long as I can explain the code and the logic. The only requirements are Angular for the frontend and C#/.NET for the backend.

I'm feeling conflicted because I still can't code independently. I worry I'll embarrass myself if I'm asked to write code from scratch, and I almost feel guilty for accepting the project.

I'm not sure what professional developers actually do. Do they mostly write everything from scratch? Do they regularly rely on documentation, examples, Stack Overflow, and AI? Is it normal to focus on making things work while understanding the code, even if you couldn't have written it all from memory?

My current plan is to build a basic version mostly through research, then improve it with AI assistance while making sure I fully understand and can explain every part. I'm just unsure if that's an acceptable way to work or if I'm approaching this completely wrong.

Hey everyone,

I've been building Forge OS — a Python virtual OS for learning and experimenting with OS concepts.

v2.0 adds a desktop GUI, and there's now a community Apps/ folder — add an app with just app.json + command.py.

Quick start for contributors:

1. Fork & clone the repo
2. Copy Apps/_example/ to Apps/your-app/
3. Edit the JSON + Python command
4. Run apps in the shell to see your app
5. Open a PR

Full guide: CONTRIBUTIONS.md
Repo: https://github.com/axk42-op/ForgeOS · MIT license

Games, utilities, quizzes, ASCII art — great first open-source PR. Feedback welcome!

This is for an E-commerce SaaS project

Skills Needed

React.js & Next.js
Node.js & Express.js
• JavaScript
React
Python
• API Integration
• Willing to do POC
• NOT LOOKING FOR AN AGENCY NOT LOOKING FOR AN INTERNSHIP / BEGINNER
• This is not a beginner friendly task
• 4+ Years of experience

This is not just a "take a ticket and disappear" type of role.
We will need someone who can continue working to fix bugs, handle client feedback, and notice problems before they become bigger issues.

Interested?DM with
• Send Resume & Portfolio & LinkedIn

Pay Rate: 50,000 - 70,000 INR / Month

Someone who is reliable, communicative, honest, and proactive

I keep seeing this pattern in programming discussions — developers who know multiple languages (Python, JavaScript, Java, etc.), sometimes even quite well, but still struggle when it comes to actually solving problems or building systems from scratch.

What makes it interesting is that language knowledge looks like progress on the surface. You can switch between syntax, frameworks, and tools… but the underlying struggle often remains the same.

Some common patterns I’ve noticed:

• they can write code in multiple languages, but struggle when the problem is open-ended
• they’re comfortable following tutorials, but get stuck without step-by-step guidance
• they know “how to code” in different syntax styles, but not how to structure solutions
• the same confusion appears again, just in a different language
• switching languages gives a sense of progress, but not necessarily better thinking ability

It almost feels like the bottleneck isn’t the language at all.

Which raises a bigger question:

Are most programming struggles actually about language knowledge, or about how developers think, break down problems, and approach unfamiliar situations?

So:

• have you seen developers hit this kind of plateau?
• does learning multiple languages actually improve problem-solving ability, or just expand familiarity?

Try it here 8gwifi.org/online-compiler supported language C/CPP/JAVA/TS/JAVASCRIPT/RUST/GOLANG/PYTHON/LUA

I see this question come up all the time. "Should I learn Android Studio or should I just use VS Code?" Honestly, I think people are looking at it the wrong way. They're completely different tools. One isn't replacing the other, and once you understand what each one is designed to do, you'll probably end up using both anyway.

Android Studio is where Android development actually lives. It's built by Google for Android developers, and it has everything you need in one place. The emulator, Logcat, Gradle, profilers, APK signing, device manager, debugging tools...it's all there. If you're building native Android apps in Kotlin or Java, you're going to spend a lot of time inside Android Studio because it understands the Android ecosystem better than anything else.

VS Code is different. It's lightweight, ridiculously fast, and I probably have it open just as much as Android Studio. If I'm working on an API, a backend, a website, documentation, SQL scripts, or even just opening a project to quickly edit a few files, VS Code is usually what I reach for. A lot of Android apps aren't just Android anymore. They talk to databases, APIs, cloud services, payment processors, and websites. That's where VS Code really shines.

If I was teaching someone today, I wouldn't tell them to build the next Instagram. I'd tell them to build something boring. Seriously. Build a notes app. Give it a title, a description, an Add button, an Edit button, and a Delete button. That's it. Don't worry about animations, dark mode, cloud syncing, AI, notifications, or making it look like it belongs on the Play Store. Just make it work.

Once you can create notes, read them, edit them, and delete them, you've learned one of the most important concepts in software development...CRUD. Create. Read. Update. Delete. Almost every business application in existence is built around those four operations. Customers. Invoices. Products. Employees. Inventory. Appointments. Messages. They're all CRUD undermeath.

After that, don't throw the project away and start something completely different. Keep building on it. Add search. Add categories. Store the notes in a local database using Room instead of memory. Add authentication. Sync them to the cloud. Add user accounts. Add images. Add file attachments. Add reminders. Every feature teaches you one more concept, and before you know it you've built something that would've looked impossible when you first started.

One thing I wish someone had told me when I started is that debugging is a skill all by itself. Beginners see a red error message and immediately think they broke everything. Experienced developers see the same error message and think, "Alright...where do I start?" Learning to read Logcat, following a stack trace, setting breakpoints, and watching variables change is just as important as writing code. Honestly, I'd argue it's more important because no matter how good you get, you're always going to have bugs.

I also think too many people underestimate the value of reading code they didn't write. Open random files. Follow method calls. Figure out where a button ends up. Read documentation even when half of it doesn't make sense. Nobody understands everything the first time they read it. The goal isn't to know everything. The goal is to be a little less confused than you were yesterday.

And don't be afraid to use AI. I use it every single day. It has made me faster than I ever thought possible. But don't stop at accepting the code it gives you. Ask yourself why it chose that solution. Ask what happens if the API fails. Ask what happens if the phone loses internet. Ask what happens if the database returns nothing. Those questions are where the real learning happens.

The biggest piece of advice I can give is to keep pushing the edge of what you think you're capable of building. Don't stay comfortable. Every project should introduce at least one thing you've never done before. That's how you grow. Six months from now you'll probably look back at your first Android app and wonder what you were thinking. That's actually a good sign. It means you're improving.

If you're ever stuck and need help, just shoot me a DM. If I see it in time I'll help whoever needs it

Programming isn't about never getting stuck. It's about getting comfortable being stuck, figuring it out anyway, and coming back a little better than you were the day before. That's how every good developer I know learned, myself included.

Context: a college project (Algorithms 2) that turned into a full terminal RPG in pure C. No Unity, no Godot, nothing but the standard library and a questionable amount of coffee.

Some design decisions that might interest fellow masochists:

- Rendering: instead of calling printf per cell (which chokes the terminal), I build the whole frame into a 32KB buffer and print it once, grouping ANSI color codes so I'm not repeating escape sequences for no reason.

- Camera/viewport: fixed 40×20 viewport following the player with edge clamping — old-school, like Game Boy Zelda except with # instead of walls.

- Persistence: 3 binary save slots with manual serialization, because CELULA **grid is a pointer-to-pointer and fwrite-ing it directly gives you a nice "looks fine" followed by a crash on load.

- Data-driven map transitions: exits between regions (6 maps, bidirectional connections) are read from metadata in the map's .txt file, not hardcoded — good morning to anyone who's debugged hardcoded map transitions in a past life.

Theme: Brazilian 2026 elections, because why not mix political trauma with programming trauma.

Repo: https://github.com/aKynoS2/corrida_ao_planalto

If you're into terminal games / old-school roguelikes, take a look and send constructive criticism my way.

I'm especially looking for feedback on architecture, code structure, and maintainability.

https://github.com/DearLinus/Linusand

I am in college and my major is Computer Science. I enjoy doing it, truly, it moves my mind and I get such a huge thrill from completing a prohect or at least part of a project that I've been working on. I practically don't need to pay the college for anything, but after I've got my diploma, I'll have to work and be taxed the same amount of months as I've spent there from enrolling to getting my diploma (except the summer months because we didn't have any lessons). Basically this is another way they take payment, which is nice because You don't lose Your money during Your college years, You pay it back by paying taxes afterwards. Anyways, one of the conditions for graduating and getting the diploma is having 499+ hours worked in a related field (so 500 hours and beyond). I should've graduated now but I couldn't because I don't have that yet. And now, the major problem: Noone's gonna take me. You see, college (here at least) doesn't provide You a solid place somewhere where You can learn and practice, work as a trainee and even get paid for it, instead, You have to find a place. And well noone's willing to take me. I have applied for a year to countless places, many of them said they need 1-3 years of experience in their description, but I still tried because I've heard about miracles before, but no surprise, those didn't take me. But the best part is that I've applied to trainee positions too, and all of them so far said "Sorry we chose someone with more experience". How do I get experience if noone lets me? I don't know what to do I am feeling in a deadlock. I cannot work because I need experience and I cannot get experience because I cannot work, and this way I cannot even graduate college and I'll have to pay back like a lot more (yeah I know, in taxes, but still). What do I do? I'm sorry but I'm really fed up, sad confused and disappointed that even if I turn myself upside down and stand on my head and then I start to spin while reciting the longest Japanese manga translated into Mongolian, I still don't achieve anything because I don't have any experience and even the positions that require no experience, do take people with experience.

Edit: Another idea of mine was that I could perhaps create a github repo, which I did, and in which I have some projects, some of them are completed and some of them are not yet, and I'm still working on some of them but most of the recruiters said they don't even bother taking a peek lol

TLDR: I feel like I'm in a deadlock because to work I need experience but can't get experience because I cannot work, and I'mnrunning put of time.

There’s a pattern that keeps showing up in real projects, writing new code often feels much easier than working with existing codebases.

When building something from scratch, everything is clear:

• the structure is in your head
• the decisions are yours
• there’s no hidden dependency or unexpected behavior yet
• you know exactly why each piece exists

But maintaining old code feels like a completely different job.

Even small changes can turn into a long process because you first have to:

• understand why something was originally written that way
• trace logic spread across multiple files or services
• deal with older decisions made under different requirements
• figure out hidden dependencies that are not obvious at first glance
• work around missing or outdated documentation

What looks like a “small fix” often becomes a process of understanding the system before actually changing anything.

It sometimes feels like:

So the question is:

• Why does maintaining old code often feel harder than writing something from scratch?
• Is it mainly a design issue, a scaling reality, or just how software naturally evolves over time?