Quite chuffed someone else mentioned Djokovic, who is close to 39 and just played an Australian Open final. (Yes he got lucky with 2 freebies but he _did_ beat Sinner in the semifinal fair and square, and managed to win the first set before running out of juice)
He probably means when I took VC funding in 2019 and started to rip apart the framework to try build a platform and business. The 2-3 years after were very chaotic.
My goal was never to serve the community but instead leverage it to build a business. Ultimately that failed. The truth is it's very difficult to sustain open source. Go-micro was never the end goal. It was always a stepping stone to a platform e.g microservices PaaS. A lot of hard lessons learned along the way.
Now with Copilot and AI I'm able to go back and fix a lot of issues but nothing will fix trust with a community or the passage of time. People move on. It served a certain purpose at certain time.
Note: The company behind connect-rpc raised $100m but for more of a build system around protobuf as opposed to the rpc framework but this was my thinking as well. The ability to raise $10-20m would create the space to build the platform off the back of the success of the framework.
Obligatory "this is why I love HN" but even for that standard, this is is an incredibly open account, thank you for the insight and sorry it hasn't seemed to pan out quite how you hoped. Still sounds like you got your bag, built something cool, and have your "micro" share of Internet legacy, so not too bad eh?
I've interviewed 3k people with Karat as a professional interviewer, and several hundred more as a hiring manager. The very few times I received direct emails from candidates attempting to circumvent the normal process were met with unequivocally negative reactions. First, I find the Internet sleuthing they'd undergo to find my email address a bit creepy – for example, Karat would only show the first name and profile pic for your interviewer. But more importantly, the sheer audacity to go for such a stunt would firmly anchor them in the box of people I'd never want to work with. I'd still be polite and professional to a fault, of course, but I'd never seriously consider them past that point.
But in bad times where "the normal process" can't even let you have a human look at your resume, it's different. "circumventing" is at worst a simple act of rebellion to annoy people who can change their process. It's a best a chance to actually get the response that isn't even granted with a form rejection these days.
I've been calling this context.md in my projects (alongside a progress.md for TODOs and breaking down complex tasks). I don't care what we call it as long as we settle on a convention.
I use it mostly as smarter autocomplete and it's still absolutely worth it. I really tried having it write unit tests in Go, write simple Astro websites, etc, but I'm never satisfied with how dumb it is when "vibe coding", so I use it as Intellisense on steroids for now, but I don't doubt it will become even better soon. The chat feature is fantastic and between it and the contextual help I barely ever have to reach for actual (code) documentation.
Having used Go professionally for over a decade, I can count on one hand the times I used recover(). I've actually just refactored some legacy code last week to remove a panic/recover that was bafflingly used to handle nil values. The only valid use case I can think of is gracefully shutting down a server, but that's usually addressed by some library.
I used to do thousands of interviews across the industry and I vividly remember Apple backend devs being almost always unmitigated disasters. They would always pick Java and could barely use it - to the point where a for loop would be challenging. Their Swift guys were fairly decent though IIRC.
reply