Forem: Kelvin Murithi

MVC RANDOMS

Kelvin Murithi — Wed, 21 Feb 2024 10:44:08 +0000

Unedited, random as the just come to my head
Model view controller

Everything has a model even a model is a model of itself
Controller controls/works on/over a model

ModelController is trivially redundant since controller works on model anyway.(Think about adding model features without extending with a new class. Maybe using ModelExtender?)

ViewContoller- controls a view via its model. Controls a model that we just happen to know is for a view. Restricted to be controlling views only. Otherwise it is just a controller working some model.
ViewModel- same as 8* above but for Model. Only change it if you want to change what the stuff of/in a Model is (made/made up of) .

ControllerModel- model of a controller. If you want to control a controller using another controller. Like a Process controlling another process. E.g of that is when creating/instantiating a new Controller instance.

Controller controls CRUD operations for any model it is given and for
any of its functions/behaviors. Eg. If the model is

Page for displaying a table
Example:
Page is a View. PageController is a controller, PageModel is a Model
Table is a Model.
We want to View(Table). So we need the models for View and Table. We need a Controller for view,page and table. Controller instance is from ControllerModel.

//new Controller(Object extends Model)
aTable new Table()
aView new View()
aPage new Page()
viewController new Controller(View)
pageController new Controller(Page)
tableController new Controller(Table)

//Now we want to put the Table on the Page and View the Page
aPage.put(Table)
aView.put(Page)
aView.do()//show the result of the verb "view" so that Viewer can do
//OR Viewer.do(View) if we have a new View passed in from some external scope or if Viewer can also do other external doable things like spin() for example. Viewer.do(Spin) which calls Spin.do() equivalent to Spin.do(selfReference)
Viewer.view(Page). Viewer has View that holds objective form of view() eg. She view Page, results in a View with the Page being viewed.
//If we call view(Table), it implies create a Page and Page.put(Table) then View.put(Table), aView.show() internally

Notice how all of these models going into the controller are from verbs. They are things you can do. But since controller only needs a model, it means we can give it something that is not from a verb E.g Person. You can't "Person" around. It is not an activity. But we can still pass it to the controller. So we might think of "model" as a verb or also think that we are controlling the set of all verbs applicable to/on/from the provided model. So Controller controls CRUD operations for any model it is given and for
any of its functions/behaviors. Eg. If the model is for Person, it controls CRUD(construct/destruct/update/Access) [CreateAccess(rwx)Destroy] or if the Person has some jump function, we spin off a
Jump aJump= new Person.jump(aBarrier){//returns Jump.initialize()} jumpController= new Controller(Jump);

5W- Who,what,where,when,why... Recursive resolution of semantic meaning

Kelvin Murithi — Sun, 04 Feb 2024 19:12:37 +0000

Problem identification process
Describe the ideal, describe the current status quo/state of affairs and describe the deviation from the ideal. These deviations form the basis of the problem- the what. Describe the identifiable and unidentifiable causes of the deviations as the reasons- the why

Problem solution process
involves identifying causes of the deviations and prescribing mitigative or corrective measures

What, is an interrogative nominative indicator. Asks the recipient of the message to replace
the word "What" with a representation of something pertaining to part of the sentence that follows.
Why asks them to replace the word "why" with a description of the desired resultant state which is intended to be caused by the action; or the prior state that came before which resulted in the action.

Where-
Who-
When-
These three apply context to the why. Eg. What because why. The what could be a verb or a noun. In the case where the What is a verb: eg. Jump, and the why is the where, you jump because of the position. If the why (reason) is who you are supposed to jump if they are encountered(maybe a game) or the why is a when, you are supposed to jump at a certain time... and so on and so forth.

https://www.youtube.com/watch?v=E-pfSLHHojU

A recursive reasoning resolving/resolution step involves a (set of one or more) what and (set of one or more) why then to recurse one level deeper, whatever was the why gets promoted to the "what", and the subsequent part of the sentence becomes the why... repeat over and over to the end until the whole sentence is fully resolved.

Definitions for design domain

Kelvin Murithi — Sat, 20 Jan 2024 10:29:14 +0000

Nominal-objects=same class but differ by the value held in/by a set of variables. Same actual set of variables they are made up of. Only some value differs
Structural speaks for itself.
Prefixes
"...-or"- takes ownership of the decision to cause occurrence (ties to logic)
"...-ion"- instance of an occurrence observed/attributable to an "...-or" as the cause. Connection between the "...-or" and an instance or several of what it does/causes/its resultants/outcomes.

Captures the nominally differentiable state of an "...-or" to a nominally differentiable observed state of its resultant/outcome.
eg. Account(or)a.k.a accountant- who does the action named account, resulting in an outcome as an object called an account which represents a particular observed instance of a certain set of state values for the variables that are the defined properties of what the action causes to happen to some defined state.

All "...-ions" cause changes in some predefined/predetermined state.`

Digital Forensics; hiding process ownership

Kelvin Murithi — Wed, 17 Jan 2024 14:14:11 +0000

so a daemon can be hacked, forked, terminated and leave the orphaned processes showing up as init processes and this could prove hard for digital forensics?

ChatGPT

While it is technically possible for a daemon to be compromised, resulting in the forking and termination of the daemon process, which leaves orphaned processes showing up as init processes, it is not a common scenario. Proper security measures and best practices are typically implemented to minimize the likelihood of such compromises.

However, in the event of a compromised daemon and the presence of orphaned processes showing up as init processes, it can indeed pose challenges for digital forensics. The orphaned processes may not have a direct association with the original daemon process, making it harder to trace their origins and determine the root cause of the compromise.

Digital forensics investigations often involve examining process information, logs, network connections, and other artifacts to reconstruct the sequence of events and identify the source of an incident. In cases where the compromised daemon has left orphaned processes that appear as init processes, additional analysis and techniques may be required to establish the connection between the compromised daemon and the orphaned processes.

It's important to note that digital forensics is a complex and evolving field, and forensic analysts employ various tools and methodologies to investigate such scenarios. While it can be challenging, with the right expertise and techniques, it is possible to uncover evidence and gain insights into compromised systems.
https://systemized.hashnode.dev/forensics-digital

How My shmancy overthinking self-precludes (me) from online work. Commentary on underwhelming job listings.

Kelvin Murithi — Thu, 31 Mar 2022 13:17:07 +0000

https://medium.com/p/3c96b019a816