Topics for developer-focused blogposts?

Hey DAML community,
We are exploring having a stream of a bit more developer-focused blogposts.

For that reason, we would like to have a technical blog post series and we are asking the community which specific topics they would like to read about? :thinking:

Some previous technical topics that we wrote:

Comment below if you have any topic ideas :point_down:


I want to see a post on common tips and tricks. Simple things like increasing the cache or daml.yaml options that we might overlook.


yes, tips and tricks please, but language-focused: record / list / tuple destructuring, the .., {..}, or $ syntax, advanced patter matching constructs, etc.

These kind of tricks are nowhere to be found in our docs (as they’re mostly inherited from Haskell), but are extremely helpful for writing elegant code. Some of them were real eye openers when I first encountered them.

Another topic: DAML style guide - would be great to learn from our language experts how they structure code / syntax and why. In the absence of an auto-formatter it’s sometimes hard to come up with a good convention yourself.


Echoing a bit what @georg said, tips and tricks for better DAML language syntax would be great! It would also be great for those tricks to find their way into the docs. When writing and adjusting contracts, I find myself surveying other DAML contracts/repos for new ideas first before referencing the documentation because parts of the docs provide very little context.


Same. I sometimes find myself looking for how to do things in Haskell in order to do them in DAML.

1 Like

On another note, I came across this question and answer from @georg and @cocreature the other day. I am pretty new to development and am unfamiliar with setting up debug statements, etc. An article that showed step-by-step how to set this up with (with DAML code, debugging statements throughout DAML code, reading Sandbox logs) could be very helpful.


this one @jamesljaworski85 is a great topic i find, will pursue it further.