Brian P. Hogan
@bphogan
Followers
9K
Following
2K
Media
554
Statuses
54K
Technical content expert, developer education leader, author, educator, mentor, and software developer. I develop people, content, and code. He/Him.
Wisconsin
Joined December 2007
The person on the stage or the person who wrote that book isn’t better than you. They just took a shot. Don’t be afraid to take yours and share your knowledge. And don’t listen to anyone who tells you you’re not good enough. Especially the voice in your head. It’s a jerk.
14
230
944
The Minnesota Wild plays at the Grand Casino Arena and airs games on FanDuel Sports Network, and we are supposed to be surprised there’s a current sports betting scandal in another sport?
0
0
0
HOW DARE YOU, MR. HOCKEY PLAYER! HOW DARE YOU USE YOUR HOCKEY STICK TO PUT A PUCK IN THE NET! NO GOAL FOR YOU!
1
0
0
The DigitalOcean documentation team was fantastic, but they were laid off—just in time for the big LLM content scraping runs that would have catapulted their work into the AI zeitgeist.
8
4
102
The joy I get out of programming has slowly waned over the years, because most interesting problems are now "solved" via standard libraries, open-source dependencies, and HTTP APIs. Novel problem solving gradually gave way to "digital pipefitting" of stuff built by others.
5
3
26
watched a guy use claude code to copy a folder from one location to another because he didn't know the command
319
47
3K
About 10 years ago, I got pushed out for the first time from a company. I guess some people say fired. I like the sound of pushed out better. I was heartbroken. I had given my all to this company. I had made them millions and millions of dollars. And they had told me I wasn't
98
73
840
This isn't a Ruby vs. Go problem. It's an "we hired 50 engineers so let's split everything apart" problem. Here's what happens: Company grows fast. Leadership comes from Big Tech. They bring their playbook. Split the app into pieces. One piece per team. Everybody owns
At a past company, the head of engineering and the principal engineers decided to break our Ruby on Rails application into a Go microservices mesh. They created very detailed design documents and architecture diagrams. They went all out and used Kubernetes, gRPC, service
43
126
1K
Yesterday I published Issue 45 of my monthly newsletter, and it's about why Markdown might not be the best way to implement content. Read it and subscribe to be the first to read next month's issue. https://t.co/iC8ABtnqgT
newsletter.bphogan.com
Explore why Markdown, despite its ubiquity, might not be the best fit for technical content.
3
4
8
Everyone wants corporate sponsorship of OSS until they find out that sponsorship means control. Do what we want or the money you depend on goes poof. No free lunch. Disappointing. https://t.co/0TKHJeCpnl
joel.drapper.me
Ruby Central recently took over a collection of open source projects from their maintainers without their consent.
1
0
1
"Let's all band together to get consumer protections rolled back, and we'll say it will increase competition" is a hell of a sales pitch. https://t.co/3lCkGl5T52
travelandtourworld.com
American Airlines, Delta, Southwest, United, and other US airlines are pushing to remove key protections for passengers and add more fees by rolling back rules, claiming it will lower costs and boost...
0
0
0
How to make your Dev tool more consumable by @AnthropicAI Claude Code? @mintlify founder Han: "Just write better docs for humans."
1
4
5
Vale is my go-to tool to catch style errors and enforce consistency in content, and after implementing it in multiple jobs and projects, it was time to create a guide anyone can follow. Now in beta. https://t.co/SR56nw73Jh
pragprog.com
Lint your docs like code: turn any style guide into enforceable rules with Vale and publish clear, consistent content every time.
0
2
12
Been thinking about this… The thing that drew me to Ruby on Rails was that they created abstractions to eliminate manual boilerplate. That kind of effort isn’t necessary now that we can make LLMs generate boilerplate for us. It probably won’t even be encouraged.
I totally respect all you people out there avoiding AI because "you enjoy the journey" or whatever, but like... do you actually enjoy the journey of writing GitHub actions slash being a YAML engineer? I really, really don't. GHA with AI is bliss.
0
0
0