2025-12-07

2025-12-07 Sunday - Book Review - Microsoft Azure in Action

  

[image source: Amazon.com]

Thanks to Divya Aravind for the very kind invitation to review this book. 

Microsoft Azure in Action, by Lars Klint 
https://www.amazon.com//dp/1617299650 

[My Amazon review entry

A concise introduction and overview of Microsoft Azure

This is a good book if you are new to Microsoft Azure - and it is appropriate for leadership teams, managers, delivery teams, infrastructure folks, networking staff, cybersecurity, operations personnel, and architects of all types. Everyone for whom Azure is new - will gain beneficial insights, for their respective roles, by reading this book. 

While trying to comprehensively tackle Azure in a single book (in less than 370 pages) is an impossible task for anyone - this book provides an excellent means for IT staff to quickly get oriented and familiarized with much of the core Azure concepts, services, and best practices. 

A few words about the quality that has gone into the writing of this book: 
First, the content is well organized. 
Second, the writing is concise. 
Third, the selected material is the most relevant information to impart to the reader - to get them hands-on, soonest. 

From the Forward, I agree with this sentiment: 
"I first met Lars at TechEd Sydney in 2014, where he was doing what he does best: making complex technology feel approachable and energizing. ... Lars doesn’t just explain what Azure can do; he offers a hands-on guide
-- Scott Gutherie 

From the Preface, note the author's goals for the book: "hands-on", "straight to the point", "practical examples", and "relatable". 
These objectives are well met by this book. 

One of the best aspects of the author's writing - is the patient step-by-step detailed guidance - that includes the WHY of many decision decisions - and the REASON for choosing particular configuration options. 

Four parts of the book - that I think the majority of folks will find most interesting - in particular, include: 
Chapter 4 (Networking in Azure) 
Chapter 6 (Security)
Chapter 8 (Serverless) - re: touching on API Gateway usage 
Chapter 10 (Relational databases) - re: 10.5 Disaster Recovery 

I'm giving this book a solid 4 Stars - as I believe it is a worthwhile book to have on your bookshelf. 
 

 

During my background research for this review, I found a number of additional resources that readers of the book might find of possible interest:

Official Microsoft Azure resources:  

 Other non-Microsoft Azure resources

2025-12-07 Sunday - Lessons from an HR Thought Leader

I've just read some of the posts by Bryan Howard  (Chief Executive Officer, Peoplyst) - an  HR consulting/advisory thought leader - and just really enjoyed his writing so very much...so insightful.

Sharing some snippets from two of his recent posts that really caught my attention...

https://www.linkedin.com/feed/update/urn:li:activity:7393677270416105472/

  • "We can't afford to give raises," the division leader said.
  • "So you won't pay someone 15% more to stay,
  • but you'll pay someone else 30% more to start?"

 

https://www.linkedin.com/feed/update/urn:li:activity:7403164257367900161/

  • "Our one-on-ones are pointless."
  • Everyone says they're fine. Then they quit," the director told me.
  • "It's not a one-on-one," I said.
  • "It's an interrogation." 
  • "Turns out when you stop interrogating people,
  • they start telling you the truth."

 

2025-11-21

2025-11-21 Friday - A most frivolous and minor milestone - 500K Visitors

This week marks a most frivolous and minor milestone for this blog - 500K visitors, since re-launching in 2006 (I threw the first incarnation away, after quite a few years of plodding in my early writing efforts).  

Growth, in terms of visitors and the engagement metrics, are a bit skewed - since Google changed how some content is ranked in search results, some years ago (after which I noted a dramatic fall-off in traffic) - and with the more recent increasing nuisance of bots scouring the web for content. 

I do not write for an audience - I write to explore my thinking - and to record how my thinking changes, over time. 

I write to understand...

The blank page is my dojo, my canvas...

This blog has been personally useful to me - as a means of collecting and organizing information - and it helps facilitate sharing some selected bits, from time-to-time, with folks that I meet in the course of my professional work. 

Words sing to me. Words have texture, nuance, and meaning - and there is a rhythm to writing something well.  Which is not to say that I write well - but that I aspire to become a better writer, always. 

 

[image credit: Tama66 on pixabay.com]

 

2025-09-20

2025-09-20 Saturday - Why is Software Development Hard?

This post was spurred by a recent LinkedIn post by Keith V., Manager, Software Engineer, with The Knot Worldwide

[image source: LinkedIn]


 

I would argue that AI isn't going to solve the problem of getting better requirements - when the root cause is buried under complex layers of organizational politics, competing agendas, and incomplete/partial visions/strategies.

I would have included some references to the very real struggle to solicit/understand the *actual* requirements, correctly. As well as getting alignment and agreement.

Based on my observations, writing the code is rarely the real blocker / reason for delay / cause of rework.

It is usually attributable to delays (and rework) in divining the vision/idea that is sometimes just a wisp of a thread...floating around in the heads of several/many different stakeholders...which may encompass competing ideas, or sometimes - even antagonistic/hidden agendas.

Real, meaningful, clarifications of requirements - requires human-to-human conversations. 

[Also see my reply on LinkedIn

[My LinkedIn companion post, referencing this blog post]

2025-08-24

2025-08-24 Sunday - Remember to Pause - and Allow Time for Reflection and Contemplation of the Design

 

 

[image credit: UltraWorldJY on pixabay.com]

Today's meditation:

Most people are pretty good at designing systems to handle first-order effects.

It is the second- and third-order effects that catch most folks by surprise.

But not because they can't anticipate them.

If your teams are racing to complete a sprint, or meet a deadline - that pressure can create a hole, or weakness, in your design...and teams rarely have the luxury of thinking about those second- and third-order effects.

For the critical sections/paths - leveraging a second pair of eyes can help spot what others, too close to the solution, may have missed.

Remember to pause, and allow time for reflection and contemplation of the design.



 

2025-08-19

2025-08-19 Tuesdday - Donald Raab's New Book - Eclipse Collections Categorically

[image source: Amazon.com]

Donald Raab's new book, on Amazon:

https://www.amazon.com/Eclipse-Collections-Categorically-Level-programming/dp/B0DZVK69D3/ 

 

The Author’s Inside Guide to Reading Eclipse Collections Categorically

https://donraab.medium.com/the-authors-inside-guide-to-reading-eclipse-collections-categorically-950b245e8cab 

"Eclipse Collections Categorically: Level up your programming will be free to read worldwide on Amazon Kindle ONLY from August 21st, 2025 through August 25th, 2025."


 

2025-08-05

2025-08-05 Sunday - My True North

 

[Isla San Martín, on a sailing sabbatical in 2004, Baja California, Mexico]

Today's meditation:
My True North, throughout my professional life - has NOT been...
- to be rich 
- to dominate anything 
- to crush the competition
- to win at all cost
- to be #1 

It has simply been to...
- work on interesting problems.
- feed my insatiable curiosity for learning. 
- make a decent living.
- be of service to my clients. 

I consider myself fortunate, that I learned early...the value of needing little, and recognizing what is enough. 

Decades ago, I decided to exit the never-ending treadmill of corporate life...of annual reviews...and existing within the rigid maze of structured hierarchies, that more often than not - limited my options. 

There are corporate rewards I purposefully chose to not pursue.
Titles held little appeal to me, for the shackles they would entail - were too costly.

Instead, I chose to start my solo consulting practice. 

To work as an outsider - offers a freedom to give advice, unencumbered - without the fear of annual review/bonus/promotion ramifications, or repurcussions. It is essential to being able to say what needs to be said, and not just what folks may wish to hear. 

My experiences have been many and varied...offering many opportunities to work across many diverse cultures, industries, technologies, and companies. 

I work when I want, and I decide which clients I will accept. 
I set my own rates - priced fairly, for the value I help create. 

In my life's work, I have found a degree of the freedom that I first discovered sailing upon the ocean. 

Freedom is a potent wine. 


My companion post on LinkedIn



2025-08-03

2025-08-03 Sunday - The Icarus Strategy

Jacob Peter Gowy's The Fall of Icarus (1635–1637) - source: Wikipedia 

 

In Greek mythology, Icarus was the son of the master craftsman Daedalus, the architect of the labyrinth of Crete. After Theseus, king of Athens and enemy of King Minos, escaped from the labyrinth, Minos suspected that Icarus and Daedalus had revealed the labyrinth's secrets and thus imprisoned them—either in a large tower overlooking the ocean or in the labyrinth itself, depending upon the account. Icarus and Daedalus escaped using wings Daedalus constructed from birds’ molted feathers, threads from blankets, the leather straps from their sandals, and beeswax. Before escaping, Daedalus warned Icarus not to fly too low or the water would soak the feathers and not to fly too close to the sun or the heat would melt the wax. Icarus ignored Daedalus's instructions not to fly too close to the sun, causing the beeswax in his wings to melt. Icarus fell from the sky, plunged into the sea, and drowned.

~ Wikipedia

 

A meditation today, after reading yet another Agentic AI / LLM / GenAI Tech Bro Vibe Coding Dependent "success" story...  

Based on the observed statements (and collective behavior) of quite a few companies, one might surmise that the following are core tenets of how they operate... 

The Icarus Strategy  - Core Tenets:

1.      “It’s different this time.”

2.      “Gravity doesn’t apply to us.”

3.      “Growth at all costs.”

4.      “Reliability is a nuisance.”

5.      “Quality is an afterthought…but only if we have some spare time.”

6.      “Consequences are for peasants.”

7.      “Releasing half-baked products IS our product strategy.”

8.      “Don’t bother me with your piddly-ass security concerns.”

9.      “Liquidity events/exits are more important than building for sustainability.”

10.  “Disciplined Software Engineering is a boat anchor - for others.”

11.  “Shortcuts don’t have consequences, and if they did, they don’t matter - for us.”

12.  “Who cares if the underlying algorithms, tools, infrastructure, architecture are unreliable?”

13. "Everyone else's intellectual property must be sacrificed for the greater good...really, we couldn't operate without it."

14. "Growing junior devs into senior devs - that's someone else's problem". 

15. "All must worship at the feet of the great stochastic parrot."  

 

 

[image credit: Couleur on pixabay.com]

 

 My companion post on LinkedIn

WordCount

Copyright

© 2001-2025 International Technology Ventures, Inc., All Rights Reserved.