At ONS, Google describes Espresso, the next step in its SDN strategy.
Espresso is the fourth pillar of Google’s SDN strategy.
Using proper formatting can make it much easier to read code and log samples. Yet so many people don’t bother putting proper formatting around blocks of text. Take some time to learn how to format text in common applications and forums, and make things easier for those trying to help you.
This?
version: ‘2.0’
examples.mistral-yaql-st2kv-user-scope:
vars:
polo: unspecified
tasks:
task1:
action: std.noop
publish:
polo: <% st2kv('marco') %>
on-complete:
– fail: <% $.polo != polo %>
Or this?
Which one is easier to read? Which one lets you parse key information faster? Which one clearly shows file formatting and indentation? Obvious, right?
Yet far too often, I see people paste unformatted text into Slack, GitHub comments, and web forums. They dump huge blocks of unformatted, difficult to read code and logs. Even after repeated prompts to use proper formatting, they just dump big blocks of text.
The good thing is that it’s not that hard to change the display formatting. Many applications contain shortcuts to make this easy. It’s worth your time learning a few of the tips and tricks.
Both Slack and GitHub use a form of Markdown to make it easy Continue reading
Using proper formatting can make it much easier to read code and log samples. Yet so many people don’t bother putting proper formatting around blocks of text. Take some time to learn how to format text in common applications and forums, and make things easier for those trying to help you.
This?
version: ‘2.0’
examples.mistral-yaql-st2kv-user-scope:
vars:
polo: unspecified
tasks:
task1:
action: std.noop
publish:
polo: < st2kv(‘marco’) %>
on-complete:
- fail: < $.polo != polo %>
Or this?
version: '2.0'
examples.mistral-yaql-st2kv-user-scope:
vars:
polo: unspecified
tasks:
task1:
action: std.noop
publish:
polo: <% st2kv('marco') %>
on-complete:
- fail: <% $.polo != polo %>
Which one is easier to read? Which one lets you parse key information faster? Which one clearly shows file formatting and indentation? Obvious, right?
Yet far too often, I see people paste unformatted text into Slack, GitHub comments, and web forums. They dump huge blocks of unformatted, difficult to read code and logs. Even after repeated prompts to use proper formatting, they just dump big blocks of text.
The good thing is that it’s not that Continue reading
The post Worth Reading: IPAM and RIRs appeared first on 'net work.
It's about finding the right service for the right location.