Like

Liked Marco Rogers (@polotek@social.polotek.net)
Post details
As soon as you decide to get more comfortable doing business with people, you realize there are a bunch of people you've met over your career that you definitely don't want to do business with. It's an odd feeling. In this case I ran into something that looked cool on LinkedIn. I was gonna find out more about it, then I saw who it was from. "Oh, that guy? Yeah, no. Fuck that guy."

 Listen

Listened to API Evangelist Conversation with Pat Patterson, Chief Technical Evangelist at Backblaze by The API Evangelist Conversations by Kin Lane 
Post details
This is the first actual edition of the API Evangelist Conversation podcast with my friend Pat Patterson, the Chief Technical Evangelist at Backblaze. Always enjoy learning from Pat as we dove into the meaning behind his title, as well as how Backblaze has standardized their API around the Amazon S3 storage API--essentially treating the API as the industry standard for storage.

 Repost

Reposted Alberto Cottica (@alberto_cottica@mastodon.green)
Post details
Dear fellow Europeans, I am respectfully asking you to consider signing this European Citizen Initiative to institute a billionaire tax. It was invented by leading French economist Thomas Piketty; I read the whole thing, and it is technically excellent. Hit me if you have questions, but please sign it, it is important. https://www.tax-the-rich.eu/ It needs 1 million signatures (currently 300K) and seven countries over their threshold (currently three: Denmark, France, Germany). #economics #tax

 Like

Liked Pelle Wessman (@voxpelli@mastodon.social)
Post details
Attached: 1 image Data informed decisions when bumping the engine range / peer dependency range of a npm module you maintain? With a new pretty-print and markdown option in my "list-dependents-cli" utility (that I created to drive the canary tests for #neostandard) that's now easy! With it one can now easily list the relevant data of modules dependent on ones module – in the terminal as well as copy it as markdown into an issue. Here's a real world example: https://github.com/eslint-community/eslint-utils/issues/233#issuecomment-2355754090

 Reply

Yup! I wrote about this in a bit more detail a few months back

 Repost

Reposted Ian Betteridge (@ianb@well.com)
Post details
Remember everyone: if your CEO insists that you can only work at the office, only work when you’re at the office. Leave when your contracted hours end. Do not work at home. Take whatever your contracted breaks are. Oh and join a union. https://www.aboutamazon.com/news/company-news/ceo-andy-jassy-latest-update-on-amazon-return-to-office-manager-team-ratio

 Listen

Listened to E135: Riding the Homebrew Wave by Open Source Startup Podcast
Post details
John Britton & Mike McQuaid are Co-Founders of Workbrew, the company that provides additional features and support for companies using Homebrew. Homebrew's main project, brew, is a wildly popular open source project with 40K GitHub stars and provides the missing package manager for macOS (or Linux). In this episode, we dig into John & Mike's history with Homebrew and their time together at GitHub, how Homebrew has kept projects simple over time and avoided feature creep, how Homebrew has managed to get a lot of value from contributors, how their ICP has shifted from mac admins to dev and security teams & more!

 Listen

Listened to "Kristen Bell" on Where Everybody Knows Your Name
Post details
<p>Ted Danson is thrilled to introduce Woody Harrelson to his dear friend Kristen Bell! Woody is curious about her anti-aging methods plus her fateful meet cute with hubby Dax Shepard. Kristen shares how she juggles a schedule filled with family, an acting career, and jiu-jitsu badassery. Bonus: Ted and Kristen trade tips on how to deal with difficult people, in a silent but deadly way. </p><p> </p><p>Like watching your podcasts? Visit <a href="http://youtube.com/teamcoco">http://youtube.com/teamcoco</a> to see full episodes.</p>

 Listen

Listened to "Will Arnett" on Where Everybody Knows Your Name
Post details
<p>Ted Danson and Woody Harrelson are reunited, and it feels so... nerve-wracking? For their first episode, the guys are joined by one of the funniest people they know, Will Arnett. Will gives them some podcasting tips from his gilded perch as co-host of the mega-hit podcast Smartless. They also get into Will's extreme Cheers fandom and his winding journey from getting kicked out of boarding school to starring in shows like Arrested Development and Murderville. Bonus: Woody's Gob Bluth impersonation.</p><p> </p><p>Like watching your podcasts? Visit <a href="http://youtube.com/teamcoco">http://youtube.com/teamcoco</a> to see full episodes.</p>

 Reply

Hand writing the spec, then validating (ie via http://gitlab.com/jamietanna/httptest-openapi) is a valid option - keeps it in sync very well from quite a few big Go apps I know using it

Or you could wrap your implementation in https://github.com/oapi-codegen/oapi-codegen/ from a hand rolled spec - we support net/http - and that then starts towards the process of being closer to the spec

Either way, you still need to validate the spec and implementation are in sync, and IMO, hand-writing the spec is the only "right" solution that makes sure you're intentionally making changes to the API, whereas generating spec from code could lead to just documenting what's in place and ie accidental breaking changes being missed