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...

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?

When I was working on a Python project, most of my focus went into getting the features working.

When it was nearly done, I started thinking about the boring but important stuff, like how to share it, how the licensing should work, and how much of the code would be exposed once other people had a copy.

It made me realise that completing the code is not always the end of the work.

If you have sold or shared small software projects, when did you start thinking about licensing, distribution, or protecting your code?

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.

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?

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!

https://preview.redd.it/sg451iy8e1bh1.png?width=1920&format=png&auto=webp&s=20a96419aabadbe9ef8565ce435f96a32f4f7e47

I work at a VERY AI-forward company and our products exist at the forefront of the capabilities of current models. My total comp is probably around $200k, but I'm going to be giving all that up in order to land a career in a different field that has lower potential of AI taking my job.

Some of you might have differing opinions of how all this will shake out. To you, I would say until you've worked at the forefront pushing the limits of agentic AI everyday, you opinion will inevitably be skewed thinking "AI could never do my job." I have a feeling I'll end up having to argue my position regardless in the comments with those who are desperate to convince my their 80 IQ is more useful than Claudes 140+.

In any case, I went back and forth between career options. I didn't want to go back to school, but still wanted a high income potential. I also wanted something where I could work for myself at some point. Finally, it had to be something I was passionate about. I eventually landed on personal trainer.

I started my cert and will be finished in the coming weeks. Once I have that finished, I plan to use a portion of my savings to open a small studio in an affluent area.

To those of you worried about the longevity of the field, consider this: regardless of if the field continues to exist or becomes extinct, is it worth continuing in a job where all you're doing all day is telling a robot in plain english what to do? Personally, I find it extremely unfulfilling.

EDIT: To those claiming there won't be people to afford PT if AI takes white collar jobs, think again. Middle managers will be safe — they'll be the ones prompting. Blue collar jobs will be safe and will likely boom. Single-person businesses that were impossible before are now possible. Basically anything that requires any real person-to-person communication is safe (HR, sales people, etc). It's just us IC's that are going to be gone.

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?

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.

I have applied to over 150+ dev related opportunities and I keep getting the we will consider you for future opportunities reguardless of getting a number of gcp and aws and ibm certifications I know several programming languages and still no luck. Does anyone have any other ideas for getting more affirmed job leads???

Hi,

I’m currently 15 (turning 16 soon), and I’ve decided to pursue backend development as a self-taught path.

I started learning HTML and CSS last year when I thought I wanted to become a full-stack developer, but I realized I’m more interested in backend development. After that, I moved on to JavaScript.

So far, I have learned:

• Variables, booleans, if statements, functions, objects
• Arrays and loops
• Basic DOM manipulation
• Modules

I also just finished my first full frontend project (a small web app called College Launchpad), which helped me apply these concepts in a more practical way. Link will be in the first comment.

My current roadmap

• Finish JavaScript concepts(async/await, fetch API, local storage, etc)
• Learn Node.js and Express
• Learn Databases(likely PostgreSQL)
• Build backend/full-stack projects
• Learn Java + Spring Boot
• Rebuild some projects using Java/Spring Boot

Why Java

I also want to learn Java because after high school I’m interested in applying for programs like the JPMorgan Chase Emerging Talent Experience Program, and I’ve heard Java/Spring Boot is commonly used in enterprise environments.

My question

• Am I learning in the right order?
• Is there anything important I should focus on earlier or avoid?
• Is it a good idea to learn Java/Spring Boot after Node.js, or should I go deeper into JavaScript first?

Any feedback or criticism is appreciated. I’m mainly trying to make sure I’m building good foundations and not missing anything important.

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

>https://github.com/DearLinus/Linusand

I can relate to the frustrations programmers feel about people getting into vibecoding (I've read multiple horrible ChatGPT-generated legal pleadings by people who represent themselves in court).

I want to become competent at creating various basic web applications that I can use when I go off to start my own law firm, to make the running of the firm more efficient. I'm sure you can imagine the type of programs I envision.

It is my impression that vibecoders very often launch products with significant security risks and bugs and inefficiencies.

I have significant time on my hands the next 12 months. I'd love to learn a combination of actual practical programming combined with the benefit of AI. It is very difficult to find solid footing on where to begin. So many tutorials I've found emphasize how you don't need to learn any coding at all, and the basic programming tutorials posted years ago obviously don't incorporate vibecoding, which seems like an inefficient for a newcomer to learn.

Would anyone mind pointing me in the right direction?

When people first get into programming, they usually ask, "Where do I even start?" Honestly, the biggest mistake I see is people trying to learn everything before they build anything. You don't need to know everything. You just need to start.

If I were starting over today and wanted to learn Android development, this is exactly what I'd do.

First off, Don't let AI steer the ship. I catch AI making more and more bad mistakes than good calculated decisions when it comes to infrastructure. ( Example: I was running server side edge functions, despite me laying out my architecture, auditing the repo, it still wanted to write functions to server.ts. ) These are the things that will trip you up later on. But for now....

Step 1: Learn the Basics

Before you worry about building apps, you need to understand programming itself.

I'd focus on learning things like:

• Variables
• If statements
• Loops
• Functions
• Classes and objects
• Arrays and lists

Don't stress if it doesn't click immediately. Everyone gets confused at first. The important part is writing code yourself instead of just watching videos.

Step 2: Download Android Studio

Android Studio is the official software Google provides for building Android apps.

Install Android Studio, let it download everything it needs, and create your first project using the Empty Activity template.

Don't worry if it looks overwhelming. I remember opening it for the first time and wondering what half the buttons even did. You'll figure it out as you go.

Step 3: Don't Build the Next Instagram

One thing I'd avoid is trying to build some massive app right away.

Start with something simple like:

• A calculator
• A notes app
• A to-do list
• A habit tracker

A simple project teaches you way more than spending six months planning an app that's too big to finish.

Step 4: Learn How Everything Connects

Every Android app is really just a bunch of pieces working together.

You have:

• The screen the user sees.
• The code that runs when someone taps a button.
• The data your app saves.

Once you understand how those three things work together, building apps starts making a lot more sense.

Step 5: Make It Work Before Making It Pretty

A lot of beginners spend hours trying to make their app look perfect.

Don't.

I'd rather have an ugly app that actually works than a beautiful app where none of the buttons do anything.

Get the functionality working first.

You can always improve the design later.

Step 6: Save Information

Eventually you'll notice that every time you close your app, everything disappears.

That's when you learn how to save data.

Start with local storage first before worrying about cloud databases.

Once you're comfortable, move on to something like Room or a backend service.

Step 7: Learn to Debug

Here's something nobody tells beginners...

Programming isn't about writing perfect code.

It's about figuring out why your code doesn't work.

You're going to see error messages.

You're going to break things.

Sometimes you'll spend an hour looking for a missing comma.

That's completely normal.

The developers who improve the fastest aren't the ones who never make mistakes—they're the ones who get good at fixing them.

Step 8: Keep Adding Features

Once your first version works, start adding things.

Maybe add:

• Dark mode
• Notifications
• Search
• Categories
• Login
• Cloud syncing

Don't try to build everything at once.

Add one feature.

Make sure it works.

Then move to the next one.

Step 9: Build More Apps

This is probably the biggest piece of advice I can give.

Don't stop after one project.

Your first app teaches you the basics.

Your second app teaches you confidence.

Your third app starts to make you feel like an actual developer.

Every project teaches you something the last one didn't.

Final Thoughts

If there's one thing I've learned, it's that programming isn't about being the smartest person in the room. It's about refusing to quit when something doesn't work.

Everyone starts out confused.

Everyone gets stuck.

The difference is that the people who become developers keep building anyway.

So don't wait until you think you're "ready."

Build something small.

Finish it.

Then build something a little bigger.

Repeat that enough times, and one day you'll look back and realize just how far you've come.

I always thought writing the code was the hardest part.

Then I asked a few people to try one of my projects.

It didn't take long before they started finding things I had completely missed. One person couldn't get it running. Someone else had a different setup. Another got stuck before they could even get started.

None of those problems ever showed up while I was testing it myself.

That was the moment I realized that getting a project to work on my own machine was only part of the job. Making it easy for other people to use turned out to be just as important.

Has sharing a project with other people ever changed the way you build software?

Hello, I am a product designer working on a configurator for vehicles. I recognize that my question may be slightly misinformed but please exercise patience. I am quite new to product design and even a stranger to programming.

I will list the features of the configurator below so I can get recommendations or at least a scope of what languages/platforms to consider or use.

1. The configurator should feature 3D models 2D images.

2. The 3D models should have pan, rotated, and zoomed functionality. But it should be limited (not complete 360 degrees all around)

3. Next, it should be able to toggle between light and dark scenes and change environments. Perhaps a minimum of three different environments.

4. Next it should be able to change colors and skins and perhaps rims and wheels.

I understand that there’s phases to this— there’s the development of optimized assets for the web and then the code to host the assets. My knowledge is embarrassingly limited. I will appreciate any help, thanks!