Can you imagine web serving where the configuration isn't a thousand-line labyrinth of nested blocks and cryptic brackets, but a clean, flat stream of logic? I can.
>>> https://qwaderton.org/d2o/
#Webserver #DevOps #SysAdmin #WebDev #Suckless #DeveloperExperience #Backend #OpenSource #GoLang #Linux
Automate JSON Localization. From raw JSON to publish-ready multilingual copy.
Designed for teams shipping frequent product and API copy updates across regions.
Search demand signal this week: "json translator".
See it in action: www.json-translate.com
#ProductMarketing #DeveloperExperience #Startup
Oh I do love how you have your Kitten¹ app’s database in memory – thanks to Kitten’s built-in JavaScript Database (JSDB)² – and accessible via the Kitten Shell (REPL)³ during dev.
(If I do say so myself.) ;)
💕
¹ https://kitten.small-web.org
² https://kitten.small-web.org/tutorials/persistence/
³ https://kitten.small-web.org/tutorials/kitten-s-interactive-shell-repl/
Syntax Integrity by Design. Scale translations without spreadsheet chaos.
Designed for teams shipping frequent product and API copy updates across regions.
Search demand signal this week: "json translator".
See it in action: www.json-translate.com
#ProductMarketing #DeveloperExperience #Startup
AI is Changing the Relationship Between Developers and Open Source
AI is making open source more valuable than ever, but it’s also changing how developers interact with the communities that maintain it. Two recent LeadDev articles prompted me to think about a growing tension: AI is increasing demand for open source while also increasing the burden on the maintainers who sustain it.https://jeffpaul.com/2026/02/ai-is-changing-the-relationship-between-developers-and-open-source/
via @dotnet : Modernize .NET Anywhere with GitHub Copilot
https://ift.tt/5x4R9PK
#dotnet #NET #GitHubCopilot #Copilot #modernize-dotnet #modernize # modernization #VSCode #VisualStudio #GitHubCLI #CLI #codingagents #customskills #developerexperience #softwaredev…
"Consumers want to be able to try an API operation and access concrete example information, or configuration data, such as credentials. Markdown alone isn’t going to provide these elements for you. Fortunately, there’s something else that will, as we’ll see next.
The solution you need is called MDX. It’s a superset of Markdown that lets you embed components within your content. Or just render dynamic information obtained from executing JavaScript. You get to keep the simplicity and versatility of Markdown. But now, you can also use dynamic elements and data. This completely changes the game for API documentation. You can, for instance, embed a component to show the consumer’s API key, or one to make an API request and show its response. This hands-on interactivity helps users test the API faster. And, because of that, it significantly reduces the Time to First Call, or TTFC. Since a low TTFC means the API onboarding experience is excellent, it translates directly into a higher perception of quality. Which is exactly what you’re looking for.
Moving from pure Markdown to MDX doesn’t have to be complicated. However, and especially if you have little coding experience, putting an MDX system together from scratch can be challenging. Luckily, there are many systems that already support MDX. Docusaurus, for instance, supports it by default. Astro is another example of a content system where you can use MDX. There are more options, including commercial ones. What I’d recommend, though, is to check out the official documentation and have a go at the MDX playground."
https://apichangelog.substack.com/p/making-api-documentation-dynamic
#API #APIDocumentation #TechnicalWriting #Markdown #MDX #APIDesign #DX #DeveloperExperience
🎉 Microcks Community Meeting.
Join us for the Microcks Community Meeting, a friendly space to connect, share, and co-create what’s coming next.
🗓 Thursday, Mar 12, 2026
⏰ 9–10 a.m. CET / 1–2 p.m. Bengaluru
🔗 Join us live:
https://buff.ly/ndAN9tN
🤝 Whether you’re a long-time contributor, a curious user, or just discovering Microcks, this is your chance to meet the community, share your ideas, and help shape the project.
#OpenSource #APIs #DeveloperExperience #Community #Collaboration
Our company is moving toward being AI-first, with a strong no-code mindset and more code expected to be generated by AI. After a 2-day workshop, I have to admit the progress was impressive: we finished sprint tasks in just 2 days, and the delivery speed felt multiplied.
So I’m genuinely split.
On one hand, the benefits are obvious: faster prototyping, less repetitive work, quicker iteration, and much more output in less time. On the other hand, I keep asking myself: where does this lead us? What happens to software engineering as a craft if writing code becomes less central? Do our jobs evolve, or do parts of them disappear?
Maybe the future is not fewer engineers, but engineers working differently: more architecture, more critical thinking, more review, and more responsibility for what AI produces.
Curious how others are thinking about this shift.
#AI #NoCode #SoftwareEngineering #FutureOfWork #DeveloperExperience #TechLeadership
Atarwn Gard
JSON Translate
Aral Balkan
jeffpaul
Brandon H 
Miguel Afonso Caetano
Microcks
JohnnyD
Matthias Andrasch