Internship number two.

*walks downstairs to get a coffee*
*CTO (my guider) walks in*
CTO: (dead serious face) "linuxxx (not using my first name :P), come with me please"
*walks along to his office, starting to get reallly fucking nervous*
*CTO and me walk into his office, he sits down and looks at me very serious*
*I'm slightly shaking, nervous, sweating*
CTO: "So."
*oh yes here it is its gonna come I did something wrong fuck fml 😫😥😨😩*
CTO: "So you know quite some stiff around security/privacy. Could you tell me some stuff about why I'd want to use VPN and recommend me some good providers? 😀"
😅
*nearly falls onto the ground from relief*

I explained him some stuff and sent him a list of good providers 😀

Anybody else sometimes do not like being a team lead?

I am the senior most person in my team (in fact took interviews of the rest of them). While I love the work and the team, I sometimes feel that I do not get to code that much. I am mostly assigning work, or helping others. Even if I get in the zone, there is always someone who needs some assistance or some meeting, which breaks the flow. Also the tension about non technical stuff like salary increments, giving feedback and assigning backups. I do love it mostly, but my ass is nearly always on fire. The team loves me though. I am still young, took this responsibility because the owner trusted me with this (he has no complaints). Thoughts ?

story of a release
v2.1.0 major changes went live : new features, bug fixes, optimisations. also included releases for 2 associated libraries
release process tasks:
- do code
- update test cases
- test sample app
- test on another sample app
- get code reviewed and approved by senior ( who takes his own sweet time to review and never approves on first try)
- get code reviewed again
- merge to develop after 20 mins( coz CICD pipeline won't finish and allow merging before that)
- merge to master after 20 mins( coz CICD again)
- realise that you forgot to update dates in markdown files as you thought the release will be on 10th sept and release is happennig on 12th sept coz of sweet senior's code fucking/reviewing time
- again raise a branch to develop
- again get it a review approval by sr (who hopefully gives a merge approval in less time now)
- again get it merged to develop after waiting for 20 mins
- again get it merged to master after waiting for 20 mins
- create a clean build aar file
- publish to sonatype staging
- publish to sonatype release
- wait for 30 mins to show while having your brain fucked with tension
- create a release doc with all the changes
- update the documentation on a wyswig based crappy docs website
- send a message to slack channels
- done

===========

why am i telling you this? coz i just found a bug in a code that i shipped in that release which still got in after all the above shitty processes. its a change of a 3 lines of code, but i will need to do all the steps again. even though i am going through the same shitty steps for another library version upgrade that depends on this library 😭😭

AND I AM THE ONE WHO CAUGHT IT. it went unnoticed because both of those shitty samples did not tested this case. now i can keep mum about it and release another buggy build that depends on it and let the chaos do its work, or i can get the blame and ship a rectification asap. i won't get any reward or good impression for the 2nd, and a time bomb like situation will get created if i go with 1st :/

FML :/

DIGITAL TECH GUARD RECOVERY, A TRUSTED PARTNER FOR BITCOIN ASSET RETRIEVAL.

contact @ digital tech guard . com

telegram +56 997 059 700

In the bustling city of Sydney, a conversation with my cousin opened the door to the world of cryptocurrency. Intrigued by his passion for Bitcoin, I initially approached the idea with caution. After all, investing in such a volatile market felt daunting. Yet, my cousin’s compelling stories of success convinced me to invest 15,000 AUD. To my surprise, the investment skyrocketed. Over the following months, the value soared to an astonishing 400,000 AUD. I was thrilled, imagining all the possibilities—travel, a new home, and financial freedom. This sudden windfall transformed my outlook on life and my future. However, this newfound excitement quickly turned sour. A family disagreement erupted, creating tension between my cousin and me. In a heated moment, he locked me out of my email account, cutting off my access to vital information related to my Bitcoin investment. I felt a wave of panic wash over me as I realized that my financial security was now at risk. Determined to regain control, I reached out to other family members for support. They were empathetic and offered various suggestions to resolve the situation. One family member mentioned Digital Tech Guard Recovery, a service known for helping individuals regain access to locked accounts. Though hesitant at first, I knew I had to act quickly. I decided to contact Digital Tech Guard Recovery, and their team proved to be incredibly efficient. They guided me through the recovery process, explaining each step clearly and reassuring me along the way. Within a short period, I regained access to my email and, subsequently, my Bitcoin account. The relief I felt was immense; my investment was secure, and my dreams were once again within reach. This experience taught me important lessons about the significance of digital security and the fragility of relationships. While the disagreement with my cousin was unfortunate, it prompted me to take proactive steps in safeguarding my financial future. Now, I’m more vigilant and informed, ensuring that I’m never left vulnerable again.