James Sinkala
997 posts

James Sinkala
@xinnks
Full Stack Developer | Technical Writer. Breaking apps & writing content.

We unfortunately had to let @Michael_Ludden go. He is simply put, the best developer marketer I have worked with in my entire career. If you run a developer-centric company, I am sure you understand how hard it is to find a marketing professional that understands the developer mind. Michael always makes it look easy.


Last but not least, @joaomarcosgris was one of the stars of our backend. He knows Go very well, and was the one-man-show behind all of our data analysis pipelines, our integrations with all of our 3rd party providers, and did a lot of work on the epic Turso CLI, Backend, and even our frontend. Not only Gris made it all happen, he was also always ready and willing to fix anything.

We also had to part ways with @giovannibenussi. He is is a great frontend developer. He knows React and the JS/TS ecosystem like few others, and combines that with a dependable attitude. A Turso user before we even hired him - he was always on our Discord server, always willing to help, and always willing to jump on issues unprompted and keep users happy.








A first look at the weekend project @sarna_dev and I have been working on: writing a book all about writing engineering blog posts! It’s now in early access at mng.bz/Y7oK - use the code mldunlop for 50% off until June 1. The heart of the book is the discussion of “blog post patterns”: The Bug Hunt, We Rewrote It in X, How We Built It, etc. 7 patterns in total, one chapter for each. We also share practical strategies for making your writing clearer and more convincing, ways to reach more readers, and even what to consider if you’re tempted to enter the wild world of book writing. Also -- examples, examples, everywhere. We discuss 5 real blog posts in every pattern chapter, plus we created a fake @ziglang blog post to demonstrate all the writing and revision strategies (including some good fun with AI). Many thanks to the entire @manningbooks team, especially @JonathanGennick for making it happen as well as @ericlippert and Doug Rudder for making it a much better book!














