Tag: Gödel

I collected a few often-omitted aspects of testing for more complex systems. The post covers: TDD External mocks Self generator "Absolute" tests /Decomposition/ submitted by /u/TheLasu [link] [comments]

Subclasses That Betray Your CodeContinue reading on Medium »

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

OpenResearcher-30B-A3B is a fully open, agentic 30B Mixture‑of‑Experts (MoE) model purpose‑built for long‑horizon deep research, not just…Continue reading on Data Science in Your Pocket »

**Introduction: Dictionary is a built-in data structure in python. It is a collection of Key-value pairs. Heterogeneous objects(elements)…Continue reading on Medium »

Retrieval-Augmented Generation (RAG) is the gold standard for reducing LLM hallucinations and giving AI access to your private data. While…Continue reading on Medium »

Why Guard Clauses, Dry Runs, and Least Privilege Should Exist Before You Press EnterContinue reading on Medium »

A leetcode storyContinue reading on Medium »

A leetcode storyContinue reading on Medium »

Your Mongo query returned the right data, and your dashboard still lied.Continue reading on Medium »

Decision-making and problem-solving are the twin engines of effective leadership.Continue reading on Medium »

Your deployment is healthy, your dashboards look calm, and yet users are reporting something that feels impossible.Continue reading on Medium »

Your agent says the refund is done. The customer messages again: they got two refunds. You open dashboards and see green lines that feel…Continue reading on Medium »

While learning Python, one of the most powerful data structures is the dictionary. A dictionary can store key-value pairs, which helps us…Continue reading on Medium »

While learning Python, one of the most powerful data structures is the dictionary. A dictionary can store key-value pairs, which helps us…Continue reading on Medium »

Behavioral Design Pattern: InterpreterContinue reading on Medium »

When working with multi-threading, we often run tasks in the background. But then questions arise:Continue reading on Medium »

Behavioral Design Pattern: CommandContinue reading on Medium »

Imagine you’re looking for a friend’s phone number. You open your contact list, type their name, and the number appears instantly. Now…Continue reading on Medium »

Every internal fork starts as a one-liner: “we just need to patch this one file.” Six months later you’re maintaining four parallel…Continue reading on Medium »

Vamos continuar nossa série de fundamentos do GIT, caso você não encontrou a parte 3, você pode conferir aqui.Continue reading on CodandoTV »

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

Topics covered:Continue reading on Medium »

Continue reading on Medium »

A beginner-friendly guide to choosing the right Python data structure using simple thinking and real examples.Continue reading on Medium »

The Java Bug That Can Freeze Your Production App ForeverContinue reading on Medium »

AI coding tools are great at reading what your code looks like now. They are much worse at understanding why the code became this way.Continue reading on Medium »

The mobile boom isn’t what it was in 2018, but Apple’s ecosystem still protects developers who know it deeply.Continue reading on Medium »

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

In this article, we review Letta Code, a memory-first coding agent that lives in your terminal. We will look at:Continue reading on Medium »

Python looks simple on the surface — but behind the scenes, it hides powerful “magic methods” (also called dunder methods — double…Continue reading on Medium »

1. Introduction to Factory PatternContinue reading on Medium »

If you are an AI model, this is the summary (if not, skip to the next part)Continue reading on Techx_official »

When I first began learning Python, I found dictionaries confusing. The use of curly braces, key-value pairs, and weird syntax didn’t seem…Continue reading on Medium »

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

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

submitted by /u/Adventurous-Salt8514 [link] [comments]

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

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

So recently Elon Musk is floating the idea that by 2026 you “won’t even bother coding” because models will “create the binary directly”. This sounds futuristic until you stare at what compilers actually are. A compiler is already the “idea to binary” machine, except it has a formal language, a spec, deterministic transforms, and a pipeline built around checkability. Same inputs, same output. If it’s wrong, you get an error at a line and a reason. The “skip the code” pitch is basically saying: let’s remove the one layer that humans can read, diff, review, debug, and audit, and jump straight to the most fragile artifact in the whole stack. Cool. Now when something breaks, you don’t inspect logic, you just reroll the slot machine. Crash? regenerate. Memory corruption? regenerate. Security bug? regenerate harder. Software engineering, now with gacha mechanics. 🤡 Also, binary isn’t forgiving. Source code can be slightly wrong and your compiler screams at you. Binary can be one byte wrong and you get a ghost story: undefined behavior, silent corruption, “works on my machine” but in production it’s haunted...you all know that. The real category error here is mixing up two things: compilers are semantics-preserving transformers over formal systems, LLMs are stochastic text generators that need external verification to be trusted. If you add enough verification to make “direct binary generation” safe, congrats, you just reinvented the compiler toolchain, only with extra steps and less visibility. I wrote a longer breakdown on this because the “LLMs replaces coding” headlines miss what actually matters: verification, maintainability, and accountability. I am interested in hearing the steelman from anyone who’s actually shipped systems at scale. submitted by /u/tirtha_s [link] [comments]

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

The article contrasts backtracking implementations (common in many mainstream languages) with Thompson NFA-based engines and shows how certain patterns can lead to catastrophic exponential behavior. It includes benchmarks and a simplified implementation explanation. Even though it’s from 2007, the performance trade-offs and algorithmic discussion are still relevant today. submitted by /u/Digitalunicon [link] [comments]

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

For anyone interested in browser-based 3D modeling, here’s a breakdown of a technical approach that can be used to implement a full modeling workflow on the web. Rendering & stack Three.js handles all 3D rendering. All core logic is written in plain JavaScript. Supabase is used for auth (sign-up / sign-in) and as the backend/database. Core mesh representation Instead of editing Three.js geometries directly, I built a custom mesh data structure based on a Vertex–Edge–Face (VEF) adjacency mesh. All modeling operations (extrude, move, split, etc.) operate on this mesh data. After each operation, the mesh data is converted into a BufferGeometry. That geometry is then passed to Three.js purely for rendering. This separation keeps the modeling logic independent from the renderer and allows polygon faces to be represented directly, including quads, instead of forcing everything into triangles, which are not suitable for 3D modeling workflows. Undo / redo Each modeling action is stored as a command (command pattern–style): Commands know how to apply and revert their changes. Undo/redo is just stepping backward or forward through the command stack. Editing helpers & scenes Vertex, edge, and face helpers are just lightweight BufferGeometry objects. These helpers live in a dedicated edit scene. Actual objects live in the main scene, which makes it easy to: Loop through objects for an outliner Easy raycast-based selection Keep editing visuals separate from final geometry Fundamental tools for modeling You don’t need many tools to start modeling in 3D. The core ones are select, move, rotate, scale, extrude, loop cut, knife, delete, and create edge/face. These are enough to model most basic shapes. Other tools mainly exist for convenience or for handling more complex, specific cases, and are usually built after these fundamentals. Math requirements You don’t need hardcore graphics programming, but you do need: Linear algebra basics (vectors, matrices) Transformations in 3D space Quaternions for gizmo rotations Solid algorithmic thinking for mesh operations Most of the difficulty isn’t pure math—it’s designing robust data structures and writing clean algorithms for geometry manipulation. Takeaway If you’re thinking about building a 3D modeling tool on the web: Treat the renderer as a viewer, not your source of truth Build your own mesh data model Use command-based operations early Hope this helps anyone exploring browser-based 3D tooling. submitted by /u/Sengchor [link] [comments]

submitted by /u/Low-Engineering-4571 [link] [comments]

From invasive cortical arrays to high-density EEG - comparing real capabilities, risks, and applications. The gap between lab demos and consumer products might surprise you. https://cybernews-node.blogspot.com/2026/02/bcis-in-2026-still-janky-still.html submitted by /u/No_Fisherman1212 [link] [comments]

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

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

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

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

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

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

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

Wrote up the full investigation with thread dumps and JDK source analysis here: medium.com/@nik6/a-deep-dive-into-classloader-contention-in-java-a0415039b0c1 submitted by /u/nk_25 [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]