Built on top of the open-source Hermes project, Vertu's new foldable combines AI-agent workflows, enterprise integrations, and ultra-premium luxury finishes.
AI wrote the code in 30 seconds Three lines A simple function I prompted it generated I copied It...
The conversation about cognitive debt in AI-assisted development has been framed as a tradeoff: you can go fast, or you can understand your system, but not both. The proposed mitigations — pair programming, code reviews, requiring a human to understand each change — are braking mechanisms. They trade speed for comprehension. TRIZ (Theory of Inventive Problem Solving) says braking is a compromise, not a resolution. A resolved contradiction eliminates the conflict. You don't choose between speed and understanding. You restructure the system so they don't conflict. There are six root causes of cognitive debt in AI-augmented development. Each one is a contradiction. Each one has a TRIZ resolution that doesn't involve slowing down. Root Cause 1: The Velocity-Comprehension Gap AI generates complex logic in seconds that would take a human hours to write. The human never spends the time typing the code during creation. The theory of the program is never fully formed. The Contradiction Technical contradiction: Improving development speed (AI generates code faster) worsens depth of understanding (human doesn't internalize the logic). Physical contradiction: The development process must be simultaneously FAST (to capture AI's productivity gains) and SLOW (to allow human assimilation of the system's behavior). Resolution: Separation in Space (Principle 2 — Extraction + Principle 1 — Segmentation) The contradiction assumes that the thing being understood IS the code. Extract the understanding target from the code and put it somewhere else — a smaller, slower-moving, human-readable artifact that captures what the code must satisfy, not how it works. Segment the system's theory into independent, composable units. Each unit is one property: "this service must never accept unauthenticated requests," "this data pipeline must preserve ordering," "this retry loop must terminate within 30 seconds." Each property is 1-3 sentences in natural language or 3-10 lines in a predicate language.
I’m a big fan of PostgreSQL and recently started thinking about building a new database system as a side project. I know creating a database is a huge challenge, and I’m still learning, but I really like the idea. If a few passionate people team up together, I believe we can build something interesting. I’d love to know: What struggles do you face with current databases? What features are missing in existing systems? What problems do you wish databases solved better? Performance? Scaling? RAM usage? Replication? Developer experience? Your feedback and ideas would really help. Or shorter and more Reddit-style: Title What problems do you face with existing databases? Content I’m thinking about creating a new database project because I really enjoy working with PostgreSQL. I know it’s a huge challenge, but I like the idea and want to learn deeply by building something. If a few passionate developers team up, maybe we can create something interesting. What problems or frustrations do you currently face with databases? What would you improve if you could design your own database? I’m deeply interested in backend architecture, distributed systems, and database engineering. Previously, I built a backend framework in Go called KVolt, which gave me strong experience in scalability, API architecture, performance optimization, and system design. Recently, I started exploring a bigger challenge: I’m a big fan of PostgreSQL, but I believe there’s still room for innovation in areas like: Performance Scalability Distributed systems Replication Memory optimization Developer experience Modern architecture design I know database engineering is one of the hardest areas in software development, and that’s exactly why it interests me. I’m also looking for a few passionate developers, backend engineers, and system-level programmers who genuinely enjoy solving hard engineering problems and would like to team up on this open-source journey. I’d love to hear from the community: What struggl
I was playing around with antigravity/claude last weekend and put together a 2026 rendition of a project I did almost 15 years ago. Basically it's an app that lets you watch videos with friends. Back in the day it was a great way to share and discover music, especially stuff you normally wouldn't listen to. I'm not quite sure it would work in today's age but maybe there's something there. Either way it's pretty awesome that you can prototype something so quick by just chatting with an LLM. submitted by /u/Zenpher [link] [留言]
give some suggestion in that my company two partner and one partner has no knowledge of development and he will do the busineess related things submitted by /u/Party-Tension-2053 [link] [留言]
In part 1 , the single-document case was easy. In part 2 , two documents brought Write Skew, and we saw that even a native ACID transaction — snapshot isolation — lets it through. So teams reach for the reflex fix: a distributed lock — Redis-based, often a Redlock-style implementation. Acquire a lock on a key, do your Read → Modify → Write, release. On paper, you've finally serialized the critical section — operationally, at least. In practice, you've stepped on three mines. 1. Network latency Every guarded transaction now makes extra round-trips to Redis — before and after hitting your NoSQL store. You've doubled your coordination surface and taken a hard dependency on a second system being up, reachable, and fast on the hot path of every write. The "fast" database is now gated by the lock service. And the coupling bites harder than the average latency suggests: every Redis tail-latency spike becomes your write-latency spike — your p99 inherits Redis's p99 — and if Redis fails over mid-transaction, the lock you think you're holding can effectively vanish on the new primary, dropping you straight into the corruption case below. 2. Deadlock You can dodge deadlock entirely with a single coarse lock — but then every writer serializes on it, and you've thrown away the very concurrency you reached for NoSQL to get. So to keep throughput you go fine-grained, one lock per resource — and the moment an invariant touches more than one key (across this series, it always does), deadlock is back on the table: Transaction A locks key X, then needs Y. Transaction B locks Y, then needs X. Both block until timeout or intervention. The textbook cure — real deadlock detection, maintaining a wait-for graph across every lock holder and breaking cycles as they form — is a distributed-systems project in its own right: not something you bolt onto a cache you reached for precisely to save engineering time. So nobody builds it. Instead teams impose a standing discipline: always acquire locks
submitted by /u/mrpro1a1 [link] [留言]
For a few glorious years, a $399 portable gadget could run almost anything you'd want to play. In 2022, the Steam Deck finally made PC gaming portable and affordable. I played through the vast majority of Elden Ring on a Steam Deck, agape that such a rich world could comfortably fit between my two hands. […]
That "authenticity of host can't be established" message isn't just noise. Here's what's actually happening — and why blindly typing "yes" is a security mistake. Every developer has seen this: The authenticity of host 'example.com (203.0.113.1)' can't be established. ED25519 key fingerprint is SHA256:abc123xyz... Are you sure you want to continue connecting (yes/no/[fingerprint])? Almost everyone types yes without reading it. Then they move on. This message is SSH trying to protect you from one of the most dangerous attacks in network security: the man-in-the-middle attack. Understanding what's happening here — and what the ~/.ssh/known_hosts file actually does — will change how you think about every SSH connection you make. The Problem SSH Is Solving When you connect to ssh user@example.com , how do you know you're actually talking to example.com ? You can't rely on the IP address — IP addresses can be spoofed or rerouted. You can't rely on DNS — DNS can be poisoned. You can't rely on the network path — traffic can be intercepted at any point between you and the server. Without verification, an attacker positioned between you and the server could intercept the connection, pose as the server, decrypt everything you send, re-encrypt it, and forward it along. You'd type your password or authenticate with your key and never know the attacker saw every keystroke. This is a man-in-the-middle (MITM) attack . It's not theoretical. It happens on compromised networks, corporate proxies, malicious Wi-Fi hotspots, and misconfigured infrastructure. SSH's defense is host key verification . Every SSH server has a unique cryptographic identity — its host key. Before you exchange any sensitive data, the server proves it holds the private key corresponding to a public key you've previously verified. If the keys don't match, SSH warns you — loudly. What a Host Key Actually Is When OpenSSH is installed on a server, it automatically generates a set of host key pairs. These live in /etc
AI Glossary: A to Z An A-to-Z glossary of AI terms, created with help from AI itself. Because in 2026, the best way to study AI is apparently to ask AI itself. 🤣 Written for beginners and practitioners alike. Each term includes a plain English definition and a real-world example. Quick Navigation A · B · C · D · E · F · G · H · I · J · K · L · M · N · O · P · Q · R · S · T · U · V · W · X · Y · Z ↑ Back to top A Term Definition Example Agent (AI Agent) An AI system that perceives its environment, makes decisions, and takes autonomous actions to achieve a goal A coding agent that writes, runs, and debugs its own code without human intervention AGI (Artificial General Intelligence) A hypothetical AI that can match or exceed human-level intelligence across any task — does not yet exist Often cited as a long-term goal by companies like OpenAI and DeepMind AI (Artificial Intelligence) The field of computer science focused on building machines that can perform tasks normally requiring human intelligence ChatGPT writing an essay, an algorithm detecting cancer in X-rays AI Ethics The principles and practices for developing and deploying AI in ways that are fair, transparent, and safe Auditing a hiring algorithm to ensure it doesn't discriminate by gender or race AI Safety The field dedicated to ensuring AI systems remain reliable, controllable, and beneficial as they grow more capable Research into preventing AI from pursuing goals that harm people Alignment The challenge of ensuring an AI system's goals and behaviour match what its designers and users actually intend Preventing a powerful AI from optimising for a metric in a way that causes unintended harm Annotation The process of labelling raw data so it can be used to train supervised learning models Humans drawing bounding boxes around cars in images to train a self-driving model API (Application Programming Interface) A defined interface that lets software systems communicate with each other Calling the OpenAI API to
GitHub Finish-Up-A-Thon Challenge Submission There’s something strangely emotional about reopening an old unfinished game project. Especially one that once felt like “the next big idea” at 2 AM during a hackathon 😭 You open the folder expecting nostalgia… …and instead find: broken UI random commits duplicated code missing assets unfinished features and functions named things like test2_final_REAL.js That’s exactly what happened when I reopened WhatUsee . A multiplayer browser game I originally started building as a fun experimental idea. At first, it wasn’t meant to become anything serious. It was just a simple concept: “What if players had to race against each other to identify hidden objects inside chaotic images?” That tiny idea slowly turned into a real-time multiplayer hidden-object game. And honestly? At the beginning, building it was insanely fun. 💡 The Original Idea Behind WhatUsee Most multiplayer browser games focus on: shooting drawing trivia racing But I wanted something different. Something that created those chaotic: “WAIT I SEE IT—NO WAY 😭” moments. The idea was simple: Players join a room together. An image appears. Somewhere inside that image is: a hidden object an animal a logo a random item or something cleverly camouflaged And everyone races to identify it before the timer ends. Fast reactions. Visual focus. Pure multiplayer chaos. That became WhatUsee . At first, the project was extremely small. Just: Socket.IO basic image display simple guessing and a rough scoreboard No polish. No proper lobby. No smooth UI. But even in that early state… …the game already felt fun. And that’s what made me continue building it. 😭 Then The Project Slowly Got Abandoned Old unfinished WhatUsee multiplayer game interface with basic UI and minimal styling Like most side projects… life happened. College work. Burnout. Other responsibilities. Random unfinished ideas. And slowly, WhatUsee became: “that project I’ll definitely finish later.” The game technically worked.
Cloudflare recently added support for Claude Managed Agents, allowing developers to run and manage Claude agents within Cloudflare. Developers can connect agents to private systems, choose their runtime environment, and monitor agent activity using Cloudflare services. By Renato Losio
When you build a PowerApps Component Framework (PCF) component that will be used across multiple geographies, need to serve labels, button captions, validation messages, and tooltips in the user's preferred language. PCF has a built-in answer based on .resx resource files, the same format used by .NET applications. The mechanism is elegant in production — but surprisingly tricky during local development. This walkthrough takes you through the full setup, step by step, and then explains a problem that arises while locally debugging your PCF. Step 1 — Create the strings folder and your first .resx file PCF expects your localized strings to live in a folder (the conventional name is strings ) inside your component directory. Each language gets its own file, named with the pattern: <ComponentName>.<LCID>.resx The <LCID> part is the numeric Locale ID , not the textual code ( en-US , it-IT ). The framework relies on this naming convention to identify which file to load for a given user. Common LCIDs: Language LCID English (en-US) 1033 Italian (it-IT) 1040 German (de-DE) 1031 French (fr-FR) 1036 Spanish (es-ES) 3082 Japanese (ja-JP) 1041 Chinese Simplified (zh-CN) 2052 Portuguese (pt-BR) 1046 For a component called EquipmentGrid , the structure looks like this: EquipmentGrid/ ├── ControlManifest.Input.xml ├── index.ts └── strings/ ├── EquipmentGrid.1033.resx ├── EquipmentGrid.1040.resx └── EquipmentGrid.1031.resx Tip: Always include 1033.resx (English). The PCF runtime falls back to the first <resx> declared in the manifest when the user's preferred language isn't available, and English is the safest default. Step 2 — Author the resource file content A .resx file is just XML. Here's a minimal Italian version ( EquipmentGrid.1040.resx ): <?xml version="1.0" encoding="utf-8"?> <root> <resheader name= "resmimetype" > <value> text/microsoft-resx </value> </resheader> <resheader name= "version" > <value> 2.0 </value> </resheader> <resheader name= "reader" > <value> System.Resou
We let AI agents loose on a payment platform. They crushed the boring stuff. Then they silently broke the stuff that matters. A survey came out last week. 54% of all code is now AI-generated. Up from 28% last year. I read that number and thought: yeah, that tracks. We're probably in that range too. But here's the thing nobody's asking — which 54%? Not all code carries equal weight. A CRUD endpoint for fetching merchant details? Low risk. The webhook handler that transitions a payment from pending to complete ? That's someone's rent. Someone's payroll. Get that wrong and money moves where it shouldn't, or worse, money doesn't move at all. I'm the CTO of a payment platform. FCA-authorised, processing real money, real merchants, real consequences. We run NestJS microservices, Docker, Traefik — the usual stack. And we've been using AI agents aggressively for over a year now. I'm not here to tell you AI is dangerous. It's not. I'm here to tell you it's dangerous when you forget what it's actually good at. The 80% Where AI Agents Are Genuinely Brilliant Let me give credit where it's due. AI agents have made our team faster in ways that would have seemed absurd two years ago. API scaffolding. Generating service boilerplate. Writing Zod validation schemas. Spinning up new endpoints. Creating test stubs. Refactoring imports. Migrating patterns across repos. We run multiple microservices. When we need a new service, an agent can scaffold the entire thing — module structure, base configuration, Docker setup, Traefik labels — in minutes. What used to be a half-day of copy-paste-and-tweak is now a conversation. When we overhauled our env management across all repos, AI agents did the grunt work. They mapped every .env file, found naming conflicts, identified common variables, and generated a unified Zod schema. What would have taken a team days of grep-and-spreadsheet work took hours. For this 80% of the codebase — the predictable, pattern-following, structurally repetitive code