When I try to switch between File Explore, Search etc tabs in my VSCode keybindings using ctrl-shift-e. It fails to work.
Tl;dr
Remove this EMOJI Keyboard shortcut from IBus Preferences.
Corporates and semi corporates
Startup
It’s a story about how I practically understood computer networks and put it for use to scratch my own itch.
Lately, I had my eyes on my spare PC from quite some time where I just wanted to put it for some good use. Also, my issue in these unprecedented times were mosquitoes arriving in the evening randomly and causing a ruckus while I was working.
Big O (n²):
Here, just when I thought I resolved both my problems.
Big O (nlogn):
Time to think differently, I thought I could use my Fedora OS machine professionally instead of my MacBook pro. Currently, I’m working with Apache software tools Java backend server and Reactjs mostly from my parent’s living room.
Then I realized I’ll have to make use of my iPad for the video calls since my PC doesn’t have a camera and frankly, I was finding myself trying to bring the Gnome UI closer to macOS which is currently offered by Elementary OS.
But then what next?
Big O (n):
My brother Nitin stepped in. He heard what I was up to lately and suggested I drop the UI entirely from my Fedora OS machine use it as a server and notice the CPU usage.
“Use your spare machine over OpenSSH and let it do the heavy stuff.” – Nitin
I was quickly able to connect the dots. Then I moved back on my MacBook Pro and got all my repositories on my machine “Anton”. Made it run all my docker containers, Apache software tools, and the backend API my front end was consuming data from. Soon, after my brother introduced me to SSH extension on VSCode by Microsoft and that’s when I delegated all the heavy tasks on my Anton.
Guess what? My MacBook's fan's speed is low and back to normal. Now, macOS is my interface and the fedora OS server is my dev server doing all the heavy lifting.
Coming back to my other initial issue with mosquitoes. Now I get a much better battery life on my MacBook pro so I finally got my “portability” feature back and I can spray the mosquitoes repellent in only my room and when the deadlines get close can work from there too.
Mosquitoes: 0, Anton: 1
It is a slow process.
First, we write silly code then probably something that works. We learn what we were telling our “dumb” computer. All of a sudden we learn about mistakes like global variables and how bad they are.
Then we gain some wisdom and call ourselves Jon Snow of tech. We start automating our own work and call it smart work. Soon, we start visualising patterns and different ways of solving similar problems efficiently (Big O nerds hit the clap button! :D).
One fine day we realise languages, and frameworks are basically tools and we are all problem solvers.
Understanding when and where to use them to provide value is the key.
Maybe, I’m wrong. Who knows! I’m Jon Snow.
[Disclaimer] I’m not an expert. However, I’ve revived through this cycle once. Maybe you should open up and talk about it with your close ones first.
Being handed over a pink slip is tough! Losing a job is NOT an end to anything. It’s not under your control to have a stable journey through an economy meltdown.
Some of you might end up on a clock with your visas, bills, or up-coming expenses.
Okay, maybe have your favourite drink to calm yourself down. First night you might go sleepless. It’s all normal to over-think and be confused. Focus on what you have to offer as value and how to fix the “situation” that you’re in.
Let’s look at the positives
There are always companies out there ready to consume people of your skill set. Since your ex-employer needed you at one point of time too!
Also, there’s nothing wrong in opening up about your situation with your potential employer. Their empathetic reaction to it will give you a nice understanding of their company culture and people. Makes it easy to pick the right employer for yourself.
Plus, probability of landing a better job of interest is high!
Note:
Maybe it's a much needed break from the "rat race". Time to re-evaluate your goals and aspirations. Maybe, if you’ve got enough savings in the bank, start your own venture you always dreamt of.
All the best!
It all began with my following dev.to post dated September 16, 2017. It’s when I turned curious around this question to get an understanding and plan for my own engineering career roadmap.
While agreeing with the contextual answer on my post, I’d like to share some of my own experiences.
In my opinion, a senior software engineer is who has the potential to unblock other team members and can lead with empathy, while giving the right direction to other team members.
Also, I’ve noticed by showing confidence in, sharing knowledge, and occasionally challenging your team members with interesting problems that add value to the company leads to a healthy work culture while generating growth opportunities for all.
By the time you step out of it or asked to leave, you might end up wanting more from yourself.
You might be left with a feeling or a sense of confidence that you can do a lot more with your time than ever before.
Oh! one more thing, “there’s no place for emotions”.
In this post, I will be talking about my experience of stepping down a role in the career ladder to be able to re-live the fun (Problem-solving).
I’ve been blessed enough to have worked for two corporate organizations, and two startups where I was the initial employee and in my second shot I got to lead a team of 4 engineers at the age of 27. Although, I do believe that age is just a number. However, the point I wish to bring your focus on is that it’s not necessary for everyone to be enjoying a higher role. No disrespect to the ones who are leading teams of any size. I’m only trying to put my own experience here when I started performing the job of a team lead.
I was really turning disinterested to slowly stop solving issues/bugs and start delegating and get serious about projects milestones. I care about the product. However at this stage of life, I really enjoy creating them instead of taking care of them. I do believe it is necessary for any creator to maintain the code-bases they once wrote in smaller team sizes.
In my defense, the code-bases I got to write weren’t perfect yet they were written with a lot of consideration and keeping robustness, scalability, and quality in mind. The problem arises when a product based company becomes stable and under a well-drafted process.
When the major contributors are made the leads it instantly becomes a choice for them to either lead a team that takes the seed way ahead in scalability or to find more problems to solve.
When I was given a chance to lead a team, in my opinion, I did perform the job of satisfying the milestones of the project and getting things done of around 6 months. Where I started noticing that I wasn’t really enjoying my work and found myself disinterested in leadership. Rather, used to wait for other engineers to come up to me with interesting problems to solve.
With time, my team became independent, Since, I was mentored by my mentor to become self-sufficient and independent in problem finding and solving. That’s all I had to replicate within my team.
One fine day my friend noticed me sitting in the corner discreetly when he asked what’s wrong with you? To which I had no answer. Since I was under the impression that leading a team was the-next-step for me in my career.
To which he instantly replied saying Ashish find some other job. A request I instantly rejected. The feeling of fun was still missing and when I came back home met my friend over the weekend where he instantly, suggested me to meet some folks from a company he worked with on some cool project lately.
When your inner circle notices something and brings it in front of you, time to self introspect.
It was a surprise recommendation that came in through my friend while I was driving him back home. It was interesting how in a split second I replied to him “tell me more”.
From there on I got into interviews with 3 companies and got selected for 2 after rejecting one which I couldn’t find to be the perfect fit for me.
Then I was asked this amazing question by the recruiter why do you want to join us as a senior software engineer as you’ve been leading a team at your current organization. To which my answer was simple. I feel I am too young for it. I deserve to get more experience and need to learn from people much better than me which I believe your company can provide me.
That was my transition from a Team lead to a Senior Software Engineer. I’m not saying leadership isn’t my thing. All I’m trying to say is that there’s always a way to get back on what you really love doing and If you really think there’s more for you to learn, never regret letting go an opportunity coming early at your doorstep.
If you wish to read something similar about management:
17 REASONS NOT TO BE A MANAGER https://charity.wtf/2019/09/08/reasons-not-to-be-a-manager/
Broke? (Basics)
Write a kindle ebook
Affiliate marketing
Lease
Advertising
Create online courses
Invest in the stock market (*at your own risk)
Royalties
In this post, I’m going to jot down a few facts about “financial freedom”.
As Dave Ramsey, repeats his golden steps of ending financial miseries:
The world of financial freedom awaits!
How to grow your assets even further?
Invest your money, wisely! Understand the meaning of compounding.
Note:
Avoid online/offline impulsive buying.
Understand the true meaning of assets and liabilities.
Start planning for a better future of yourself and for your loved ones. Feel free to share your experience or wisdom, if I forgot to add something you already know to make it simple in the comments.
