[{"data":1,"prerenderedAt":434},["ShallowReactive",2],{"fragments-latest":3,"systems-latest":234},[4,81],{"id":5,"title":6,"slug":5,"publishedAt":7,"excerpt":8,"epigraph":9,"epigraphAuthor":9,"body":10,"bodyMarkdown":70,"tags":71,"seo":77},"on-the-desire-to-share-with-the-world","On the Desire to Share with the World",["Date","2026-02-22T00:00:00.000Z"],"I really couldn't keep a journal until a certain age. Not at all. I didn't understand what it was, why it was needed, what it even meant.",null,[11,22,30,38,46,54,62],{"_key":12,"_type":13,"style":14,"markDefs":15,"children":16},"k0","block","normal",[],[17],{"_key":18,"_type":19,"text":20,"marks":21},"k1","span","I really couldn't keep a journal until a certain age. Not at all. I didn't understand what it was, why it was needed, what it even meant. Some kind of nonsense - writing down your own thoughts.",[],{"_key":23,"_type":13,"style":14,"markDefs":24,"children":25},"k2",[],[26],{"_key":27,"_type":19,"text":28,"marks":29},"k3","Then I just started writing. Exactly the thing I thought was nonsense - that's what I began to do: writing down everything that appeared in my head. At first, these were just short notes about my mood, about how I felt, about plans. A short reflection. Attempts to understand, to comprehend, and to become more aware of myself. It worked great.",[],{"_key":31,"_type":13,"style":14,"markDefs":32,"children":33},"k4",[],[34],{"_key":35,"_type":19,"text":36,"marks":37},"k5","Sometimes the desire to write would disappear, then reappear. By the way, before journaling, for some time I was also writing poetry. Same thing there - sometimes I wrote effortlessly, sometimes I didn't write at all and didn't understand what it even was.",[],{"_key":39,"_type":13,"style":14,"markDefs":40,"children":41},"k6",[],[42],{"_key":43,"_type":19,"text":44,"marks":45},"k7","I came across my article about weakness. I think that's the only \"something\" of mine on a specific topic. A few collected theses and thoughts about one thing.",[],{"_key":47,"_type":13,"style":14,"markDefs":48,"children":49},"k8",[],[50],{"_key":51,"_type":19,"text":52,"marks":53},"k9","I read it, saw that people had even left likes on it, that someone had highlighted fragments from it. It felt nice. And I thought that right now I have nothing to say again. But it turns out that I do - I am writing, after all.",[],{"_key":55,"_type":13,"style":14,"markDefs":56,"children":57},"k10",[],[58],{"_key":59,"_type":19,"text":60,"marks":61},"k11","It seemed interesting to me, this very phenomenon - that sometimes I have something to say, and sometimes absolutely nothing. Very often my head is just empty. I don't see it as either bad or good. Or maybe it's both bad and good at the same time. It sounds paradoxical, but that only makes it more interesting.",[],{"_key":63,"_type":13,"style":14,"markDefs":64,"children":65},"k12",[],[66],{"_key":67,"_type":19,"text":68,"marks":69},"k13","I don't have a conclusion about why sometimes I want to share and sometimes I don't. I often say: \"I'll do it if I feel like it. If there's desire and opportunity - I'll do it. If not - I won't.\" Most likely it's the same here. Not a final conclusion, but already quite a solid hypothesis. And where does the mood come from, or why does it disappear? That's a good question. That's just how it turned out in this world.",[],"\nI really couldn't keep a journal until a certain age. Not at all. I didn't understand what it was, why it was needed, what it even meant. Some kind of nonsense - writing down your own thoughts.\n\nThen I just started writing. Exactly the thing I thought was nonsense - that's what I began to do: writing down everything that appeared in my head. At first, these were just short notes about my mood, about how I felt, about plans. A short reflection. Attempts to understand, to comprehend, and to become more aware of myself. It worked great.\n\nSometimes the desire to write would disappear, then reappear. By the way, before journaling, for some time I was also writing poetry. Same thing there - sometimes I wrote effortlessly, sometimes I didn't write at all and didn't understand what it even was.\n\nI came across my article about weakness. I think that's the only \"something\" of mine on a specific topic. A few collected theses and thoughts about one thing.\n\nI read it, saw that people had even left likes on it, that someone had highlighted fragments from it. It felt nice. And I thought that right now I have nothing to say again. But it turns out that I do - I am writing, after all.\n\nIt seemed interesting to me, this very phenomenon - that sometimes I have something to say, and sometimes absolutely nothing. Very often my head is just empty. I don't see it as either bad or good. Or maybe it's both bad and good at the same time. It sounds paradoxical, but that only makes it more interesting.\n\nI don't have a conclusion about why sometimes I want to share and sometimes I don't. I often say: \"I'll do it if I feel like it. If there's desire and opportunity - I'll do it. If not - I won't.\" Most likely it's the same here. Not a final conclusion, but already quite a solid hypothesis. And where does the mood come from, or why does it disappear? That's a good question. That's just how it turned out in this world.\n",[72,73,74,75,76],"philosophy","reflections","journaling","creativity","reflection",{"title":78,"description":79,"ogImage":9,"noIndex":80},"On the Desire to Share with the World — ilsrbn","A personal reflection on writing, journaling, and the impulse to share thought in public.",false,{"id":82,"title":83,"slug":82,"publishedAt":84,"excerpt":85,"epigraph":9,"epigraphAuthor":9,"body":86,"bodyMarkdown":226,"tags":227,"seo":231},"reflections-on-weakness","Reflections on Weakness",["Date","2023-12-01T00:00:00.000Z"],"What can one ponder when speaking about weakness? What is it? How does one live with it, and is it even worth considering?",[87,93,100,106,112,118,124,130,138,146,154,162,170,178,186,194,202,210,218],{"_key":12,"_type":13,"style":14,"markDefs":88,"children":89},[],[90],{"_key":18,"_type":19,"text":91,"marks":92},"*What can one ponder when speaking about weakness? What is it? How does one live with it, and is it even worth considering?*",[],{"_key":23,"_type":13,"style":94,"markDefs":95,"children":96},"h2",[],[97],{"_key":27,"_type":19,"text":98,"marks":99},"Definition, Classification of Weakness",[],{"_key":31,"_type":13,"style":14,"markDefs":101,"children":102},[],[103],{"_key":35,"_type":19,"text":104,"marks":105},"In the concept of weakness, I include not only physical weakness but also the **weakness of my spirit and will**. It's the inability to resist temptations and bad habits. It's also the inability to compel oneself to do what needs to be done. The incapacity to follow one's plan is part of it, as well as emotional weakness: the desire to manipulate, dominate, susceptibility to irritation, provocations, and the desire to show off.",[],{"_key":39,"_type":13,"style":14,"markDefs":107,"children":108},[],[109],{"_key":43,"_type":19,"text":110,"marks":111},"In addition to the already mentioned weaknesses, physical and spiritual, I also consider **intellectual weakness**. For me, this primarily entails a lack of quick-wittedness, logic, and financial literacy.",[],{"_key":47,"_type":13,"style":14,"markDefs":113,"children":114},[],[115],{"_key":51,"_type":19,"text":116,"marks":117},"To a large extent, certain **human convictions** can also be included here. For example, the inclination to make enemies rather than friends. Or the conviction that everyone around is lying and wishing you harm. The belief that someone has some power over someone.",[],{"_key":55,"_type":13,"style":94,"markDefs":119,"children":120},[],[121],{"_key":59,"_type":19,"text":122,"marks":123},"Motivation",[],{"_key":63,"_type":13,"style":14,"markDefs":125,"children":126},[],[127],{"_key":67,"_type":19,"text":128,"marks":129},"I read about weakness along the lines of:",[],{"_key":131,"_type":13,"style":14,"markDefs":132,"children":133},"k14",[],[134],{"_key":135,"_type":19,"text":136,"marks":137},"k15","> I am weak. I acknowledge that I am weak. Weak in body, spirit, and mind. I agree with this. It's the truth. > > I acknowledge it, I accept it, but I do not agree to it. I will fight my weakness and become stronger. > > Rough interpretation of words from the book *Discipline Equals Freedom* by Jocko Willink. Chapter on Weakness.",[],{"_key":139,"_type":13,"style":14,"markDefs":140,"children":141},"k16",[],[142],{"_key":143,"_type":19,"text":144,"marks":145},"k17","I like these words. I agree with them.",[],{"_key":147,"_type":13,"style":14,"markDefs":148,"children":149},"k18",[],[150],{"_key":151,"_type":19,"text":152,"marks":153},"k19","**But agreeing with them is not enough.**",[],{"_key":155,"_type":13,"style":94,"markDefs":156,"children":157},"k20",[],[158],{"_key":159,"_type":19,"text":160,"marks":161},"k21","The Importance of Actions",[],{"_key":163,"_type":13,"style":14,"markDefs":164,"children":165},"k22",[],[166],{"_key":167,"_type":19,"text":168,"marks":169},"k23","The main idea of this thought is **actions**. Struggling with weaknesses is a constant **effort** that needs to be **executed**, not just agreed with in theory. You need to **do**.",[],{"_key":171,"_type":13,"style":14,"markDefs":172,"children":173},"k24",[],[174],{"_key":175,"_type":19,"text":176,"marks":177},"k25","I'm not a supporter of working on oneself 25 hours a day and 8 days a week. Super productivity doesn't appeal to me at all.",[],{"_key":179,"_type":13,"style":14,"markDefs":180,"children":181},"k26",[],[182],{"_key":183,"_type":19,"text":184,"marks":185},"k27","Nevertheless, working on oneself is necessary. If development doesn't come naturally, for example through a hobby or by going deeper into something meaningful, then it needs to be done consciously.",[],{"_key":187,"_type":13,"style":14,"markDefs":188,"children":189},"k28",[],[190],{"_key":191,"_type":19,"text":192,"marks":193},"k29","For conscious work on weaknesses, you first need to identify them.",[],{"_key":195,"_type":13,"style":14,"markDefs":196,"children":197},"k30",[],[198],{"_key":199,"_type":19,"text":200,"marks":201},"k31","Next, filter out only what hinders you personally, not what might simply be disliked by someone around you or isn't accepted socially.",[],{"_key":203,"_type":13,"style":14,"markDefs":204,"children":205},"k32",[],[206],{"_key":207,"_type":19,"text":208,"marks":209},"k33","Once they are identified, prioritize them. It should be clear what needs to be eradicated first and what can wait.",[],{"_key":211,"_type":13,"style":14,"markDefs":212,"children":213},"k34",[],[214],{"_key":215,"_type":19,"text":216,"marks":217},"k35","And after that, when we clearly know our weaknesses, all that's left is to take control of ourselves. We work on weaknesses consciously, being aware of it and not hoping that just because we've made a plan, it will execute itself.",[],{"_key":219,"_type":13,"style":14,"markDefs":220,"children":221},"k36",[],[222],{"_key":223,"_type":19,"text":224,"marks":225},"k37","It's important to monitor oneself, one's thoughts, and actions. Record successes when we manage to work on a weakness, when we win once. It's equally important to make interim assessments and recall situations when we succumbed to weaknesses.",[],"\n*What can one ponder when speaking about weakness? What is it? How does one live with it, and is it even worth considering?*\n\n## Definition, Classification of Weakness\n\nIn the concept of weakness, I include not only physical weakness but also the **weakness of my spirit and will**. It's the inability to resist temptations and bad habits. It's also the inability to compel oneself to do what needs to be done. The incapacity to follow one's plan is part of it, as well as emotional weakness: the desire to manipulate, dominate, susceptibility to irritation, provocations, and the desire to show off.\n\nIn addition to the already mentioned weaknesses, physical and spiritual, I also consider **intellectual weakness**. For me, this primarily entails a lack of quick-wittedness, logic, and financial literacy.\n\nTo a large extent, certain **human convictions** can also be included here. For example, the inclination to make enemies rather than friends. Or the conviction that everyone around is lying and wishing you harm. The belief that someone has some power over someone.\n\n## Motivation\n\nI read about weakness along the lines of:\n\n> I am weak. I acknowledge that I am weak. Weak in body, spirit, and mind. I agree with this. It's the truth.\n>\n> I acknowledge it, I accept it, but I do not agree to it. I will fight my weakness and become stronger.\n>\n> Rough interpretation of words from the book *Discipline Equals Freedom* by Jocko Willink. Chapter on Weakness.\n\nI like these words. I agree with them.\n\n**But agreeing with them is not enough.**\n\n## The Importance of Actions\n\nThe main idea of this thought is **actions**. Struggling with weaknesses is a constant **effort** that needs to be **executed**, not just agreed with in theory. You need to **do**.\n\nI'm not a supporter of working on oneself 25 hours a day and 8 days a week. Super productivity doesn't appeal to me at all.\n\nNevertheless, working on oneself is necessary. If development doesn't come naturally, for example through a hobby or by going deeper into something meaningful, then it needs to be done consciously.\n\nFor conscious work on weaknesses, you first need to identify them.\n\nNext, filter out only what hinders you personally, not what might simply be disliked by someone around you or isn't accepted socially.\n\nOnce they are identified, prioritize them. It should be clear what needs to be eradicated first and what can wait.\n\nAnd after that, when we clearly know our weaknesses, all that's left is to take control of ourselves. We work on weaknesses consciously, being aware of it and not hoping that just because we've made a plan, it will execute itself.\n\nIt's important to monitor oneself, one's thoughts, and actions. Record successes when we manage to work on a weakness, when we win once. It's equally important to make interim assessments and recall situations when we succumbed to weaknesses.\n",[72,228,229,73,230],"will","weakness","self-improvement",{"title":232,"description":233,"ogImage":9,"noIndex":80},"Reflections on Weakness — ilsrbn","A reflection on physical, spiritual, and intellectual weakness, and on the need to confront it through action.",[235,336],{"id":236,"title":237,"slug":236,"company":238,"role":239,"period":240,"description":241,"isNda":242,"tags":243,"metrics":249,"highlights":253,"body":257,"bodyMarkdown":332,"order":278,"seo":333},"sharkscode-frontend-leadership","Frontend Leadership & Delivery","Sharkscode","Frontend Team Lead","Aug 2024 - Present","Leading frontend delivery, team growth, and execution quality across active client work in a fast-moving environment.",true,[244,245,246,247,248],"leadership","frontend","delivery","mentoring","process",[250,251,252],"Team leadership across active frontend delivery","Mentoring developers and raising execution quality","Stronger coordination between technical direction and delivery",[254,255,256],"Built a healthier balance between hands-on engineering and team leadership","Helped developers grow through day-to-day review, guidance, and support","Improved delivery predictability by making priorities and ownership clearer",[258,264,270,276,284,290,296,302,308,314,320,326],{"_key":12,"_type":13,"style":94,"markDefs":259,"children":260},[],[261],{"_key":18,"_type":19,"text":262,"marks":263},"Context",[],{"_key":23,"_type":13,"style":14,"markDefs":265,"children":266},[],[267],{"_key":27,"_type":19,"text":268,"marks":269},"This role sits at the intersection of leadership and hands-on engineering. The work is not limited to writing code. It includes shaping how the frontend team delivers, how technical decisions get made, and how developers grow over time.",[],{"_key":31,"_type":13,"style":94,"markDefs":271,"children":272},[],[273],{"_key":35,"_type":19,"text":274,"marks":275},"Focus",[],{"_key":39,"_type":13,"style":14,"listItem":277,"level":278,"markDefs":279,"children":280},"bullet",1,[],[281],{"_key":43,"_type":19,"text":282,"marks":283},"Clarifying priorities and delivery expectations",[],{"_key":47,"_type":13,"style":14,"listItem":277,"level":278,"markDefs":285,"children":286},[],[287],{"_key":51,"_type":19,"text":288,"marks":289},"Supporting the team through reviews, direction, and mentoring",[],{"_key":55,"_type":13,"style":14,"listItem":277,"level":278,"markDefs":291,"children":292},[],[293],{"_key":59,"_type":19,"text":294,"marks":295},"Keeping implementation quality high without slowing delivery down",[],{"_key":63,"_type":13,"style":14,"listItem":277,"level":278,"markDefs":297,"children":298},[],[299],{"_key":67,"_type":19,"text":300,"marks":301},"Acting as the bridge between execution, architecture, and day-to-day team needs",[],{"_key":131,"_type":13,"style":94,"markDefs":303,"children":304},[],[305],{"_key":135,"_type":19,"text":306,"marks":307},"What This Work Looks Like",[],{"_key":139,"_type":13,"style":14,"markDefs":309,"children":310},[],[311],{"_key":143,"_type":19,"text":312,"marks":313},"In practice, this means helping the team move with less ambiguity. Some tasks are managerial, some are technical, and many sit in between: deciding where standards need to be enforced, where speed matters more, and where a developer needs guidance instead of just feedback.",[],{"_key":147,"_type":13,"style":14,"markDefs":315,"children":316},[],[317],{"_key":151,"_type":19,"text":318,"marks":319},"The strongest part of this role is not a single system or metric. It is the ability to keep delivery moving while raising the quality bar for the people doing the work.",[],{"_key":155,"_type":13,"style":94,"markDefs":321,"children":322},[],[323],{"_key":159,"_type":19,"text":324,"marks":325},"Constraints",[],{"_key":163,"_type":13,"style":14,"markDefs":327,"children":328},[],[329],{"_key":167,"_type":19,"text":330,"marks":331},"Client and project details are abstracted. The public version of this case focuses on the leadership shape of the work rather than implementation specifics.",[],"\n## Context\n\nThis role sits at the intersection of leadership and hands-on engineering. The work is not limited to writing code. It includes shaping how the frontend team delivers, how technical decisions get made, and how developers grow over time.\n\n## Focus\n\n- Clarifying priorities and delivery expectations\n- Supporting the team through reviews, direction, and mentoring\n- Keeping implementation quality high without slowing delivery down\n- Acting as the bridge between execution, architecture, and day-to-day team needs\n\n## What This Work Looks Like\n\nIn practice, this means helping the team move with less ambiguity. Some tasks are managerial, some are technical, and many sit in between: deciding where standards need to be enforced, where speed matters more, and where a developer needs guidance instead of just feedback.\n\nThe strongest part of this role is not a single system or metric. It is the ability to keep delivery moving while raising the quality bar for the people doing the work.\n\n## Constraints\n\nClient and project details are abstracted. The public version of this case focuses on the leadership shape of the work rather than implementation specifics.\n",{"title":334,"description":335,"ogImage":9,"noIndex":80},"Frontend Leadership & Delivery — ilsrbn","Frontend team leadership, delivery ownership, and mentoring work at Sharkscode.",{"id":337,"title":338,"slug":337,"company":238,"role":239,"period":240,"description":339,"isNda":242,"tags":340,"metrics":345,"highlights":349,"body":353,"bodyMarkdown":429,"order":430,"seo":431},"sharkscode-frontend-architecture","Frontend Architecture & Technical Direction","Owning frontend architecture decisions, technical direction, and long-term maintainability across production work.",[341,245,342,343,344],"architecture","vue","nuxt","typescript",[346,347,348],"Architecture decisions aligned with delivery realities","Better maintainability across evolving frontend codebases","Technical direction shaped with production constraints in mind",[350,351,352],"Balanced delivery pressure with long-term code health","Chose technical directions that teams could realistically sustain","Stayed hands-on enough to keep architectural decisions grounded",[354,359,365,370,376,382,388,394,400,406,412,418,423],{"_key":12,"_type":13,"style":94,"markDefs":355,"children":356},[],[357],{"_key":18,"_type":19,"text":262,"marks":358},[],{"_key":23,"_type":13,"style":14,"markDefs":360,"children":361},[],[362],{"_key":27,"_type":19,"text":363,"marks":364},"Architecture work here is practical, not ornamental. The point is not to create ideal diagrams. The point is to make decisions that survive production pressure, team constraints, and real delivery timelines.",[],{"_key":31,"_type":13,"style":94,"markDefs":366,"children":367},[],[368],{"_key":35,"_type":19,"text":274,"marks":369},[],{"_key":39,"_type":13,"style":14,"listItem":277,"level":278,"markDefs":371,"children":372},[],[373],{"_key":43,"_type":19,"text":374,"marks":375},"Defining frontend direction without over-engineering",[],{"_key":47,"_type":13,"style":14,"listItem":277,"level":278,"markDefs":377,"children":378},[],[379],{"_key":51,"_type":19,"text":380,"marks":381},"Keeping systems maintainable as scope evolves",[],{"_key":55,"_type":13,"style":14,"listItem":277,"level":278,"markDefs":383,"children":384},[],[385],{"_key":59,"_type":19,"text":386,"marks":387},"Making architectural choices the team can actually support",[],{"_key":63,"_type":13,"style":14,"listItem":277,"level":278,"markDefs":389,"children":390},[],[391],{"_key":67,"_type":19,"text":392,"marks":393},"Preserving development speed while avoiding fragile solutions",[],{"_key":131,"_type":13,"style":94,"markDefs":395,"children":396},[],[397],{"_key":135,"_type":19,"text":398,"marks":399},"Working Style",[],{"_key":139,"_type":13,"style":14,"markDefs":401,"children":402},[],[403],{"_key":143,"_type":19,"text":404,"marks":405},"This kind of architecture work depends on judgment. Every decision trades off speed, clarity, and future cost. The role requires staying close enough to implementation to understand the codebase honestly, while still thinking one or two layers above the immediate task.",[],{"_key":147,"_type":13,"style":94,"markDefs":407,"children":408},[],[409],{"_key":151,"_type":19,"text":410,"marks":411},"Why It Matters",[],{"_key":155,"_type":13,"style":14,"markDefs":413,"children":414},[],[415],{"_key":159,"_type":19,"text":416,"marks":417},"In many teams, architecture becomes disconnected from delivery. Here, the value comes from keeping them tied together. Technical direction is useful only when it helps the team build better, faster, and with less accidental complexity.",[],{"_key":163,"_type":13,"style":94,"markDefs":419,"children":420},[],[421],{"_key":167,"_type":19,"text":324,"marks":422},[],{"_key":171,"_type":13,"style":14,"markDefs":424,"children":425},[],[426],{"_key":175,"_type":19,"text":427,"marks":428},"Specific clients, products, and implementation details are withheld. The public version is intentionally abstracted while preserving the real shape of the work.",[],"\n## Context\n\nArchitecture work here is practical, not ornamental. The point is not to create ideal diagrams. The point is to make decisions that survive production pressure, team constraints, and real delivery timelines.\n\n## Focus\n\n- Defining frontend direction without over-engineering\n- Keeping systems maintainable as scope evolves\n- Making architectural choices the team can actually support\n- Preserving development speed while avoiding fragile solutions\n\n## Working Style\n\nThis kind of architecture work depends on judgment. Every decision trades off speed, clarity, and future cost. The role requires staying close enough to implementation to understand the codebase honestly, while still thinking one or two layers above the immediate task.\n\n## Why It Matters\n\nIn many teams, architecture becomes disconnected from delivery. Here, the value comes from keeping them tied together. Technical direction is useful only when it helps the team build better, faster, and with less accidental complexity.\n\n## Constraints\n\nSpecific clients, products, and implementation details are withheld. The public version is intentionally abstracted while preserving the real shape of the work.\n",2,{"title":432,"description":433,"ogImage":9,"noIndex":80},"Frontend Architecture & Technical Direction — ilsrbn","Architecture decisions, technical direction, and maintainability work at Sharkscode.",1775381662659]