Embarking on a new journey through Golang to warp my mind around the language and bring my thought to contorsions. The promise of a new language is always exciting given Sapir-Whorf hypothesis. Your language shapes how you see and think about the world as you are in the world. The new ways of thinking about concurrency is what I am excited about. Python is hamstringed by the global interpreter lock (GIL) which prevents it from being multithreaded in the sense of being able to use multiple cores in a multi-core processor. I found this super frustrating for some reason to implement concurrency in Python that I might find how Golang treats concurrency easier to understand. But to be honest it was a minor trifle because I never was performant in the language of Python merely playing with toy examples and toy problems without having any impact. Nevertheless Golang will bend my mind and morph it into understanding the system underneath the hood without hiding anything in its glory and explicitness. This should be a good change because Python hid a lot of magic behind the scenes and it was hard to grok what was going on behind the veil. I'll likely produce nothing and it will be an exercise of futility but my goal in learning a language is to exercise my brain in a way to dust off the old synapses and peruse a code book thoroughly. My brain is badly damaged from multiple head injuries and a deluge of psychotropics that were deleterious to the brain. I am trying to rehab my brain with exercise, diet, sleep, and learning. I will not return to 100 percent of my capacity however limited that initial capacity was but I will be better than my previous self that was in a drug addled state of mind playing with needles like a complete moron shooting dry wall thinking it was dope. No my dear reader I aspire to more despite the Software as a Service apocalypse with the coming AI capabilities. The computer will program itself according to specifications given to it in a prompt. You just have to know what you want to build and properly convey this information to the AI Agent to code in an ensemble. Nautrally you would have to know a little about time and space complexity to have more efficient code seeing how the AI Agent may diverge into less efficiency. The problem though is lacking the creativity to think up an application with a wide use value that can harness the network effect and be taken up rapidly by users. There seems to have been every permutation and alternative for everything that has already been thought up already in applications and the difference now is implementation in newer languages to improve latency making the application run smooth and seamless. There seems to be another category of software of software for software creating tools for creatives to create stuff. This is the idea of creating widgits that create widgits which is a good business model. Perhaps I will clone a previous app and approximate its functionality in Golang with my own code. This will be a herculean task depending on the app. Likely I'll sputter out and return to Python because Python is the lingua franca of machine learning and deep neural networks and Golang is more suitable for speedy backend systems that deliver data in a pipeline or the microservice jazz. Apologies my dear reader for I am a little simp.
Knowing how to pivot is important in OSINT it seems and to go from a wide scope to a narrower scope. Pivot charts are useful to collect information of results from selectors, each pivot being a resultant node of information. Going from a wide search to a narrower search is like the goldilock's effect, a little too wide and you lose focus but too focused you can lose out on other wider details. All sources state that methdology trumps tools and the focus early on in an OSINT career is to develop your methodology like knowing how to pivot and knowing the intelligence cycle. Being nimble and flexible in your search queries is important to hone your searches using Google as a primary tool to locate information. You just have to Google it. You Google to find tools like websites that facilitate investigations. It seems that Rae Baker, the author of Deep Dive into OSINT, is adept at using Google to serve her needs though she stresses the importance of methodology. Cynthia Hetherington of ...
Comments
Post a Comment