Hello Mishamigos, in a week we will be the last day of October. The day where ghouls and demons will sprout and throw one more spell at us humble coding people. The day where until the last second you will look at your inbox petrified waiting for the next jump scare. As you guessed, in case you were oblivious to the post title, tomorrow is the first day of the last week of Hacktoberfest, 2018 edition.
Category: Stuff
Help (verb) make it easier or possible for (someone) to do something by offering them one’s services or resources
Today we will talk about help, more precisely helping people who refuse help. However, before I delve any further, you should have a quick read at the Agile Manifesto.
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
As I go through the (true) stories I am about to tell, it will be up to you to figure which principles tie in the way I tackle today’s topic. That way we both put the work in one of my posts. I’ll do the same for yours if requested. The stories will be told in chronological order so you may even notice changes in reactions from on end. Talking about ends…
Food for thought while having food and thoughts
I just had lunch having some Char Siu pork with ginger and wine sauce along with some brown rice while staying in Glasgow for work matters. As I finished my food and moved back to my pint of Cobra I started thinking about the original G, God.
I have been reading a lot over the the few months. Mostly books revolving around programming principles and patterns as I figured they would help improve myself. Most recently I read “The clean coder” from Robert “Uncle Bob” Martin. It is basically a compilation of his life experiences and lessons he learned from them. And there is a lot of things to take away from that book. It is a very hard book to put down once started but you should be the judge of that.
Vectors of trust: Simplify validation for secure transactions
Posted in Stuff
A few weeks ago, the Internet Engineering Task Force (IETF) introduced a new Request For Comments (RFC) document about Vectors of Trust, the RFC8485. It is the work of Leif Johansson from the Swedish University Network. The original draft went through 15 iterations since 2015 and Justin Richer from Bespoke Engineering edited the current version.
Enough with the credits, what issue the Vectors of trust document is trying to solve? It seems that the purpose is to bring an effective method to measure the trust of credentials for digital transactions. The two main approaches at the moment are known as Level of Assurance (LoA) and Attribute-Based Access Control (ABAC). Let me try to introduce these to you first.