标签:#c
找到 32690 篇相关文章
We Don't Have to Be This Bad at Improving Society
Watch a Steam Controller Skitter Itself to Its Charge Puck
The Field Equation, living shader geometry folded into a breathing object
The Fall of the Theorem Economy
EU could announce social media ban for kids in September
The Age of Personalized Hardware Is Coming
Evaluation order and nontermination in query languages
Some Robots Just Can’t Handle The Expo
As you'd expect, there were robots aplenty at the AI Engineer World's Fair Expo, although with mixed...
Applied Creativity and Concept Generation - Brainstorming
Thomas Edison put it plainly: "To have a great idea, have a lot of them." Steve Jobs said something similar. "Creativity is just having enough dots to connect... to connect experiences and to synthesise new things." Both of them are saying the same thing. Your first idea is rarely your best one. The reason why people you call creative can come up with great ideas easily is that they have had more experiences or have thought more about their experiences than other people. So the question becomes: how do you get more ideas, faster? The Most Used Method for Applied Creativity The answer has a name. It was coined by advertising executive Alex Osborn in the 1940s. He called it brainstorming - using the brain to storm a creative problem, with each person in the room attacking the same objective. It sounds simple. Most teams think they already do it. Most of them are wrong. Real brainstorming is a structured process with rules. Break the rules, and you get something that looks like brainstorming but produces far fewer useful ideas. Why Most Brainstorming Sessions Fail Here is what kills a brainstorming session before it even starts. Someone says an idea. Someone else says, "That won't work." The room goes quiet. People stop sharing. That is it. That is the whole problem. When people fear judgment, they self-censor. They only say the safe, obvious ideas. The interesting ones, the ones that could actually lead somewhere, stay locked inside people's heads. Most teams have that one gaffer who has already decided which ideas are worth hearing before anyone has finished their sentence. Or the one who gives you the floor, listens patiently, and then quietly bins everything you said, not because it was bad, but because it was not theirs. Both types do the same damage. The room reads it. People stop sharing. And just like that, the best idea in the session never gets spoken. The goal of brainstorming is to get more ideas. That means the number one rule is: defer judgment . The Rule
Google VP of Technology says he’s given up on coding
In his keynote on Wednesday, Benoit Schillings, vice president of Technology at Google DeepMind and...
X is making a fresh push for live video with new creator payouts
X has launched a new live streaming command center and additional creator payouts.
From Passwords to Token-based Authentication
Every authentication mechanism in use today emerged to address a specific set of constraints the previous one wasn't designed for. This article walks through that chain — not as a list of definitions, but as a sequence of problems and the constraints that shaped each solution. 1. The Problem With Sending Passwords Every Request The earliest widely used approach, HTTP Basic Authentication, is also the simplest to understand. The client sends the username and password, base64-encoded, on every single request: GET /api/data Authorization: Basic dXNlcjpwYXNzd29yZA== Base64 is not encryption — it's just a reversible encoding. Anyone who intercepts this header has the raw credentials. This approach has three structural problems. First, the password is transmitted on every request, which means every request is a new opportunity for it to leak — through logs, proxies, or a compromised network. Second, the server has to validate credentials against the database on every single call, since there's no concept of an established session; that's a database hit for every API request, which doesn't scale. Third, there's no way to limit what the credentials can do or for how long. The password grants full access until it's changed, and changing it is the only way to revoke access — there's no way to invalidate just one client's access without affecting every other client using the same password. 2. Sessions Try to Fix It, But Introduce New Problems The next evolution moved the credential check to a single moment: login. After verifying the password once, the server creates a session, stores it (in memory or a database), and gives the client a session ID, usually via a cookie. Every subsequent request just sends that ID, not the password. The user logs in by submitting their username and password. Browser ───────────────▶ Server Login Request The server validates the credentials. Server ── checks username/password ──▶ Database If the credentials are valid, the server creates a new se
Seattle Just Had an Earthquake
I was just laying in bed getting some work done and my house started shaking. Camano Island, north of Seattle. Anyone else?
My Story of 3D Realms / Apogee Part I (2020)
Fable Is Set Free - There’s A Brand New Claude In Town
As we initially covered yesterday, after some heavy lobbying by Anthropic, U.S. Commerce Secretary...
You're Not Lazy — You're Time Blind. Here's How Lock In Fixes It.
I sat down to work for 2 hours. I actually worked for 45 minutes. Sound familiar? You open your...
The Complete Homemade Juggling Beanbag Guide
Show HN: I wrote a Rust book ending with a Redis clone
Indian tech tycoon bets $30M of his own money to build AI alternative to Microsoft Office
Neo is Bhavin Turakhia’s fifth venture and his latest involving enterprise software. This time he's taking on Microsoft Office, Google Apps with AI.