Skip to content

Add ROSCon 2025 Summary blog post#59

Merged
mikelikesrobots merged 2 commits into
mainfrom
roscon-2025-blog-post
Apr 14, 2026
Merged

Add ROSCon 2025 Summary blog post#59
mikelikesrobots merged 2 commits into
mainfrom
roscon-2025-blog-post

Conversation

@mikelikesrobots
Copy link
Copy Markdown

No description provided.

@mikelikesrobots mikelikesrobots self-assigned this Feb 26, 2026

We made some observations based on the talks and how they fit with our ongoing.

1. **Make versus Buy decision**: Broadly, tools seem to break down into:
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This heading somehow doesn't make sense for me here. The two bullet points that follow don't seem to be related to make-vs-buy.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-reading, I can see what I intended, but you're right that it doesn't follow on logically. I've added some extra detail to try to make my intention more clear. What do you think?

Comment thread blog/2026-02-25-roscon-logging-observability-findings/index.md Outdated

2. **Technical vs Non-Technical Audience**: Most tools seem to be aimed at engineers who are actively developing their robots. However, as robots become more mature and scale up, non-technical users need to be able to monitor and perform basic debugging for robots. We are starting to see some tools offer high-level interfaces for non-technical users, such as the robot web server presented by Hilary Luo.

## What This Means for the Guide
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After reading this section I didn't actually get the sense that these conclusions are actually supported/implied by the preceding sections. It's also a bit weird, because conclusions shouldn't (can't logically) be more detailed and longer than the thing they conclude from.

I would hold these back because to they do not relate to "Logging and Observability at ROSCon 2025".

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this was presented as a conclusion, but it's not really intended to be one. I don't think the blog post is long enough to need a conclusion.

The flow was meant to be:

  • here are the talks we looked at
  • here are the take-aways from the talks mixed with our own experience as robotics developers (more of an interpretation with extra context)
  • here is how it will feed back into our work making the community guide

I've tried to make that a little more obvious, but not sure I've managed it. What are your thoughts here? Just trash the section, or try to massage it into the flow I wrote above?

@mikelikesrobots
Copy link
Copy Markdown
Author

@chfritz appreciate your comments on the blog post draft! Could you look at the updated changes, please? I've responded to your comments as well.

@mikelikesrobots mikelikesrobots merged commit 0e96560 into main Apr 14, 2026
1 check passed
@mikelikesrobots mikelikesrobots deleted the roscon-2025-blog-post branch April 14, 2026 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants