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

Todoist launches new import tool to help Microsoft To Do users

1 Share
Following the announcement of the upcoming retirement of Microsoft To Do, users with personal accounts have been trying to find alternative tools to manage their to do lists. With little help available from Microsoft, Todoist has stepped in, announcing the launch of a new importer designed specifically to help people migrate from Microsoft To Do to Todoist. Fast facts: Home users of Microsoft To have been left feeling somewhat abandoned by the company’s decision to close the app in the middle of next year. While Microsoft has provided a relatively simple way for school and work users to move from… [Continue Reading]
Read the whole story
alvinashcraft
5 hours ago
reply
Pennsylvania, USA
Share this story
Delete

Anthropic Mathematician Claims to Prove Riemann Hypothesis

1 Share
Slashdot has been covering the Riemann Hypothesis for years. 2000: Prove The Riemann Hypothesis And Make.Money.Fast 2002: More on Riemann Hypothesis 2008: Claimed Proof of Riemann Hypothesis 2008: Prominent Mathematicians Rebuke Recent Riemann Hypothesis Proof Add a new headline to the list... 2026: Using AI, mathematician claims to have solved one of math's great mysteries joshuark shares a report from Scientific American: Levent Alpoge, a mathematician at Anthropic, has claimed to have solved the Riemann Hypothesis with the help of Anthropic's AI model Claude, but the proof is not yet independently verified and remains under scrutiny. [An AI-generated solution of the 167-year-old problem, long considered far out of reach to human mathematicians, would cap off the technology's year-long conquest of math in spectacular fashion.] The Riemann hypothesis was first proposed in 1859 by the mathematician Bernhard Riemann. It claims that the locations of the prime numbers along the number line, which appear random at first blush, are actually determined by an intricate, meaningful order. [...] Alpoge posted his Claude proof coded in the programming language Lean, which verifies the mathematical correctness of each argument. Issues can arise in Lean, but it shouldn't take long for experts to verify whether the hypothesis is properly coded, and if the proof is correct. If that happens, it will cap off a year in which AI's mathematical capabilities ascended from unreliable college student to a superhuman force, leaving no part of the discipline undisrupted. [...] Alpoge's statement is elegiac -- recognizing the sense of grief many mathematicians are feeling -- but also optimistic. "It is natural to feel that this is an end, in my case a loss of a principal guiding light," he wrote, "but what I saw during the course of progress so amazed me that I believe it is one dawn across science of something far greater." [...] The Riemann result, if correct, will echo far beyond mathematics. It doesn't have any immediate real-world applications -- it won't upend global banking or make the internet run faster. But after a year of watching LLMs surpass one math benchmark after another, there is no more staggering achievement it could possibly reach. A machine may have just solved a problem that the smartest people on the planet all agreed they were nowhere close to figuring out. As MIT mathematician Andrew Sutherland once put it to me: "An AI that can prove the Riemann hypothesis is not one I'd want to meet. If that happens, mathematicians having jobs will be the least of our problems." "If the proof is correct and understood, this completes a dictionary between different branches of math where the connections were only partial," says Hector Pasten, a mathematician at the Pontifical Catholic University of Chile. "Something like a Rosetta Stone." "If true, even from a first high level scan of the summary of the proposed argument, it is very plausible to me that the new ideas in the proof will open up brand new avenues of thinking in number theory and have an immense impact beside the obviously extremely influential result in itself," added mathematician Carlo Pagano, a professor at Concordia University and a visiting researcher at Google DeepMind. In a separate article from Scientific American, independent mathematicians say the AI-assisted proof is almost certainly valid. MIT mathematician Andrew Sutherland said the chance of anything being wrong was "approximately zero" after independently compiling and checking the code. However, researchers are still conducting final checks to ensure the proof accurately represents the original hypothesis and does not exploit any loopholes in Lean's verification system. But did a human beat the AI? The Washington Post reports: Just hours after AlpÃgeâ(TM)s claim circulated on social media, Ravi Vakil, president of the American Mathematical Society and a professor at Stanford University, said in a hurried statement that mathematician Alessandro Masullo had a proposed proof of the Riemann hypothesis without AI several months earlier. The draft, which runs some 940 pages, is in need of significant revisions, Masullo said in a statement, and was not ready for publication. Online observers quickly noted that it contained omissions and apparent errors. But in the introduction to the draft, he published a striking flag. âoeIf any message at all this work is meant to send to the mathematician who feels discouraged by the pace and tone of the current climate, it is this,â he wrote. âoeWe are still here. We are very much alive. We are not going anywhere.â

Read more of this story at Slashdot.

Read the whole story
alvinashcraft
5 hours ago
reply
Pennsylvania, USA
Share this story
Delete

BONUS How Network Design Makes Teams Smarter With Damon Centola

1 Share

BONUS: How Network Design Makes Teams Smarter With Damon Centola

What if the way your team is connected matters as much as the people on it? Damon Centola, author of Goodthink, joins Vasco Duarte to explain why networks do more than move information: they shape trust, legitimacy, coordination, and creativity. This conversation gives software leaders a practical way to think about AI adoption, Slack, and the conditions for better collective thinking.

Networks Are Prisms, Not Pipes

"The networks aren't actually pipes, they're prisms."

 

When leaders announce a new tool or practice, the message does not land in a vacuum. People interpret it through colleagues they trust, through the risks they see in changing their work, and through the signals that tell them whether the change is legitimate. Centola explains why a campaign that simply broadcasts information can fail: behavior change needs social reinforcement, not just a clearer message.

Build Legitimacy Before Asking for Adoption

"It's not just about teaching people facts, it's about getting them to believe and want to believe."

 

For software leaders introducing AI or another new way of working, the useful question is not only how to communicate the change. It is whether people can see peers like them trying it, adapting it to their work, and making it safe to join. Broad bridges between groups help a practice cross from one team into another because people can build trust and confidence together rather than being sold an idea by a broker.

Match the Network to the Problem

"The kinds of structural solutions that facilitate and answer the coordination challenge would actually undermine the creativity challenge."

 

Fast, highly connected channels can be exactly right when a team needs to coordinate under pressure. They can be harmful when a team needs to explore, because everyone quickly converges on the first promising answer. Centola suggests treating organization design as something fluid: amplify fast coordination when the work calls for it, then create more space and separation when the next challenge is discovery.

Slow Down Information to Find Better Ideas

"By slowing down the learning process in terms of peer learning, you accelerate the local discovery process."

 

Centola's experiment with data scientists compared fully connected teams with groups organized more like hallways. In the fully connected teams, everyone saw the current best answer and rushed toward it. The hallway networks allowed different approaches to develop for longer; every one of those networks outperformed the fully connected networks across eight competitions. The lesson is not to abandon collaboration, but to protect enough diversity for people to explore beyond the obvious local peak.

Design Places for Useful Collisions

"We really are these geographic beings. We live in the spaces that are immediately around us."

 

MIT's Building 20 became an unlikely source of creativity because people from unrelated disciplines kept running into one another without being pulled constantly back into their home departments. The same principle applies to digital workplaces. Leaders can ask which connections help people coordinate, which ones create conformity, and where a smaller set of unexpected conversations might give an idea time to grow.

Turn Network Research into Better Decisions

"All the studies I've ever done are up there, but also all the data, all the scripts, so you can kind of dig in."

 

At the Network Dynamics Group, Centola and his colleagues connect fundamental network research with practical work in organizations, hospitals, and civic life. Their work includes network-based clinical consultation designed to reduce bias and medical errors. For listeners who want to go deeper, the group shares papers, data, and scripts alongside the research.

 

[The Scrum Master Toolbox Podcast Community CTA]

About Damon Centola

Damon Centola is the Elihu Katz Professor of Communication, Sociology, and Engineering at the University of Pennsylvania, director of the Network Dynamics Group, and author of Goodthink. His research studies social networks, behavior change, and collective intelligence, including how structure shapes decisions. LinkedIn: [missing]. Check out Damon's work at the Networks dynamics group of the University of Pennsylvania.

 

You can connect with Damon through the Network Dynamics Group. No LinkedIn profile or Twitter/X account was provided in the interview material.





Download audio: https://traffic.libsyn.com/secure/scrummastertoolbox/20261121_Damon_Centola_BONUS.mp3?dest-id=246429
Read the whole story
alvinashcraft
5 hours ago
reply
Pennsylvania, USA
Share this story
Delete

Finding a leak rooted by an event handler or a timer with an AI agent

1 Share
The previous post found a leak whose root was a static cache, which is the case everybody recognises. This one has no cache, no static collection, and nothing that looks like storage. It leaks because objects subscribe to an event and because they schedule a timer. Same three commands, but the gcroot chain looks completely different, and the output is large enough that reading it becomes a problem of its…
Read the whole story
alvinashcraft
5 hours ago
reply
Pennsylvania, USA
Share this story
Delete

I Built a Tool That Saves Me 6 Hours Editing Time on Every Course I Make

1 Share

I use Camtasia to record my courses when I partner with Pluralsight or LinkedIn Learning.

Every recording ends up with long pauses while I think, lip smacks and mouth clicks the microphone picks up, or a mouse click or keyboard clatter right in the middle of a quiet gap.

Cleaning that up by hand is dull.

Scrub the timeline, zoom in, ripple delete, repeat. Multiply by a 60 minute course and it becomes a big part of the job.

A typical 60 minute course takes me 30 to 40 hours to create from start to finish.  This initial clean-up pass alone used to eat about 6 of those hours.  I decided to build a small Windows app to do this initial cleanup phase for me.

You point it at a Camtasia project, it finds the noise, you review what it found, and it writes a new project with the edits already applied.

~

What It’s Used For

Camtasia Cleanup takes a .tscproj file and removes the stuff you’d otherwise cut out by hand:

  • Long pauses
  • Mouth clicks and lip smacks
  • Swallows and quiet mouth noise
  • Mouse clicks and keyboard typing that sit on their own in a quiet gap
  • Dead air at the very start and end of the recording

Full transparency – it’s not a magic “make me sound professional” button. It’s a time saver for the dull first pass, and you stay in charge of what gets removed.

One rule I stuck to from day one: it never touches your original project or raw recording. Everything is written next to the input with a -cleaned suffix, so the worst case is you delete the new files and carry on as before.

~

How It Works

There’s no AI model or cloud service involved. It’s classic audio analysis, which means it’s fast, it’s repeatable and nothing leaves your machine.

  1. Read the project. The .tscproj file is JSON. The app reads the clips, the recording each one points at, and anything layered on top (b-roll, callouts).
  2. Analyse the audio. It decodes the recording with ffmpeg and measures the loudness in tiny slices. From that it works out where speech is, where the silences are, and where short sharp sounds live. A mouth click, a swallow and a keystroke all have different shapes, so each gets its own set of rules.
  3. Plan the edits. Pauses over your threshold get shortened, but the app keeps a little breathing room either side of your words. If something on screen is changing during a pause, it can leave that pause alone.
  4. Write a new project. The cuts are applied to the video, the cleaned audio is written as a WAV, and anything layered on the timeline is cut in step with the narration so it doesn’t drift out of sync.

The slow bit, the analysis, runs once and is cached. After that, moving a slider or unticking an edit re-plans instantly.

~

Features

The main features:

  • Adjustable pause removal. Choose how long a pause has to be before it gets shortened (0.8 seconds by default), and how much to keep before and after speech (0.2 seconds each).
  • Protect screen changes. If the screen is changing while you’re quiet, such as a page loading or a demo running, the pause is kept.
  • Mouth clicks and lip smacks. The quiet ones. Silenced with tiny fades so you don’t hear the edit.
  • Mouse clicks and keyboard taps. The louder ones. A separate, optional checkbox because they’re a judgement call, and it only touches a sound that is sharp, short and alone. A click stuck to a word is left alone.
  • Swallows and quiet mouth noise. With a sensitivity slider, since what counts as “noise” depends on your microphone and your room.
  • Word endings are protected. A quiet “s” or “ch” on the end of a word (the “ix” of “six”, the “ch” of “speech”) looks a lot like a lip smack, and early versions clipped them. The app now treats a hissy sound that belongs to a word as part of that word.
  • Played audio and a microphone, kept apart. If you play a file while recording, Camtasia stores your microphone and the desktop’s sound as separate streams. The app keeps them as two audio tracks, cut in step, so you can still balance them.
  • The microphone’s echo of a played file is silenced. When a file plays through your speakers, your microphone picks it up too, so you hear it twice, a fraction of a second apart. Where the microphone holds only that quieter copy, the app silences it. Speaking over the file is left alone, and every stretch is a row you can untick.
  • Review everything. Every edit is listed as a row with its time, length and reason. Untick anything you disagree with. Click a row to hear it from a second before to a second after.
  • Original / Cleaned toggle. Flip between the two while the playhead stays in the same spot.
  • Multi-clip projects. Projects with several clips on the timeline are handled, with b-roll and callouts following the cuts.
  • Flags, not guesses. Anything it’s unsure about is flagged as a CHECK and kept by default. You decide.
  • Cut list and preview. Optionally export a CSV of every edit and a quick preview MP4.
  • Inhales are listed, never removed for you. Early versions chopped a breath up or removed it by accident, depending on how loud it was. Now the app finds a steady, quiet breath just before a word and lists it as a “possible inhale” CHECK row. It stays in unless you tick it.
  • Silence long gaps (optional, off by default). After the cuts, some pauses are still long, typically the ones kept because something is moving on screen. Tick one box and the app silences the narration in those gaps, as long as they are really quiet. Typing, clicks or a quiet remark leave a gap alone.

Now, how to use it.

~

How To Use It

1. Open a project. Click Open project… or drag a .tscproj file anywhere onto the window. If the recording has moved, the app offers to let you locate it.

2. Analyse. Hit the green button. It runs once and is cached for next time. Here’s a short 2 minute clip from one of my courses once the analysis has finished:

Camtasia Cleanup after analysing a two minute clip, with settings on the left, the waveform in the middle and the list of edits on the right

The waveform shows what it found. Red marks a cut pause, orange is a click that will be removed, blue is a place it kept because the screen was changing. The list on the right has every edit, and the bar at the bottom tells you what you get: 2:03 down to 2:01 here, 4 pauses shortened, 28 clicks removed.

3. Tune it. Move the sliders or untick rows. Everything re-plans instantly from the cache, so you can experiment freely.  I find I don’t need to use that so much.

4. Check the result. Switch to Cleaned to see and hear the result. The playhead stays on the same moment, so you can jump straight to something that sounded odd.

The same clip in the Cleaned view, the waveform now shorter and shown in green

5. Export. Click Export. Next to your original you’ll get:

  • yourproject-cleaned.tscproj, which you open in Camtasia as normal
  • yourproject-cleaned-audio.wav, the cleaned narration (one per clip for multi-clip projects; a clip that also has a played file gets -narration and -system files on two tracks)
  • optionally a cut list CSV and a preview MP4

Open the -cleaned project in Camtasia and carry on editing.

~

Teaching It From My Own Edits

After the first version I still did a manual pass in Camtasia on every clip. So I gave Claude Code two project files: the raw recording and the cleaned version I had edited by hand. The question was simple: what do I keep fixing that the app misses?

The answer was in the gaps between words.

On a slide-deck clip I had muted every gap of 0.7 seconds or longer that the app left in: 26 out of 26. Almost all of them were the pauses it keeps because the screen is changing. That became the optional “silence long gaps” rule. It also showed that four of the five inhales the app flagged were ones I had muted by hand, which gave me some confidence in that rule.

I held back on turning it on by default, because of something my own recordings made obvious. A slide-deck pause is usually deliberate. An IDE recording has long gaps while I type, copy and paste, so silencing them blindly is a different decision. So it is off by default, it skips any gap that is not really quiet, every gap is a row I can untick, and I checked what it would do on an IDE clip before trusting it.

~

How Much Time It Saves

There are two savings here, and they’re easy to mix up.

1. Less recording to deal with. The app cuts the dead air out for you. On one of my course modules it took the recording from about 10 minutes to under 8, before I’d touched a razor blade. That’s more than two minutes of pauses and noise I never had to find, zoom into and delete. Even the short 2 minute clip in the screenshot above came down from 2:03 to 2:01, with 4 pauses shortened and 28 clicks removed. Each of those is a cut I’d otherwise have made by hand.

2. Less of my time. A typical 60 minute course takes me 30 to 40 hours from start to finish: planning, scripting, recording, editing, reviewing. The app saves me about 6 hours of that editing. That’s roughly 15 to 20 percent of the whole job, from one tool that handles the dullest part of it.

The workflow is: open the project, analyse (once, then it’s cached), skim the list of edits, untick anything I disagree with, export.

Six hours is nearly a full working day back on every course, time best used on other tasks.

The main time saving is in the dull first pass and I still listen to every cleaned clip. So that is still a thing. It’s a great first pass but it’s not the finished edit. The 6 hours is my own estimate across my courses, not a stopwatch measurement.

~

Things to Know

A few caveats:

  • I built and tuned this against my own voice, microphone and room. The thresholds for clicks, taps and swallows are sensible defaults -not universal recording laws. Your recordings may need the sliders nudged.
  • I’ve tested the cleaned projects in Camtasia 2019. Other versions may behave differently.
  • Word endings are the hardest thing to get right. A final “s” or “ch” can sound like a lip smack, and I only found the cases above by listening to real clips. If you hear a word clipped, find its row in the list and untick it.
  • The inhale and long-gap rules were tuned on one recording each. A few inhale rows will turn out to be swallows or room noise, which is why they are CHECK rows and not automatic.
  • “Silence long gaps” came from slide recordings. Try it on a coding recording and read the rows before you trust it.
  • It’s a first pass. I still listen to the result. That part of the job hasn’t gone anywhere.

~

Where It’s At

It does what I need it to do.

Open your project, analyse, review, export, carry on editing in Camtasia and go!

If you record in Camtasia and you’re tired of the same clean-up routine, it might save you some time too.

~

Enjoy what you’ve read, have questions about this content, or would like to see another topic covered?

You can schedule a call using my Calendly link to discuss consulting and development services.

~

Courses

Check my AI courses. From developers to decision makers, these have you covered:

~

JOIN MY EXCLUSIVE EMAIL LIST
Get the latest content and code from the blog posts!
I respect your privacy. No spam. Ever.
Read the whole story
alvinashcraft
5 hours ago
reply
Pennsylvania, USA
Share this story
Delete

F# Weekly #47, 2026 – Aspire 17 & NuGet staging publishing

1 Share

Welcome to F# Weekly,

A roundup of F# content from this past week:

Microsoft News

Videos

Only 7 more volunteers needed to complete the F# Advent Calendar 2026! 🎄Who wants a December slot? 🙋‍♂️🙋‍♀️#fsharp #FsAdvent

— Sergey Tihon 🦔🦀 (@sergeytihon.com) 2026-11-17T20:03:04.769Z

Blogs

Highlighted projects

New Releases

That’s all for now. Have a great week.

Buy Me A Coffee





Read the whole story
alvinashcraft
5 hours ago
reply
Pennsylvania, USA
Share this story
Delete
Next Page of Stories