u/Tech_Invite09233

was looking through accelerometer data from CNC milling runs, comparing good and bad toolpaths.

The Z-axis looked like the obvious channel to monitor because it had the highest vibration energy. But in bad runs, its RMS only moved from about 1024 to 1081. That is roughly a 5% increase.

The Y-axis told a much clearer story. Healthy RMS was around 195, but bad runs jumped to about 305. That is a 56% spike on the axis you might ignore because the numbers look smaller.

Kurtosis was even more useful. In good runs, X and Y were around 6.5. In bad runs, they dropped closer to 3.5. So the failure was not just "more vibration". The vibration pattern changed.

Main takeaway: do not just watch the loudest axis.

For this run, Y-axis RMS and kurtosis were better signals than raw Z-axis energy. Also, thresholds need to move over time as the machine wears. Static models will age badly.

I tried automating data extraction from a batch of AS1100 agricultural hardware drawings for planting equipment and implement frames.

The goal was simple: pull dimensions, tolerances, and metadata into a downstream workflow.

I assumed AS1100 compliance would help. It did not help as much as expected.

A lot of drawings looked compliant at first glance, but were missing fields automation depends on. Scale was the first issue. Some drawings did not show it clearly, or placed it inconsistently in the title block. A human can work around that. A parser usually cannot.

General tolerances were another problem. If the tolerance block is blank, inconsistent, or formatted strangely, the system either guesses, drops precision, or passes bad assumptions downstream.

What stood out was that these issues seemed to cluster. Drawings with missing scale or poor tolerance data often came from the same drafting habits, not random one-off mistakes.

Main takeaway: AS1100 compliant does not always mean extraction-ready.

Before parsing, I would run a quick audit for:
scale
general tolerances
revision history
title block consistency

Otherwise the extracted data can look valid while quietly relying on missing or guessed context.

People often assume engineering drawing extraction means running OCR and cleaning up the text.

That works reasonably well for title blocks. Part numbers, revisions, and drawing numbers are usually in predictable places.

The harder part is the drawing area itself. Dimension callouts often sit on top of extension lines, center lines, hatching, and other geometry. A standard OCR tool can mistake those lines for noise or formatting and misread the actual callout.

There is also a separate issue: sometimes the information is missing from the drawing entirely. If the scale or general tolerance field is blank, OCR cannot fix that. It needs to be flagged as a drawing issue, not a reading issue.

So the pipeline needs more than text recognition. It needs to separate geometry from annotations and check whether the required fields are present.

Title block OCR may look good early on, but that does not mean the full extraction is reliable.

I used to assume drawing extraction would fail on the complicated stuff: views, dimensions, GD&T, projection symbols.

But in an AS1100 dataset I looked at, most of that came out fine.

The real problems were in the title block.

The repeated issues were basic:
missing scale
missing general tolerance

That sounds small, but it breaks the whole output. If the scale is missing, the dimensions lose context. If the general tolerance is missing, any untoleranced feature becomes ambiguous.

The annoying part is that the geometry can look perfectly extracted while the drawing is still not usable for manufacturing.

So now I think title blocks should be a gate, not an afterthought.

The story everyone still repeats is that cafes and restaurants are getting squeezed because ingredient costs never really came back down.

That was true in 2022. It is a lot harder to defend now.

I pulled BLS data for processed-food PPI vs. food-away-from-home CPI from Jan 2019 to Mar 2026. The 2022 shock was ugly. In July 2022, input-cost inflation was 13.81 percentage points higher than menu-price inflation. Operators were taking the hit.

But then it flipped.

By July 2023, the spread was -19.80 pp. Menu prices were still going up while processed-food input costs were falling.
And that gap has mostly stayed negative.

March 2026:

Food away from home CPI: +3.78% YoY
Processed-food PPI: -3.60% YoY
Spread: -7.38 pp

2026 YTD average: -10.15 pp
2022 average: +10.66 pp

So if you run a cafe and your food cost percentage still is not improving, “inflation” probably is not the whole answer anymore.

It might be waste.
It might be portion creep.
It might be buying outside supplier contracts.
It might be prep overproduction.
It might be the team quietly leaking margin before it reaches the P&L.

Small caveat: the spread narrowed in March, from -11.10 pp in February to -7.38 pp, so the tailwind may be getting weaker.

But the broad point still stands.

2022 was an external cost shock.
2026 looks more like an operations problem.

Lately it feels like originality isn't dead exactly, but trust in originality is getting weaker.

People publish books now and instead of readers talking about the ideas, the style, or the story, the comments often turn into "this is AI". I've seen it happen a lot this past year. Sometimes the work might be AI-generated, sure. But sometimes it feels like people assume first and read second.

So where does that leave actual writers?

You could sit down, write every word yourself, and still have people doubt it. That's the depressing part. If nobody trusts the process anymore, does originality still carry the same value?

At the same time, a lot of writers are using AI in some way. Maybe not to write the whole book, but for brainstorming, editing, fixing structure, tightening dialogue, or working through ideas. Even people in film and screenwriting are using it to polish scenes or develop concepts.

So now we're in this weird place:
People use AI.
People assume everyone uses AI.
And anything creative gets questioned by default.

It feels like writing has become a credibility problem as much as a creative one.

So I'm genuinely asking: is there still a real reason to write a book today, or has the value of writing been diluted too much?

People usually jump straight to the tools:

Louvain or Leiden?
PageRank or betweenness?

Which layout looks better?

But the real question is: what does this graph actually represent?

If the graph is badly defined, the metrics will still give clean numbers. They just won't mean much.

The first trap is node definition. Is a node a person, account, company, document, or event? If one person has multiple accounts, their role gets split. If several people share one account, it gets inflated.

Edges are just as messy. A follow, reply, mention, email, transaction, and shared event are not the same thing. Treating all of them as "relationships" can wreck the analysis.

Centrality also gets overused:

Degree = direct activity or visibility, not automatic influence.
Betweenness = brokerage, but very sensitive to missing edges.
Eigenvector = connection to important nodes, but often just rewards the dominant core.
PageRank = useful for directed attention networks, but only if links actually mean attention or endorsement.

Community detection is not magic either. Louvain, Leiden, and label propagation produce partitions based on assumptions. They do not automatically reveal "real groups."

Sampling bias can do even more damage. Snowball samples overrepresent connected nodes. Ego networks are bad for global rankings. Bad network boundaries can create fake bridges or fake communities.

Visualization can also fool people. A pretty force-directed graph is not proof of structure. Sometimes it is just a colorful hairball.

That distinction is the whole point.

SNA is useful, but only when the graph is defensible, the metric matches the question, and the result survives basic sensitivity checks. Most findings should be read as:
given this data, boundary, time window, and method, this is the structure we observe.