That's frustrating. My usual solution to this problem is just to use the rentable city bikes. I usually bring a helmet with lights attached.

We got a vote that will probably not succeed to maintain healthcare insurance subsidies.

It will be abundantly clear who is responsible for raising premiums for small business owners and independent contractors.

Thank you!

Is there a PowerShell cheat sheet or tutorial that you recommend?

Can we tell them made to the best decision in hiring you, but we really need to see more examples in Julia?

Most dogma in biology is hubris. Terms like "junk DNA" or non-coding make the assumption that we understand the full scope of how DNA works or what it codes for.

It would be like claiming to understand how a computer works by looking only at persistent storage and snapshots of RAM.

I have been thinking about this lately, and I have realized how many other patterns forcing one module per file suppresses.

The most egregious is that Python encourages long files rather than short ones. Whereas it may make sense to break things up per driver function or even per function.

I usually do try to talk to them when I see them. They usually do buy a ticket except for that one time they asked the MIT President's Office for free tickets. If you recognize, thank them for buying a ticket and helping them to fund JuliaCon and Julia!

There is always a MATLAB employee at JuliaCon Global. I'm not sure if they make it to the "local" JuliaCons though.

They want to know what we are up to. Also, most of Julia is liberally licensed. They could probably incorporate it if they really wanted to.

In short, the VS Code and Pluto experience do differ. However, both offer some ability to do incremental development through a dynamic workflow. VS Code is not inherently reactive at the moment, but with Revise.jl can update method definitions.

Combined with Revise.jl this can be a very powerful development environment. The main legacy issue is changing struct definitions, which is possible in Pluto but not in the general REPL or Revise.jl. Upcoming development versions of Julia do address this, however.

Julia and VSCode workflow can take many forms, including running Jupyter notebooks.

There are some attempts to integrate Pluto.jl into VS Code, but those have been inactive.

The main Julia VS Code workflow is the ability to execute code from the editor in a running REPL.

What were you doing previously?

The blog discusses `@chain` in comparison to R's pipe operators. Julia also has a `|>` operator for pipes.

I think you mean "congestive heart failure."