Eric Saraniecki

“How to Start a Startup" panel of six Entrepreneurs

How to Start a Startup: What to Consider Before You Take the Plunge

In this “How to Start a Startup” episode, our panel of founders will discuss their planning — and their inspiration — leading up to the launch of their startups.

'Helvetica Neue', Helvetica, Arial, sans-serif

DAML Driven Blog

DAML Driven

<html>
 <head></head>
 <body>
 Welcome to <a href="/daml-driven/how-to-start-a-startup" rel="noopener" target="_blank">“How to Start a Startup,”</a> a short series aimed at giving aspiring entrepreneurs a range of views about starting a new team, product, or initiative. 
 </body>
</html>

https://hub.daml.com/hubfs/Howtostartastartup.png

Welcome to <a href="/daml-driven/how-to-start-a-startup" rel="noopener" target="_blank">“How to Start a Startup,”</a> a short series aimed at giving aspiring entrepreneurs a range of views about starting a new team, product, or initiative.

module_15571537756151858

module_1557431396199392

module_1563914750727231

name

post_body

Shayne Fletcher

DLint : Expert help writing DAML

DLint analyzes your code while you’re typing it, looking for issues and making suggestions on how you might care to improve it. It’s highly configurable (you can turn warnings off and on with granular scope control).

DAML Engineering Blog

Engineering Notes

For developers of all skill levels, it’s a constant challenge to keep in mind the myriad of ways the code we write could be better. For DAML developers it’s not different. We wish to produce programs that are elegant, efficient, readable by others ... the list goes on. With each PR, we look to our code reviewers to advise us on (at least) the most obvious improvements we could make. This is especially true for DAML newcomers. One of our main goals with DAML is to make developers extremely productive, and to make it easy for them to build high quality and secure code. The faster a developer gets feedback, the more productive they are. Relying on code review has an unfavorable feedback latency and getting full value can be "hit and miss". Wouldn't it be ideal if, while programming, you had an expert at your shoulder offering advice? With the linting features we are integrating into the DAML IDE, the developer gets that advice as they type. DLint analyzes your code while you’re typing it, looking for issues and making suggestions on how you might care to improve it. It’s highly configurable (you can turn warnings off and on with granular scope control). The suggestions are easy for programmers of all levels to understand and where it makes sense, provides suggested code. Taking advantage of it is very easy and its use improves code quality! The image below shows DLint in action. The IDE is warning that it found a block of duplicated code (suggesting an improved version would “factor out” the common block into a function).
<img src="https://hub.daml.com/hubfs/main.png" alt="main" width="1051" style="width: 1051px;">Here’s another example of the sort of thing it can do. Given this function,
<img src="https://hub.daml.com/hubfs/negate.png" alt="negate" width="1083" style="width: 1083px;">DLint provides the following suggestion:
<img src="https://hub.daml.com/hubfs/foldr.png" alt="foldr" width="1084" style="width: 1084px;">
The suggestion here is that we replace our multi-equation recursive function with a one line version using the idiomatic standard library function foldr. 
This is an engineering note, so now let’s get a little into how it's implemented.
DLint is achieved by the adaption and integration of <a href="https://ndmitchell.com/">Neil Mitchell</a>'s celebrated HLint package. HLint is a venerable program with over 15+ years of active development and HLint's use by the Haskell community is ubiquitous. The integration is made possible by the fact that we wrote the DAML IDE in Haskell and that the DAML compiler <a href="https://www.youtube.com/watch?v=mQulFrOp0Rg">uses the GHC stack "under the hood"</a>.
We do a lot of cool open source work at DA. Part of getting this functionality into the IDE means submitting lots of updates to upstream <a href="https://github.com/ndmitchell/hlint">hlint</a> (to use the <a href="http://hackage.haskell.org/package/ghc-lib-parser">ghc-lib-parser</a> package). Also, check out the <a href="https://github.com/digital-asset/ghcide">ghcide project</a> where we're contributing parts of this technology to the Haskell community! DAML itself is completely open source <a href="https://github.com/digital-asset/daml">here</a>.
We are super proud of how the DAML IDE is coming along. Try the new DLint features for yourself! You can download the DAML SDK <a href="https://docs.daml.com/getting-started/installation.html">here</a> and <a href="https://github.com/shayne-fletcher-da/lint-demo">this git repository</a> will give you a quickstart exploring some of DLint’s capabilities.

<html>
 <head></head>
 <body>
 For developers of all skill levels, it’s a constant challenge to keep in mind the myriad of ways the code we write could be better. For DAML developers it’s not different. We wish to produce programs that are elegant, efficient, readable by others ... the list goes on. With each PR, we look to our code reviewers to advise us on (at least) the most obvious improvements we could make. This is especially true for DAML newcomers. One of our main goals with DAML is to make developers extremely productive, and to make it easy for them to build high quality and secure code. The faster a developer gets feedback, the more productive they are. Relying on code review has an unfavorable feedback latency and getting full value can be "hit and miss". Wouldn't it be ideal if, while programming, you had an expert at your shoulder offering advice? With the linting features we are integrating into the DAML IDE, the developer gets that advice as they type. DLint analyzes your code while you’re typing it, looking for issues and making suggestions on how you might care to improve it. It’s highly configurable (you can turn warnings off and on with granular scope control). The suggestions are easy for programmers of all levels to understand and where it makes sense, provides suggested code. Taking advantage of it is very easy and its use improves code quality! The image below shows DLint in action. The IDE is warning that it found a block of duplicated code (suggesting an improved version would “factor out” the common block into a function). 
 </body>
</html>

For developers of all skill levels, it’s a constant challenge to keep in mind the myriad of ways the code we write could be better. For DAML developers it’s not different. We wish to produce programs that are elegant, efficient, readable by others ... the list goes on. With each PR, we look to our code reviewers to advise us on (at least) the most obvious improvements we could make. This is especially true for DAML newcomers. One of our main goals with DAML is to make developers extremely productive, and to make it easy for them to build high quality and secure code. The faster a developer gets feedback, the more productive they are. Relying on code review has an unfavorable feedback latency and getting full value can be "hit and miss". Wouldn't it be ideal if, while programming, you had an expert at your shoulder offering advice? With the linting features we are integrating into the DAML IDE, the developer gets that advice as they type. DLint analyzes your code while you’re typing it, looking for issues and making suggestions on how you might care to improve it. It’s highly configurable (you can turn warnings off and on with granular scope control). The suggestions are easy for programmers of all levels to understand and where it makes sense, provides suggested code. Taking advantage of it is very easy and its use improves code quality! The image below shows DLint in action. The IDE is warning that it found a block of duplicated code (suggesting an improved version would “factor out” the common block into a function).

SDK Release Process

Release of DAML SDK 1.1.1

DAML SDK Release Notes

Release Notes

DAML SDK 1.1.1 has been released on 13th May 2020. You can install it using

daml install latest
If you're planning to upgrade your DAML SDK to take advantage of our newest features please note that some action may be required on your part. If you're not planning to upgrade then no change is necessary.
Note that we had to skip the 1.1.0 version number due to a glitch in our release process. The 1.1.1 release is the release of 1.1.0-snapshot.20200506.4107.0.7e448d81, which was the release candidate for SDK 1.1.0
<h2>Summary</h2>
<ul>
<li>New package management endpoints on the JSON API</li>
<li>Better TLS Support for the JSON API</li>
<ul>
<li>Action required if you start the JSON API using daml json-api and do not run it behind a reverse proxy.</li>
</ul>
</ul>
<h2>What’s New</h2>
<h3>New Package Management Endpoints on the JSON API</h3>
Background
The Ledger API’s package management service allows uploading, downloading and listing of DAML packages available on a DAML Ledger. For situations where connecting to the Ledger API is not possible or is inconvenient, these services are now available through the JSON API as well.
Specific Changes
<ul>
<li>The JSON API has three new endpoints</li>
<ul>
<li>GET /v1/packages -- returns all package IDs</li>
<li>GET /v1/packages/&lt;package ID&gt; -- downloads a given DALF package</li>
<li>POST /v1/packages -- uploads a DAR file to the ledger</li>
</ul>
</ul>
Impact and Migration
This is a purely additive change. Users who connect to gRPC from their applications for the sole purpose of managing DAML packages may switch over to the new endpoints to eliminate dependencies on gRPC or Ledger API language bindings.
<h3>Better TLS Support for the JSON API</h3>
Background
In addition to the numerous new TLS options introduced in SDK 1.0.0, the JSON API can now also connect to the Ledger API via TLS. To protect against insecure connections which may leak access tokens, it also adds a warning if not run behind a reverse proxy that terminates TLS connections. This warning will become an error in a future release.
Specific changes
<ul>
<li>The JSON API accepts new command line parameters --pem, --crt, --cacrt, and --tls, which configure it to connect to the Ledger API using TLS.</li>
<li>By default, the JSON API now checks that connections are made through a reverse-proxy providing HTTPS, ensuring that JWT tokens don't leak. To disable this check, such as for development, pass --allow-insecure-tokens. A failed check currently results in a warning.</li>
</ul>
Impact and Migration
daml start&nbsp;automatically sets this flag so there is no migration needed. If you are starting the JSON API manually, we advise you to add the flag --allow-insecure-tokens for development environments, and to run the JSON API behind a TLS-enabled reverse proxy in production.
<h3>Minor Improvements</h3>
<ul>
<li>Faster Sandbox reset via the ResetService.</li>
<li>daml trigger and&nbsp; daml script now default to wall clock time if&nbsp; neither --wall-clock-time or --static-time&nbsp;is passed.</li>
<li>daml script now has an --output-file option that can be used to specify a file the result of the script should be&nbsp; written to. Similar to --input-file the result will be output in the DAML-LF JSON encoding.</li>
<li>You can now disable implicit party allocation of the Sandbox by passing the flag --implicit-party-allocation=false. This makes it easier to test as you would against another ledger which does not support this feature.</li>
<li>The daml ledger commands no longer require the Bearer prefix in the access token file. This matches the behavior of DAML Script and other SDK tools.</li>
<li>Added --max-commands-in-flight&nbsp;to Sandbox CLI configs. This limits the maximum number of unconfirmed commands in flight in CommandService.</li>
</ul>
<h3>Improvements to Early Access Features</h3>
<ul>
<li>daml damlc visual&nbsp;now works properly in projects consisting of multiple packages.</li>
<li>Fix a bug where `exerciseByKey` was not properly recognized by daml damlc visual.</li>
<li>DAML REPL now produces better error messages on calls to&nbsp; error and abort.</li>
</ul>
<h3>Bug Fixes</h3>
<ul>
<li>Fix a bug where scenarios with names containing special characters resulted in a crash in the scenario service.</li>
<li>The Sandbox properly respects the --log-level CLI parameter</li>
<li>The sandbox now properly delays command submissions using minLedgerTimeAbs or minLedgerTimeRel. See <a href="https://github.com/digital-asset/daml/issues/5480" rel=" noopener">issue #5480</a>.</li>
<li>Migrating from Sandbox 0.13.55 to Sandbox Classic 1.0.0 could have introduced contracts falsely reported as active when in fact they are not. Migrating to Sandbox Classic 1.1.0 will fix the issue. See <a href="https://github.com/digital-asset/daml/issues/5659" rel=" noopener">issue #5659</a>.</li>
</ul>
<h3>Changes to Ledger Integration Kit</h3>
These changes only affect ledger integrators and operators that consume the metrics emitted by the DAML Integration Kit. We have introduced new metrics and adjusted the naming of existing metrics to be consolidated. If you have built a dashboard for a ledger built using the integration kit, then you will need to adapt that dashboard. The changes are as follows.
<ul>
<li>We have introduced these new metrics:</li>
<ul>
<li>a timing metric for the commit at daml.kvutils.writer.commit.</li>
<li>a metric for command validation upon submission, daml.commands.validation.</li>
<li>daml.commands.submissions&nbsp;is a new timer that measures all submissions.</li>
<li>daml.commands.valid_submissions&nbsp;is a new meter that counts valid (unique, interpretable) submissions.</li>
<li>daml.kvutils.reader.parse_updates&nbsp;is a new timer that measures the translation time of ledger log entries when serving state updates to the indexer</li>
<li>daml.kvutils.reader.open_envelope&nbsp;is a new timer that measures the deserialization time of ledger log entries when serving state updates to the indexer</li>
<li>daml.ledger.log.append&nbsp;is a new timer that measures the time for writing new log entries</li>
<li>daml.ledger.state.read&nbsp;is a new timer that measures reading from the ledger state</li>
<li>daml.ledger.state.write&nbsp;is a new timer that measures writing to the ledger state</li>
</ul>
<li>We have renamed these metrics:</li>
<ul>
<li>daml.lapi.command_submission_service.failed_command_interpretations has been renamed to daml.commands.failed_command_interpretations.</li>
<li>daml.lapi.command_submission_service.deduplicated_commands has been renamed to daml.commands.deduplicated_commands.</li>
<li>daml.lapi.command_submission_service.delayed_submissions has been renamed to daml.commands.delayed_submissions.</li>
<li>daml.lapi.command_submission_service.submitted_transactions has been renamed to daml.services.write.submit_transaction.</li>
</ul>
<li>The metrics registry should now be passed using the new com.daml.metrics.Metrics type, which wraps/replaces com.codahale.metrics.MetricsRegistry</li>
<li>maxDeduplicationTime configuration (the maximum time window during which commands can be deduplicated) has moved from SubmissionConfiguration to the Configuration class</li>
<li>Engine is now mandatory in several&nbsp; participant api server related constructors to avoid running multiple interpretation engines.</li>
</ul>

DAML SDK 1.1.1 has been released on 13th May 2020. You can install it using

Get your distributed app to market first

Productive

Innovative

Developer Driven

The platforms

by Blockchain Technology Partners