οΌ»>_οΌ½
~$ sudo -i -u ${USER} whoami --for-real -- 1> >(tee -a tl.dr) 2>/dev/null
~$ cat tl.dr
Hi, I'm Lucas, a Philomaph by heart and self-proclaimed Polymath, currently in a full-time learning journey towards becoming a modern Renaissance man.
In my spare time, I'm a professional "Jack of All Trades/Master of Some" (Ph.D. from Google Not-University).
ππ» More aboute me β²
~$ whoami
I'm Lucas, a Cloud DevSecOps Evangelist and Full Stack Developer. I love puzzles, patterns, semantic structures and adding "by-design" and "as-code" suffixes to everything.
π¨ Well, that covers a lot, so let me clear up some questions you might be inclined to ask: π¬
What is your stackβ In what language do you codeβ
- The most proper and honest answer to is: "that's not up to me!"
- It is the project that defines the stack and, needless to say, the language.
Contradicting islike using a hammer to put on your shoes
- is contradicting reason itself. - The context defines the stack, not otherwise - our goal is to choose the right tool for the job.
- With that being said, by "full stack" I mean that I am an "end-to-end" developer, language-agnostic
- For a technology to arise, it has both to start and to end - it has to be released into the wild.
The only way to accomplish this by relentlessly pursuing curiosity, through a endless journey of continuous learning and evolvement. - Plainly put: I develop using the most appropriate tools for the given project, learning them on demand. More than often, also relearning them on demand.
Ok, what about the Cloud DevSecOps? Is that even a job? Is this even a wordβ
- Until someone comes up with a better name, it is a job, because someone has to do it.
- From ideation to production, the IT lifecycle is composed by a myriad of small pieces and events that, once pulled together, exists as a true living organism. For lack of a better term, I call "DevSecOps Evangelist" the one who orchestrates these processes and build a whole culture around them - the one who "spread the word".
My work is to orchestrate how the development will play out, making sure that the engines are in sync, while also placing myself on the remaining empty seats. Speaking of which, here is where I play my role as a full-stack developer. - And, yes, there is a "Sec" in between. Rather than a tendency, shifting left on security is already a vital part within the technology industry.
- An Agile Environment by itself is no longer enough to achieve excellency. To take full advantage of the agility and responsiveness it provides, the development, security and operations teams must march together throughout the entire IT lifecycle. Nowadays, this means fully integrating InfoSec into the processes and, furthermore, establishing OpSec best-practices among everyone's playbook.
- Lastly, regarding the "Cloud" part, well, those who stay grounded soon shall be carried away be the wave.
- Nonetheless, I'll list below some tools-of-choice I'm currently using or have used along the way, after all, for you to find me, I still have to spread some keywords around here.
No way! How do you even find the time to learn all these stuff, apply them and still keep up to dateβ
- Again, one must must be relentlessly curious.
- However, there is indeed a trick to effectively get all these things done:
I enjoy coding, but just once. By wrapping my code around functional modules and leveraging on meta-programming, I spend less time with things I've already done and invest that time on learning. - Inevitably it comes to a point where most of the coding is actually refactoring. This is the sweet spot, inasmuch as each code refactoring emerges from discovering a better way to reach the same result.
- Summing up: learning > refactoring > coding/implementing.