# standard A document or rule that specifies requirements, guidelines, characteristics, or procedures for consistent use in products, systems, services, processes, or testing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The skills CLI now supports Notion hosted skills DevFeed: [The skills CLI now supports Notion hosted skills]() Original publisher: [Read original article]() Author: Ben Sabic Published: 2026-09-17T18:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Agent Skills](), [Notion](), [Command-line interface](), [API](), [personal access token](), [standard]() Tags: [agent](), [agent-skills](), [api](), [cli](), [commands](), [install](), [integration](), [notion](), [permissions](), [personal-access-token](), [skills](), [standard]() ### AI overview The skills CLI now supports Notion-hosted skills as an installation source. Teams can author, review, and update reusable agent skills in Notion, then install selected skill packs or individual skills through the CLI. Authentication uses a Notion personal access token and respects Notion page permissions. ### Source excerpt skills@1.7.0 adds Notion skills databases as an install source for agent skills . Notion skills are reusable agent skills written as Notion pages. Teams author, review, and update them in the workspace they already use, then install them into any agent the skills CLI supports. No Git repository required. To browse your Notion workspace's skills, run: The CLI lists the skill packs shared with you and installs every skill in the packs you select. To install a single skill, pass its Notion page URL: Both commands use the Notion CLI (ntn) to authenticate. To set it up: ntn login requires a Notion personal access token, so your workspace must allow them. Access follows Notion's page permissions. You only see skills shared with you, so controlling who can install a skill is the same as controlling who can view the page. This integration is built on Notion's new Agent Skills API, which exposes skills stored in Notion as standard Agent Skills folders. Because the format is standard, the same skills work in any agent that reads them. Get started by creating a Notion skill. Read more ## Winner: Identifying a Bandgap Voltage Reference Circuit in a Chip Micrograph DevFeed: [Winner: Identifying a Bandgap Voltage Reference Circuit in a Chip Micrograph]() Original publisher: [Read original article]() Author: bunnie Published: 2026-08-30T06:27:57Z Content type: article Language: en Sources: [bunnie's blog]() Topics: [circuit](), [standard]() Tags: [2026](), [baochip](), [circuit](), [name-that-ware](), [process]() ### AI overview The article identifies the featured chip structure as a bandgap voltage reference built around paired NPN transistors. It explains how the circuit maintains a near-constant voltage and why dummy transistors surround the active devices. ### Source excerpt The structure in question for last month's ware are a pair of NPN transistors that form the core of a bandgap voltage reference circuit. As its name implies, a bandgap voltage reference generates a near-constant voltage for use inside chips. The voltage is intended to be fairly constant over process variations, temperature variations, and power [...] ## TBM 435: 20 Unfiltered Operating Takes DevFeed: [TBM 435: 20 Unfiltered Operating Takes]() Original publisher: [Read original article]() Author: John Cutler Published: 2026-08-08T00:31:35Z Content type: opinion Language: en Sources: [The Beautiful Mess]() Topics: [Framework](), [standard](), [Exception handling]() Tags: [advice](), [implement](), [simplify](), [strategy]() ### AI overview An opinionated set of operating advice argues that the North Star Framework is more useful as a teaching tool than as a rigid organizational practice. The article also cautions that vision-to-tactics pyramids can distract teams by turning labels and abstractions into substitutes for understanding real work. ### Source excerpt I had a friend reach out recently for advice. I started writing... ## RFC 10005: BGP Community for link capacity DevFeed: [RFC 10005: BGP Community for link capacity]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-01T13:31:00Z Content type: article Language: en Sources: [Justin Wilson (j2sw)]() Topics: [BGP](), [standard](), [Load Balancing](), [Network]() Tags: [bgp](), [capacity](), [internet](), [load-balancing](), [network](), [network-operations](), [rfc](), [rfc-10005](), [route](), [routers](), [routing](), [standard](), [traffic]() ### AI overview RFC 10005 defines a BGP extended community for carrying link bandwidth information in routes. When multiple BGP paths are eligible, routers can use the value to weight traffic according to link capacity, while normal best-path policy still determines route eligibility. The RFC is currently a draft. ### Source excerpt RFC 10005 defines a BGP extended community that lets a router attach link bandwidth information to a route. Another router can use that value when it spreads traffic across multiple BGP paths. RFC 10005 matters because links are not always of the same capacity. This RFC provides routers with a standard way to carry bandwidth ... Read more The post RFC 10005: BGP Community for link capacity appeared first on Justin Wilson (j2sw). ## Obfuscated Rhythm Games DevFeed: [Obfuscated Rhythm Games]() Original publisher: [Read original article]() Author: Dan Lew Published: 2026-06-23T14:17:46Z Content type: opinion Language: en Sources: [Dan Lew Blog]() Topics: [obfuscation](), [standard]() Tags: [game](), [games](), [music](), [obfuscation](), [standard]() ### AI overview The article examines three rhythm games released in 2025 that intentionally obscure which buttons players should press and when. It discusses how Rift of the Necrodancer, Rhythm Doctor, and Unbeatable derive much of their challenge from less legible note charts and altered visual or auditory cues. ### Source excerpt I've been a rhythm game fiend since my introduction to Dance Dance Revolution in the early 2000s. I spent years obsessed with DDR, took a detour into Beatmania, then played Guitar Hero / Rock Band nonstop for years. I haven't gone deep on any rhythm games recently, ## Unsigned char std::basic\_string\<\> in C++ DevFeed: [Unsigned char std::basic\_string\<\> in C++]() Original publisher: [Read original article]() Published: 2026-01-03T22:00:02Z Content type: tutorial Language: en Sources: [Bert Hubert's writings]() Topics: [C++](), [standard](), [LLVM](), [clang](), [gcc]() Tags: [bits](), [c-plus-plus](), [clang](), [concatenation](), [cryptographic](), [freebsd](), [gcc](), [llvm](), [openbsd](), [standard](), [string]() ### AI overview A C++ post explains why code using std::basic_string can fail on FreeBSD and OpenBSD. The issue involves std::char_traits: LLVM 19 removed its unconstrained base template because the C++ Standard does not require it for unsigned-character types. Code may need string concatenation and related operations replaced or a correct custom specialization provided. ### Source excerpt Brief post on a somewhat vexing and irritating C++ problem I ran into some time ago. I hope that this page will help other people deal with this problem more quickly than I did. I've long used std::basic_string, an unsigned char string, for fiddling with bits. You could use a regular char string, but especially when doing cryptographic or sub-byte operations, it is more convenient to not have to deal with sign bits. ## Reflecting on Threats: The Frame DevFeed: [Reflecting on Threats: The Frame]() Original publisher: [Read original article]() Author: Adam Published: 2023-04-10T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [systems](), [standard](), [passwords](), [spoofing](), [bug](), [Pull Request](), [YAML]() Tags: [bug](), [code](), [password](), [spoofing](), [standard](), [yaml]() ### AI overview The author reflects on how the framing and subtitle of the Threats book shaped its content. The article discusses the value of shared engineering terminology and argues that common understandings, standards, and available tools can support more consistent threat assessment and evaluation of software flaws. ### Source excerpt Reflecting on the framing of the Threats book ## How SerenityOS declares ssize\_t DevFeed: [How SerenityOS declares ssize\_t]() Original publisher: [Read original article]() Author: Andreas Kling Published: 2023-04-04T00:00:00Z Content type: opinion Language: en Sources: [Andreas Kling]() Topics: [C](), [POSIX](), [Operating system](), [compilers](), [standard](), [Library]() Tags: [c](), [compilers](), [cpp](), [libraries](), [library](), [posix](), [serenityos](), [standard](), [technical](), [unix]() ### AI overview This article explains how SerenityOS declares ssize_t using a C preprocessor macro technique. It contrasts the approach with more architecture-specific declarations commonly used by other C libraries and notes the limitations of the hack. ### Source excerpt This post explores one of my favorite hacks in SerenityOS. I don't recommend doing this in your codebase, but it has worked for us so far. :^) ## A very small Rust binary indeed DevFeed: [A very small Rust binary indeed]() Original publisher: [Read original article]() Author: Graham King Published: 2022-07-01T16:00:32Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [Rust](), [Assembly](), [Linux](), [Optimization](), [x86](), [standard]() Tags: [assembly](), [linux](), [optimization](), [rust](), [software](), [standard](), [standard-library](), [x86]() ### AI overview A tutorial explores how to reduce the size of an x86_64 Linux Rust binary, starting from 3.6 MiB and applying techniques such as stripping symbols, adjusting panic handling, link-time optimization, and rebuilding the standard library. It compares the result with a pure assembly program and explains relevant Linux program-loading and Rust runtime behavior. ### Source excerpt Can we make a Rust program that's as small as it's assembler equivalent? ## NIST Brings Threat Modeling into the Spotlight DevFeed: [NIST Brings Threat Modeling into the Spotlight]() Original publisher: [Read original article]() Author: Adam Published: 2021-09-23T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [standard](), [Code]() Tags: [article](), [code](), [nist](), [post](), [spotlight](), [standard](), [verification]() ### AI overview This post announces a Dark Reading article about NIST and threat modeling. It mentions NIST releasing a minimum standard for vendor or developer verification of code in July. ### Source excerpt New at Darkreading, a post on NIST and threat modeling ## Threat Model Thursday: NIST's Code Verification Standard DevFeed: [Threat Model Thursday: NIST's Code Verification Standard]() Original publisher: [Read original article]() Author: Adam Published: 2021-07-15T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [standard](), [Testing](), [Code](), [Development]() Tags: [code](), [cybersecurity](), [fuzzing](), [gcc](), [nist](), [software](), [standard](), [testing](), [verification]() ### AI overview The article examines NIST's Recommended Minimum Standard for Vendor or Developer Verification of Code, including its technical requirements and emphasis on threat modeling. It highlights the standard's coverage of automated testing, static and dynamic analysis, included software, and bug fixing, while arguing that developers should prepare for the new requirements. ### Source excerpt Earlier this week, NIST released a Recommended Minimum Standard for Vendor or Developer Verification of Code. I want to talk about the technical standard overall, the threat modeling component, and the what the standard means now and in the future. ## Medical Device Security Standards DevFeed: [Medical Device Security Standards]() Original publisher: [Read original article]() Author: Adam Published: 2019-11-02T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Security](), [Cybersecurity](), [standard]() Tags: [checksums](), [connectivity](), [cost](), [cybersecurity](), [digital-signature](), [disclosure](), [funding](), [medical-devices](), [network](), [pii](), [security](), [standards]() ### AI overview This commentary compares four cybersecurity approaches for medical devices: a comprehensive process-centered framework, MITA's factual material data sheet, disclosure of device behavior and cybersecurity properties, and funded threat-modeling work. It notes that differing national requirements can increase costs and create conflicting demands. ### Source excerpt Recently, I've seen four cybersecurity approaches for medical devices, and we can learn by juxtaposing them. ## Comparison of OWASP ASVS v3 and v4 Password Requirements DevFeed: [Comparison of OWASP ASVS v3 and v4 Password Requirements]() Original publisher: [Read original article]() Author: adam Published: 2019-06-26T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Requirements](), [passwords](), [standard]() Tags: [analysis](), [comparison](), [cost](), [errors](), [password](), [passwords](), [requirements](), [standard](), [standards](), [useful]() ### AI overview The article highlights Bruce Marshall's comparison of password requirements in OWASP ASVS versions 3 and 4. It argues that standards bodies should provide clear difference documents when updating or building on standards, because this reduces user analysis, errors, cost, and wasted effort. ### Source excerpt Bruse Marshall has put together a useful comparison of password requirements from OWASP ASVS v3 and v4. ## Threat Modeling as Code DevFeed: [Threat Modeling as Code]() Original publisher: [Read original article]() Author: Adam Published: 2019-01-23T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [engineering-culture](), [Code](), [standard]() Tags: [code](), [delivery](), [engineering](), [practices](), [productivity]() ### AI overview This commentary explores representing threat models as code and aligning threat modeling with established engineering practices. It argues that converting threat-modeling analysis into code and selecting suitable code representations can increase delivery consistency and productivity, while requiring upfront effort. ### Source excerpt Exploring threat models as code. ## Writing more legible SQL DevFeed: [Writing more legible SQL]() Original publisher: [Read original article]() Author: Map Published: 2016-01-08T20:55:56Z Content type: tutorial Language: en Sources: [Craig Kerstiens]() Topics: [SQL](), [formatting](), [Code](), [standard]() Tags: [code](), [formatting](), [postgres](), [postgresql](), [sql](), [standard]() ### AI overview The article recommends formatting SQL for readability and maintainability. Its suggestions include putting one column, table, or join per line; aligning projections and conditions; using explicit column names in grouping and ordering; commenting queries; adopting consistent keyword casing; and using CTEs to make complex queries easier to reason about. ### Source excerpt A number of times in a crowd I've asked how many people enjoy writing SQL, and often there's a person or two. The follow up is how many people enjoy reading other people's SQL and that's unanimously 0. The reason for this is that so many people write bad SQL. It's not that it doesn't do the job, it's just that people don't tend to treat SQL the same as other languages and don't follow strong code formatting guidelines. So, of course here's some of my own recommendations on how to make SQL more readable. One thing per line Only put a single column/table/join per line. This is going to make for slightly more verbose SQL, but it will be easier to read and edit.. Here's a basic example: SELECT foo, bar FROM baz Align your projections and conditions You can somewhat see this in the above with foo and bar being on the same line. This is reasonably common for columns you're selecting, but it's not applied as often in AND or GROUP BY clauses. As you can see there is a difference though between: SELECT foo, bar FROM baz WHERE foo > 3 AND bar = 'craig.kerstiens@gmail.com' And a cleaner version: SELECT foo, bar FROM baz WHERE foo > 3 AND bar = 'craig.kerstiens@gmail.com' Use column names when grouping/ordering This is personally an awful habit of mine, but it is extremely convenient to just order by the column number. In the above query we could just ORDER BY 1. This is especially easy when column 1 may be something like SUM(foo). However, ensuring you explicitly ORDER BY SUM(foo) will help limit any misunderstanding of the data. Comments You comment your code all the time, yet so few seem to comment their queries. A simple -- allows you to inline a comment, perhaps where there's some oddities to what you're joining or just anywhere it may need clarification. You can of course go much further, but at least some basic level of commenting should be required. Casing As highlighted in these examples, having a standard for how you case your queries is especially handy. Sticking wit ## How the Linux Kernel's container\_of() Macro Works DevFeed: [How the Linux Kernel's container\_of() Macro Works]() Original publisher: [Read original article]() Published: 2012-11-10T00:00:00Z Content type: article Language: en Sources: [Radek Pazdera]() Topics: [C](), [Linux Kernel](), [container](), [Compiler](), [standard]() Tags: [c](), [compiler](), [container](), [implementation](), [library](), [linux-kernel](), [standard](), [standard-library](), [value]() ### AI overview This tutorial explains how the Linux Kernel's container_of() macro derives a pointer to a containing structure from a pointer to one of its members. It describes GNU C extensions, including braced groups within expressions and typeof(), and explains the zero-pointer dereference and member-offset techniques used in the implementation. ### Source excerpt Probably the most confusing piece of C code I've encountered ## Static and extern keywords in C DevFeed: [Static and extern keywords in C]() Original publisher: [Read original article]() Published: 2011-09-01T00:00:00Z Content type: tutorial Language: en Sources: [Radek Pazdera]() Topics: [C](), [standard](), [Code]() Tags: [c](), [compilation](), [external](), [function](), [local-variables](), [memory](), [runtime](), [scope](), [standard]() ### AI overview A tutorial explaining how the static and extern keywords in C affect linkage, storage duration, memory allocation, and visibility across scopes and compilation units. It also describes external, internal, and no linkage, along with static and automatic storage duration. ### Source excerpt What does the C standard actually say about these? ## Tiling a Chessboard DevFeed: [Tiling a Chessboard]() Original publisher: [Read original article]() Published: 2011-06-26T20:24:09Z Content type: tutorial Language: en Sources: [Jeremy Kun]() Topics: [color](), [standard]() Tags: [chessboard](), [color](), [dominoes](), [mathematics](), [standard](), [tiling]() ### AI overview The article uses coloring arguments to show that certain chessboard and grid regions cannot be tiled with dominoes. It first analyzes 2-by-1 dominoes on a chessboard with two opposite corners removed, then applies a specially chosen coloring to a 3-by-1 domino problem and generalizes the proof method. ### Source excerpt Problem: Take a chessboard and cut off two opposite corners. Is it possible to completely tile the remaining board with 2-by-1 dominoes? Solution: Notice that every domino covers exactly one white tile and one black tile. Counting up the colors, we have 32 white and 30 black. Hence, any tiling by 2-by-1 dominoes will leave two extra white squares unaccounted for. So no such tiling is possible. Problem: Cut one corner off a chessboard. ## Valuing Employees DevFeed: [Valuing Employees]() Original publisher: [Read original article]() Author: Map Published: 2010-02-28T01:10:23Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Job](), [standard]() Tags: [business](), [employees](), [joel-spolsky]() ### AI overview The article argues that employee compensation should reflect the value people deliver and that retention depends on more than pay. Employees who are no longer challenged should seek new challenges within their role or move elsewhere. ### Source excerpt A coworker and I were recently having conversations over employee compensation. We covered the gambit around employee feedback, evals, and compensation. He mentioned Joel Spolsky, and his format of being very open about where individuals were ranked. He also pointed me to: http://alumnit.ca/~apenwarr/log/?m=200904#05 which provided good insight, though I most like his final point. The end goal with evaluating your employees and compensation for them is to make sure they're happy. Sure the business should make sure they feel like you're worth what you're being paid, but usually there is no question about this, or if there is you're quickly escorted out the door. While this is an interesting model, I think it can be much simpler, but companies usually confine themselves too much in giving credit to employees. There was another recent occasion where a statement was made of 'no more playing stick them up, until next year'. When I first thought about this, I knew I didn't like the statement, but was unsure of why. The reason is that there can be several reasons why employees leave. Only one of which is compensation. If you feel you're being adequately compensated for the job you're doing it makes sense. But there's another reason thats very clear in the valley but less clear in other parts of the country. Paul Buchheit at Startup School this weekend in Berkeley said it very well: If you've been at your job too long, QUIT. Meaning if you're comfortable, you know the people, you know how to do your job, and you're not being challenged, then you should go somewhere where you are challenged. So what does this have to do in regards to playing stick em up? Well if you're at a comfortable place you should be compensate appropriately that's fair. However if you're at a comfortable place, you should either find ways to be challenged there or move on. If you're challenged there it means your role over time will change, there's not a standard guide for how quickly you become experi