Tag: What are the concepts every Java programmer must know?

Introduction When you first start building apps with Jetpack Compose, one question comes up very quickly:Continue reading on Medium »

🧭 IntroductionContinue reading on Medium »

PHP Variables with Examples — Easy Learning GuideContinue reading on Medium »

0.0000001 BTC ฟังดูไม่มีความหมายอะไรเลย จนกว่าคุณจะคูณมันด้วย 1 ล้าน transaction นั่นคือ 0.1 BTC ที่หายไปจากระบบโดยไม่มีใครสังเกตเห็น…Continue reading on Medium »

So I challenged Gemini and Claude to making a great poster about a lullaby. We can see Gemini is way ahead in terms of creativity and…Continue reading on Medium »

Sometimes, a website issue reveals more than technical gaps; it shows us how we handle stress, plan for uncertainty, and value our…Continue reading on Medium »

Scanned PDFs are essentially images wrapped in a PDF container. That means you can view them — but you can’t search, copy, or extract text…Continue reading on Python in Plain English »

Master semantic search and context-aware retrieval using LangChain, AutoGen, and CrewAI. Learn 4 retriever patterns with production code…Continue reading on Medium »

It worked perfectly in demos, and quietly collapsed the moment real users showed upContinue reading on Stackademic »

It worked perfectly in demos, and quietly collapsed the moment real users showed upContinue reading on Stackademic »

What the Universe Looks Like When You Are the Pattern Looking BackContinue reading on Medium »

I’ve been building with Claude Code daily — automating real client workflows, shipping AI systems, debugging production code at odd hours…Continue reading on Medium »

Tugas Pemograman dan Data Raya LanjutanContinue reading on Medium »

Our always goto option for fake json dataContinue reading on Medium »

Modern enterprise systems often have powerful databases, but accessing that data efficiently is still a challenge. This project focuses on…Continue reading on Medium »

How Claude Code makes you a better tester by finding the cases you never thought to askContinue reading on Medium »

How to Rotate Proxies in Python: A Step-by-Step Guide for 2024Continue reading on Medium »

Most products don’t start with accessibility in mind.Continue reading on Medium »

Real-Life Example: How Systems Handle Corrupted DataContinue reading on Medium »

Tools like n8n, Make, Langflow, and Flowise usually give you a single input box called “System Prompt."Continue reading on Towards AI »

A developer pushed a .env file to GitHub.Continue reading on Medium »

Reliable tools you’ll keep forever (advanced edition).Continue reading on Stackademic »

Hello everyone!! In this article i will talk about some security headers. I wrote this for people like me who get confused when they see…Continue reading on Medium »

MCP gave AI agents a way to reach your systems of record. Jira, Slack, GitHub, Notion, your data warehouse. As of April 2026, that part of…Continue reading on AI Advances »

Feature engineering bugs hide in joins. Here is how to build synthetic relational databases that expose them before production does.Continue reading on Towards AI »

Continue reading on Medium »

Continue reading on Medium »

Continue reading on Medium »

Using steering documents to turn generic output into code that belongs in your projectContinue reading on Medium »

Not smarter — just more consistent.Continue reading on JavaScript in Plain English »

I've spent the last few months working on this project and now it's done i've done a writeup of alllll the learnings (mistakes). Hope a few of you find it nice! submitted by /u/Xerax [link] [comments]

submitted by /u/ScottContini [link] [comments]

submitted by /u/fagnerbrack [link] [comments]

submitted by /u/DanielRosenwasser [link] [comments]

Using invariant-based testing to locate and resolve tricky hidden bugs with complex state transitions in Seastar, an open-source, high-performance C++ framework for I/O-intensive, asynchronous applications submitted by /u/swdevtest [link] [comments]

Almost all architecture offices I’ve seen have a policing stance. When you want to get your software, tooling, or approach implemented, you’re going to need to pass through the architecture board (or some kind of board). In these boards, there are architects that go through all the documents required (artefacts) and either approve or disapprove the setup. I would call this the stick approach. People don’t want to go through this procedure. They have to prepare all of these documents, follow all of these guidelines and after all of this work, the faceless board can still stop everything in its tracks. With rework and unclear deadlines as a result. The reality is that most people try to avoid this entire setup and either go the shadow IT route, or try to make their new project part of an existing (and allowed) project. An alternative to this setup is the carrot approach. This often works a lot better. Every project gets an architect appointed to it. They guide the project so it aligns to the way of working of the organization. As you can imagine, this is a lot more work for the architecture team and also results in more things the project has to keep track of. Even if the architect takes care of all the governance and rules, you still have to have all the meetings in place. You also don’t have to pass the board (or the architect takes care of all of that), but you’ve inherited a team member whose job is to say ‘yes, but’ at every turn. What if there is a 3rd way? “Hey we’ve heard you wanted to automate some workflows. We have a standard for that. It’s fully approved and brings you these benefits … and by the way, it also handles security, logging, and legal. So you don’t have to pass there any more”. What a dream. As a customer someone came to you and gave you not only part of your project worked out, they also took a security and legal board off your plate. This is a direct positive impact to your project timeline. Next project I’m going to seek out these people. And what if said workflow doesn’t fit? Then we adapt it, but the foundation is already there. You’re not talking over process adaptations and not the base structure. This is called paved road architecture and is used by Netflix and Spotify. Path of least resistance Projects will always follow the path of least resistance, that’s just project management. Try to minimize your risks and guard your scope and timelines. Paved road architecture plays into that. If we make the easy route the “good” route, people will default to that. Everyone wins. And more importantly is that you will automatically discourage people from not following it. If they don’t follow the carved-out route, they will have to carve out their own route. That will take time and risk. submitted by /u/GeneralZiltoid [link] [comments]

submitted by /u/Dear-Economics-315 [link] [comments]

submitted by /u/goto-con [link] [comments]

What retries, Retry-After, and hedging actually do under controlled network chaos submitted by /u/OtherwisePush6424 [link] [comments]

submitted by /u/Skaarj [link] [comments]

submitted by /u/Vinserello [link] [comments]

submitted by /u/mttd [link] [comments]

submitted by /u/mttd [link] [comments]

submitted by /u/Dear-Economics-315 [link] [comments]

submitted by /u/PulseBeat_02 [link] [comments]

submitted by /u/Dear-Economics-315 [link] [comments]

submitted by /u/Shriracha [link] [comments]

Hi everyone, I wrote the original "Why Crystal?" blog post back in 2015 when Crystal was just v0.9.1. Ten years and many versions later, I am revisiting that post to analyze the road to v1.20. If you are interested in how a language matures from a syntax experiment to a high performance standard, this one is for you. submitted by /u/sdogruyol [link] [comments]

Given that the current frontend ecosystem complexity is rivaling Tower of Babel, I asked: Can we start from scratch and figure out a much simpler approach, given how browsers have evolved in recent years? Have a read to find out 😉 submitted by /u/BinaryIgor [link] [comments]

submitted by /u/Successful_Bowl2564 [link] [comments]

submitted by /u/Digitalunicon [link] [comments]

submitted by /u/nfrankel [link] [comments]

https://x.com/DiffeKey/status/2045813085408051670 submitted by /u/arduinoRPi4 [link] [comments]

Hey folks, After a lot of discussion, we've decided to trial a ban of any and all content relating to LLMs. We get a lot of posts related to LLMs and typically they are not in line with what we want the subreddit to be — a place for detailed, technical learning and discourse about software engineering, driven by high quality, informative content. And unfortunately, the volume of LLM-related content easily overwhelms other topics. We also believe that, generally, the community have been indicating that, by and large, they aren't interested in this content. So, we want to see how a trial ban impacts how people use the sub. As such: While this post is stickied, for 2-4 weeks over April, we're banning all LLM-related content from the sub. That's posts, articles, videos about LLMs. We've had a ban on LLM-generated text for ages already, this doesn't change that. Note that this doesn't ban all AI related content. An article detailing how what would have traditionally been called an AI was made for Go? Totally fine. A technical breakdown of a machine learning process? Great! Just so long as it's not about LLMs. Edit: Yes, this is real, it's not an April Fool's joke. submitted by /u/ChemicalRascal [link] [comments]

tl;dr: mods applications and minor rules changes. Also it's 2026, lol. Hello fellow programs! It's been a while since I've checked in and I wanted to give an update on the state of affairs. I won't be able to reply to every single thing but I'll do my best. Mods applications I know there's been some frustration about moderation resources so first things first, I want to open up applications for new mods for r/programming. If you're interested please start by reading the State of the Subreddit (May 2024) post for the reasoning behind the current rulesets, then leave a comment below with the word "application" somewhere in it so that I can tell it apart from the memes. In there please give at least: Why you want to be a mod Your favourite/least favourite kinds of programming content here or anywhere else What you'd change about the subreddit if you had a magic wand, ignoring feasibility Reddit experience (new user, 10 year veteran, spez himself) and moderation experience if any I'm looking to pick up 10-20 new mods if possible, and then I'll be looking to them to first help clean the place up (mainly just keeping the new page free of rule-breaking content) and then for feedback on changes that we could start making to the rules and content mix. I've been procrastinating this for a while so wish me luck. We'll probably make some mistakes at first so try to give us the benefit of the doubt. Rules update Not much is changing about the rules since last time except for a few things, most of which I said last time I was keeping an eye on 🚫 Generic AI content that has nothing to do with programming. It's gotten out of hand and our users hate it. I thought it was a brief fad but it's been 2 years and it's still going. 🚫 Newsletters I tried to work with the frequent fliers for these and literally zero of them even responded to me so we're just going to do away with the category 🚫 "I made this", previously called demos with code. These are generally either a blatant ad for a product or are just a bare link to a GitHub repo. It was previously allowed when it was at least a GitHub link because sometimes people discussed the technical details of the code on display but these days even the code dumps are just people showing off something they worked on. That's cool, but it's not programming content. The rules! With all of that, here is the current set of the rules with the above changes included so I can link to them all in one place. ✅ means that it's currently allowed, 🚫 means that it's not currently allowed, ⚠️ means that we leave it up if it is already popular but if we catch it young in its life we do try to remove it early, 👀 means that I'm not making a ruling on it today but it's a category we're keeping an eye on ✅ Actual programming content. They probably have actual code in them. Language or library writeups, papers, technology descriptions. How an allocator works. How my new fancy allocator I just wrote works. How our startup built our Frobnicator. For many years this was the only category of allowed content. ✅ Academic CS or programming papers ✅ Programming news. ChatGPT can write code. A big new CVE just dropped. Curl 8.01 released now with Coffee over IP support. ✅ Programmer career content. How to become a Staff engineer in 30 days. Habits of the best engineering managers. These must be related or specific to programming/software engineering careers in some way ✅ Articles/news interesting to programmers but not about programming. Work from home is bullshit. Return to office is bullshit. There's a Steam sale on programming games. Terry Davis has died. How to SCRUMM. App Store commissions are going up. How to hire a more diverse development team. Interviewing programmers is broken. ⚠️ General technology news. Google buys its last competitor. A self driving car hit a pedestrian. Twitter is collapsing. Oculus accidentally showed your grandmother a penis. Github sued when Copilot produces the complete works of Harry Potter in a code comment. Meta cancels work from home. Gnome dropped a feature I like. How to run Stable Diffusion to generate pictures of, uh, cats, yeah it's definitely just for cats. A bitcoin VR metaversed my AI and now my app store is mobile social local. 🚫 Anything clearly written mostly by an LLM. If you don't want to write it, we don't want to read it. 🚫 Politics. The Pirate Party is winning in Sweden. Please vote for net neutrality. Big Tech is being sued in Europe for gestures broadly. Grace Hopper Conference is now 60% male. 🚫 Gossip. Richard Stallman switches to Windows. Elon Musk farted. Linus Torvalds was a poopy-head on a mailing list. The People's Rust Foundation is arguing with the Rust Foundation For The People. Terraform has been forked into Terra and Form. Stack Overflow sucks now. Stack Overflow is good actually. 🚫 Generic AI content that has nothing to do with programming. It's gotten out of hand and our users hate it. 🚫 Newsletters, Listicles or anything else that just aggregates other content. If you found 15 open source projects that will blow my mind, post those 15 projects instead and we'll be the judge of that. 🚫 Demos without code. I wrote a game, come buy it! Please give me feedback on my startup (totally not an ad nosirree). I stayed up all night writing a commercial text editor, here's the pricing page. I made a DALL-E image generator. I made the fifteenth animation of A* this week, here's a GIF. 🚫 Project demos, "I made this". Previously called demos with code. These are generally either a blatant ad for a product or are just a bare link to a GitHub repo. ✅ Project technical writups. "I made this and here's how". As said above, true technical writeups of a codebase or demonstrations of a technique or samples of interesting code in the wild are absolutely welcome and encouraged. All links to projects must include what makes them technically interesting, not just what they do or a feature list or that you spent all night making it. The technical writeup must be the focus of the post, not just a tickbox checking exercise to get us to allow it. This is a technical subreddit, not Product Hunt. We don't care what you built, we care how you build it. 🚫 AskReddit type forum questions. What's your favourite programming language? Tabs or spaces? Does anyone else hate it when. 🚫 Support questions. How do I write a web crawler? How do I get into programming? Where's my missing semicolon? Please do this obvious homework problem for me. Personally I feel very strongly about not allowing these because they'd quickly drown out all of the actual content I come to see, and there are already much more effective places to get them answered anyway. In real life the quality of the ones that we see is also universally very low. 🚫 Surveys and 🚫 Job postings and anything else that is looking to extract value from a place a lot of programmers hang out without contributing anything itself. 🚫 Meta posts. DAE think r/programming sucks? Why did you remove my post? Why did you ban this user that is totes not me I swear I'm just asking questions. Except this meta post. This one is okay because I'm a tyrant that the rules don't apply to (I assume you are saying about me to yourself right now). 🚫 Images, memes, anything low-effort or low-content. Thankfully we very rarely see any of this so there's not much to remove but like support questions once you have a few of these they tend to totally take over because it's easier to make a meme than to write a paper and also easier to vote on a meme than to read a paper. ⚠️ Posts that we'd normally allow but that are obviously, unquestioningly super low quality like blogspam copy-pasted onto a site with a bazillion ads. It has to be pretty bad before we remove it and even then sometimes these are the first post to get traction about a news event so we leave them up if they're the best discussion going on about the news event. There's a lot of grey area here with CVE announcements in particular: there are a lot of spammy security "blogs" that syndicate stories like this. ⚠️ Extreme beginner content. What is a variable. What is a for loop. Making an HTPT request using curl. Like listicles this is disallowed because of the quality typical to them, but high quality tutorials are still allowed and actively encouraged. ⚠️ Posts that are duplicates of other posts or the same news event. We leave up either the first one or the healthiest discussion. ⚠️ Posts where the title editorialises too heavily or especially is a lie or conspiracy theory. Comments are only very loosely moderated and it's mostly 🚫 Bots of any kind (Beep boop you misspelled misspelled!) and 🚫 Incivility (You idiot, everybody knows that my favourite toy is better than your favourite toy.) However the number of obvious GPT comment bots is rising and will quickly become untenable for the number of active moderators we have. 👀 vibe coding articles. "I tried vibe coding you guys" is apparently a hot topic right now. If they're contentless we'll try to be on them under the general quality rule but we're leaving them alone for now if they have anything to actually say. We're not explicitly banning the category but you are encouraged to vote on them as you see fit. 👀 Corporate blogs simply describing their product in the guise of "what is an authorisation framework?". Pretty much anything with a rocket ship emoji in it. Companies use their blogs as marketing, branding, and recruiting tools and that's okay when it's "writing a good article will make people think of us" but it doesn't go here if it's just a literal advert. Usually they are titled in a way that I don't spot them until somebody reports it or mentions it in the comments. r/programming's mission is to be the place with the highest quality programming content, where I can go to read something interesting and learn something new every day. In general rule-following posts will stay up, even if subjectively they aren't that great. We want to default to allowing things rather than intervening on quality grounds (except LLM output, etc) and let the votes take over. On r/programming the voting arrows mean "show me more like this". We use them to drive rules changes. So please, vote away. Because of this we're not especially worried about categories just because they have a lot of very low-scoring posts that sit at the bottom of the hot page and are never seen by anybody. If you've scrolled that far it's because you went through the higher-scoring stuff already and we'd rather show you that than show you nothing. On the other hand sometimes rule-breaking posts aren't obvious from just the title so also don't be shy about reporting rule-breaking content when you see it. Try to leave some context in the report reason: a lot of spammers report everything else to drown out the spam reports on their stuff, so the presence of one or two reports is often not enough to alert us since sometimes everything is reported. There's an unspoken metarule here that the other rules are built on which is that all content should point "outward". That is, it should provide more value to the community than it provides to the poster. Anything that's looking to extract value from the community rather than provide it is disallowed even without an explicit rule about it. This is what drives the prohibition on job postings, surveys, "feedback" requests, and partly on support questions. Another important metarule is that mechanically it's not easy for a subreddit to say "we'll allow 5% of the content to be support questions". So for anything that we allow we must be aware of types of content that beget more of themselves. Allowing memes and CS student homework questions will pretty quickly turn the subreddit into only memes and CS student homework questions, leaving no room for the subreddit's actual mission. submitted by /u/ketralnis [link] [comments]