 |
| Photo by Simon English on Unsplash https://unsplash.com/photos/48nerZQCHgo |
If I had a child, that would be graduating in 2021 - and going out into the professional world...I would spend the next 6-8 months finding different ways to communicate, illustrate, and educate them on these most important lessons that took me decades to learn:
What you will earn is largely limited by your own perceptions of your limitations - and not the perception of other's of your abilities.Effort is necessary - but not all efforts are compensated equally, nor in a consistently linear fashion.While you need to earn a decent living - always value learning, new challenges that will cause you to stretch and grow, and new experiences - over a mere title, or a salary.Never stop learning.Who you collaborate with - is one of the most important factors in your future growth - and fitness for future opportunities.Value building relationships over transactions.
Updating my personal development toolchain today with Docker 3.0.0 and reading this excellent series of articles by Christopher Crone (from the Docker blog's go-env-series):
Containerize Your Go Developer Environment (parts 1,2,3)
Doing a bit of research today on variations in how different API implementations have chosen to support filter syntax. This blog post is a placeholder for organizing additional examples that I am working collect and organize.
AND, OR, or NOT operators."{work-in-progress post - I'll continue to elaborate on this post in the future, with additional sections and narrative text}
In response to this recent article on DZone: Load Balancer Explained – Simplified Through Comics - I prepared this blog post.
A few additional suggested background reading articles that may be of interest for those who want to understand load balancing - and some of the related concerns/considerations - a bit deeper:
 |
| Photo by iMattSmart on Unsplash |
Today I've spent some time browsing through Stack Overflow questions - looking for interesting questions that I might take a stab at answering.
An outcome of that effort has been the serendipity of learning about the following...
"Puppeteer is a Node library which provides a high-level API to control Chrome or Chromium over the DevTools Protocol. Puppeteer runs headless by default, but can be configured to run full (non-headless) Chrome or Chromium."
What can it do?
Here are some interesting links:
Additionally, these tutorial resources might be of interest
Nitay Neeman has some interesting Puppeteer content:
 |
| Photo by Ryan Quintal on Unsplash |
I spent some time this evening assembling a response to a Stackoverflow question:
"How should I design a REST API?"
https://stackoverflow.com/questions/64940600/how-should-i-design-a-rest-api/64940695#64940695
My answer:
Reading the RFCs is highly recommended
RFC 7231 Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
https://tools.ietf.org/html/rfc7231In particular, pay close attention to Section 4.3 Method Definitions
https://tools.ietf.org/html/rfc7231#section-4.3
- "The POST method requests that the target resource process the representation enclosed in the request according to the resource's own specific semantics."
- "The PUT method requests that the state of the target resource be created or replaced with the state defined by the representation enclosed in the request message payload."
Which is to say - that you will find variation in how an update action is processed (some folks use POST, some use PATCH, many use PUT), depending on their implementation-specific resource semantics.
In your example, it appears that the PUT resource-specific semantic implementation is treating the submitted data element as a full replacement - and since you did not include the age element - it is left as null.
PATCH is indeed intended as the verb for doing a partial update, refer to:
RFC 5789 PATCH Method for HTTP
https://tools.ietf.org/html/rfc5789
- "The PATCH method requests that a set of changes described in the request entity be applied to the resource identified by the Request-URI. The set of changes is represented in a format called a "patch document" identified by a media type."
- "The difference between the PUT and PATCH requests is reflected in the way the server processes the enclosed entity to modify the resource identified by the Request-URI. In a PUT request, the enclosed entity is considered to be a modified version of the resource stored on the origin server, and the client is requesting that the stored version be replaced. With PATCH, however, the enclosed entity contains a set of instructions describing how a resource currently residing on the origin server should be modified to produce a new version. The PATCH method affects the resource identified by the Request-URI, and it also MAY have side effects on other resources; i.e., new resources may be created, or existing ones modified, by the application of a PATCH."
- "PATCH is neither safe nor idempotent"
- "There is no guarantee that a resource can be modified with PATCH. Further, it is expected that different patch document formats will be appropriate for different types of resources and that no single format will be appropriate for all types of resources. Therefore, there is no single default patch document format that implementations are required to support."
- "Clients need to choose when to use PATCH rather than PUT. For example, if the patch document size is larger than the size of the new resource data that would be used in a PUT, then it might make sense to use PUT instead of PATCH. A comparison to POST is even more difficult, because POST is used in widely varying ways and can encompass PUT and PATCH-like operations if the server chooses. If the operation does not modify the resource identified by the Request-URI in a predictable way, POST should be considered instead of PATCH or PUT."
When using PATCH for JSON type documents, see
RFC 6909 - JavaScript Object Notation (JSON) Patch
https://tools.ietf.org/html/rfc6902
- "JSON Patch defines a JSON document structure for expressing a sequence of operations to apply to a JavaScript Object Notation (JSON) document; it is suitable for use with the HTTP PATCH method. The "application/json-patch+json" media type is used to identify such patch documents."
Additionally, you may find these resources useful
POST method to make a partial update and the PUT method to delete unspecified properties."PUT method. Any property not specified
in the request is deleted." PUT method for partial updates.""For customers who want to simplify complex and distributed environments across on-premises, edge and multicloud, Azure Arc enables deployment of Azure services anywhere and extends Azure management to any infrastructure."
"The following functionality found in the managed gateways is not available in the self-hosted gateways:...", (KM: see article for details)
"When connectivity to Azure is lost, self-hosted gateway will be unable to receive configuration updates, report its status, or upload telemetry."
"Hosting self-hosted gateway in Docker is best suited for evaluation and development use cases. Kubernetes is recommended for production use."
"The self-hosted gateway sends telemetry to Azure Monitor and Azure Application Insights according to configuration settings in the associated API Management service. When connectivity to Azure is temporarily lost, the flow of telemetry to Azure is interrupted and the data is lost for the duration of the outage. Consider setting up local monitoring to ensure the ability to observe API traffic and prevent telemetry loss during Azure connectivity outages."
Integrate API Management in an internal VNET with Application Gateway
"Azure Virtual Networks (VNETs) allow you to place any of your Azure resources in a non-internet routable network that you control access to. These networks can then be connected to your on-premises networks using various VPN technologies."
For one who seeks to be a master of their craft - you must continually attend to sharpening the saw.
Today: A deep dive back into C++ POSIX threaded programming, using the G++ compiler, available with the GNU Compiler Collection (GCC 10.2) - and exploring the differences in C++17, and the experimental implementation of some C++20 features.
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-cygwin/10/lto-wrapper.exe
Target: x86_64-pc-cygwin
Configured with: /mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/configure --srcdir=/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0 --prefix=/usr --exec-prefix=/usr --localstatedir=/var --sysconfdir=/etc --docdir=/usr/share/doc/gcc --htmldir=/usr/share/doc/gcc/html -C --build=x86_64-pc-cygwin --host=x86_64-pc-cygwin --target=x86_64-pc-cygwin --without-libiconv-prefix --without-libintl-prefix --libexecdir=/usr/lib --with-gcc-major-version-only --enable-shared --enable-shared-libgcc --enable-static --enable-version-specific-runtime-libs --enable-bootstrap --enable-__cxa_atexit --with-dwarf2 --with-tune=generic --enable-languages=c,c++,fortran,lto,objc,obj-c++ --enable-graphite --enable-threads=posix --enable-libatomic --enable-libgomp --enable-libquadmath --enable-libquadmath-support --disable-libssp --enable-libada --disable-symvers --with-gnu-ld --with-gnu-as --with-cloog-include=/usr/include/cloog-isl --without-libiconv-prefix --without-libintl-prefix --with-system-zlib --enable-linker-build-id --with-default-libstdcxx-abi=gcc4-compatible --enable-libstdcxx-filesystem-ts
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.2.0 (GCC)
"The LLVM Project is a collection of modular and reusable compiler and toolchain technologies. Despite its name, LLVM has little to do with traditional virtual machines. The name "LLVM" itself is not an acronym; it is the full name of the project."
"LLVM began as a research project at the University of Illinois, with the goal of providing a modern, SSA-based compilation strategy capable of supporting both static and dynamic compilation of arbitrary programming languages. Since then, LLVM has grown to be an umbrella project consisting of a number of subprojects, many of which are being used in production by a wide variety of commercial and open source projects as well as being widely used in academic research. Code in the LLVM project is licensed under the "Apache 2.0 License with LLVM exceptions" "
 | ||
| Photo by Diego PH on Unsplash |
A meditation for tomorrow:
Do one good thing before the sun sets tomorrow - for someone else - without any expectation of reward.
Plant a seed.
Offer a suggestion.
Make a recommendation.
Send a thank you.
Remind someone of the impact they had on your life, your career.
Reach out to someone and offer your help.
Volunteer.
Speak words of encouragement.
Offer praise for a job that was truly well done.
Pause for a moment and find something in another - for which you are grateful.
Be the thread of inspiration.
Be The Light For Others.
There are many different schools of thought in the world of IT, software engineering, and architecture today.
The
pendulum has swung so far in the direction of "Continuous delivery of
throwing spaghetti against the wall - to see what sticks" - that many
have lost sight of the need (and value) of doing __any__ deep design
work.
That has an often predictable outcome: "Continuous Rework".
Which is neither agile, lean, efficient, or economical.
Consider this feat of engineering:
"This digital model was created for the project of the virtual exhibition 'Prague at the time of Charles IV' and shows how the construction of the Charles Bridge took place in the 14th century"
"construction began at 5:31am on 9 July 1357...[and] was completed 45 years later in 1402" https://en.wikipedia.org/wiki/Charles_Bridge
Analysis. Design. Architecture. Planning. Calculations. Engineering.
All went into this effort.
Much good would accrue - if we make a distinction between what is appropriate for trial-and-error engineering - and what benefits may accrue to valuing some judicious levels of investment in deep design work.
Flailing may create the appearance of a lot of activity (and perhaps may seem to imply progress) - but, it is not a very efficient operating model.
Also see:
The github repo ("A curated list of Chaos Engineering resources.") maintained by Pavlos Ratis
and:
https://principlesofchaos.org/
https://github.com/chaos-eng/chaos-eng.github.io/
and:
"The Chaos Toolkit aims to be the simplest and easiest way
to explore building your own Chaos Engineering Experiments."
Illuminating the dark spaces of healthcare with ambient intelligence
Nature | Vol 585 | 10 September 2020 (p-193)
https://www.nature.com/articles/s41586-020-2669-y.pdf
"Advances in machine learning and contactless sensors have given rise to ambient intelligence—physical spaces that are sensitive and responsive to the presence of humans. Here we review how this technology could improve our understanding of the metaphorically dark, unobserved spaces of healthcare. In hospital spaces, early applications could soon enable more efficient clinical workflows and improved patient safety in intensive care units and operating rooms. In daily living spaces, ambient intelligence could prolong the independence of older individuals and improve the management of individuals with a chronic disease by understanding everyday behaviour. Similar to other technologies, transformation into clinical applications at scale must overcome challenges such as rigorous clinical validation, appropriate data privacy and model transparency. Thoughtful use of this technology would enable us to understand the complex interplay between the physical environment and health-critical human behaviours"
The implications for healthcare, treatment, restoring capabilities - are staggering
https://initialcommit.com/blog/7-versatile-vim-commands
I also have a Tips.VIM.md file that I maintain in my Tips repository on github.
 |
| Photo by Sergey Zolkin on Unsplash https://unsplash.com/photos/m9qMoh-scfE |
I've begun drafting some ideas for what kind of information may be useful to include in "Title Block" for architecture diagrams.
I think that the current state (or, lack thereof) of annotating software design architectural drawings - is abysmal - and much might be gleaned by looking left-and-right - and seeing how other industries annotate their diagrams.
Problem Statement:
Writing this post was cathartic for me. It is an expression of hope, of optimism - that COVID-19 is only a temporary condition - and that we will be able to travel safely and freely again - at some point in the future.
 |
| Photo by Callum Chapman on Unsplash https://unsplash.com/photos/R01A9PJQNIM |
STATUS OF THIS POST: WORKING DRAFT
The motivation for writing this blog posting arose this evening - when I learned that a family member will soon begin joining the ranks of Road Warriors (as a traveling nurse). This is written to provide her with some tips, suggestions, ideas.
My first choice in booking travel reservations is Expedia.com - (and, if you are 50+, and have AARP membership, you can use the AARP Expedia site - which usually will reflect the typical 10% AARP discounted rate)
My rationale:
While booking through a third-party service provider, such as Expedia, means that you will forego earning points with a hotel's own rewards program - I find the peace of mind (in the following points) to be a primary factor in my decision.Additional travel reservation resources that you might consider:
If you will be paying your travel expenses out of your own pocket - then, for convenience, value, quality, and comfort - here are my recommendations for hotels, in order of preference:
However, If the client will be reimbursing you for your travel costs, here are a few additional hotel recommendations - offering a higher tier of services, quality, comfort, and convenience:
Of course, there are other alternative strategies for arranging accommodations - particularly if you need to plan for long-duration stays:
 | |
| [image credit: HarborFreight.com] |
 |
| Photo by Sven Scheuermeier on Unsplash https://unsplash.com/photos/AXsJBByg4Ic |
Additional passport services that may be useful to know about (however, I suggest checking their latest reviews on Yelp, first):
For any of the above that I don't find immediately nearby - I'll spend an hour putting together a file in a /Locations directory that I maintain (part of a personal "knowledge management" process I've developed over the years) - that will then be my handy list for organizing information that I discover about that particular area - should I need to find something quickly in the future, or return after some time may have passed.
An additional goal of my perimeter walk is to assess the vibe of the neighborhood - and assess its relative safety - and identify any potential risks or threats. Noting the safe, and possibly less safe - passages.
Within a week - I will have made a personal connection with a number of people in that immediate neighborhood - including the hotel front desk personnel - establishing a network of potential information resources.
With Gratitude! (and, in order of submissions received)
