Sr. Content Developer at Microsoft, working remotely in PA, TechBash conference organizer, former Microsoft MVP, Husband, Dad and Geek.
162177 stories
·
33 followers

100+ Years of Student Radio History in the DLARC College Radio Collections

1 Share
2024 KUSF College Radio Day Zine cover

Happy College Radio Day! In honor of the annual celebration of student radio (this year on October 2), we invite you to explore the college radio collections in the Internet Archive’s Digital Library of Amateur Radio and Communications (DLARC). Some of the latest additions include materials that shed light on college radio’s earliest days.

College Radio Club Launches at Harvard in 1906

In the first decade of the 20th century, radio clubs started to form on college campuses. In 1906, students at Harvard University offered to send wireless messages across “the yard” as part of the activities of the Weld Phonepterograph Company, which founder Robert Gowen described as “the first college radio club” in a 1923 article for Radio News. Robert Rydzewski digs into the story of this largely forgotten club at Harvard in a 2023 article for The Antique Wireless Association Review, which can also be found in DLARC. Other clubs followed and while they focused primarily on what we think of as amateur or ham radio, these groups were also responsible for some of the first student-created radio broadcasts and student-built college radio stations in the 1920s.

Radio News, September 1923

Radio Clubs and Broadcast Experiments in the 1920s

Recently added items to DLARC from the archives of the Dartmouth College Radio Association help to tell the early story of college radio. By June 1920, the club operated amateur station 1YB, hosted guest lecturers on radio-related topics, and ran code classes. In 1924, licenses were obtained for both an experimental station and a commercial broadcast station (WFBK). Located in the Wilder Physics Laboratory, WFBK’s brief time on the air included reports from sporting events and performances by campus music groups. A newspaper account at the time explained that a radio communication class utilized the broadcast station’s facilities for sending and receiving Morse code messages as well.

Circa 1940 QSL card from Dartmouth College Radio Association. Source: Dartmouth College, Radio Club [Dartmouth Amateur Radio Association] records, DO-5, Rauner Library Archives and Manuscripts

Newly added materials from The Milwaukee School of Engineering represent the wide range of radio-related activities at the school, including courses, amateur radio stations, and broadcast radio (beginning in the early 1920s). Within the Milwaukee School of Engineering Amateur Radio collection, there are clippings from campus publications, QSL cards, and construction plans for a “high grade radio-phone.” The Milwaukee School of Engineering Radio Stations collection contains items related to broadcast stations on campus, including current station WMSE-FM and its predecessors WIAO and WSOE. Gems in the collection include WMSE metal charts from the 1980s, which reported on airplay for new music releases from bands like Slayer, Megadeth and Anthrax.

WMSE Metal Chart showing top airplay from March and April 1987. Source: Milwaukee School of Engineering Archives

New Additions to Campus Radio Collections

While perusing the DLARC College Radio collection, one can see the trajectory of college radio, especially as campus-only carrier current transmissions became more common throughout the 1940s and 1950s. By this point, we see separate student organizations devoted to either amateur radio or college radio of the broadcast variety, although at times, the clubs might collaborate on technical projects. The Duke University Radio collection contains many article clippings and photos of student station WDBS from the 1950s as well as ephemera from short-lived dorm-based WDUK. More recent items include show flyers from currently operating station WXDU.

Poster from the files of Duke University’s college radio station WXDU.

Additionally, contributions to the Vanishing Culture GoFundMe campaign allowed our scanning team to digitize college radio collections from the archives at Amherst College, Middlebury College, and The College of William & Mary. With materials from stations dating back to the 1940s and 1950s, these collections contain documentation that paints a picture of the ever-changing student radio scene. Handmade posters, DJ manuals, correspondence, program guides, studio notebooks (with scribbled comments written by DJs) and scrapbooks are rich sources of information about the management and activities of each station, as well as offering a look at how stations interacted with each other.

The DLARC College Radio collection can be viewed at archive.org/details/collegeradio. Materials from college-based amateur radio stations can be found within the collection at archive.org/details/collegiate-amateur-radio.

The Digital Library of Amateur Radio & Communications is funded by a grant from Amateur Radio Digital Communications (ARDC) to create a free digital library for the radio community, researchers, educators, and students. DLARC invites radio clubs, radio stations, archives and individuals to submit material in any format. To contribute or ask questions about the project, contact: Kay Savetz at kay@archive.org. Questions about the college radio sub-collections can be directed to Jennifer Waits at jenniferwaits@archive.org.

The post 100+ Years of Student Radio History in the DLARC College Radio Collections first appeared on Internet Archive Blogs.

Read the whole story
alvinashcraft
24 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Coding Agents Love Decision Records

1 Share

The following article originally appeared on Duncan Davidson’s blog and is being republished here with the author’s permission.

Decision records give coding agents durable project context—as long as they don’t turn every decision into a courtroom transcript.

Architectural Decision Records (ADRs) help human teams establish rules and carry context forward in software projects. They capture significant design choices, their context, and the reasons behind them. Like many tools built for human software teams, ADRs work well for coding agents too.

Agents often arrive with little memory of yesterday and only a narrow view of a codebase. Even systems with persistent memory may preserve context without establishing whether it is accurate, current, or accepted by the human team. Decision records help them understand the intent behind the code rather than having to infer it. Keeping them in a project repository spares agents from having to trawl through issues, search chats, and perform code archaeology. When you record intent explicitly, an agent is less likely to mistake an implementation detail for a foundational rule.

Once a decision enters an agent’s context window, the agent may adhere to it even more rigidly than a human would. In my own work, I’ve seen agents fight tooth and nail to apply an accepted decision even when it is obsolete. In one case, an agent preserved an outdated storage abstraction across a new feature because an ADR still described it as mandatory. Instead of flagging the mismatch, it added another layer to keep the new requirement technically compatible with the old ruling.

The first remedy is to give agents explicit permission to question decisions that no longer fit—and to watch for signs that they’re overfitting. But that solves only half the problem. When you invite an agent to update a decision, a second tendency appears: preserving the deliberation. Every clarification becomes an amendment explaining its own existence at the expense of clarity. Small implementation details become rules, and cross-references acquire their own restatements and justifications. The result is overlitigated prose that is hard for humans to read.

ADRs should absolutely be readable by humans, especially as we lean on agents to generate more and more code. To counter this, I’ve become explicit in my projects’ AGENTS.md files about how agents should apply and maintain ADRs. Here’s an excerpt from one:

Architectural Decision Records (ADRs) are stored as Markdown files in the
docs/decisions directory. Treat accepted ADRs as binding. Proposed ADRs
are non-binding context. Superseded ADRs are historical context and do
not govern current work. If a given task conflicts with an accepted ADR,
stop and discuss whether the task or ADR should change and propose the
change that you think should be made. Propose new ADRs or updates to
existing ones when a change introduces or revises a durable product or
architectural decision.

Keep ADRs succinct. Each ADR carries only its current text; Git history
is its changelog, so do not add or maintain amendment logs in ADR
headers. When substantively changing an accepted ADR, add or update a
single Updated: date line after Date:—its presence signals that history
exists and Git has the details. A superseded ADR records a Superseded-On:
date instead of Updated: , matching the Supersedes: line on the ADR that
replaced it. State each rule once in the ADR that owns it and cross-reference
it from other ADRs instead of restating it.

These instructions are still evolving in my projects, and different projects will need different conventions. Some teams will prefer immutable ADRs that are superseded rather than revised; in my projects, I’m happy to have Git carry that history.

If you do something similar, adapt the guidance to your own needs. The essential principle is that each governing ADR should describe the decision currently in force, with enough rationale to apply it. An agent doesn’t need the transcript of every argument. It needs the ruling that governs today and clear permission to stop when the ruling no longer fits.



Read the whole story
alvinashcraft
24 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Constraints that make developers faster

1 Share
Ryan chats with Julien Verlaguet, CEO at Skip Labs, about finding the balance between human tolerance and tooling constraints, the spectrum of typed programming languages, and building cost-effective tooling for AI agents.
Read the whole story
alvinashcraft
24 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Amazon writes scary blog warning communities not to block data centers

1 Share
Photo collage of a data center.

Amazon is calling for people to support AI data center projects, or risk irreparable harm to the US economy and national security. In a more than 3,000 word blog posted today, Amazon web services CEO Matt Garman pushed back on public concerns around the impact that data centers may have on jobs, power demands, and the environment, saying "our nation can't afford to lose" the race for AI dominance.

"With any change, there will be important questions raised, but there will also be misinformation and outright lies, and in the age of social media and 24/7 news, myths take hold faster than ever before," said Garman. "In fact, this build out is s …

Read the full story at The Verge.

Read the whole story
alvinashcraft
24 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

OpenAI Alerts More Than 100 Groups About Rogue AI Agent Activity

1 Share
An anonymous reader quotes a report from Reuters: OpenAI has informed more than 100 organizations about incidents involving unauthorized activity tied to its AI agents, according to a blog post by the ChatGPT maker, as AI labs face mounting scrutiny over rogue AI agent activity. Here are some other details: - The Sam Altman-led company has been conducting a broad review of the activities of its AI models after the accidental hacking of Hugging Face. - OpenAI is searching through roughly 50 petabytes of data as it works to understand the full scope of its rogue agent activity. - A string of high-profile breaches globally by rogue AI agents in recent months has sparked widespread worries within the AI industry over its ability to control the more powerful AI models now under development. - "In some cases, models used internet access in unintended ways or, in retrospect, did not have the ideal restrictions applied. Over the last several months, we have been applying new technical and operational measures to avoid similar problems, or catch them very early, and will continue this work," OpenAI said. - OpenAI previously said the review would take months to complete given the scale of the work. - The Hugging Face incident remains the most severe rogue agent activity OpenAI has identified from its AI models so far.

Read more of this story at Slashdot.

Read the whole story
alvinashcraft
25 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Python 3.15: Exploring the New Features

1 Share

Python 3.15 is (almost*) here! Christopher Trudeau and Bartosz Zaczyński return to discuss the new version. Bartosz coordinated the series of preview articles with members of the Real Python team and wrote the showcase tutorial, “Python 3.15: Cool New Features for You to Try.” Christopher’s video course “What’s New in Python 3.15” covers the topics from the article and shows the new features in action.

Christopher and Bartosz dug into the release to create code examples of the new features for the tutorial and course. We cover the new built-in types, unpacking in comprehensions, and developer experience enhancements. We also look into the performance improvements, including lazy imports, the upgraded JIT compiler, and a new sampling profiler.

We share our thoughts on the updates and offer advice about incorporating them into your projects. We also discuss when you should start running Python 3.15.

Course Spotlight: What’s New in Python 3.15

Explore the new features in Python 3.15, including lazy imports, frozendict, sentinel values, a sampling profiler, and a faster JIT.

Topics:

  • 00:00:00 – Introduction
  • 00:00:02 – * NOTE: Python 3.15 release delayed!
  • 00:03:35 – Real Python 3.15 Preview Articles and Video Course
  • 00:04:40 – Sentinel Values
  • 00:08:55 – Lazy Imports
  • 00:14:48 – Unpacking in Comprehensions
  • 00:17:12 – Mathematical functions
  • 00:20:07 – Sampling Profiler
  • 00:27:43 – Video Course Spotlight
  • 00:29:18 – frozendict
  • 00:33:12 – The speed round of features
  • 00:36:04 – Continued work on free-threaded Python and upgrading the JIT
  • 00:39:34 – Upgrading to 3.15
  • 00:44:35 – Thanks and goodbye

Show Links:

Additional Links:

Level up your Python skills with our expert-led courses:

Support the podcast & join our community of Pythonistas





Download audio: https://dts.podtrac.com/redirect.mp3/files.realpython.com/podcasts/RPP_E313_03_Python3_15.d4b0b6ec2049.mp3
Read the whole story
alvinashcraft
25 minutes ago
reply
Pennsylvania, USA
Share this story
Delete
Next Page of Stories