Adam Warski (@adamwarski) 's Twitter Profile
Adam Warski

@adamwarski

Sharing elegant solutions to everyday problems | R&D @ SoftwareMill | #Scala / functional programmer #FP | Blogger | #OSS developer

ID: 11352392

linkhttps://warski.org calendar_today19-12-2007 22:27:37

5,5K Tweet

7,7K Followers

183 Following

Adam Warski (@adamwarski) 's Twitter Profile Photo

Since commit messages are now computed from the source code (via LLMs), I'm catching myself not paying much attention to them. Which reinforces a good practice: source code should capture all relevant information. If necessary, in a comment. Commit msgs should be just summaries.

Adam Warski (@adamwarski) 's Twitter Profile Photo

Is there some standard / adopted (as in: used by Cursor / Anthropic / coding agents) way to provide documentation for libraries? My use-case: I've got a library which works best when using certain approach to concurrency, error handling etc. So an MCP which has access to

Adam Warski (@adamwarski) 's Twitter Profile Photo

More MCP examples written using Chimp! 1. proxying to a service available via HTTP: github.com/softwaremill/c… 2. exposing multiple tools: github.com/softwaremill/c…

More MCP examples written using Chimp!

1. proxying to a service available via HTTP: github.com/softwaremill/c…

2. exposing multiple tools: github.com/softwaremill/c…
Adam Warski (@adamwarski) 's Twitter Profile Photo

The time has come even for JavaScript frameworks to mature; Bartek Butrym created a walk-through of a modern React , Next.js-based application architecture, everything from the folder structure, through tooling (linters), to validating forms! softwaremill.com/modern-full-st…