"You too now begin to be a magician"
Cobra has a sense of humor, naming these particular exhaust pipes, the “Neighbor Haters”.
I took Bob out and started warming him up for a couple hours of riding today, wish the pipes weren’t so embarrassingly quiet. š
Nothing more serene than the sound of spring tree frogs.
COVID has broken a lot of things, not the least to mention is our view of the world.
This morning I made a comment to Braeden, that I was performing my morning mental exercise, e.g. trying to find matching sock colors in the “sock bin”.. it’s not an easy thing to do.
His response: “Why do you have to wear socks, people can’t see your feet on video chat.”
I wonder how far you could take that line of reasoning, or how far some people do take it… š¤Ø
Lying on a hammoc, listening to the pre-spring peepers..
What a lovely night.
; This is the way the world ends, in Assembly
; Author: Jediah Logiodice
; Date: 11/05/2020
start:
push ebp
mov ebp, esp
xor eax, eax
starttask:
add esp, 4
cmp eax, eax
je starttask
mov esp, ebp
pop ebp
ret 0
Just finished up a thought provoking and highly-entertaining treatment of concepts and ideas swirling around related to life, the universe and everything.
Unlike some reviewers of the book, I specifically appreciate that the author tries to synthesize the scientific world view with the religious world view.
There are too many in life that think the world is so black and white, on both sides, thus being completely unwilling to give credence to what another might say or think across the divide.
The dichotomy reminds me of a couple maxims summarized by Covey and Bragg: 1) first seek to understand, then to be understood, and 2) science and religion are opposed as the thumb and forefinger – between the two you can grasp anything.
I came to a similar simulation theory ages ago (without much science knowledge to back it up, just through general observation and cognitive experiences), I’m glad to see we have some great thinkers spending significant clock-cycles on it.
Somewhere in our future is “The Theory of Everything”. Keep seeking!
While having conversations with a couple friends the last few weeks, I came to the conclusion that there might be value in writing down some of the ideas I have floating around in the big tin-can on my shoulders, as it relates to opensource software (oss).
Or, then again maybe not.
Regardless, I took a few minutes to jot down some thoughts. This list is by no means exhaustive, itās just a quick brain dump around what comes to mind when I think about using oss in the enterprise.
Talent implications:
There are some definite and perhaps obvious implications to attracting talent when it comes to participating in the oss community. First and foremost, it is an easy way for an organization to market itself, its culture, its people and its technology capabilities. Secondarily, in my mind, developers that engage with the oss community show an increased dedication and passion for ongoing learning and development outside of the 9×5. So participatory individuals definitely represent a type of individual I want to have in my organization.
Technology practices:
OSS can be fickle, as it involves many people with diverse backgrounds and perspectives agreeing to agree. š
When using oss, I would suggest setting up a company repository where oss and dependencies are curated and maintained as approved for corporate use. In addition, I would also recommend blocking teams from using external repositories, in order to manage and mitigate various risks based on company appetite. JFrog Artifactory is one such example of a solution that can be used for a corporate repository.
The link below gives a brief example of what can happen if you aren’t careful in how you manage the repository in the oss world. š³
In addition, in order to maintain bench strength, autonomy, ensure continuity, and enforce corporate quality gates, it is also important to not become reliant on compiled binaries; as such, I would ensure the company has the toolchains and configurations to compile source code into binaries in a CI/CD type of model.
Security of open source:
On the upside, oss allows for easier identification and crowdsourced remediation of vulnerabilities; however, on the flip-side, it is easier for hackers to identify vulnerabilities, fingerprint companies using the oss, and subsequently exploit vulnerabilities, without disclosing them.
Thus, it is important to have a solid program in place for monitoring for emergent vulnerabilities and patching in a timely manner, especially for externally facing solutions. This also drives back to the discussion of having a centralized repository for curating approved oss.
Licensing models:
Iām not a legal expert by any means but know enough to state that careful considering needs to be made as it relates to the usage and mixing of different license models in the oss and proprietary world.
As an example, some license models cannot be combined with others and some licenses like ācopyleftā licenses are viral (to a greater or lesser degree) and may require disclosure of source even for derivative or combined works.
In addition, there are nuances and interpretations related to words like āpropagateā or ādistributeā when modifying oss. As an example, using it on your internal corporate network may have different implications compared to embedding it into a website and having people remotely access it, which may also be viewed differently than using it in the mobile app and putting it in an app store.
Cost factors:
OSS has many cost factors, but I saved cost for last because it is tired to all the previous discussions. While the initial investment is often lower for an individual package, taking on maintenance and support for more complex oss packages will likely increase the TCO and have a negative impact on opportunity cost over time, as you will have teams that will need to continue to maintain and provide upkeep for what is likely to be a commodity for the organization – rather than focusing that same time slice on things that are of a competitive advantage.
Summary
A quick wrap up. I am a huge proponent of both the concepts and implementations of oss, however, I often see companies going down the route of oss because it is perceived to be “cheaper”. While, in some cases, that may be true, especially for smaller companies with very limited IT budget and a high tolerance for risk.
My advice is to think through the risk and exposure around the use of OSS for the company, and then compare what it would take for investments to make oss elevate to the same first class citizen as internally developed software. That’ll give you a head start on understanding the TCO and opportunity costs of using oss in the overall aggregate of your technology economy.
Finally – while I admit, I really haven’t read much of it, this looks like a great resource. https://opensource.org/faq
My hope is that you will find ways to manage the corporate risk, and still commit to engaging with, and supporting the OSS community!
As always, I am happy to learn from others, so if you have a perspective you’d like to share on oss – feel free to reach out to me and engage.
Watched #AlexanderHamilton for a second time with Bella.
After the second time (with captions) I picked up so much more of the story. #exceptionallydone
That said, couldn’t help but being emotionally stirred thinking of the idealism and the intentionality of the founding mothers and fathers to create a better world, and how quickly corruption took over in our governing class.
There is little room in my mind to question how ashamed they would be today, seeing the qualities that began to reign around self-centered, squabbling, and petty leadership; those who are corrupt, dishonest and drunk on power – feeding off of the souls of the people they were sworn to serve.
Even in the begining, when human nature began to take over our newly formed government, there appeared to be a level of constraint based on the rawness of the recent bloodshed, and some semblance of human decency.
It seems we have come such a far distance from “by the people and for the people”, I can almost understand how Jesus felt when he wept over Jerusalem: “Would that you, even you, had known on this day the things that make for peace!”
#ContemplativeAndSad
I have to admit, Iām not one to go stir-crazy. I could be completely happy sitting around the house, as long as I have access to a computer, iPad, Instruments (like a Piano or Guitar), and/or Kindle.
Iāve spent a lot of my āextraā time going back and refreshing my programming skills, and recently someone @Work reminded me of PlantUML. I had completely forgotten about it!
With PlantUML you can program pictures. If you like to draw UML/Architecture type pictures to express ideas, I highly recommend you check it out.
So here I am, on a Sunday morning, doing another thing that I enjoy: brain teasers.
So – I had this brain teaser that I was staring at and I thought: Why donāt I draw it out. Which is where PlantUML comes into the picture. Here we go. I hope you enjoy it as much as I do (@Amanda says – you are so boring).
You live on an island, you are coming back from a trip to the store, you have in your inventory a duck, some seeds and a fox. You can only carry one item across on the boat at a time. You cannot leave the duck alone with the seeds or the fox alone with the duck, as they will eat each other. How do you get the Duck, the Seeds, and the Fox over to your island?
@startuml
Participant "Left Shore" as L
Participant "Boat" as B
Participant "Right Shore" as R
Rnote over R
Duck
Seeds
Fox
Endrnote
R->L: bring over duck
Rnote over L
Duck
Endrnote
Rnote over R
Seeds
Fox
Endrnote
L->R : go back for fox
R->L: Bring over Fox
Rnote over L
Fox
Endrnote
Rnote over L
Duck
Endrnote
L->R : bring back Duck
Rnote over R
Seeds
Endrnote
Rnote over R
Duck
Endrnote
R->L : bring over seeds
Rnote over L
Fox
Seeds
endrnote
rnote over R
duck
Endrnote
L->R : Go back for duck
R->L : Bring over Duck
Rnote over L
Duck
Seeds
Fox
Endrnote
@enduml
Ignore the click bait title related to “contentious leadership”, but according to this columnist, the Army has started down a path of understanding #transformationalleadership and #servantleadership.
I have used this lesson to weigh and measure my leaders over the last two decades; to learn what behaviors I wanted to emulate, and those behaviors I wanted to filter out of my own.
Those lessons and experiences have helped to shape and mature me into a leader that strives to inspire others to the same, and here is that lesson, which appears to be at the core of what the Inc columnist is trying to capture:
Humility is not a form of weakness, it’s not about becoming a door mat for others, it’s not being unwilling to make the hard decisions.
Humility is a form of strength, it’s being self-aware in understanding the uniqueness and value of those you work around and with, and being willing to learn from them, while serving them to help reach their individual and the overall organizational potential: humility is power under control.
Be a Multiplier, not a Diminisher.
#leadershipdevelopment #leadership #humility #inspirationalleaders